You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by sn...@apache.org on 2002/07/03 21:25:55 UTC
cvs commit: xml-soap/java/docs/install tomcat31.html tomcat32.html index.html tomcat.html
snichol 2002/07/03 12:25:55
Modified: java/docs/install index.html tomcat.html
Added: java/docs/install tomcat31.html tomcat32.html
Log:
Help users willing to help themselves by providing installation
instructions for multiple versions of Tomcat.
Revision Changes Path
1.26 +4 -1 xml-soap/java/docs/install/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/index.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- index.html 16 May 2002 13:27:23 -0000 1.25
+++ index.html 3 Jul 2002 19:25:54 -0000 1.26
@@ -88,7 +88,10 @@
another. Here are instructions for the following servers:</p>
<ul>
- <li><a href="tomcat.html">Apache Tomcat v3.2</a></li>
+ <li><a href="tomcat.html">Apache Tomcat v4.0</a></li>
+ <li><a href="tomcat32.html">Apache Tomcat v3.2</a></li>
+ <li><a href="tomcat31.html">Apache Tomcat v3.1</a>. You can also use this
+ as a rough guideline for earlier versions of Tomcat.</li>
<li><a href="weblogic51.html">BEA WebLogic Application Server
v5.1</a></li>
<li><a href="weblogic60.html">BEA WebLogic Application Server
1.12 +31 -42 xml-soap/java/docs/install/tomcat.html
Index: tomcat.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/tomcat.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- tomcat.html 25 Jun 2002 05:16:27 -0000 1.11
+++ tomcat.html 3 Jul 2002 19:25:54 -0000 1.12
@@ -8,37 +8,20 @@
<body bgcolor="#FFFFFF">
<h1 align="center">Apache-SOAP Version 2.3: Installing the Server Side
-Under Apache Tomcat v3.2</h1>
+Under Apache Tomcat v4.0</h1>
-<p><strong>NOTE</strong>: These instructions do <strong>not</strong> apply to
-Tomcat 4.0 and later. That version does not require any manipulation of the
-startup scripts or classpath. Apache SOAP need only be deployed as a Web
-application.</p>
+<p><strong>NOTE</strong>: These instructions do apply to
+Tomcat 4.0. There are separate instructions for <a href="tomcat31.html">Tomcat 3.1</a>
+and <a href="tomcat32.html">Tomcat 3.2</a>.</p>
<h2>Getting Tomcat ready:</h2>
-<p><strong>IMPORTANT</strong>: Tomcat comes with an XML parser (lib/xml.jar)
-which has the DOM level 1 interfaces. Even if you put Xerces 1.1.2's
-xerces.jar in your classpath, the wrong interfaces are found by
-any Java code running in Tomcat because the shell script / batch
-file that runs Tomcat puts the user's classpath at the end. So,
-you must edit tomcat.sh or tomcat.bat in the bin/ directory and
-put xerces.jar at the BEGINNING of the classpath the script
-builds. </p>
-
-<p>If you run startup.bat, then line 105 (or there abouts) of <b>tomcat.bat</b>
-should look like this (line 69 for Tomcat 3.2.1) :</p>
-
-<blockquote>
- <code>set CP=path-to-xerces\xerces.jar;%CLASSPATH%;%CP%</code>
-</blockquote>
-
-<p>If you run startup.sh, add the following line to <b>tomcat.sh</b> after
-line 113 (or there abouts), so long as it's before the export line:</p>
-
-<blockquote>
- <code>CLASSPATH=path-to-xerces/xerces.jar:${CLASSPATH}</code>
-</blockquote>
+<p><strong>IMPORTANT</strong>: With Tomcat 4.0, you do not need to change
+the startup scripts or place any jar or class files in any of Tomcat's
+private directories. You need only place files within Tomcat's webapps
+directory. If you cannot resist, jars should be placed in %CATALINA_HOME%/lib
+and classes in %CATALINA_HOME%/classes. Anything placed in these directories is
+visible to all Web applications running on the Tomcat server.</p>
<h2>Deploying Apache-SOAP on Tomcat:</h2>
@@ -47,31 +30,37 @@
<h3>Method 1: Deploying the web archive.</h3>
<p>The Apache SOAP distribution includes a web archive at <code>/soap-2_3/webapps/soap.war</code>.
-Simply drop this web archive into Tomcat's webapps directory (i.e. <code>%tomcat_home%/webapps</code>).
-If you deploy Apache SOAP into Tomcat in this manner, you will not need to have anything from the
-<code>/soap-2_3</code> 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
+Simply drop this web archive into Tomcat's webapps directory (i.e. <code>%catalina_home%\webapps</code>).
+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.</p>
<p>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
-<code>%tomcat_home%/webapps/soap</code> directory, and replace the
-<code>%tomcat_home%/webapps/soap.war</code> file with the newer one.</p>
+<code>%catalina_home%/webapps/soap</code> directory, and replace the
+<code>%catalina_home%/webapps/soap.war</code> file with the newer one.</p>
<h3>Method 2: Creating a new <Context> in Tomcat's server.xml file.</h3>
-<p>Simply add a new <code><Context></code> element into
-<code>%tomcat_home%/conf/server.xml</code>:</p>
+<p>There are two ways to approach this. First, you can add a new <code><Context></code>
+element for the WAR file into <code>%catalina_home%/conf/server.xml</code>:</p>
+
+<code><Context path="/soap" docBase="path-to-apache-soap/webapps/soap.war"
+ debug="1" reloadable="true" />
+</code>
+
+<p>With this approach, you must put the classes or jars for your services in
+%CATALINA_HOME%/classes or %CATALINA_HOME%/lib, respectively.
+
+<p>For the second approach, you first unjar the WAR file into the <code>path-to-apache-soap/webapps/soap</code>
+directory. Then you can add a new <code><Context></code> element into
+<code>%catalina_home%/conf/server.xml</code>:</p>
<code><Context path="/soap" docBase="path-to-apache-soap/webapps/soap"
- debug="1" reloadable="true">
-</Context></code>
+ debug="1" reloadable="true" />
+</code>
-<p>Now, make sure you have the jar files from the lib directory
-of this distribution on your classpath and start up tomcat. Also,
-you will want to have on the classpath any of your code that you
-want to deploy as services (e.g. <code>/soap-2_3</code> if you want to deploy
-any of the included samples).</p>
+<p>With this method, you can either put your service classes and jars in the
+directories under %CATALINA_HOME% or under <code>path-to-apache-soap/webapps/soap/WEB-INF</code>.
<h2>Accessing the Apache SOAP context:</h2>
1.1 xml-soap/java/docs/install/tomcat31.html
Index: tomcat31.html
===================================================================
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
<title>Apache SOAP & Tomcat v3.1 Installation Instructions</title>
</head>
<body bgcolor="#FFFFFF">
<p><strong>NOTE</strong>: These instructions do apply to
Tomcat 3.1. There are separate instructions for <a href="tomcat32.html">Tomcat 3.2</a>
and <a href="tomcat.html">Tomcat 4.0</a>.</p>
<h1 align="center">Apache-SOAP Version 2.3: Installing the Server-Side
Under Apache Tomcat v3.1</h1>
<p><strong>IMPORTANT</strong>: Tomcat comes with an XML parser (lib/xml.jar)
which has the DOM level 1 interfaces. Even if you put Xerces 1.1.2's
xerces.jar in your classpath, the wrong interfaces are found by
any Java code running in Tomcat because the shell script / batch
file that runs Tomcat puts the user's classpath at the end. So,
you must edit tomcat.sh or tomcat.bin in the bin/ directory and
put xerces.jar at the BEGINNING of the classpath the script
builds. </p>
<p>If you run startup.bat, then line 38 of tomcat.bat should look
like this:</p>
<blockquote>
<pre>set CLASSPATH=path-to-xerces\xerces.jar;%CLASSPATH%;%cp%</pre>
</blockquote>
<p>If you run startup.sh, add the following after line 111:</p>
<blockquote>
<pre>CLASSPATH=path-to-xerces/xerces.jar:${CLASSPATH}</pre>
</blockquote>
<p>The easiest way to set up for Tomcat is to add a <Context>
to conf/server.xml:</p>
<pre><Context path="/soap" docBase="path-to-apache-soap/webapps/soap"
debug="1" reloadable="true">
</Context></pre>
<p>Now, make sure you have the jar files from the lib directory
of this distribution on your classpath and startup tomcat. Also
you will want to have on the classpath any of your code that you
want to deploy as services.</p>
<p>You should be able to deploy services by pointing a browser to</p>
<blockquote>
<pre><a href="http://hostname:port/soap">http://hostname:port/soap</a></pre>
</blockquote>
<p>where hostname is the host on which Tomcat is running and port
is the port. See the User's Guide for details on the
aministration tool. The SOAP end-point for invoking services on
this server is:</p>
<blockquote>
<pre><a href="http://hostname:port/soap/servlet/rpcrouter">http://hostname:port/soap/servlet/rpcrouter</a></pre>
</blockquote>
<p>Happy SOAP-ing!</p>
</body>
</html>
1.1 xml-soap/java/docs/install/tomcat32.html
Index: tomcat32.html
===================================================================
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Apache SOAP & Tomcat Installation Instructions</title>
</head>
<body bgcolor="#FFFFFF">
<h1 align="center">Apache-SOAP Version 2.3: Installing the Server Side
Under Apache Tomcat v3.2</h1>
<p><strong>NOTE</strong>: These instructions do apply to
Tomcat 3.2. There are separate instructions for <a href="tomcat31.html">Tomcat 3.1</a>
and <a href="tomcat.html">Tomcat 4.0</a>.</p>
<h2>Getting Tomcat ready:</h2>
<p><strong>IMPORTANT</strong>: Tomcat comes with an XML parser (lib/xml.jar)
which has the DOM level 1 interfaces. Even if you put Xerces 1.1.2's
xerces.jar in your classpath, the wrong interfaces are found by
any Java code running in Tomcat because the shell script / batch
file that runs Tomcat puts the user's classpath at the end. So,
you must edit tomcat.sh or tomcat.bat in the bin/ directory and
put xerces.jar at the BEGINNING of the classpath the script
builds. </p>
<p>If you run startup.bat, then line 105 (or there abouts) of <b>tomcat.bat</b>
should look like this (line 69 for Tomcat 3.2.1) :</p>
<blockquote>
<code>set CP=path-to-xerces\xerces.jar;%CLASSPATH%;%CP%</code>
</blockquote>
<p>If you run startup.sh, add the following line to <b>tomcat.sh</b> after
line 113 (or there abouts), so long as it's before the export line:</p>
<blockquote>
<code>CLASSPATH=path-to-xerces/xerces.jar:${CLASSPATH}</code>
</blockquote>
<h2>Deploying Apache-SOAP on Tomcat:</h2>
<p>There are two different ways to actually deploy Apache SOAP on Tomcat:</p>
<h3>Method 1: Deploying the web archive.</h3>
<p>The Apache SOAP distribution includes a web archive at <code>/soap-2_3/webapps/soap.war</code>.
Simply drop this web archive into Tomcat's webapps directory (i.e. <code>%tomcat_home%/webapps</code>).
If you deploy Apache SOAP into Tomcat in this manner, you will not need to have anything from the
<code>/soap-2_3</code> 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.</p>
<p>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
<code>%tomcat_home%/webapps/soap</code> directory, and replace the
<code>%tomcat_home%/webapps/soap.war</code> file with the newer one.</p>
<h3>Method 2: Creating a new <Context> in Tomcat's server.xml file.</h3>
<p>Simply add a new <code><Context></code> element into
<code>%tomcat_home%/conf/server.xml</code>:</p>
<code><Context path="/soap" docBase="path-to-apache-soap/webapps/soap"
debug="1" reloadable="true">
</Context></code>
<p>Now, make sure you have the jar files from the lib directory
of this distribution on your classpath and start up tomcat. Also,
you will want to have on the classpath any of your code that you
want to deploy as services (e.g. <code>/soap-2_3</code> if you want to deploy
any of the included samples).</p>
<h2>Accessing the Apache SOAP context:</h2>
<p>You should be able to deploy services by pointing a browser to</p>
<blockquote>
<code><a href="http://hostname:port/soap">http://hostname:port/soap</a></code>
</blockquote>
<p>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:</p>
<blockquote>
<code><a href="http://hostname:port/soap/servlet/rpcrouter">http://hostname:port/soap/servlet/rpcrouter</a></code>
</blockquote>
<p>Happy SOAP-ing!</p>
</body>
</html>