Redeploying an application deploys a new version of the application while preserving the settings and other options with which the application was originally deployed.
Ensure that the application that you are redeploying is already deployed.
The Applications page opens.
The application 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.
The Redeploy Applications or Modules page opens.
The client machine is the host on which you are viewing the Administration Console through a browser.
Click Browse to browse to the file, or type the full path to the file.
The server machine is the host that is running the domain administration server (DAS).
Click Browse Files to browse to a file, or Browse Folders to browse to a directory. Alternatively, type the full path name to the file or directory. Deploying from an exploded directory is for advanced developers and is not recommended for production environments.
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 session-manager 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.
If this option is disabled, JSP files are compiled at runtime when they are first accessed. This option is disabled by default.
If this option is selected and if verification fails, redeployment 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.