The Applications page opens.
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 Oracle GlassFish Server 3.1 Application Deployment Guide.
The Edit Application page opens.
By default, the status of an application is Enabled as soon as it is deployed unless the application is deployed to a cluster, in which case the application is Disabled by default.
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.
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.
In the URL of the web application, the context root immediately follows the port number (http://host:port/context-root/...). Ensure that the context root starts with a forward slash, for example, /hello.
If you select Enable Availability for the application, you must also enable availability at all higher levels; such as the named configuration, the web container, or EJB container.