Deploy EJB modules

When you deploy an EJBs module, you install that module on a server that has been configured to support deployed modules.

Assemble one or more EJB modules, assemble one or more Web modules, and assemble them into a J2EE application.

Assemble one or more EJB 3.0 modules, assemble one or more Web modules, and assemble them into a J2EE application.

For an overview about the changes to the EJB deployment model for EJB 3.0, see the topic "EJB 3.0 deployment overview."

 

1. Prepare the deployment environment.

2. Update the configuration for each EJB module as needed for the deployment environment.

3. Address potential interoperability issues.

   There can be unexpected results if a WebSphere stack product, or another product, that runs on a version of Application Server that does not support EJB 3.0 attempts to remotely invoke a method on an EJB 3.0 compliant enterprise bean on a separate server that is running a version Application Server that supports EJB 3.0. If these products attempt to invoke a method through the enterprise bean's EJB 3.0 remote business interface, they might encounter exceptions that were introduced in EJB 3.0 that will be pushed back to the environment not EJB 3.0 compliant.

   This scenario could also be an issue for an administrator of an environment that includes a combination of stack products that contain a mixture of EJB 3.0 compliant and non-compliant instances of Application Server.

   The following is a list of the exception classes that have been introduced in EJB 3.0:

   • javax.ejb.ConcurrentAccessException

   • javax.ejb.EJBAccessException

   • javax.ejb.EJBTransactionRequiredException

   • javax.ejb.EJBTransactionRolledbackException

   • javax.ejb.NoSuchEJBException

   1. Ensure that Application Server is updated to 7.0.0.3.

   2. Manually copy the <APP_ROOT>/runtimes/ejb3exceptions.jar file from Application Server to a directory on each of the stack products installations, or other product installations, that you will use as the EJB 3.0 client.

   3. Verify the directory that contains the ejb3exceptions.jar file is in the class path. One possible location for the JAR file that would satisfy this requirement is the <APP_ROOT>/lib directory on a server not EJB 3.0 compliant.

      Avoid trouble: Just like the EJB thin client jars, if an update becomes available, users will need to copy the ejb3exceptions.jar file again after installing the version of the WAS containing the updated version.

4. Deploy the application.

 

Next steps

If we specify that the EJBDeploy tool be run during application installation and the installation fails with a NameNotFoundException message, verify the input JAR or EAR file does not contain source files. Either remove the source files or include all dependent classes and resource files on the class path. If there are source files in the input JAR or EAR file, the EJB deployment tools runs a rebuild before generating the deployment code.

If the module deploys successfully, test and debug the module.

EJB 3.0 deployment overview
EJBDEPLOY relationships – troubleshooting tips
EJB module settings

 

Related concepts

EJB 3.0 module packaging overview
EJB modules