Deploying an EJB Module
See Also
There are two ways to deploy an EJB module:
- As part of an enterprise application. When an EJB module is part
of an enterprise application, its enterprise beans can be accessed from external
clients and web application modules through its remote interfaces, and by
other modules in the enterprise application through its local interfaces.
All of the JAR files needed for execution are packaged in the enterprise
application's EAR file and the classpath to these JAR files are written in
the EJB module's manifest file. This is the most common way of deploying an
EJB module.
- As a stand-alone EJB module. Enterprise beans in a stand-alone EJB
modules can only be accessed through their remote interfaces. All of the JAR
files needed for execution are packaged in the EJB JAR file itself.
There are two commands you can use to deploy an EJB module or an enterprise
application:
- Deploy. This stops the enterprise application, undeploys
the application or stand-alone module from the application server, and deploys
your local version.
- Run. Like Deploy, except that for enterprise applications,
this command also opens the client module's default URL in the external browser.
To deploy an enterprise application:
- In the Projects window, right-click the enterprise application project and
choose Run or Deploy.
To deploy a stand-alone EJB module:
- In the Projects window, right-click the EJB module project and choose Run
or Deploy.
- See Also
- Building an EJB Module
- Debugging an EJB Module
- Testing an EJB Module
- Adding a
Module to an Enterprise Application
- Registering a Server
- Redeploying an Application to a Different Server
Legal Notices