BC4J Deployment Prerequisites for OC4J and Oracle Application Server Deployment

Before deploying a BC4J project, make sure that the following deployment prerequisites have been met for deploying to a standalone Oracle Application Server Containers for J2EE (OC4J) or to Oracle Application Server via Distributed Configuration Management (DCM):

Step 1: Verify that all BC4J Runtime libraries are installed

If you are using a standalone OC4J server, you must set it up with the BC4J runtime libraries. Skip this step if you are deploying to the embedded OC4J server or directly to Oracle Application Server as the BC4J runtime libraries should already be installed with JDeveloper and Oracle Application Server.

Note: The embedded OC4J server's application.xml file contains a listing of the J2EE application runtime files and sets the classpath to these files. These files are also located in your JDeveloper installation directory in:

<jdev_install>/bc4j/lib

Step 2: Start OC4J

If you are deploying your applications against a standalone OC4J, you'll need to start it from the command line as follows:

java -jar oc4j.jar

If you are using the JDeveloper embedded OC4J server to first test your deployments, it is automatically started when you run, debug, profile, CodeCoach, and locally deploy your applications. See the Help topics related to the embedded OC4J server for more information.

Step 3: Create an application server connection(s)

Create a connection(s) to any of the following supported target application server connection types:

Step 4: Create a Business Components for Java project

You'll need to create a BC4J project using the Business Components Package Wizard.

Step 5: Define Business Component Runtime Properties for Web Applications

For web application deployments, make sure that the server connection information to connect to deployed business components is properly configured in the bc4j.xcfg file. This file defines all of the deployment configurations of a particular application module in the business components project and permits data tags and data web beans to access a specific view object belonging to the application module.

See About BC4J Configuration Properties and Defining BC4J JSP Runtime Properties in the bc4j.xcfg File for more information.

Step 6: Deploy bc4j.ear to Standalone OC4J

When deploying BC4J web applications to standalone OC4J, make sure that the bc4j.ear file is deployed to OC4J. Skip this step if you are deploying to the embedded OC4J server or directly to Oracle Application Server as this file and the BC4J runtime libraries should already be installed with JDeveloper and Oracle Application Server.

The bc4j.ear file contains the required web application and UIX files required for deployment. You only need to perform this task one time (not every time a BC4J web application is deployed).

In the Navigator, right-click bc4j.ear below the project in the Navigator (below <projectname_jpr_War.deploy>) and choose Deploy to <application_server_connection>. The bc4j.ear file is also located in the JDeveloper installation directory at the following location:

<jdev_install>/BC4J/redist