Configuring for database session persistence

You can configure a database to collect session data for database session persistence.

1. Create and configure a JDBC provider.
2. 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

3. 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)

4. Create a DB2 table in the z/OS DB2 database that will be used for session persistence.
5. Configure the DB2 table for session persistence.
6. Go to the appropriate level of Session Management.
7. Under Additional Properties, click Distributed Environment Settings
8. Select and click Database.
9. Specify the Data Source JNDI name from a previous step.
   The database user ID and password are case-sensitive.
10. 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.
11. 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.

12. Retype the password for confirmation.
13. Configure a table space and page sizes for DB2 session databases.
14. Switch to a multirow schema.
15. Click OK.
16. If you want to change the tuning parameters, click Custom Tuning Parameters under Additional properties.
17. Click Apply.
18. Click Save.