EAServer Manager enhancements  FIPS and TLS support

Chapter 2: New features in EAServer 5.2

In-memory mirror caching

EAServer 5.2 provides in-memory mirror caching for objects saved in the EAServer object cache. This allows objects to be accessed by any server in a cluster, and offers better performance than persistent database caching. For a new server that joins a mirror group or cluster, this feature provides in-memory synchronization. You can use in-memory mirror caching for stateful session components and HTTP sessions.

Mirror caching guarantees that:

To use mirror caching feature, the message service must be active. The mirror object cache uses the following message queues to send and receive messages:

StepsConfiguring EAServer to use mirror caching for HTTP sessions

  1. Configure the server in a cluster, and designate mirror pairs:

  2. In the Web Application Properties dialog box:

    1. On the General tab, check the Distributable option.

    2. On the Advanced tab, add the com.sybase.jaguar.webapplication.distribute.type property, and set the value to “mirror.”

StepsConfiguring EAServer to use mirror caching for stateful session components

  1. Configure the server in a cluster, and designate mirror pairs:

  2. In the Component Properties dialog box, set the following properties before you generate skeletons:

    1. On the Persistence tab, set Persistence to “Java Serialization” and set the Storage Component to “CtsComponents/JavaMirrorStorage.”

    2. On the Transactions tab, select Automatic Failover.

    3. On the Instances tab, unselect Transient.

“Configuring the object cache” in Chapter 4, “EJB CMP Tuning,” in the EAServer Performance and Tuning Guide describes how to enable and configure the object cache. The CtsComponents/ObjectCache component, which previously provided the default implementation of the cache manager, has been replaced by CtsComponents/JavaObjectCache.





Copyright © 2005. Sybase Inc. All rights reserved. FIPS and TLS support