Database Session Persistence
1.0

This feature enables persistence of HTTP sessions to a datasource using JDBC. Persisting HTTP session data to a database allows recovery of the data after a server restart or unexpected server failure. Failover of HTTP sessions can be achieved by configuring multiple servers to persist data to the same location

Enabling this feature

To enable the Database Session Persistence 1.0 feature, add the following element declaration into your server.xml file, inside the featureManager element:

<feature>sessionDatabase-1.0</feature>

Examples

Minimum configuration to persist session data to a database

The following example shows the minimum configuration for database persistence:

<fileset id="DerbyFiles" includes="*.jar" dir="derby/client"/>
<library id="DerbyLib" filesetRef="DerbyFiles"/>
<jdbcDriver id="DerbyDriver" libraryRef="DerbyLib"/>
<dataSource id="SessionDS" jdbcDriverRef="DerbyDriver">
    <properties.derby.client user="user1" password="password1"
                             databaseName="SessionDB"
                             createDatabase="create"/>
</dataSource>

<httpSessionDatabase id="SessionDB" dataSourceRef="SessionDS"/>

The dataSourceRef attribute identifies the dataSource element with the id attribute SessionDS, which the session manager uses to persist HTTP session data. The jdbcDriverRef attribute points to the jdbcDriver element with the id attribute DerbyDriver, which connects to the dataSource.

Feature configuration elements

Features that this feature enables

Supported Java versions

  • JavaSE-1.8

  • JavaSE-11.0

  • JavaSE-17.0

  • JavaSE-21.0

  • JavaSE-25.0

  • JavaSE-26.0

Developing a feature that depends on this feature

If you are developing a feature that depends on this feature, include the following item in the Subsystem-Content header in your feature manifest file.

com.ibm.websphere.appserver.sessionDatabase-1.0; type="osgi.subsystem.feature"