en.help.task-webcontaineravailability.html Maven / Gradle / Ivy
Show all versions of console-web-plugin Show documentation
To Configure Availability Settings for the Web Container
-
In the navigation tree, expand the Configuration node.
-
Select the configuration that you are changing.
-
Under the configuration's node, select the Availability Service node.
The Availability Service page opens.
-
On the Availability Service page, click the Web Container Availability tab.
The Web Container Availability page opens.
-
In the Availability Service field, check the Enabled box to enable availability for the web container.
To disable availability, remove the check from the Availability Service Enabled box.
-
From the Persistence Type drop-down list, select the persistence mechanism.
-
If Availability Service Enabled is not checked, select one of the following:
-
memory for no session persistence
-
file for session persistence based on the file system that is not highly available
-
If Availability Service Enabled is checked, select replicated for session persistence based on cluster failover that is highly available.
-
From the Persistence Frequency drop-down list, select the frequency at which the HTTP session is stored:
-
web-method — The session state is stored at the end of each web request prior to sending a response back to the client. This mode provides the best guarantee that the session state is fully updated in case of failure. This is the default.
Persistence Frequency is only applicable if the Persistence Type is replicated.
-
From the Persistence Scope drop-down list, select the scope of HTTP session changes required for storage to occur:
-
session — The entire session state is stored every time. This mode provides the best guarantee that your session data is correctly stored for any distributable web application.
-
modified-session — The entire session state is stored if it has been modified. A session is considered to have been modified if HttpSession.setAttribute() or HttpSession.removeAttribute() was called. You must guarantee that setAttribute() is called every time an attribute is changed. This is not a Java EE specification requirement, but it is required for this mode to work properly.
-
modified-attribute — Only modified session attributes are stored. For this mode to work properly, you must follow these guidelines:
-
Call setAttribute() every time the session state is modified.
-
Make sure there are no cross-references between attributes. The object graph under each distinct attribute key is serialized and stored separately. If there are any object cross references between the objects under each separate key, they are not serialized and deserialized correctly.
-
Distribute the session state across multiple attributes, or at least between a read-only attribute and a modifiable attribute.
Persistence Scope is only applicable if the Persistence Type is replicated.
-
In the Single-Sign-On State field, check the Enabled box to make the single sign-on state available for failover.
To make the single sign-on state unavailable for failover, remove the check from the Single-Sign-On State Enabled box.
-
To restore the default values of all the settings, click the Load Defaults button.
-
In the Additional Properties section, specify additional properties.
The GlassFish Server does not define any additional properties for web container availability.
-
To add a property, click the Add Property button. In the blank row that appears, type the property name in the Name field, and type the property value in the Value field.
-
To modify a property, edit that property's Value field.
-
To delete a property, select the checkbox to the left of the Name field of the property that you are deleting, then click the Delete Properties button.
-
Click Save.
See Also
-
-
-
-
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices