Creating session data grids

You can create data grids to store HTTP sessions from your Java or .NET applications.

About this task

For some configurations, you must create a session data grid in the user interface before you continue the configuration. If you are configuring WebSphere® Application Server session persistence, you can use an existing data grid or create a new data grid when you deploy your session application.

Procedure

Optional: Create a session data grid In the user interface, click Data Grid > Session. Click the add icon (

) and specify a name for the data grid that you want to create. The following characters cannot be used in the name of the data grid: ^ . \\ / , # $ @ : ; \ * ? < > | = + & % [ ] " ".

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 HTTP session manager with WebSphere Portal
You can persist HTTP sessions from WebSphere Portal into a data grid.
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.
Migrating a WebSphere Application Server memory-to-memory replication or database session to use WebSphere eXtreme Scale session management
You can migrate any previously set memory-to-memory replication session or database session to use WebSphere eXtreme Scale session management.
Configuring the ASP.NET session state store provider
You can store session state from your ASP.NET applications in a data grid.
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.
Splicing a session data grid application with the addObjectGridFilter script
Use the addObjectGridFilter command-line script to splice an application with filter declarations and configuration in the form of servlet context initialization parameters.
Editing the splicer.properties file
After you have configured the appliance to store HTTP sessions, you can edit other aspects of the HTTP session configuration with the splicer.properties file.
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.

Parent topic: Configuring data grids