The Applications page opens.
The Deploy 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.
If you specified either a Packaged File to Be Uploaded to the Server or a Local Packaged File That Is Accessible From the GlassFish Server, the application type is detected automatically. If you specified a Directory That Is Accessible From the GlassFish Server, you must specify the type manually.
In the URL of the web application, the context root immediately follows the port number (http://host:port/context-root/...). The context root must start with a forward slash, for example, /hello.
The default name appears if you chose to upload a file. The application name must be unique.
The name can include an optional version identifier, which follows the name and is separated from the name by a colon (:). The version identifier must begin with a letter or number. It can contain alphanumeric characters plus underscore (_), dash (-), and period (.) characters. For more information about module and application versions, see the Module and Application Versions in Oracle GlassFish Server 3.1 Application Deployment Guide.
The Virtual Servers option appears if only the default server instance, server, exists. If clusters or other standalone server instances exist, you can select virtual servers after deployment. Go to the Edit Application page, select the Target tab, and select Manage Virtual Servers for the desired target.
This option is selected by default. If this option is disabled, the application is unavailable.
If the Enabled checkbox is selected, high-availability is enabled for web sessions. If set to false (default) all web session saving is disabled for the specified web application. If set to true, the specified web application is enabled for high-availability. Set this option to true only if high availability is configured and enabled at higher levels, such as the server and container levels.
This option appears if clusters or standalone server instances aside from the default server instance (server) exist.
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, deployment is not performed. The verifier examines the structure and content of the deployment descriptors. Verification of large applications is often time-consuming. This option is disabled by default.
Verifier packages must be installed from the Update Tool or a warning is logged and this option is ignored.
If this option is not selected, an attempt to deploy an application that is already deployed results in an error. This option is disabled by default.
This option is disabled by default. This option is supported only on the default server instance, named server. It is not supported and ignored for any other target.
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) and must be set to file, which is the default and recommended value.
If any active web session, SFSB instance, or EJB timer 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, GlassFish Server serializes the data and saves it in memory. To restore the data, the class loader of the newly redeployed application deserializes the data that was previously saved.
This option is disabled by default.
The paths may be absolute or relative. A relative path is relative to domain-dir/lib/applibs. If the path is absolute, the path must be accessible to the domain administration server (DAS), which means it must be under domain-dir. The libraries are made available to the application in the order in which they are specified.
The Target option appears if clusters or standalone server instances aside from the default server instance (server) exist. By default, the module or application is deployed to the default server instance, named server. Use the Add All button to deploy to all targets. Use the Remove and Remove All buttons to remove targets from the Selected Targets list.
See Also