When using this option to replicate session data, EAServer stores all session data in a remote database, connecting through the predefined JDBC connection cache ServletPersistenceCache. All servers in the cluster share the same database. Sybase recommends that you configure this cache to connect to an enterprise-grade database server. The database cannot be shared between servers that are not running in the same EAServer cluster.
The sample ServletPersistenceCache properties
must be changed
As preconfigured, the ServletPersistenceCache connects to
the sample database that is included with the EAServer sample applications.
This sample uses the evaluation version of Adaptive Server Anywhere,
which does not allow connections from multiple hosts. You must use
another database that allows connections from multiple hosts, and
supports the number of connections required by your cluster.
Configuring persistent session storage
These steps must be performed in EAServer Manager, while connected to the primary server for your EAServer cluster:
Select the Distributed checkbox on the General tab in the Web Application Properties dialog box.
Install the Web application to one or more logical servers that are part of the cluster.
Configure the properties of the connection cache named ServletPersistenceCache to connect to the database that you use for persistent session storage. This cache must use JDBC and have cache-by-name access allowed. See Chapter 4, “Database Access,” for instructions.
Make sure the ServletPersistenceCache cache is installed in each logical server where the Web application is installed.
If using a database other than Sybase Adaptive Server Enterprise or Adaptive Server Anywhere, create a table as described in “Creating the database table”.
Synchronize the EAServer cluster to propagate the configuration changes to other servers in the cluster. See “Synchronization” for more information.
