Configuring for database session persistence

Why and when to perform this task

To configure the session management facility for database session persistence, complete the following:

Steps for this task

  1. Creating and configuring a JDBC provider using the administrative console
  2. Create a data source pointing to the z/OS DB2 database containing the DB2 table for session persistence, using the JDBC provider that you defined.
    Resources > 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.

    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 for the value of the databaseName property under Data Sources > datasource_name > Custom Properties.
    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. Configuring a DB2 table for session persistence.
  6. Go to the appropriate level of Session Management.
  7. Click Distributed Environment Settings
  8. Select and click Database.
  9. Specify the Data Source JNDI name from step 3.
  10. Specify the database user ID and password for accessing the database.
  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 pass the 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 pass the schema name: userid::schemaName.
  12. Switch to a multirow schema.
  13. Click OK.
  14. If you want to change the tuning parameters, click Custom Tuning Parameters and select a setting or customize one.
  15. Click Apply.
  16. Click Save.

Related concepts
Distributed sessions
Sessions
Related reference
Database settings
Problems creating or using HTTP sessions
Multirow schema considerations



Searchable topic ID:   tpercnfp
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_cnfp.html

Library | Support | Terms of Use | Feedback