See information about the latest product version
Configuring the embedded global cache by using WebSphere Message Broker Explorer
You can set cache manager properties at broker level and execution group level by using WebSphere® Message Broker Explorer.
For more information about the default global cache topology, see Data caching overview.
If you are using the default global cache topology, you can use WebSphere Message Broker Explorer to set a port range for the cache manager to use, and to specify a listener host for the cache components to use (see Broker properties).
You can also use WebSphere Message Broker Explorer to turn off the default topology and set execution group properties explicitly (see Execution group properties), or disable cache components. If you want to share the data in the global cache between multiple brokers, or configure the cache for enhanced availability, you can use WebSphere Message Broker Explorer to specify an XML policy file.
Broker properties
Execution group properties
- Before you can set properties explicitly for an execution group, you must set the cache policy property to none for the broker, as described in Broker properties. The execution group properties that were set most recently by the broker-level policy are retained as a starting point for customization.
- For the change in policy to take effect, you must restart the broker.
To set cache manager properties for an execution group by using WebSphere Message Broker Explorer, complete the following steps.
- Open WebSphere Message Broker Explorer.
- In the Navigator view, expand the Brokers folder, then expand the broker that contains the execution group for which you want to set properties.
- Right-click the execution group, then click Properties. The broker properties are displayed.
- Click Global Cache. The global cache properties are displayed.
- Set the properties as appropriate. For a description of the properties that you can set, see Parameter values for the cachemanager component.
- To save your settings, click OK.
- To use the new settings, restart the execution group. (Remember that if you stop and restart the execution group that contains the catalog server, the cache becomes unavailable.)