NonStop Server Guide for BEA WebLogic Server 8.1

Using the WS Plug-in
HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001
8-16
Configuring the iTP WebServer to Process Static
Content
The WS Plug-in configuration database can be reloaded using the make utility. The
utility must be run from the directory referred to by the PLUGIN_PATH_NAME setting
shown above:
make dbload
The WS Plug-in processes will utilize the new setting the next time they load the
configuration from the database. This occurs at process startup and restarts following a
process termination. Note that the HTTP daemon terminates the WS Plug-in process
when a request is canceled, so you should be aware that some of the WS Plug-in
servers could begin using the new configuration at any time. Also, note that if the
configuration changes the addition of a new application, the AUTO_LOAD directive can
be used to force the WS Plug-in processes to load the new configuration as required.
Alternatively, the make utility can be used to force all WS Plug-in processes to reload
the configuration before processing a new request:
make refresh
Configuring the iTP WebServer to Process Static Content
The iTP WebServer is capable of serving static content (web pages, image files,
applets, etc.) much more efficiently than an application server. It is possible to
configure the iTP WebServer to perform this function for the applications deployed to
the WebLogic Server. To do this, add a Filemap to the iTP WebServer configuration
file (httpd.conf file in the iTP WebServer's conf directory,
/usr/tandem/webserver/conf, by default).
First, add a Filemap directive for the WS Plug-in URL prefix.
Filemap /wls-MyDomainName /Apps/MyDomain
The Filemap should map the prefix used by the client to a directory where the .war file
has been unpacked. This directory can be located anywhere in the OSS filesystem.
One approach is to create a subdirectory in the directory where your .ear or .war file
is and name it the same as the WebLogic Server URL prefix. For example, assuming
that your application directory is /Apps and this directory contains a MyDomain.war
or MyDomain.ear file, create a directory called MyDomain and unpack the contents of
the .war file (which is in the .ear file) into this directory. For example:
cd /Apps/
mkdir MyDomain
jar -xf MyDomain.ear MyDomain.war - Skip this if your
application is in a .war file.
cd MyDomain
jar -xf ../MyDomain.war
rm -rf *-INF
Note the last line removes the WEB-INF directory, which contains non-static content.
The META-INF and WEB-INF directories are standard and will probably not contain
static content, so they can be safely removed in most cases. In general, you should
remove the *-INF directories and also any *.jsp files. Note that the .war file might
contain multiple directories, possibly containing subdirectories. You need to ensure