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-17
Creating the Database
that all non-static content is removed from all these directory subtrees. The easiest
way to do this is the use the find utility to list files that should be processed by the
application server and then remove them.
Note that if you use prefix mapping, it is necessary to enter one of these filemap
directives for each different WS Plug-in URL prefix that maps to the same application.
For example, WS Plug-in URL prefixes /wls-MyDomainName and /wls4-
MyDomainName map to the same version of the MyDomain application (deployed in
different clusters). In this case add:
Filemap /wls-MyDomainName /Apps/MyDomain
Filemap /wls4-MyDomainName /Apps/MyDomain
Note that welcome-file specified in the WEB.XML should be added to the
IndexFile directive. For example, if your application has a welcome file called
myindex.html, you should add this to the existing IndexFile directive in the iTP
WebServer configuration file.
# List of html files to look for when a client only specifies a
# directory name
#
IndexFile index.html index.htm home.html home.htm myindex.html
Creating the Database
You must update the database files to configure the WS Plug-in. HP recommends that
you use the entries in the cluster table to configure the individual target application
server processes of an application server. This action causes the WS Plug-in to update
the DBFILES and DBSTATUS tables with details of failed target application server
processes, which alerts other WS Plug-in processes about failed application server
processes. If you do not use the cluster configuration approach and configure the
individual target application server processes in the DBACCESS table, then each WS
Plug-in independently identifies failed server processes in its application server and
does not retry them unless all target application server processes are marked as failed.
To customize the database, edit the file dbload.sqlci in the iTP Secure
WebServer's /bin/rmt directory. When you run the make command to build the WS
Plug-in, the data in dbload.sqlci is loaded into the DBACCESS, CLUSTER and
PATHMAP tables.
Note. HP strongly recommends that you configure the application server processes by using
the entries in the cluster table. The option of configuring individual target application server
processes in the DBACCESS table is provided solely for compatibility with previous version of
the RLS.