en.help.task-appredeploy.html Maven / Gradle / Ivy
To Redeploy a Deployed Application
Redeploying an application deploys a new version of the application while preserving the
settings and other options with which the application was originally deployed.
Before You Begin
Ensure that the application that you are redeploying is already deployed.
- In the navigation tree, select the Applications node.
The Applications page opens.
- In the Deployed Applications table, click Redeploy in the row for the application
that you are redeploying.
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.
- Specify the location of the application to redeploy.
- If the application is an archive file that resides on or is accessible
from the client machine, select the option Packaged File to Be Uploaded to
the Server.
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.
- If the application is an archive file that resides on the server machine,
or is an unpackaged application from an exploded directory, select the option Local
Packaged File or Directory That Is Accessible From the GlassFish Server.
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.
- If you require active web sessions, stateful session bean instances, or EJB timers
of the application to be preserved and then restored when the redeployment is
complete, select the Preserve Sessions checkbox.
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.
- Select the Precompile JSPs checkbox to precompile JavaServer Pages (JSP) files.
If this option is disabled, JSP files are compiled at runtime when they
are first accessed. This option is disabled by default.
- Select the Run Verifier checkbox to run the verifier before redeployment.
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.
- Click OK.
See Also
-
-
-
-
-
-
-
-
-
-
-
-
-
Broken Link (Target ID: TASK-EJBCONTAINERAVAILABILITY)
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices