NonStop SOAP for Java User's Manual

Configuring NonStop SOAP for Java
NonStop SOAP for Java User’s Manual523860-001
3-2
Run the Setup Script
After doing these steps, the setup script prompts you to make changes at specific
locations in the file usr/tandem/webserver/conf/servlet.config. These changes are
shown in Steps 4 & 5 (typical values).
4. Using the editor of your choice, modify the
/usr/tandem/webserver/conf/servlet.config file as follows:
a. Locate the statement:
Server $server_objectcode {
Insert these lines directly above it:
#######################################################
#
# config file for SOAP 4 Java
#
if { [file exists $root/conf/soap4java.config] } {
source $root/conf/soap4java.config
}
5. Add an option to Arglist. In the Arglist of the "Server $server_objectcode" in the
/usr/tandem/webserver/conf/servlet.config file, add another -D variable as follows:
-DORBdbm=$env(SOAP_NSDOM_CFG_DBM)
6. Restart the iTP WebServer by executing these commands:
OSS: cd /usr/tandem/webserver/conf
OSS: ./restart
Note. If the iTP WebServer or the NSJSP product has MAXSERVERS > 1, then the SOAP
services under the NSJSP environment has the following behavior:
If a service is being deployed, it is available on all the NSJSP instances. If a service is being
undeployed, it may still be available on some of the NSJSP instances.
For consistent behavior across all NSJSP instances, you need to restart the iTP WebServer
when undeploying services.