If your application uses stateful components such as EJB stateful session beans, you must configure a mechanism for EAServer to replicate state data between servers in the cluster. You can use a remote database server or in-memory replication. For more information, see Chapter 28, “Configuring Persistence for Stateful Session Components,” in the EAServer Programmer’s Guide.
If using in-memory replication, EAServer replicates state data between mirror pairs, that is, a pair of servers configured to share the same user session. In-memory replication can perform better than using a database, but requires more memory on each server. Configure the cache size and session timeout to control how much memory the cache uses. For instructions, see “Requirements for in-memory stateful failover” in Chapter 29, “Configuring Persistence Mechanisms,” in the EAServer Programmer’s Guide:
If using database replication, all servers in the cluster store session data in a remote database. This mechanism can perform slower than in-memory replication, but requires less memory. Also, EAServer can share a client’s session data on more than two servers. If using this technique:
Tune the connection cache settings as described in “Connection cache settings”.
Make sure the table used is indexed. For information on creating the database table, see “Table schema for binary storage” in Chapter 29, “Configuring Persistence Mechanisms,” in the EAServer Programmer’s Guide.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
