The HTTP session manager provides
session replication capabilities
for an associated application. The session manager works with the
Web container to create and manage the life cycles of HTTP sessions
that are associated with the application.
Configuring the HTTP session manager with WebSphere Application Server
While WebSphere Application Server provides
session management function, the performance degrades as the number
of requests increases. WebSphere eXtreme Scale comes bundled with a session management implementation that
provides session replication, high availability, better scalability,
and more robust configuration options.
Using WebSphere eXtreme Scale for SIP session management
You can use WebSphere eXtreme Scale as
a Session Initiation Protocol (SIP) replication mechanism as a reliable
alternative to the data replication service (DRS) for SIP session
replication.
Configuring the HTTP session manager for various application servers WebSphere eXtreme Scale is bundled with a session management implementation
that overrides the default session manager for a web container. This
implementation provides session replication, high availability, better
scalability, and configuration options. You can enable the WebSphere eXtreme Scale session replication manager and generic embedded ObjectGrid
container startup for various application servers such as Tomcat.
XML files for HTTP session manager configuration
When you start a container server that stores HTTP session
data, you can either use the default XML files or you can specify
customized XML files. These files create specific ObjectGrid names,
number of replicas, and so on.
Servlet context initialization parameters
The following list of
servlet context initialization parameters
can be specified in the splicer properties file as required in the
chosen splicing method.
splicer.properties file
The splicer.properties file contains
all of the configuration options for configuring a servlet-filter-based
session manager.