These instructions assume:
IMPORTANT
WebSphere comes with an XML parser (WebSphere\AppServer\lib\xml4j.jar)
which uses DOM level 1 interfaces.
If you are using at least fixpack 4, or have
efix PQ47050 installed, then you need to
add the following string to the command line
arguments for each application server:
-classpath ....:xxx/xerces.jar...
Substitute the directory where you have stored
the jar for the xxx. If you are using Windows,
then use a semi-colon instead of a colon.
Restart the server so that the classpath
takes effect.
If you do not have the above fix installed
then even if you put the Xerces 1.1.2's (or
later) xerces.jar in your classpath, the
wrong interfaces are found by any Java code
running in WebSphere because WebSphere puts
the user's classpath at the end. In that
case you must edit WebSphere\AppServer\bin\admin.config
file and put xerces.jar at the BEGINNING
of the com.ibm.ejs.sm.adminserver.classpath=
variable
To set up a SOAP server:
From the WebSphere menu off of the NT Start menu:
Launch "Start Admin Server" and wait until it completes.
Launch "Administrator's Console".
From the Administrator's Console:
Console/Tasks/Create Application Server
Select Web Applications: You do not need Enterprise Beans for SOAP. Next
Application Server Properties: set the Application Server Name to "SOAP" (or another name of your choice). Next
Application Server Start Option: "Do not start the server automatically after creating it". Next
Node Selection: select your node. Next
Select Virtual Host: select "default_host". Next
Servlet Engine Properties: take the defaults. Next
Web Application Properties: Set the Web Application Web Path to "/soap". You can use any web path you like, including the WebSphere default of "/webapp/SoapWebApp", but using "/soap" keeps the URLs simple and is used in these instructions. Next
Specify System Servlets: Enable JSP 1.0 or 1.1.
Finish to create the SOAP Application Server.
In the tree view, open the SoapWebApp, and select the Advanced tab:
Change Document Root to "C:\install-dir\soap-2_3\webapps\soap".
Set the classpath to
C:\XML\apache\soap-2_3\lib\soap.jar
C:\XML\apache\soap-2_3
C:\tools\BSF\lib\bsf.jar
C:\tools\BSF\lib\bsfengines.jar
C:\Tools\Rhino\js.jar
C:\Tools\Rhino\jstools.jar
your SOAP server classes, if any
Console/Tasks/Add a Servlet
You can list and deploy SOAP services by pointing a browser to
http://hostname:port/soap/admin
Alternatively, you can deploy services by setting up your classpath and using
java org.apache.soap.server.ServiceManagerClient http://hostname:port/soap/servlet/rpcrouter deploy <DeploymentDescriptor.xml>
See the User's Guide for details on the aministration tool. The SOAP end-point for invoking services on this server is:
http://hostname:port/soap/servlet/rpcrouter
Happy SOAP-ing!