Apache Tomcat migration tool for Jakarta EE. This tool is a work in progress. The aim of the tool is to take a web application written for Java EE 8 that runs on Apache Tomcat 9 and convert it automatically so it runs on Apache Tomcat 10 which implements Jakarta EE 9. The tool can be used from the command line or as an Ant task. Setting up a re-direct to Tomcat using the Jakarta ISAPI Redirector. Last Modified: 05 Apr 2019 User Level: Administrator. Version 8.0+ and up.
The Jakarta Project created and maintained open source software for the Java platform. It operated as an umbrella project under the auspices of the Apache Software Foundation, and all Jakarta products are released under the Apache License. As of December 21, 2011 the Jakarta project was retired because no subprojects were remaining.
In 2018 Jakarta EE, a part of the Eclipse Enterprise for Java (EE4J) project, became the new name for the Java EE platform at the Eclipse Foundation.[1]
Subprojects[edit]
Major contributions by the Jakarta Project include tools, libraries and frameworks such as:
- BCEL - a Java byte code manipulation library
- BSF - a scripting framework
- Cactus - a unit testing framework for server-side Java classes
- Apache JMeter - a load- and stress-testing tool.
The following projects were formerly part of Jakarta, but now form independent projects within the Apache Software Foundation:
Apache Tomcat 7.0 Free Download
- Ant - a build tool
- Commons - a collection of useful classes intended to complement Java's standard library.
- HiveMind - a services and configuration microkernel
- Maven - a project build and management tool
- POI - a pure Java port of Microsoft's popular file formats.
- Struts - a web application development framework
- Slide - a content repository primarily using WebDAV.
- Tapestry - A component object model based on JavaBeans properties and strong specifications
- Tomcat - a JSP/Servlet container
- Turbine - a rapid development web application framework
- Velocity - a template engine
Project name[edit]
Jakarta is named after the conference room at Sun Microsystems where the majority of discussions leading to the project's creation took place.[2] At the time, Sun's Java software division was headquartered in a Cupertino building where the conference room names were all coffee references.[unreliable source?]
References[edit]
- ^Richard Chirgwin (March 2018). 'Java EE renamed 'Jakarta EE' after Big Red brand spat'. The Register. p. 1. Retrieved 19 March 2018.
- ^Hunter, Jason (June 1, 1999). 'Sun and Apache team up to deliver servlet and JSP code'. JavaWorld. InfoWorld. IDG Communications. Retrieved 2020-07-10.
External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Jakarta_Project&oldid=996432418'
Linux How-To's
Getting Started
Before insalling Jakarta Tomcat on your Linux box, be sure you have a JSDK installed. You can obtain a JSDK for your version of linux from Blackdown.org or Sun Microsystems. To install and configure Java in Linux, please follow the instructions provided here.
For the purposes of this paper, it will be assumed that you have installed a JSDK and it is located in:
/usr/java/j2sdk1.4.0/
And java is then located in:
/usr/java/j2sdk1.4.0/bin/
If your setup is different, please adjust accordingly.
If your setup is different, please adjust accordingly.
Obtaining Tomcat
First, you need to decide how you intend to run Tomcat. You have two options for doing this. The first option is running Tomcat standalone, and the second is to integrate it into your existing web server. For the purposes of this document, we will discuss running Tomcat standalone, and integrating it with Apache web server. Tomcat will integrate with other brands of web servers, but only Apache will be discussed here.
If you are choosing to run Tomcat standalone, I recommend you download and install version 4. However, if you plan to integrate Tomcat with Apache, I found it a lot easier to integrate version 3. Again, for the purposes of this document, we will only discuss integrating version 3 with Apache.
Select your download:
Apache Tomcat 3.3 | Apache Tomcat 4.0.1 |
jakarta-tomcat-3.3a.zip | jakarta-tomcat-4.0.1.zip |
Unzipping and Placing Tomcat
Once you've obtained Tomcat, you need to unzip and place it. Use the following command to unzip your package:
/usr/java/j2sdk1.4.0/bin/jar xf jakarta-tomcat-x.x.zip
Where x.x is the version of Tomcat you have chosen to download. Once unzipped, you should have a directory named 'jakarta-tomcat-x.x'. Now, move that directory and its contents to /var/jakarta:
mv jakarta-tomcat-x.x /var/jakarta
Configuring Jakarta
![Jakarta Jakarta](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7b/Tomcat-logo.svg/1200px-Tomcat-logo.svg.png)
Now, go into /var/jakarta/bin/ and chmod a+x *.sh. Now, while still in that directory, you are going to have to do a hack on the tomcat.sh (version 3) or catalina.sh (version 4) depending on which version you are installing. This is technically not how it is supposed to be done, but this saves a lot of time, and takes away a lot of the guesswork. Add the following to the beginning of the .sh file based on your version (the line following the #!/bin/sh):
export JAVA_HOME=/usr/java/j2sdk1.4.0
export TOMCAT_HOME=/var/jakarta # (Version 3)
export CATALINA_HOME=/var/jakarta # (Version 4)
export TOMCAT_HOME=/var/jakarta # (Version 3)
export CATALINA_HOME=/var/jakarta # (Version 4)
Basically, by adding these two lines, you are short circuiting the config mechanism used by Jakarta to find the Home of Java and Tomcat. This is much easier than hunting down all of the config files and changing them individually.
Setting Jakarta to Start at Boot
This section will be completed at a later date. For the time being, jakarta can be started manually with the following command:
/var/jakarta/bin/tomcat.sh start
for version 3, or:
/var/jakarta/bin/catalina.sh start
for version 4.
Using Jakarta
By default, in standalone mode, Jakarta runs on port 8080. Servlets must be deployed in the /var/jakarta/webapps/ROOT/WEB-INF/classes/ directory. Servlets deployed in this directory may be viewed using the URL of the form http://myhost:8080/servlet/MyServlet where MyServlet is the name of the servlet being deployed.
JSP will be discussed at a later date.
Integrating Jakarta with Apache
To integrate Jakarta with Apache, we'll assume you have followed the above instructions to set up Jakarta, and you have installed version 3.
First, you need to obtain and install mod_jk.so. You should select the correct version of mod_jk.so based on your configuration of Apache:
Apache 1.3 with extended API: | mod_jk-3.3-ap13-eapi.so |
Apache 1.3 without extended API: | mod_jk-3.3-ap13-noeapi.so |
Apache 2.0 | mod_jk-3.3-ap20.so |
Once you've downloaded the correct file, rename it to mod_jk.so and place it in /usr/lib/apache/. Be sure to chmod a+x mod_jk.so after you've copied it to /usr/lib/apache/.
Now, you need to edit your /var/jakarta/conf/jk/mod_jk.conf file. Replace:
LoadModule jk_module modules/mod_jk.dll
with:
LoadModule jk_module modules/mod_jk.so
and replace:
JkWorkersFile <fill-path-to>/workers.properties
with:
JkWorkersFile /var/jakarta/conf/jk/workers.properties
At this point, everything is configured on the Jakarta side of things. All that is left, is to configure Apache. Add the following line to the end of /etc/httpd/conf/httpd.conf:
Include /var/jakarta/conf/jk/mod_jk.conf
Now, Apache has been configured and Jakarta has been configured. Make sure Jakarta is running (See 'Using Jakarta' above), and restart apache:
/usr/sbin/apachectl restart
Download Tomcat
Assuming Apache restarts without error, your servlets can now be accessed using the following URL:
Jakarta-tomcat-connectors
http://MyHost/servlet/MyServlet
where MyServlet is the servlet being deployed. Even though Jakarta is now integrated into Apache, you still deploy your servlets in:
Apache Tomcat 8 Free Download
/var/jakarta/webapps/ROOT/WEB-INF/classes/
Congratulations! You have installed Jakarta.