en.help.ref-redeploy.html Maven / Gradle / Ivy

Go to download

Redeploy Applications or Modules
Use the Redeploy Applications or Modules page to redeploy a previously deployed application.

The Redeploy Applications or Modules page contains the following options.

Location
The location of the new archive for the application that you are redeploying.

The following options specify from where the archive is accessible and whether the archive is a file or a directory.

Packaged File to Be Uploaded to the Server
The archive is in a file that resides on or is accessible from the client machine.

The client machine is the host on which you are viewing the Administration Console through a browser.


Local Packaged File or Directory That Is Accessible From the GlassFish Server
The archive is a file that resides on the server machine, or is an unpackaged application in an exploded directory.

The server machine is the host that is running the GlassFish Server domain administration server. 




Application Name
Read-only field displaying the name of the application that you are redeploying.

The name can include an optional version identifier, which follows the name and is separated from the name by a colon (:). For more information about module and application versions, see the Module and Application Versions in Oracle GlassFish Server 3.1 Application Deployment Guide.


Preserve Sessions
If the Preserve Sessions checkbox is selected, active web sessions and stateful session bean instances of the application that you are redeploying are preserved and then restored when the redeployment is complete. Persistently created EJB timers are also preserved. This option is not supported and ignored in a clustered environment.

Some changes to an application between redeployments prevent this feature from working properly. For example, do not change the set of instance variables in the SFSB bean class.

For web applications, this feature is applicable only if in the glassfish-web-app.xml file the persistence-type attribute of the Broken Link (Target ID: BEAXQ) element is file.

For stateful session bean instances, the persistence type without high availability is set in the server (the SFSB Persistence Type option under EJB Container Availability) and must be set to file, which is the default and recommended value.

If any active web session, SFSB instance, or EJB timer of the application fails to be preserved or restored, none of these will be available when the redeployment is complete. However, the redeployment continues and a warning is logged.

To preserve active state data, the GlassFish Server serializes the data and saves it in memory. To restore the data, the class loader of the newly redeployed application deserializes any data that was previously saved.


Precompile JSPs
If this option is selected, JavaServer Pages (JSP) files are precompiled. If this option is disabled, JSP files are compiled at runtime when they are first accessed. This option is disabled by default.


Run Verifier
If this option is selected, the verifier is run before deployment. If verification fails, deployment is not performed. The verifier examines the structure and content of the file. Verification of large applications is often time-consuming. This option is disabled by default.



Related Tasks

To Redeploy a Deployed Application


To View a List of Deployed Applications


To Deploy a Web Application


To Deploy an Enterprise Application


To Deploy an Application Client


To Deploy a Connector Module


To Deploy an EJB Jar


To Edit a Deployed Application


To View Descriptors of an Application


To View Endpoint Information for a Web Service


To Launch an Application


To Launch an Application Client


To Reload a Deployed Application


Broken Link (Target ID: TASK-EJBCONTAINERAVAILABILITY)


Related asadmin Commands

deploy(1)


redeploy(1)


list-applications(1)


list-modules(1)




Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices