InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.11: Administering HTTP session support (overview) >
6.6.11.5: Procedure for configuring persistent session support

6.6.11.5: Procedure for configuring persistent session support

The default application server configuration file for Advanced Single Server Edition assumes that the name of the database for session persistence will be "Session". The administrator must either create the database or the update the configuration to reference a different database.

To configure Session Manager for persistent sessions:

  1. Create a JDBC Provider.
  2. Create a data source pointing to existing database, using the JDBC provider that you created. Note the JNDI name of the data source.
  3. Configure the Session Manager and save your changes:
    1. Enable session persistence.
    2. Specify the JNDI name from the previous step.
    3. Specify the database user ID and password for accessing the database.

The Session Manager provides a pre-configured data source for session persistence, appropriately named the Session Peristence data source. When using it, ensure that:

  • The Session database referenced by the application server configuration file exists. Or, change the configuration to point to a different existing database.
  • The JDBC provider for the data source is configured properly. That is, it must point to the location of db2java.zip (in the case of DB2).
  • The correct user ID and password are specified for accessing the database. By default db2admin is specified as both the user ID and password in the Session Manager. If you are using a different ID or password, specify it in the Session Manager configuration.
Go to previous article: Updating session management settings with the Web console Go to next article: Configuring user profile support

 

 
Go to previous article: Updating session management settings with the Web console Go to next article: Configuring user profile support