Deploying an Enterprise Application
See Also
Unless your EJB modules and web application modules are designed to be deployed as stand-alone modules,
you should always deploy them by deploying the enterprise application
that contains them. If you run the Run or Deploy commands on an individual
module that is part of an enterprise application, the IDE only deploys that
module itself. Any changes you have made in the other modules in the project are
not propagated to the server.
To deploy an enterprise application:
- In the Projects window, right-click the enterprise application project and
choose one of the following options:
- Run.
- Sub-projects are compiled.
- New and changed files are copied from a sub-project's build directory to
the EAR's deployment directory.
- The target application server and domain start.
- The EAR's deployment directory is used to redeploy the application.
- The "client" for the EAR is triggered (i.e., a web application
opens in the IDE's default browser).
- Deploy.
- Sub-projects are compiled.
- The target application server and domain start.
- If the application has already been deployed, any active sessions and
processes are terminated, and the application is undeployed from the server.
- The EAR project's deployment directory is cleared (i.e., all content is
deleted).
- All the files in the build directories for each of the sub-projects get
copied into the EAR's deployment directory.
- The EAR's deployment directory is used to redeploy the application to the
target application server and domain.
To undeploy an enterprise application (GlassFish):
- In the Services window, expand the Servers > GlassFish node.
- Expand the Applications node and locate the enterprise application you want to undeploy.
- Right-click the enterprise application node and choose Undeploy.
- See Also
- About Enterprise Applications
- Building an Enterprise Application
- Verifying an Enterprise Application
- Redeploying an Application to a Different Server
Legal Notices