Switching to a multirow schema

Why and when to perform this task

By default, a single session maps to a single row in the database table used to hold sessions. With this setup, there are hard limits to the amount of user-defined, application-specific data that WebSphere Application Server can access.

Steps for this task

  1. Modify the Session Management facility properties to switch from single to multirow schema.
  2. Manually drop and recreate the database table or delete all the rows in the database table that the product uses to maintain HttpSession objects.

    See the DB2 UDB for OS/390 and z/OS V7 Administration Guide for a description of how to drop a DB2 database table.

    Creating a DB2 table for session persistence describes how to create a new DB2 database table.


Related tasks
Tuning session management
Configuring for database session persistence
Related reference
Multirow schema considerations



Searchable topic ID:   tperswsk
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tprs_swsk.html

Library | Support | Terms of Use | Feedback