Deploying an ADF Business Components Application as an EJB Session Bean

Deploy an application containing business components through its Business Components deployment profile, which is a .bcdeploy file in your project.

A Business Components deployment profile contains subprofiles, from which parts of the application can be separately deployed.

To deploy a Business Components application as an EJB session bean:

Create a business components deployment profile.
Create a connection to the target application server.
Select the deployment profile in the Navigator, right-click, and choose one of the deployment options:
- Deploy to | <application server connection>: the EJB module is packaged as an EJB JAR file, which is encapsulated in an EAR file and is deployed to the selected application server connection.
- Deploy to JAR File: the EJB module is delivered as JAR file.
- Deploy to EAR File: the application is packaged as an EAR file and is saved to the location specified in the EAR deployment profile. See Deploying a J2EE Enterprise Archive.

To deploy a part of the application:

From the Navigator, expand the Business Components EJB deployment profile.
Select one of the subprofiles:
- <ProjectNameCommon>.deploy: the files shared between the business components and the client
- <ProjectNameEJB>.deploy : the business logic in the EJB session bean
- <ProjectNameMiddleTier>.deploy: the class and XML files
Right-click and choose one of the deployment options.

Note:

In the case of an ADF JClient application that you deploy with remote business services, you may receive an Authentication Failed error when your attempt to run the application on the application server. The application server expects to obtain the JClient login credentials and but they were were not deployed with the application server connection. If you are attempting to run the application within JDeveloper, you can edit the connection in JDeveloper and select Deploy Password in the Authentication tab of the Edit Application Server Connection dialog. When you want to deploy the JClient application to a production environment, you should not deploy the login credentials with the connection. Instead, you can generate a JClient login dialog in your JClient application by selecting Create Login Dialog in the JClient Form Wizard. Alternatively, when you do not want to provide a login dialog for your production environment, use jndi.properties to provide server credentials. For more information, see Oracle Application Server Containers for J2EE Stand Alone User's Guide.