Web Services ToolKit Configuration Tool Help

The configuration of the supported web servers is dependent upon the config.xml file located in the Web Services ToolKit lib directory. This XML file defines the configuration of servlets and parameters for the Web Services ToolKit for Embedded WebSphere, WebSphere, and Jakarta-Tomcat web servers. The port number and host name fields are used to modify the port numbers for the Embedded Websphere and Jakarta-Tomcat servers, as well as modifying the port location URLS in the demo and sample WSDL files. The port and hostname are saved in the wstlProperties.xml file.

NOTE: This configuration file is specifically for configuring only Web Services ToolKit samples and demos.


Embedded WebSphere WebSphere V3.5 WebSphere V4.0 Tomcat

Embedded WebSphere

Please configure the Embedded WebSphere server that comes packaged with the Web Services ToolKit.

Instructions


WebSphere V3.5

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 Web Services ToolKit.

Instructions

NOTE: You must use the JDK1.2.2 version that ships with WebSphere V 3.5.

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.

NOTE: To modify the port number for a WebSphere HTTP server, you must follow the HTTP server's documentation.


WebSphere V4.0 AE

For Websphere V4.0 AE, the config.xml file is read and the file was40install.xml is created which is then passed to the WebSphere XMLConfig utility to configure WebSphere for the Web Services ToolKit.

Instructions

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.

NOTE: To modify the port number for a WebSphere HTTP server, you must follow the HTTP server's documentation.

WebSphere V4.0 AEs

For WebSphere V4.0 AEs (single server), the config.xml file is read and multiple internal and WebSphere tools are invoked to deploy the Web Services ToolKit.

Instructions

NOTE: First, stop the WebSphere Application server before running wstkconfig.

NOTE: For this release, it is assumed that the Host Name node and the WebSphere Administration host name are the same.

NOTE: To modify the port number for a WebSphere HTTP server, you must follow the HTTP server's documentation.


Tomcat

To configure the Web Services 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 Web Services ToolKit demos and samples. A back up copy of both server.xml and web.xml are created as server.xml.wstk and web.xml.wstk, respectively

Instructions


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=${WSTK_CP}:${CLASSPATH}:${oldCP}".

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=%WSTK_CP%;%CP%;%CLASSPATH%".