WebSphere eXtreme Scale Administration Guide > Configure WebSphere eXtreme Scale > Cache integration > HTTP session management
Servlet context initialization parameters
The following list of servlet context initialization parameters can be specified in the properties file as required in the script or ANT-based splicing methods.
Parameters
- persistenceMechanism
- String value that defines how the session is stored in eXtreme Scale. Indicate one of the following values:
ObjectGridStore Each session attribute is stored as a different entry in the eXtreme Scale table. ObjectGridAtomicSessionStore The entire session is stored as a single entry in the eXtreme Scale table.
- objectGridName
- String value that defines the name of the ObjectGrid that will contain the session data for this Web application. This should match the ObjectGrid name in the XML files provided with eXtreme Scale. The default is "session".
- catalogHostPort
- Catalog server connection information; the value needs to be of the form...
host:port,<host:port>This list can be arbitrarily long and the first viable address is used. This property should only be used for the remote, network-attached eXtreme Scale scenario.
- defaultSessionTimeout
- An integer value that defines the amount of time in minutes that a session can be inactive (for example, not accessed from a servlet) before the session is invalidated and removed from the system. The default is 30 minutes.
- sessionIDLength
- An integer value that defines the length of the String identifiers that are created for HTTP sessions. The default is 23.
- shareSessionsAcrossWebApps
- String value of either true or false. The default is false. Per the servlet specification, HTTP sessions cannot be shared across Web applications. An extension to the servlet specification is provided to allow this sharing.
- cookieName
- String value that defines the name of the cookie for this Web application. The default is JSESSIONID.
To use a unique cookie name, add this property to the splicer.properties file.
- useURLEncoding
- String value of either true or false, with false as the default. The true setting informs the filter that cookies are not being used, and the URL request provides the session id and eXtreme Scale SessionHandle. The URI can be retrieved by calling HttpServletResponse.encodeURL(String uri).
Parent topic
HTTP session management
Related concepts
Related tasks
Configure the HTTP session manager with WebSphere Application Server
Configure the HTTP session manager with WebSphere Application Server Community Edition