All Downloads are FREE. Search and download functionalities are using the official Maven repository.

en.help.ref-uploaddev.html Maven / Gradle / Ivy


Deploy Applications or Modules

Use the Deploy Applications or Modules page to deploy an application.

The Deploy Applications or Modules page contains the following options for all applications. Additional options appear only after you specify the Location field for the application.

Location

The location of the archive for the application that you are deploying.

The following options specify from where the archive is accessible and whether the archive is a file or a directory.

Packaged File to Be Uploaded to the Server

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.

Local Packaged File or Directory That Is Accessible From the GlassFish Server

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.

Type

The type of the application. Available choices are:

  • Web Application

  • Enterprise Application

  • Application Client

  • Connector Module

  • EJB Jar

  • Other

Target

The target server instances and clusters on which to deploy the module or application.

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.

Select targets from the Available Targets list and use the Add button to move them to the Selected Targets list. 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.

Additional options for the various application types are described in the following sections.

Additional Options for a Web Application

If the application type is Web Application, the following options appear.

Context Root

The path to the application. 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.

Application Name

The name of the application.

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.

Virtual Servers

The virtual servers associated with this application.

The Virtual Servers option appears if only the default server instance, server, exists. If clusters or other stand-alone 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.

Status

If this option is selected, the application is enabled. This option is selected by default.

Availability

If the Enabled checkbox is selected, high-availability is enabled for web sessions and for stateful session bean (SFSB) checkpointing and potentially passivation. If set to false (default) all web session saving and SFSB checkpointing is disabled for the specified application, web application, or EJB module. If set to true, the specified application or 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.

Precompile JSPs

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.

Run Verifier

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.

Force Redeploy

If this option is selected, the application is redeployed if it is already deployed. 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.

Libraries

A comma-separated list of library JAR files specific to this module or application. 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.

Description

A description of the application.

Additional Options for an Enterprise Application

If the application type is Enterprise Application, the following options appear.

Application Name

The name of the application.

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.

Virtual Servers

The virtual servers associated with this application.

The Virtual Servers option appears if only the default server instance, server, exists. If clusters or other stand-alone 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.

Status

If this option is selected, the application is enabled. This option is selected by default.

Availability

If the Enabled checkbox is selected, high-availability is enabled for web sessions and for stateful session bean (SFSB) checkpointing and potentially passivation. If set to false (default) all web session saving and SFSB checkpointing is disabled for the specified application, web application, or EJB module. If set to true, the specified application or 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.

Precompile JSPs

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.

Run Verifier

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.

Force Redeploy

If this option is selected, the application is redeployed if it is already deployed. 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.

Java Web Start

If this option is selected, Java Web Start access is permitted for an application client module. This option is disabled by default.

Libraries

A comma-separated list of library JAR files specific to this application. Specifies an absolute or relative path. 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.

Description

A description of the application.

Additional Options for an Application Client

If the application type is Application Client, the following options appear.

Application Name

The name of the application.

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.

Run Verifier

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.

Force Redeploy

If this option is selected, the application is redeployed if it is already deployed. 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.

Java Web Start

If this option is selected, Java Web Start access is permitted for an application client module. This option is disabled by default.

Description

A description of the application.

Additional Options for a Connector Module

If the application type is Connector Module, the following options appear.

Application Name

The name of the application.

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.

Status

If this option is selected, the application is enabled. This option is selected by default.

Run Verifier

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.

Force Redeploy

If this option is selected, the application is redeployed if it is already deployed. 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.

Description

A description of the application.

Additional Options for an EJB Jar

If the application type is EJB Jar, the following options appear.

Application Name

The name of the application.

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.

Status

If this option is selected, the application is enabled. This option is selected by default.

Availability

If the Enabled checkbox is selected, high-availability is enabled for web sessions and for stateful session bean (SFSB) checkpointing and potentially passivation. If set to false (default) all web session saving and SFSB checkpointing is disabled for the specified application, web application, or EJB module. If set to true, the specified application or 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.

Run Verifier

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.

Force Redeploy

If this option is selected, the application is redeployed if it is already deployed. 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.

Libraries

A comma-separated list of library JAR files specific to this module or application. Specifies an absolute or relative path. 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.

Description

A description of the application.

Additional Options for Applications of Type Other

If the application type is Other, the following options appear.

Application Name

The name of the application.

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.

Virtual Servers

The virtual servers associated with this application.

The Virtual Servers option appears if only the default server instance, server, exists. If clusters or other stand-alone 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.

Status

If this option is selected, the application is enabled. This option is selected by default.

Availability

If the Enabled checkbox is selected, high-availability is enabled for web sessions and for stateful session bean (SFSB) checkpointing and potentially passivation. If set to false (default) all web session saving and SFSB checkpointing is disabled for the specified application, web application, or EJB module. If set to true, the specified application or 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.

Precompile JSPs

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.

Run Verifier

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.

Force Redeploy

If this option is selected, the application is redeployed if it is already deployed. 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.

OSGI Type

If this option is selected, it specifies a hybrid OSGi/Java-EE module. This option only appears if the Type selected is Other.

Libraries

A comma-separated list of library JAR files specific to this module or application. Specifies an absolute or relative path. 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.

Description

A description of the application.

Related Tasks
Related asadmin Commands
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices




© 2015 - 2025 Weber Informatics LLC | Privacy Policy