This section discusses the various tools that can be used to deploy modules and applications. The deployment tools include:
You can use the following asadmin commands to deploy or undeploy web or EJB modules on local servers.
deploy — Deploys a web or EJB module. If the module is already deployed, you can force redeployment by setting the --force option to true. You can also deploy a module in an expanded directory structure. See Directory Deployment.
redeploy — Redeploys a web or EJB module that is already deployed. Whenever a redeployment is done, the sessions at that transit time become invalid unless you use the keepSessions=true property of the asadmin redeploy command.
disable — Immediately disables a web or EJB module. Disabling a web module makes it inaccessible to clients.
deploydir — Deploys a web or EJB module from an expanded directory structure. Deprecated; use asadmin deploy instead.
For details, see the Sun GlassFish Enterprise Server v3 Prelude Reference Manual.
You can use the Administration Console to deploy modules to both local and remote Enterprise Server sites.
Open the Applications component.
Go to the page for the type of application or module.
For example, for a web application, go to the Web Applications page. You can undeploy, enable, or disable an application or module from the table on this page.
Click on the Deploy button.
On this page, you type the path to the WAR, JAR, or the exploded directory structure. You can also specify deployment settings that vary according to the type of module.
For details, click the Help button in the Administration Console.
For more information on deploying from an exploded directory structure, see Directory Deployment.