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.
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 Oracle GlassFish Server 3.1 Application Deployment Guide.
This option is selected by default unless the application is deployed to a cluster, in which case this option is not selected by default. If this option is disabled, the application is unavailable.
If the Enabled checkbox is selected, high-availability is enabled for stateful session bean (SFSB) checkpointing and potentially passivation. If set to false (default) all SFSB checkpointing is disabled for the specified EJB module. If set to true, the specified EJB module 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.
If this option is selected and 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.
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.
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 stand-alone 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.