You can create data grids to store HTTP sessions from your
Java or .NET applications.
Configuring WebSphere Application Server HTTP session persistence to a data grid Configure your WebSphere® Application Server application to use the appliance
for session management. You can either select the appliance when you
are installing a new application, or you can update your existing
application or server settings to use the appliance.
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.
Configuring the HTTP session manager for various application servers WebSphere eXtreme Scale Client 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 Client session
replication manager and generic embedded ObjectGrid container startup
for various application servers such as Tomcat.
Displaying HTTP session sizes
You can use the xscmd utility to display the size of sessions in your Java application.
Displaying session sizes can be useful to troubleshoot problems in
your data grid.
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.