Packaging EJBs for Deployment

A J2EE EJB module is packaged as an EJB JAR file which contains one or more EJB components as well as the standard J2EE EJB deployment descriptor, ejb-jar.xml, and possibly target-specific deployment descriptors, as well. Once you've created the deployment profile, you can deploy the application to an application server or as an archive file.

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

To package a web application for deployment:

Create a EJB JAR File 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.xml deployment descriptor to your project, if it is not already present. Normally, this file is created with the EJB JAR File deployment profile.
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 a 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.

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.