How Do I Deploy BC4J Applications to JBoss 3?

An Oracle JDeveloper How To Document
October 15, 2002

Content

• Introduction
• Deploying the BC4J runtime to JBoss
• Creating a BC4J Project
• Starting JBoss
• Creating a BC4J JSP Application
• Deploying the BC4J JSP Application
• References

Introduction

This document describes in detail the requirements and steps to deploy the BC4J runtime components as well as a BC4J Application as a Web Module to JBoss. This document was written for Oracle9i JDeveloper Release 9.0.3 and JBoss 3.0.3 with Tomcat 4.0.5, although other versions of Oracle9i JDeveloper and/or JBoss should have the same behavior.

Note: There are issues with the class loaders used in Tomcat 4.0.3. Make sure that your JBoss version either uses 4.1.x or 4.0.5.

Note: This document is intended for use with Sun's Java2 SDK 1.4.1. If you use J2SDK 1.3.1 you will get an IllegalAccessViolation exception when you use your BC4J application.

Deploying the BC4J runtime to JBoss.

To deploy the BC4J runtime to JBoss, the following JAR files need to be copied to the JBOSS_HOME\server\default\lib directory (for example, C:\jboss-3.0.3_tomcat-4.0.5\server\default\lib).

If you will be using BC4J web applications (which we will), the file bc4j.ear must also be deployed. Copy this file from %JDEV_HOME%\bc4j\redist to JBOSS_HOME\server\default\deploy (for example C:\jboss-3.0.3_tomcat-4.0.5\server\default\deploy).

The run.bat script should be modified so that crimson.jar is on the CLASSPATH before the Oracle XML parser which is installed with the BC4J runtime libraries. Here are the modifications:

After these files have been copied to the {JBOSS_HOME}\server\default\lib directory, You must restart JBoss.

Creating a BC4J Project.

Our BC4J Project will be created on the DEPT table in the SCOTT sample schema which is part of the Oracle database.

Create an Entity Object, with default View Object and default Application Module in the Business Components Package Wizard. Once created, your project should look similar to the following:

Starting JBoss

Set the JAVA_HOME environment variable and add the Java2 SDK’s bin directory to your PATH.

Windows Example:

set JAVA_HOME=C:\jdk1.4.1

UNIX Example:

export JAVA_HOME=/usr/java/jdk1.4.1

Then execute the run located in the JBoss/bin directory. (For example, C:\jboss-3.0.3_tomcat-4.0.5\bin).

After JBoss is started, you will see many lines of information printed to the command shell which end in the following:

Once started, you can ensure that JBoss with Tomcat is running by testing the URL http://localhost:8080/jmx-console/index.jsp. Here is the display that you should see.

Note: If you are behind a proxy server, you may need to change localhost to the DNS name for your machine.

Creating a BC4J JSP Application.

In order to test our BC4J business components, we will create a JSP application which will use them.

1. Create a New Empty Project
2. Using the Business Components JSP Application wizard, create a default JSP Application for the BC4J objects just created.
3. From the main menu, Choose File > Save All.

Deploying the BC4J JSP Application.

When you create a default BC4J JSP Application, a default deployment profile will be created automatically. The name of this profile is ProjectX_jpr_War.deploy. The BC4J Business Components will be included in the EAR file automatically.

Here are the steps to deploy our EAR file:

1. In the Navigator, right-click ProjectX_jpr_War.deploy (where ProjectX_jpr_War.deploy is the name of the deployment profile in the BC4J JSP Application project), and choose Deploy to EAR file.
2. On the Message window, under the Deployment tab, a message will state the location of the newly created EAR file. Copy this file to the JBoss\deploy directory.

Here is an example of the text displayed in the Message Log on the Deployment tab:

Wrote EAR file to C:\jdev\jdev\mywork\Workspace1\Project2\src\ProjectX_jpr_War.ear
Elapsed time for deployment:  8 seconds
----  Deployment finished.  ----    Oct 8, 2002 2:19:50 PM

You now have a fully functional BC4J JSP Application deployed as a Web Module. You may now invoke the Application with your web browser with the URL http://localhost:8080/<context root>, where <context root> is the J2EE Context Root for your Project containing the BC4J JSP Application ( For example: Workspace1-Project2-context-root )

References

• How Do I Deploy Enterprise JavaBeans to JBoss?
• JBoss 3.0 Documentation
• JBoss Web Site