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 sa...@locus.apache.org on 2000/08/03 18:44:25 UTC
cvs commit: xml-soap/java/doc/install index.html tomcat.html
sanjiva 00/08/03 09:44:25
Added: java/doc/install index.html tomcat.html
Log:
restructuring documentation
Revision Changes Path
1.1 xml-soap/java/doc/install/index.html
Index: index.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 Installation Instructions</title>
</head>
<body bgcolor="#FFFFFF">
<h1 align="center">Apache SOAP Version 2.0: Installation
Instructions</h1>
<p align="center">Sanjiva Weerawarana (<a
href="mailto:mailto:sanjiva@watson.ibm.com">sanjiva@watson.ibm.com</a>)</p>
<p align="center">August, 2000.</p>
<p>The Apache SOAP distribution can be installed for use as a
client or as a server. This document provides installation
instructions for both cases and also has a trouble shooting
section to help sort out common installation related problems.</p>
<h2>Common Instructions</h2>
<p>We assume that you have downloaded the binary distribution of
Apache SOAP and have extracted the archive into the directory <tt>/foo</tt>.
Thus the files from the distribution are in the directory <tt>/foo/xml-soap-2_0/</tt>.</p>
<p>Note that if you are on a Win32 machine then you should
replace "/" with "\" as you follow these
instructions.</p>
<p><strong>XML Parser</strong>: Apache SOAP requires <a
href="http://xml.apache.org/xerces-j">Apache Xerces</a> (Java)
version 1.1.2 or higher. These versions support the <a
href="http://www.w3.org/TR/DOM-Level-2/">DOM level 2 candidate
recommendation</a> which provides namespace support. If you have
any other XML parsers (or other JAR files which may have the org.w3c.dom.*
interfaces), then it is very important that you place the JAR
file xerces.jar from Xerces at the <em>front</em> of your
classpath. Apache SOAP will not work otherwise.</p>
<p>While it is possible to use another parser, the current
codebase does not support making this change conveniently; hence
the mechanism is not documented here.</p>
<p><strong>Classpath</strong>: Add <tt>/foo/xml-soap-2_0/lib/soap.jar</tt>
to your classpath. If you want to run the samples, you also need
to add <tt>/foo/xml-soap-2_0/samples</tt> to your classpath.</p>
<h2>Client-Side Instructions</h2>
<p>Once you have followed the common instructions, you are ready
to go!</p>
<h2>Server-Side Instructions</h2>
<p>To install the server-side of Apache SOAP, you need a Web
application server that supports servlets and JSPs (if you want
to run the admin client as well). </p>
<p><strong>Installing the RPC router and admin client:</strong>
The instructions for how to install varies from one app server to
another. Here are instructions for the following servers:</p>
<ul>
<li><a href="tomcat.html">Apache Tomcat v3.1</a></li>
<li>IBM WebSphere v3.02</li>
<li>JRun vx.y.z</li>
<li>Microsoft Internet Information Server</li>
</ul>
<p>Didn't find yours listed? See whether the instructions for
Tomcat (for example) gives you enough hints on how to do it. If
not, you should try asking on the Apache SOAP user's list; more
than likely someone else has done it already. You can subscribe
to the list here: <a href="http://xml.apache.org/soap/mail.html">http://xml.apache.org/soap/mail.html</a>.</p>
</body>
</html>
1.1 xml-soap/java/doc/install/tomcat.html
Index: tomcat.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 Installation Instructions</title>
</head>
<body bgcolor="#FFFFFF">
<h1 align="center">Apache SOAP Version 2.0: 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.0.3'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 BEGINING 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="/xml-soap" docBase="path-to-xml-soap/XML-SOAP-1.2/webapp"
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/xml-soap">http://hostname:port/xml-soap</a></pre>
</blockquote>
<p>where hostname is the host on which Tomcat is running and port
is the port. See the next section 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/xml-soap">http://hostname:port/xml-soap/rpcrouter.jsp</a></pre>
</blockquote>
<p>Happy SOAP-ing!</p>
</body>
</html>