WebService Configuration Tool Help
The configuration of the supported web servers is
dependent upon the config.xml file located in the
WebServices Toolkit lib directory. This XML file
defines the configuration of servlets and parameters for
the WebServices Toolkit for Embedded WebSphere,
WebSphere, and Jakarta-Tomcat web servers.
NOTE:This configuration file is specifically for configuring only
WebService Toolkit samples and demos.
Embedded WebSphere
The WebServices Toolkit comes already configured for the Embedded WebSphere web server.
No action occurs if this web server is selected.
WebSphere
For configuring a WebSphere web server, the config.xml file is read and the file wasinstall.xml is
created which is then passed to the WebSphere XMLConfig utility to configure WebSphere for
the WebServices Toolkit.
Instructions
- Select WebSphere web server,
- enter the name of the server host name in the Host Name field,
- enter the location of the installed WebSphere application, typically x:\Websphere\AppServer,
- and press the Configure button.
NOTE:If you insist on using JDK1.2.2, please use the version that ships with WebSphere.
NOTE:The WebSphere Administration server must be running.
NOTE:For this release, it is assumed that the Host Name node and the WebSphere
Administration host name are the same.
Tomcat
To configure the WebServices Toolkit for Jakarta-tomcat, the config.xml is read and the user
is offered a choice of overwriting the "server.xml" and "web.xml" files in the x:\jakarta-tomcat\conf
directory: choose "yes" to overwrite these files, choose "no" to write these files to the current
directory.
This configuration tool will update the server.xml file for WebServices Toolkit demos and samples.
A back up copy of both server.xml and web.xml are created as server.xml.bak and web.xml.bak, respectively
Instructions
- Select Jakarta-Tomcat web server,
- enter the location of the installed Jakarta-Tomcat application, typically x:\jakarta-tomcat,
- and press the Configure button.
NOTE:
Because Tomcat requires some of the Java
classes required by SOAP, but Tomcat ships
with a later incompatible versions of these
classes it is necessary to modify the Tomcat
startup so that the SOAP classes provided
by Web Services Toolkit are referenced
first.
This change depends on the version of Tomcat installed.
For version 3.1, this can be done by:
Windows NT/2000: In the tomcat.bat file on line 38, change
"set CLASSPATH=%CLASSPATH%;%cp%"
to
"set CLASSPATH=%TOMCAT_HOME%lib/servlet.jar;%cp%;%CLASSPATH%;"
.
Linux: In the tomcat.sh file, change "CLASSPATH=${CLASSPATH}:${oldCP}"
to "CLASSPATH=${oldCP}:${CLASSPATH}"
.
For version 3.2.1, this can be done by:
Windows NT/2000: In the tomcat.bat file on line 104, change
"set CP=%CP%;%CLASSPATH%"
to
"set CP=%CLASSPATH%;%CP%"
.