Use the Redeploy Applications or Modules page to redeploy a previously deployed application.
The Redeploy Applications or Modules page contains the following options.
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.
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.
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.
Read-only field displaying the name of the application that you are redeploying.
If the Preserve Sessions checkbox is selected, active sessions of the application that you are redeploying are preserved and then restored when the redeployment is complete.
If any active session of the application fails to be preserved or restored, none of the sessions will be available when the redeployment is complete. However, the redeployment continues and a warning is logged.
To preserve active sessions, the GlassFish Server serializes the sessions and saves them in memory. To restore the sessions, the class loader of the newly redeployed application deserializes any sessions that were previously saved.
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.
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.