Configuring the global cache for multiple integration nodes
Configure one or more integration nodes to share data in the global cache by using a cache policy file. Use a cache policy to enhance the availability of the cache by configuring an integration node to host two catalog servers. Also use a cache policy file to host container servers in a multi-instance integration node for high availability.
Before you begin
For more information about the default global cache topology, see Data caching overview.
About this task
- A single integration node that hosts two catalog servers; if one catalog server fails, the global cache switches to the other one.
- Two integration nodes that share a catalog server that is hosted by the first integration node.
- Two integration nodes that each host a catalog server; if one catalog server fails, the global cache switches to the catalog server in the other integration node.
- Three integration nodes in a high availability scenario. Two
integration nodes each host a catalog server, and a multi-instance
integration node hosts two container servers. If the active instance of the
multi-instance integration node fails, the global cache switches to the
container servers in the standby instance.
For specific instructions to configure the global cache for multi-instance integration nodes, see Configuring the global cache for multi-instance integration nodes.
Two of the sample policies configure the cache to contain two catalog servers. This configuration means that if one of the catalog servers is stopped, the other catalog server is used, and no cache data is lost. However, having more than one catalog server can affect startup time after the integration node is started, until the cache is available. If you have more than one catalog server, you must start at least two of them for the cache to be available. When you configure a cache across multiple integration nodes with multiple catalog servers, if you need to start one integration node before the others then you can configure this integration node to host two catalog servers.
When you set the integration node-level property to a policy file, the policy file is validated against an XML schema. A copy of the XML schema file is provided at install_dir/server/cachesupport/schema.
Do not edit the sample policy files in their original location; copy them to your own file system first. The original sample policy files might be replaced when you apply maintenance to IBM Integration Bus.
You cannot use the policy file to fix specific cache roles to specific integration servers. Instead, you must use the none policy; see Embedded global cache.
The following steps describe how to configure the global cache for multiple integration node.
Procedure
Results
mqsicacheadmin integrationNodeName -c showPlacement
You
can also use the mqsicacheadmin command
to show cache components in a multi-integration node cache. For example, the listHosts command
shows the host names, number of hosts, and number of catalogs in the
cache:mqsicacheadmin integrationNodeName -c listHosts