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

  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 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. The database user ID and password are case-sensitive.
  9. Specify the Data Source JNDI name from a previous step.
  10. Specify the database user ID and password for accessing the database. 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.

    Use the following format to append the schema name in the session User ID field:: userid::schemaName.

    There are multiple ways to append the schema name in the session User ID field:
    1. Use the Toolbox provider libraries custom property, that is held in the data source used for HTTP session persistence, to define the collection name.

      The collection name you specify is limited to ten characters. How to specify a collection name depends on which JDBC Provider you use.

      For example, to specify a collection named MYSESSN, in the administrative console, click Data Sources > datasource_name > Custom Properties, and then enter one of the following values for the databaseName custom property:
      • *LOCAL for DB2 UDB for iSeries Toolbox drivers
      • *LOCAL/MYSESSN for DB2 UDB for iSeries (native JDBC drivers)
      If you are using the DB2 UDB for iSeries Toolbox drivers, you must also specify MYSESSN for the libraries property.
    2. Use the default collection name.

      By default, the servlet session data is stored in a collection named QEJBAS5SN. This default collection is used if no collection name is specified as a Custom Property of the data source used for HTTP session persistence. It is not recommended that you use this default collection, especially in cases where you are running multiple instances of WebSphere Application Server on your server.

  12. Switch to a multirow schema.
  13. Click OK.
  14. If you want to change the tuning parameters, click Custom Tuning Parameters under Additional properties and select a setting or customize a setting.
  15. Click Apply.
  16. Click Save.



In this information ...


Related concepts
Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tpercnfp
File name: tprs_cnfp.html