Deploying Web Applications to Apache Tomcat

Deploying your J2EE web applications to the Apache Tomcat 4.1.12 server involves two main steps:

Loading BC4J Runtime Libraries to Apache Tomcat . Perform only once, and only if your deployment includes BC4J
Creating a web archive (WAR) File for Deployment to Apache Tomcat.

Note: Before you start a BC4J project to be deployed to Apache Tomcat, you must select a connection type and the corresponding SQL dialect, type maps or domains. For instructions, see Understanding Connections, SQL Dialect, Type Maps, and Domains.

Loading BC4J Runtime Libraries to Apache Tomcat

The steps in this section are a one time task which you perform when you deploy web applications created in JDeveloper to Apache Tomcat for the first time. For all subsequent deployments whenever you add a new J2EE WAR file, you only need to perform the steps in the next section and then restart Tomcat.

To load BC4J runtime libraries to Apache Tomcat:

You must first copy the various JDeveloper runtime libraries, which are located in different JDeveloper directories, to the following Apache Tomcat installation directory. In most cases, you would copy these files into <Tomcat_install>/lib. However, in general, WAR files are copied to the <Tomcat_install>/webapps directory.

Copy the BC4J runtime libraries.
Copy the UIX and JDeveloper runtime libraries. For the cabo.war file, copy this file to the <Tomcat_install>/webapps directory.
Copy the JDBC database retrieval and character conversion libraries.
Copy the interMedia Text libraries. interMedia Text is an Oracle9i feature for storing, retrieving, and manipulating audio, document, image, and video data in an Oracle database.
Copy the runtime support libraries.
Copy the XML support library.
Copy the client data model support file.
Copy the BC4J web application image and cascading style sheet support file, webapp.war, into the <Tomcat_install>/webapps directory.

Note: The correct directory location for these files in releases after Tomcat 4.1.12 may change. Check the JDeveloper Release Notes under "Deployment" for information about directory locations for later releases.

Creating a web archive (WAR) file for Deployment to Tomcat

In JDeveloper, make sure that you've created a workspace and project.
(Optional) If your web application is accessing business logic in the Oracle9i database, make sure that you've created a BC4J project.
If not already done, create a web application such as a JSP or servlet based on the business logic.
Note: JDeveloper automatically generates the web.xml deployment descriptor for the web application.
Create a deployment profile for web applications (WAR).
To edit the WAR deployment profile settings, select and right-click <webapp>.deploy and choose Settings from the context menu. The WAR Deployment Profile panel displays.
1. General Page: enter a default location for the deployed WAR file. Oracle recommends that you specify the following location for your deployed web applications:
  <Tomcat_install>/webapps/<subdirectory>
2. Enter the Enterprise Application Name. The default name is webapp but you can enter any other name.
3. On Tomcat, the system administrator must assign a context path to your application in the conf/server.xml file:
```
 
        <DefaultContext crossContext="true"/> 
```
  This will allow the WAR file in the root of <tomcat-install>/webapps to detect the /cabo/ shared installables. See Tomcat system administration documentation for more information.
4. Keep the default settings on the remaining pages.
5. Click OK when you are done.
Select and right-click <webapp>.deploy and choose Deploy to WAR file from the context menu.
The WAR which contains the generated web application files are deployed directly to location you specified in step 5.a above: <Tomcat_install>/webapps/<subdirectory>. See the Deployment Log window for details.

Note: However, if you skipped step 5 and did not specify a default location for the deployed WAR, you will need to copy the unpacked directory hierarchy into a subdirectory below <Tomcat_install>/webapps.
Stop Tomcat.
Restart Tomcat for all changes to take effect.
When Tomcat is started, it will automatically expand the WAR.
Execute the application in your browser by entering the enterprise name you specified in step 5.2 for the WAR. For example:
http://<hostname>:8080/<webapp>/main.html

Notes:

If you require further assistance for any field on any page in JDeveloper, click Help.
For more information about Apache Tomcat:
http://jakarta.apache.org/tomcat/index.html
Make sure that the web deployment descriptor is located inside the Web Application Archive (WAR) file as follows:
WEB-INF/web.xml
Make sure that you have the tools.jar in the Tomcat classpath. This file is located in <jdev_install>/jdk/lib and must match the version of the JDK being used to run Tomcat. Otherwise, you may encounter problems when running applications in Tomcat.
Oracle has certified release 4.1.12 of Tomcat.