User: vincent
Date: 00/09/05 16:42:13
Modified: . tomcat.htm
Log:
Added some more info and tried to more consistently format it.
Also tried to fix up some of the grammar.
Revision Changes Path
1.4 +64 -30 jbossweb/tomcat.htm
Index: tomcat.htm
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/tomcat.htm,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- tomcat.htm 2000/09/02 11:22:15 1.3
+++ tomcat.htm 2000/09/05 23:42:12 1.4
@@ -4,7 +4,7 @@
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<meta name="generator" content="Adobe GoLive 4">
- <title>jBoss - Coding the Future</title>
+ <title>JBoss - Coding the Future</title>
</head>
<body bgcolor="white" leftmargin="0" topmargin="0" marginwidth="0"
marginheight="0">
@@ -22,7 +22,7 @@
<tr height="37">
<td height="37"><img alt="o" height="1" src="binary.htm" width="1"><font
color="#ffcc00" face="Arial,Helvetica,sans-serif" size="6"><b>Running
- Tomcat with jBoss</b></font></td>
+ Tomcat with JBoss</b></font></td>
</tr>
</tbody>
</table>
@@ -65,7 +65,9 @@
<td valign="top" width="648">
<p> </p>
- <p>As part of project Game Over, the jboss organization wants to
deliver a complete J2EE based product to the market. The jboss organization decided
to integrate the Tomcat engine stack with a running version of jboss, and all in one
VM. Now you can serve all your servlet and JSP needs with 2 simple downloads and
couple of configuration files. You can find the Tomcat engine <a
href="http://jakarta.apache.org">here</a>. <br> The goal of this page is to
explain how to make jBoss automatically start Tomcat, so that it runs in the same
VM.</p>
+ <p>As part of project Game Over, the JBoss organization wants to
deliver a complete J2EE based product to the market. The JBoss organization decided
to integrate the Tomcat engine stack with a running version of JBoss in a single VM.
Now you can serve all your servlet and JSP needs with 2 simple downloads and a couple
of configuration files. Check out the Tomcat <a href="http://jakarta.apache.org"
target="_top">homepage</a> for information related to Tomcat.
+<p>
+The goal of this page is to explain how to make JBoss automatically start Tomcat,
so that it runs in the same VM.</p>
<p> </p>
</td>
<td valign="top" width="10"></td>
@@ -114,12 +116,12 @@
<tbody>
<tr>
<td valign="top" width="672"><br>
- <p> By running Tomcat inside the same VM as jBoss, you will have
an easier to startup/shutdown application server, but over all the goal we are
pursuing is GREATER SPEED! The reason is simple we try to keep all the invocations
inside one VM</p>
+ <p>One benefit of running Tomcat inside the same VM as JBoss is to
have an easier to manage application server. The main goal, however, is greater
performance. By eliminating unnecessary network calls and keeping all the
invocations inside one VM the performance is significantly enhanced.</p>
<p>If you have Servlets/JSPs which access some EJBs, you'll
get dramatically improved performance because the calls will
- be in-VM (no network access).</p>
+ be intra-VM (no network access).</p>
<p><font face="Myriad Web,Arial"><b><u><em>WARNING</em></u><br>
- THIS VERSION IS FOR DEVELOPMENT AND EVALUATION ONLY. Currently
you can run Tomcat in the same VM as jBoss, but the performance will not be as fast as
you would expect from in memory invocations the reason being that we serialize the
method invocations. We are working on an accelarated version, due out soon, that
works with in memory objects, non-serialized. A factor of 30 is expected with this
optimization (class loader integration). Stay tuned for the first beta version, we
appreciate your understanding and patience on this integration work in progress.
</b></font></p>
+ THIS VERSION IS FOR DEVELOPMENT AND EVALUATION ONLY. Currently
you can run Tomcat in the same VM as JBoss, but the performance will not be as fast as
you would expect from in memory invocations the reason being that we serialize the
method invocations. We are working on an accelarated version, due out soon, that
works with in memory objects, non-serialized. A factor of 30 increase in performance
is expected with this optimization (class loader integration). Stay tuned for the
first beta version. We appreciate your understanding and patience on this integration
work in progress. </b></font></p>
</td>
<td valign="top" width="10"></td>
<td align="right" valign="top" width="11"> </td>
@@ -164,10 +166,10 @@
<tbody>
<tr>
<td valign="top" width="672"><br>
- <p>You need to download both jBoss 2 and Tomcat of course...<br>
- Tomcat's integration has been tested with the latest beta
- <font size="2"><i>(3.2b3 as of 09/01/2000)</i></font> of Tomcat, so
nothing
- is guaranteed with other versions...</p>
+ <ul>
+ <li>Tomcat Version 3.1. You can get the <a
href="http://jakarta.apache.org/builds/tomcat/release/v3.1/bin/jakarta-tomcat.tar.gz">Unix/Linux</a>
version or the <a
href="http://jakarta.apache.org/builds/tomcat/release/v3.1/bin/jakarta-tomcat.zip">Windows</a>
version.</li>
+<p><font size="2"><strong>NOTE:</strong> It is also known to work with Tomcat
Version 3.2b3 as of 09/01/2000</font>
+ <li>JBoss 2.0.</li>
</td>
<td valign="top" width="10"></td>
<td align="right" valign="top" width="11"> </td>
@@ -211,7 +213,7 @@
<td valign="top" width="672">
<p><br>
<ol>
- <li>In whatever batch or shell script you use to launch jBoss and
+ <li><strong>Setup environment variables.</strong>In whatever batch
or shell script you use to launch JBoss and
Tomcat, add entries for the following environment variables:
<table border="1">
<tr><th>variable</th><th>value</th></tr>
@@ -222,12 +224,12 @@
or 1.3 installation</td></tr>
<tr><td align="RIGHT" valign="TOP">CLASSPATH</td><td>This should
<I>not include anything</I> (unless you really know what
- you're doing!). Both Tomcat and jBoss have startup scripts
+ you're doing!). Both Tomcat and JBoss have startup scripts
that load the necessary JARs onto the classpath.</td></tr>
</table>
</li>
- <li>Edit the Tomcat configuration file server.xml. It is located
- in the conf directory under your base Tomcat directory
+ <li><strong>Edit server.xml in Tomcat config directory.</strong>.
+ It is located in the conf directory under your base Tomcat
directory
(jakarta-tomcat for the binary). There are a number of lines
that deal with RequestInterceptors, the last of which are currently
the Realms (SimpleRealm, JDBCRealm, etc.). <B>After</B> the other
@@ -238,10 +240,10 @@
debug="0" />
</pre>
</li>
- <li>Edit the jBoss configuration file jboss.conf. It
- is located in the conf directory under the base of your jBoss
+ <li><strong>Edit jboss.conf.</strong> It
+ is located in the conf directory under the base of your JBoss
binary distribution, or the dist/conf directory if you built from
- the jBoss source. There are some commented-out lines near the end
+ the JBoss source. There are some commented-out lines near the end
of the file that deal with Tomcat:
<pre>
<!--
@@ -262,29 +264,61 @@
<MLET CODE = "org.jboss.tomcat.TomcatService" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
</MLET>
</pre></li>
- <li>Put your EJB's <I>Home and Remote Interfaces</I> in the
+ <li><strong>Add your EJBs</strong>.
+ Put your EJB's <I>Home and Remote Interfaces</I> in the
<b>WEB-INF/classes</b> directory under your Tomcat web app directory
(for example, jakarta-tomcat/webapps/myapp/WEB-INF/classes).</li>
- <li>Put the jBoss client files <i>jboss-client.jar</i>,
<i>jnp-client.jar</i>,
+ <li><strong>Add JBoss client Jars</strong>.
+ Put the JBoss client files <i>jboss-client.jar</i>,
<i>jnp-client.jar</i>,
<i>jta-spec1_0_1.jar</i>, and (for 1.2.2 but not 1.3) <i>jndi.jar</i>
in the
<b>WEB-INF/lib</b> directory under your Tomcat web app directory
(for example, jakarta-tomcat/webapps/myapp/WEB-INF/lib). These
- files can be found in the <B>client</B> directory under your jBoss
+ files can be found in the <B>client</B> directory under your JBoss
binary install (or <b>dist/client</b> for source builds).</li>
- <li>Put the JNDI configuration file <i>jndi.properties</i> in the
+ <li><strong>Add support for JNDI</strong>.
+ Put the JNDI configuration file <i>jndi.properties</i> in the
<b>WEB-INF/classes</b> directory under your Tomcat web app directory
(for example, jakarta-tomcat/webapps/myapp/WEB-INF/classes).
- This file can be found in the <b>conf</b> directory under you jBoss
+ This file can be found in the <b>conf</b> directory under you JBoss
binary install (or <b>dist/conf</b> for source builds).</li>
- <li>If you later want to move jBoss and Tomcat to separate
- machines, you will need to change the hostname in jndi.properties
- and alter jboss.properties in the jBoss server configuration.</li>
+ <li><strong>Start JBoss.</strong> If you start JBoss now by typing
<code>run.sh</code> (or <code>run.bat</code> for Windows) you should see the following
Tomcat related output in your log messages:
+<pre>
+ ...
+[Tomcat] Initializing
+[Tomcat] Initialized
+ ...
+[Tomcat] Starting
+[Tomcat] Started
+ ...
+[Tomcat] Testing if Tomcat is present....
+ ...
+[Tomcat] OK
+ ...
+Context log: path="/examples" Adding context path="/examples"
docBase="webapps/examples"
+Context log: path="" Adding context path="" docBase="webapps/ROOT"
+Context log: path="/test" Adding context path="/test" docBase="webapps/test"
+Starting tomcat install="/home/workspace/tomcat" home="/home/workspace/tomcat"
+classPath=".:/home/workspace/development/languages/jdk1.3/lib/tools.jar:
+ run.jar:/home/workspace/tomcat/lib:
+ /home/workspace/tomcat/lib/servlet.jar:
+ /home/workspace/tomcat/lib/webserver.jar:
+ /home/workspace/tomcat/lib/xml.jar:
+ /home/workspace/tomcat/lib/jasper.jar:
+ /home/workspace/development/languages/jdk1.3/lib/tools.jar:
+ /home/workspace/spydermq/lib/jnpserver.jar:/home/workspace/jboss/conf"
+[Default] Starting tomcat. Check logs/tomcat.log for error messages
+Context log: path="/admin" Automatic context load
+ docBase="/home/workspace/tomcat/webapps/admin"
+Context log: path="/admin" Adding context path="/admin"
+ docBase="/home/workspace/tomcat/webapps/admin"
+</pre>
+<p>
+You should only see the lines after <strong>[Tomcat] OK</strong> if you have
installed the examples that come with Tomcat. Nonetheless, you should see the same
sort of log messages you would see if you had deployed Tomcat in standalone mode.
Also, the "tomcat install", classpath, etc will also vary from installation to
installation.</li>
</ol>
-
-
-
-
- <p>That's it !! You just have to launch jBoss now and it will start
+ <p>If you later want to move JBoss and Tomcat to separate
+ machines, you will need to change the hostname in jndi.properties
+ and alter jboss.properties in the JBoss server configuration.</p>
+ <p>That's it !! You just have to launch JBoss now and it will start
Tomcat and you will have an EJB/JSPs/Servlets server running in
one VM... </p>
</td>
