Administration guide > Configure the deployment environment > Configuring cache integration > Configuring HTTP session managers



Configure HTTP session manager with WebSphere Portal

You can persist HTTP sessions from WebSphere Portal into a data grid in WebSphere eXtreme Scale.


Before you begin

Your WebSphere eXtreme Scale and WebSphere Portal environments must meet the following requirements:

Introducing WebSphere eXtreme Scale into a WebSphere Portal environment can be beneficial in the following scenarios:

Although the following scenarios introduce benefits, increased processor usage in the WebSphere Portal tier can result from introducing WebSphere eXtreme Scale into the environment.


Procedure

  1. Splice the wps WebSphere Portal application and any custom portlets to use the WebSphere eXtreme Scale session manager.

    You can splice the application by configuring HTTP session management when you deploy the application, or you can use custom properties to automatically splice the applications. See Configure the HTTP session manager with WAS for more information about splicing the application.

  2. If you are using a remote scenario where container servers run in different processes than the servlets, set the timeout.resume.session custom property in the WebSphere Application Server administrative console. By default, WebSphere Portal verifies the HTTP session ID at various times during a request. When you are running a WebSphere eXtreme Scale remote scenario and the number of HTTP sessions is higher than the configured sessionTableSize parameter, the session ID can change. For more information about the sessionTableSize attribute, see Servlet context initialization parameters. You must configure the timeout.resume.session custom property within the WP_ConfigService resource environment provider to prevent users from needing to log in again after the session times out.

    1. In the WebSphere Application Server administrative console, click Resources > Resource Environment > Resource Environment Providers > WP_ConfigService > Custom Properites > New.

    2. Create a custom property with a name of timeout.resume.session and a value of true.

  3. If you are using the remote scenario, where the container servers are outside of the WebSphere Application Server, explicitly start remote eXtreme Scale containers for remote HTTP session persistence scenarios. Start the containers with the XS/ObjectGrid/session/samples/objectGridStandAlone.xml and objectGridDeploymentStandAlone.xml configuration files. For example, you might use the following command:

    startOgServer.sh xsContainer1 -catalogServiceEndPoints
    <host>:<port> 
    -objectgridFile XS/ObjectGrid/session/samples/objectGridStandAlone.xml -deploymentPolicyFile 
    XS/ObjectGrid/session/samples/objectGridDeploymentStandAlone.xml
    

    For more information about starting container servers, see Start container processes. If you are using an embedded scenario, see Configure container servers in WAS for more information about configuring and starting container servers.

  4. Restart the WebSphere Portal servers. See WebSphere Portal v7: Starting and stopping servers, deployment managers, and node agents for more information.


Results

You can access the WebSphere Portal Server, and HTTP session data for the configured custom portlets is persisted to the data grid.


Parent topic:

Configure HTTP session managers


Related tasks

Configure the HTTP session manager with WAS

Configure the HTTP session manager for various application servers

Related reference

XML files for HTTP session manager configuration

Servlet context initialization parameters

WebSphere Portal v7.0: Configuring user session persistance