When you deploy an Enterprise JavaBeans (EJB) module, you install
that module on a server that has been configured to support deployed modules.
Procedure
- Prepare the deployment
environment.
- Update the configuration for each EJB module as needed for the
deployment environment. See the information center for the Application Server
Toolkit for more information about modifying deployment descriptors.
- Required: If a module has dependencies
on Java 5-specific extensions, such as Generics, annotations, and so on, then
you must run the ejbdeploy command-line tool separately and prior to installing
the module or application containing it. This is because the administrative
console and the wsadmin command-line tool do not allow for specifying the
ejbdeploy -complianceLevel 5.0 option.
- Deploy the application.
What to do next
If you specify that EJB deploy be run during application installation
and the installation fails with a NameNotFoundException message, ensure that
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.