Use the Edit Application page to modify an existing application.
The Edit Application page contains some or all of the following options, depending on the application type.
Read-only field that displays the name of the application that you are editing.
The 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 Application Deployment Guide.
If the Enabled checkbox is selected, the application is enabled. This option is selected by default.
For a web application, specifies 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
.
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.
This option appears if clusters or standalone server instances aside from the default server instance (server
) exist.
The virtual servers associated with this application.
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.
(For some application types) If the Enabled checkbox is selected, the application uses Java Web Start software. Java Web Start provides a browser-independent way to deploy Java applications to run in a dedicated Java Virtual Machine.
A short description of the application.
The location of the deployed application. This is a read-only field.
The deployment order of the application.
Applications with a lower number are loaded first at server startup. An application with a deployment order of 102 is loaded before an application with a deployment order of 110. If a deployment order is not specified at the time an application is deployed, the default deployment order of 100 is assigned. If two applications have the same deployment order, the application that was deployed first is loaded first. Specifying a deployment order is useful if the application has dependencies and must be loaded in a certain order.
The library JAR files required by the application. This is a read-only field.
Table that displays the names of the application's modules and their engines. For a web service endpoint, you can select View Endpoint to display the Web Service Endpoint Information page. For an application client, you can select Launch to display the Application Client Launch page or Download Client Stubs to download the client stubs.