IBM Integration Bus, Version 10.0.0.17 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Configuring the embedded global cache by using commands

You can customize the default global cache topology to use a specific port range and listener host, or you can turn off the default topology and specify your own integration server properties. Multiple integration nodes can share a cache by using a cache policy file.

Before you begin

For more information about the default global cache topology, see Data caching overview.

About this task

If you are using the default global cache topology, you can use IBM Integration Bus commands to set a port range and listener host for the cache manager to use, and to report the properties for the cache manager. If you want multiple integration nodes to share data in the cache, or to configure a cache with enhanced availability, you can use commands to specify a policy file. For more information, see Integration node properties.

Use IBM Integration Bus commands to turn off the default topology and set integration server properties explicitly (see Integration server properties).

You can also use the mqsicacheadmin command to clear data from a map. For more information, see mqsicacheadmin command.

Integration node properties

Procedure

Integration server properties

Before you begin

Before you can set properties explicitly for an integration server, you must set the cache policy property to none for the integration node. You can set the policy by using the mqsicreatebroker, mqsichangebroker, or mqsichangeproperties command, as described in Integration node properties. The integration server properties that were set most recently by the integration node-level policy are retained as a starting point for customization.

About this task

If you set the cache policy property to none, you must set properties on the integration servers. If you stop the integration server that contains the only catalog server, the cache becomes unavailable. Therefore, if you switch off the default topology, ensure that you place the catalog server appropriately. If you restart the integration server that hosts the catalog server, it can no longer communicate with the container servers in other integration servers. Although these container servers are still running, they are no longer part of the cache, and your data is lost. Therefore, you must also restart the integration servers that host the container servers. Alternatively, restart the integration node to reset all cache components.

To use the new properties that you set, restart the integration server.

Procedure


bn23781_.htm | Last updated 2019-07-13 08:13:53