About Business Components for Java (BC4J) Deployment

Deploying business components for Java in JDeveloper involves three main steps which you must perform:

Verify that the target application server has met the BC4J prerequisites: standalone OC4J and Oracle Application Server or WebLogic
Create the deployment profile for the BC4J application
Deploy the deployment profile:

When business components are deployed as a J2EE web module, the business components are packaged as a J2EE web archive (WAR) file which the client code can access. Deploying as a J2EE web module is especially suited to client code, such as JavaServer Pages and servlets, that run on fast, shared machines.

When business components are deployed as a CORBA server object or an EJB session bean, the business components run in a separate tier (middle-tier) from the client programs. For example, the CORBA object runs on the VisiBroker server and the EJB session bean runs on an EJB server such as Oracle Application Server.

At deployment time, the application module must be made available (remoteable) to the client code. In JDeveloper, you can make the application module available (remoteable) when creating a deployment profile with the Business Components Deployment Profile Wizard, Step 3 of 3: AppModules. Making the application module remoteable means creating an EJB remote interface and/or client-side proxies for application module methods which must be deployed to the client platform. For more information, see:

Sample Client Code for an EJB Client Deployed to OC4J

Sample Client Code for an EJB Client Deployed to WebLogic

Notes:

See Understanding the n-Tiered Business Components Architecture for more information.
JDeveloper lets you deploy your J2EE applications to the embedded Oracle Application Server Containers for J2EE (OC4J) in JDeveloper or to one of the supported target application servers including a standalone OC4J instance, directly to Oracle Application Server via local or remote Distributed Configuration Management (DCM), and BEA WebLogic.
Before you start a BC4J project to be deployed as an EJB session bean or deployed to a foreign application server, 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.