| Exit Print View | |
Sun GlassFish Enterprise Server v3 Application Deployment Guide |
|
|
|
1. Overview of Sun GlassFish Enterprise Server v3 Application Deployment
Deploying Applications and Modules
To Deploy an Application or Module
To List Deployed Applications or Modules
To Redeploy an Application or Module
To Disable an Application or Module
To Enable an Application or Module
To Undeploy an Application or Module
To Reload Changes to Applications or Modules Dynamically
To Deploy an Application or Module Automatically
To Deploy an Application or Module by Using a Deployment Plan
To Deploy an Application or Module in a Directory Format
Modifying the Configuration of a Web Application or Module
To Set a Web Context Parameter
To Unset a Web Context Parameter
To List Web Context Parameters
To Set a Web Environment Entry
To Unset a Web Environment Entry
To List Web Environment Entries
Web Module Deployment Guidelines
To Deploy and Configure a Standalone Connector Module
Redeploying a Standalone Connector Module
Deploying and Configuring an Embedded Resource Adapter
Assembling and Deploying an Application Client Module
To Assemble and Deploy an Application Client
To Prepare Another Machine for Running an Application Client
To Undeploy an Application Client
Lifecycle Module Deployment Guidelines
Web Service Deployment Guidelines
A. The asadmin Deployment Subcommands
B. Enterprise Server Deployment Descriptor Files
Note - "The Enterprise Server Web Profile supports the EJB 3.1 Lite specification, which allows enterprise beans within web applications, among other features. The Enterprise Server Full Platform Profile supports the entire EJB 3.1 specification. For details, see JSR 318 (http://jcp.org/en/jsr/detail?id=318
The following guidelines apply to deploying an EJB module in Enterprise Server:
JNDI Name. If no JNDI name for the EJB JAR module is specified in the jndi-name element immediately under the ejb element in sun-ejb-jar.xml, or there is no sun-ejb-jar.xml file, a default, non-clashing JNDI name is derived. A warning message is logged, recording the JNDI name used to look up the EJB JAR module.
Stubs and Ties. Use the 
get-client-stubs(1) subcommand in remote mode to retrieve stubs and ties.
|
|