NOTE: These instructions apply to Tomcat 3.3. There are separate instructions for Tomcat 3.1, Tomcat 3.2, and Tomcat 4.0 and 4.1.
Copy activation.jar and mail.jar to %tomcat_home%/lib/apps. These jars
will be "visible" from all web apps, but will not interfere with the
operation of Tomcat itself.
IMPORTANT: With Tomcat 3.3, you do not need to change the startup scripts.
The Apache SOAP distribution includes a web archive at /soap-2_3/webapps/soap.war.
Simply drop this web archive into Tomcat's webapps directory (i.e. %tomcat_home%/webapps).
If you deploy Apache SOAP into Tomcat in this manner, you will not need to have anything from the
/soap-2_3 directory on your server's classpath (the relevant items are included in the web
archive). Note: If you copy the web archive into the webapps directory while Tomcat is running, Tomcat
will need to be restarted before the Apache SOAP web application can be accessed.
Keep in mind that if you want to replace the deployed Apache SOAP web application with a
later version that you will probably have to shut the server down, remove the expanded
%tomcat_home%/webapps/soap directory, and replace the
%tomcat_home%/webapps/soap.war file with the newer one.
When you deploy your SOAP services, you will copy the necessary jar files to
/%tomcat_home%/webapps/soap/WEB-INF/lib, or the neccessary class files to
a directory structure under /%tomcat_home%/webapps/soap/WEB-INF/classes.
You should be able to deploy services by pointing a browser to
http://hostname:port/soap
where hostname is the host on which Tomcat is running and port is the port. See the User's Guide for details on the administration tool. The SOAP end-point for invoking services on this server is:
http://hostname:port/soap/servlet/rpcrouter
Happy SOAP-ing!