Deploying BC4J as an EJB Session Bean to Standalone OC4J or Oracle Application Server

When deploying a BC4J as an EJB session bean to the embedded OC4J server or to a standalone OC4J instance, you must ensure that the BC4J runtime libraries are installed and the deployment profile is created. The JDeveloper deployment wizards create all the necessary code to deploy business components as an EJB session bean.

Important: Before deploying your BC4J EJB application, ensure that you've met all the requirements in BC4J Prerequisites for OC4J Deployment.

To deploy BC4J as an EJB session bean to a standalone OC4J instance or Oracle Application Server via DCM:

Make sure you've created a BC4J EJB deployment profile.
In the Navigator, select the <ProjectNameEJB>.bcdeploy deployment profile you want to deploy.
Right-click <ProjectNameEJB>.bcdeploy and choose from the available context menu options:
- Deploy to <application_server_connection>: the EJB module is packaged as an EJB JAR. JDeveloper also generates an EAR file which contains the EJB JAR before deploying to the selected standalone OC4J connection or Oracle Application Server via DCM connection you created earlier.
- Deploy to New Connection: Launches the Connection Wizard which lets you create a new application server connection.
- Deploy to JAR file: the EJB module is packaged as a JAR file and saved to the local directory or mapped network.
- Deploy to EAR file: the EJB module is packaged as an EAR file and saved to the local directory or mapped network drive you specified in the deployment profile.
The application files including the JAR and EAR file are packaged as a EJB JAR and deployed to the standalone OC4J instance or Oracle Application Server. JDeveloper also generates an EAR file which contains the EJB JAR before deploying to the selected standalone OC4J connection or Oracle Application Server via DCM connection you created.

Refer to the "Oracle Application Server Containers for J2EE User's Guide" Part Number B10322-01 provided with the Oracle Application Server documentation library for information on the deployed location of the application files including the JAR and EAR files.

Note: See also About Deploying on Oracle Application Server for information on deploying to an Oracle Application Server using the Oracle Enterprise Manager.

Deployment Options

You can also choose to deploy the subprofiles separately in the following ways:

From the Navigator, click + to expand <ProjectNameEJB>.bcdeploy and to display the subprofiles:
- <ProjectNameCommon>.deploy: files shared between the business components and the client
- <ProjectNameEJB>.deploy: contains the business logic in the EJB session bean
- <ProjectNameMiddleTier>.deploy: contains the class and XML files
Right-click any of these subprofile icons to perform a variety of tasks including: Deploy to <application_server_connection>, Deploy to New Connection, Deploy to JAR file, Deploy to EAR file, display deployment profile Settings.