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-12
WS Plug-in Configuration Tool
The tool picks up default settings from a file called itpwls-defs.sh located in the
iTP WebServer directory/bin/rmt directory. The default contents are:
export _WLS_DOMAIN_NAME=mydomain
export _WLS_CLUSTER_NAME=MyCluster
export _TCPIP_PROCESS_NAME=ZTC0
#export _WLS_COOKIE_NAME=JSESSIONID
export _PLUGIN_PATH_NAME=/usr/webserver/bin/rmt
export _WLS_PATH_NAME=$BEA_HOME/user_projects/domains
You can update this file to reflect the environment on your system. Additionally, the
script looks for a file called itpwls-defs.sh in your current working directory. If this
file exists, any settings contained in it are used in preference to those set in the
iTP WebServer directory/bin/rmt/itpwls-defs.sh file. This means that
you can set system-wide defaults in the
iTP WebServer directory/bin/rmt/itpwls-defs.sh and also override these
on a temporary basis by creating an itpwls-defs.sh file in your current directory.
All the settings contained in the itpwls-defs.sh file(s) can be overridden using
command line arguments.
Note that the installation script updates the value of the WS Plug-in path setting in the
itpwls-defs.sh file to reference the directory this file is located.
The plugin-config.sh script accepts the following arguments:
[-w WLS URL Prefix]
This argument specifies the URL prefix of the WebLogic Server application, that is,
/SlotServletRoot.
[-u Plug-in URL Prefix]
Use the -u flag to specify the WS Plug-in URL prefix. If this argument is included (and
specifies a different URL prefix from the WebLogic Server URL Prefix specified with
the -w flag), the tool will add a mapping from the WS Plug-in URL to the WebLogic
Server URL.
This provides the facility to specify a different URL prefix from the prefix used by the
application deployed in WebLogic Server to be used by the WS Plug-in. For example,
specifying -u /Slot and -w /SlotServletRoot means that any request sent to
http://iTP WebServer Address/Slot/… will be routed to a member of the
target WebLogic Server cluster as /SlotServletRoot/…. Use the Configuration
Display feature to check that the iTP prefix chosen is not already in use.
This facility enables you to configure multiple instances of the same application in
different WebLogic Server clusters and access them through the same iTP
WebServer/Plug-in. There are a number of circumstances that might warrant this
requirement. You might want to partition users by category. For example, the Call
Center staff to a high priority cluster, high value customers to a medium priority cluster,
and other customer to a lower priority cluster. It might also be useful during the
introduction of new versions of an application.That is, deploy the new version in a
separate WebLogic Server cluster for live testing or a pilot for a restricted group of