Wiki Markup |
---|
h1. Install and run Tomcat 6 (last tested with 6.0.14)
Tomcat 5.x is not supported due to classloading differences and annotation processing support. For Tomcat installation documentation see [http://tomcat.apache.org/tomcat-6.0-doc/setup.html].
Note on Unix platforms (Linux, MacOSX):
If you unpacked the Tomcat tar.gz file, the scripts are already executable. If not, the following command will make all shell scripts executable: {code}$ chmod u+x bin/*.sh{code}
Note on all platforms: the following instructions assume running Tomcat using the bin/catalina.sh or bin/catalina.bat scripts and not running as a service or daemon.
h1. {anchor:install-openejb}Install OpenEJB
The OpenEJB plugin distributable for Tomcat runs as a separate web application and is provided as zip file.
Current version: openejb-tomcat-3.0.0-SNAPSHOT-bin.zip
h2. Unpack the OpenEJB Tomcat plugin in the Tomcat webapps directory to deploy the OpenEJB plugin container.
The OpenEJB directory should contain the following files: |
Note | ||
---|---|---|
| ||
Restrictions |
Install Tomcat 6
If you already have Tomcat 6 installed, skip to Install OpenEJB.
Unpack Tomcat
Unpack the Tomcat zip file which will create a new directory containing the complete Tomcat installation.
...
$ jar -xvf apache-tomcat-6.0.14.zip
created: apache-tomcat-6.0.14/
created: apache-tomcat-6.0.14/bin/
created: apache-tomcat-6.0.14/conf/
...snip...
Change to the new Tomcat installation directory.
...
$ cd apache-tomcat-6.0.14/
The Tomcat installation should contain the following files:
...
apache-tomcat-6.0.14$ ls
LICENSE RELEASE-NOTES bin/ lib/ temp/ work/
NOTICE RUNNING.txt conf/ logs/ webapps/
Make shell scripts executable
The shell scripts in the Tomcat installation are not executable by default, so in order to execute them, you must set mark them as executable. If you unpacked the Tomcat tar.gz file, the scripts are already executable. The following command will make all shell scripts executable:
Code Block |
---|
apache-tomcat-6.0.14$ chmod u+x bin/*.sh |
Start Tomcat
Execute the following command to start the Tomcat server to verify it is functioning properly:
...
apache-tomcat-6.0.14$ bin/startup.sh
Using CATALINA_BASE: /your/tomcat/installation/apache-tomcat-6.0.14
Using CATALINA_HOME: /your/tomcat/installation/apache-tomcat-6.0.14
Using CATALINA_TMPDIR: /your/tomcat/installation/apache-tomcat-6.0.14/temp
Using JRE_HOME: /your/java/installation
NOTE: Your output will be different from the example above due to differences in installation location.
Verify Tomcat is Running
Visit http://localhost:8080/ and you should see the Tomcat welcome page.
Stop Tomcat
Shutdown Tomcat by executing the following command:
...
apache-tomcat-6.0.14$ bin/shutdown.sh
Using CATALINA_BASE: /your/tomcat/installation/apache-tomcat-6.0.14
Using CATALINA_HOME: /your/tomcat/installation/apache-tomcat-6.0.14
Using CATALINA_TMPDIR: /your/tomcat/installation/apache-tomcat-6.0.14/temp
Using JRE_HOME: /your/java/installation
NOTE: Your output will be different from the example above due to differences in installation location.
...
Once Tomcat has been installed, the OpenEJB plugin for Tomcat can be installed. The commands in this example are executed within the Tomcat installation directory.
Unpack OpenEJB Tomcat plugin in Tomcat webapps directory
1. Change to the webapps directory:
...
apache-tomcat-6.0.14$ cd webapps
2. Unpack the openejb-tomcat-3.0.0-SNAPSHOT-bin.zip file.
...
apache-tomcat-6.0.14/webapps$ jar -xvf ../openejb-tomcat-3.0.0-SNAPSHOT-bin.zip
created: openejb/
created: openejb/WEB-INF/
created: openejb/lib/
inflated: openejb/lib/geronimo-javamail_1.4_spec-1.1.jar
inflated: openejb/lib/xbean-finder-3.1.jar
...snip...
3. The OpenEJB directory should contain the following files:
...
apache-tomcat-6.0.14/webapps$ ls openejb
WEB-INF/ lib/ openejb.xml
4. Start tomcat again
5. Visit http://localhost:8080/openejb/installer and click on the install button
6. Assuming you don't get any errors, reboot tomcat
At this point OpenEJB will be installed
Info | |||
---|---|---|---|
| |||
Code Block | |||
java | java | Wiki Markup |
{code:none}apache-tomcat-6.0.14/webapps$ cd ..{code}
h2. Add the OpenEJB listener to Tomcat
Tomcat listeners must be available in the Tomcat common class loader, so the openejb-loader jar must be copied into the Tomcat lib directory.
{code:none} apache-tomcat-6.0.14$ cp webapps/openejb/lib/openejb-loader-3.0.0-SNAPSHOT.jar lib/{code}ls openejb WEB-INF/ lib/ openejb.xml {code} h2. Unix users use http://localhost:8080/openejb/installer and click on the install button h2. Windows users need to do the following: h3.1 Install the OpenEJB listener to Tomcat. Add the following {highlight}highlighted lines{highlight} to your conf/server.xml file to load the OpenEJB listener: {panel:title=conf/server.xml} <!-- Note: A "Server" is not itself a "Container", so you may not define subcomponents such as "Valves" at this level. Documentation at /docs/config/server.html --> <Server port="8005" shutdown="SHUTDOWN"> {highlight}<!-- OpenEJB plugin for tomcat -->{highlight} {highlight}<Listener className="org.apache.openejb.loader.OpenEJBListener" />{highlight} <!--APR library loader. Documentation at /docs/apr.html --> <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> ...snip... {panel}h2 h3.1 Delete the Tomcat annotations-api.jar file Tomcat contains an old non-compliant version of the javax.annotation classes and these invalid classes must be removed so OpenEJB can process annotations. Simply, rename the annotation-api.jar so it doesn't end with {{".jar"}}. For example: {code:none}apache-tomcat-6.0.14$ $ mv lib/annotations-api.jar lib/annotations-api.jar-INVALID{code}h2 h3.1 Add OpenEJB javaagent to Tomcat startup OpenJPA, the Java Persistence implementation used by OpenEJB, currently must enhanced persistence classes to function properly, and this requires the installation of a javaagent into the Tomcat startup process. Simply, add the following {highlight}highlighted lines{highlight} to the bin/catalina.sh bat file to enable the OpenEJB javaagent: {panel:title=bin/catalina.sh} ...snip... \# Set juli LogManager if it is present if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then JAVA_OPTS="$JAVA_OPTS "-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" "-Djava.util.logging.config.file="$CATALINA_BASE/conf/logging.properties" fi {highlight}\# Add OpenEJB javaagent if [ -r "$CATALINA_BASE"/webapps/openejb/lib/openejb-javaagent-3.0.0-SNAPSHOT.jar ]; then JAVA_OPTS=""-javaagent:$CATALINA_BASE/webapps/openejb/lib/openejb-javaagent-3.0.0-SNAPSHOT.jar" $JAVA_OPTS" fi{highlight} \# ----- Execute The Requested Command ----------------------------------------- \# Bugzilla 37848: only output this if we have a TTY if [ $have_tty -eq 1 ]; then echo "Using CATALINA_BASE: $CATALINA_BASE" ...snip... {panel} *NOTE:* The example above is an excerpt from the middle of the bin/catalina.sh file. Search for "Execute" in the file to locate the correct position in the file to add the new lines. |
Test an example application
Create a stateless session bean
Create an interface
{info}
h2. Test an example application
h3. Create a stateless session bean
h4.Create an interface
{code:java}
package org.acme;
import javax.ejb.*;
@Remote
public interface Greeting{
public String greet();
}
|
Create the bean class
Code Block | ||
---|---|---|
java | java | {code} h4. Create the bean class {code:java} package org.acme; import javax.ejb.*; @Stateless public class GreetingBean implements Greeting{ public String greet(){ return "I just greeted you buddy"; } } {code} h4. Create a servlet |
...
{code | ||
:java | java | } package org.acme; import javax.servlet.*; import javax.servlet.http.*; import javax.naming.*; import java.io.*; import java.util.*; public class TestServlet extends HttpServlet{ public void doGet(HttpServletRequest request, HttpServletResponse response){ try{ response.setContentType("text/html"); PrintWriter writer = response.getWriter(); Properties p = new Properties(); p.put("java.naming.factory.initial","org.apache.openejb.client.LocalInitialContextFactory"); InitialContext ctx = new InitialContext(p); Greeting g = (Greeting)ctx.lookup("GreetingBeanBusinessRemote"); writer.print(g.greet()); }catch(Exception e){ e.printStackTrace(); } } } {code} h4.Register the servlet in web.xml |
...
{code | ||
:xml | xml | }
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<display-name>Test Application</display-name>
<servlet>
<servlet-name>TestServlet</servlet-name>
<servlet-class>org.acme.TestServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>TestServlet</servlet-name>
<url-pattern>/test</url-pattern>
</servlet-mapping>
</web-app>
|
Package the war
...
{code} h4.Package the war Compile the above classes into the WEB-INF/classes directory and package everything into testweb.war (or a file name of your liking) |
...
h4. Drop the war in the tomcat webapps directory |
...
Drop the testweb.war in the tomcat webapps directory |
...
h4. Send a request to the servlet |
...
#Open the browser |
...
#Send a request to http://localhost:8080/testweb/test |
...
#You should now see the message "I just greeted you buddy" |
...
h1. \[OPTIONAL\] Run OpenEJB |
...
Install iTests
Simply copy the OpenEJB iTests war to the Tomcat webapp directory.
Code Block | ||
---|---|---|
none | none | iTests
h2. Install iTests
Simply copy the OpenEJB iTests war to the Tomcat webapp directory.
{code:none}apache-tomcat-6.0.14$ cp openejb-tomcat-3.0.0-SNAPSHOT-itests.war webapps/ |
Start Tomcat
Code Block | ||
---|---|---|
none | none | {code} h2. Start Tomcat {code:none}apache-tomcat-6.0.14$ bin/startup.sh Using CATALINA_BASE: /your/tomcat/installation/apache-tomcat-6.0.14 Using CATALINA_HOME: /your/tomcat/installation/apache-tomcat-6.0.14 Using CATALINA_TMPDIR: /your/tomcat/installation/apache-tomcat-6.0.14/temp Using JRE_HOME: /your/java/installation{code} *NOTE:* Your output will be different from the example above due to differences in installation location. |
...
h2. Execute the test client |
...
{code | ||
:none | none | }$ java -Dtomcat.home=. -Dremote.servlet.url=http://127.0.0.1:8080/openejb/remote -jar openejb-tomcat-3.0.0-SNAPSHOT-test.jar tomcat
_________________________________________________
|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|
Running EJB compliance tests on HTTP/Tomcat Server
_________________________________________________
WARNING: No test suite configuration file specified, assuming system properties contain all needed
information. To specify a test suite configuration file by setting its location using the system
property "openejb.testsuite.properties"
test server = org.apache.openejb.test.TomcatRemoteTestServer
entry = java.naming.provider.url:http://127.0.0.1:8080/openejb/remote
entry = java.naming.factory.initial:org.apache.openejb.client.RemoteInitialContextFactory
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
.........................................
........................
Time: 10.853
OK (885 tests)
_________________________________________________
CLIENT JNDI PROPERTIES
java.naming.provider.url = http://127.0.0.1:8080/openejb/remote
java.naming.factory.initial = org.apache.openejb.client.RemoteInitialContextFactory
_________________________________________________
|
Tip | ||
---|---|---|
| ||
The tests should completely pass the first time they are run. If you execute the test client a second time, 21 tests fail for some unknown reason.{code}
{tip:title=Failures}
The tests should completely pass the first time they are run. If you execute the test client a second time, 21 tests fail for some unknown reason.
{tip}
|