Configuring for database session persistence
You can configure a database to collect session data for database session persistence.
About this task
To configure the session management facility for database session persistence, complete the following steps.
Procedure
- Create and configure a JDBC provider.
- Create a data source pointing to a database.
Use the JDBC provider that you defined: Resources > JDBC > JDBC Providers > JDBC_provider > Data Sources > New. The data source should be non-JTA, for example, non-XA enabled. Note the JNDI name of the data source.
Point to an existing database.
Point to the z/OS® DB2® database containing the DB2 table for session persistence.
Example configuration for session persistence:
Name Sessions JNDI Name jdbc/sessions Container managed persistence Selected Component-managed Authentication Alias CELL/jaasalias Container-managed Authentication Alias CELL/jaasalias - Verify that the correct database is listed under Resources > JDBC
Providers > JDBC_provider > Data Sources > datasource_name. If necessary, contact your database administrator to verify
the correct database name.
For example:
Database Name LOC1 (specify your system) Create a DB2 table in the z/OS DB2 database that will be used for session persistence.
Configure the DB2 table for session persistence.
- Go to the appropriate level of Session Management.
- Under Additional Properties, click Distributed Environment Settings
- Select and click Database.
- Specify the Data Source JNDI name from a previous step. The database user ID and password are case-sensitive.
- Specify the database user ID and password that is used to access the database and for table creation. When you created your data source, you might have specified a Container Managed Authentication Alias or a Component Managed Authentication Alias; however, these two settings are not used by the session manager for session persistence. The session manager uses the userId and password specified in this step for session persistence.
- Optional:
Append the schema name in the session User ID field if you want to have more than one instance of the session table.
The session manager uses the schema name to qualify the session table name for all database operations. If only the userid is specified without the schema name, the schema name defaults to NULL and therefore a table name with NULL as the schema name, for example, NULL.SESSIONS, is created. You can create multiple session tables with different schema names, other than NULL, and access them separately by modifying the user name to contain the appropriate schema name.
Retype the password for confirmation.
Configure a table space and page sizes for DB2 session databases.
- Switch to a multirow schema.
- Click OK.
- If you want to change the tuning parameters, click Custom Tuning Parameters under Additional properties.
- Click Apply.
- Click Save.
Subtopics
Switching to a multi-row schema
The multi-row schema configuration supports storing an unlimited amount of data that is only bounded by the database capacities in an application. The application can read individual fields instead of the whole record, which can help to improve performance by avoiding unnecessary Java object serialization. Configure the session management facility to store each attribute in a session object in its own row in the database by using the multi-row schema configuration.Configuring tablespace and page sizes for DB2 session databases
If you are using DB2 for session persistence, you can increase the page size to optimize performance for writing large amounts of data to the database. Page sizes of 8K, 16K, and 32K are supported.Creating a DB2 table for session persistence
Session data is collected and stored in a DB2 table. If you are using DB2 for session persistence, you must create and define a DB2 table that is associated with the application server.Configuring a table for session persistence
To configure a table for collecting session data, you must add the name of the table to the web container configuration properties.Creating a table for session persistence
You can use a database table to collect and store session data. If you are using a database table for session persistence, you must create and define a database table that is associated with the application server.Database settings
Use this page to specify the settings for database session support.


File name: tprs_cnfp.html