Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Configuring Ehcache on Integration Server | Configuring a Distributed Cache
 
Configuring a Distributed Cache
 
Configuring tc-config.xml on the Terracotta Server Array
Considerations for Configuring a Distributed Cache
Cache-Wide and Client-Specific Parameters for a Distributed Cache
The Rejoin Behavior of a Distributed Cache
The Nonstop Behavior of a Distributed Cache
About the Maximum Entries in Cache Value
Perform the following general steps to create a distributed cache. A distributed cache resides on a Terracotta Server Array and can be shared with other Integration Servers. Integration Server keeps a portion of the distributed cache in its on-heap memory so that it does not have to access the Terracotta Server Array every time it needs to fetch data from the cache. When you configure a distributed cache, you specify the number of elements that you want the Integration Server to maintain locally in the on-heap portion of the cache. For more information about distributed caches, see Terracotta Server Array .
Step
Description
1
If you have not already installed and configured your Terracotta Server Array, do this first. For procedures, see the product documentation for the Terracotta Server Array.
Note:
The Terracotta Server Array must be running a version of Terracotta that is compatible with the Terracotta client libraries installed on your Integration Server. To check which versions of the Terracotta Server Array are compatible with your Integration Server, see the Terracotta Compatibility with other Software AG Products on the Software AG documentation website at http://documentation.softwareag.com.
2
If you have not done so already, edit the tc-config file on the Terracotta Server Array and add the parameters that Integration Server requires. For procedures, see Configuring tc-config.xml on the Terracotta Server Array .
3
4
Verify that Integration Server is equipped with a license to use a Terracotta Server Array. For procedures, see Installing, Viewing, and Changing the Terracotta License.
5
Decide how much memory you will use for the on-heap portion of the cache on Integration Server and adjust the Java heap size if necessary. For information about changing the heap size used by Integration Server, see Changing the JVM Heap Size Used by Integration Server .
Note:
The size of the on-heap portion of a distributed cache must be the same on all Integration Servers that use the cache.
6
If the cache manager to which you want to add the cache does not already exist, create it. For information about creating a cache manager, see Creating a Cache Manager.
Note:
Be sure that the cache manager that you are using is configured to use the Terracotta Server Array.
7
Create the cache using the procedure in Creating a Cache. When you create the cache, be sure to do the following:
*Enable the Distributed setting in the Distributed Cache Configuration section of the page.
*In the Maximum Elements in Memory field, specify the number of elements that you want to maintain in the on-heap memory at the Integration Server.
Note:
Although Integration Server permits you to set Maximum Elements in Memory 0, which indicates that the number of elements is restricted only by the availability of resources, Software AG strongly recommends that you always specify an upper limit. Unlimited caches grow indefinitely and can cause performance problems or system failures if they exhaust the available resources on the machine.
*In the Maximum Entries in Cache field, specify the maximum size (in number of elements) to which this cache can grow on the Terracotta Server Array.
8
Verify that the parameters for the cache are set as you want them and enable the cache as described in Enabling a Cache.
If this is the first Integration Server on which you have created the distributed cache, the Integration Server creates the distributed cache on the Terracotta Server Array during this step.
9
If other Integration Servers will use this distributed cache, repeat steps 4 through 8 on each of them.
Note:
Instead of manually specifying the new cache on each of the other Integration Servers in step 7, you can optionally create the cache by copying the cache manager configuration file from this Integration Server to the others. You can do this by 1) using webMethods Deployer to deploy the cache manager from this Integration Server to the others or 2) manually copying the cache manager configuration file from this Integration Server to the others. For information about using webMethods Deployer, see the webMethods Deployer User’s Guide. For information about copying a cache manager configuration file to another Integration Server, see Adding a Cache Manager Configuration File to Integration Server .