Packaging ADF Business Components as an EJB Session Bean

You can package an ADF Business Components project as an EJB session bean, and subsequently deploy it as an EJB module to an application server.

EJB Components can also be deployed with a test client. See Packaging EJBs for Testing.

To package a Business Components project as an EJB session bean:

Create a Business Components EJB Session Bean deployment profile for your project. A profile may have already been created for your project. If you wish to deploy to multiple targets, create a separate profile for each.
Add a ejb-jar.xml deployment descriptor to your project, if it is not already present.
Add target-specific deployment descriptors, if required, and not already present:
- If the deployment target is Oracle Application Server or a standalone OC4J server, add an orion-ejb-jar.xml deployment descriptor to your project.
- If the deployment target is a WebLogic application server, add an weblogic-ejb-jar.xml deployment descriptor to your project.
- If the deployment target is a JBoss application server, and you want to support JBoss-specific configuration options for the EJBs, add a jboss.xml deployment descriptor to your project.
Edit the deployment descriptor to move the Session Facade (BMT) EJB type from the A vailable to the Selected list.
Edit the application module:
1. In the Navigator, right-click the Business Components application module icon and choose Configurations.
2. Select the appropriate <YourApplicationModule> OracleAS configuration.
3. Select C opy. A copy of the configuration is created and displayed below the Names list.
4. Select this configuration and click E dit.
5. In the Connection Type list, choose JDBC DataSource.
6. Enter a DataSource Name. For example: java:/OracleDS

Note:

When deploying to OC4J or Oracle Application Server, do not assemble EJB 1.1 and EJB 2.0 modules into a single J2EE application EAR file as deployment will fail and SQL and connection errors will be raised.