WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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.

Before you start:

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

Quick views are provided in WebSphere Message Broker Explorer to view the properties for a broker or an execution group. For example, you can see if an execution group is hosting a catalog server or container server. In the Navigator view, click a broker or execution group, and see the quick views in the Content view.

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

To set the cache policy and port range by using WebSphere Message Broker Explorer, complete the following steps.
  1. Open WebSphere Message Broker Explorer.
  2. Right-click the broker for which you want to set properties, then click Properties. The broker properties are displayed.
  3. Click Global Cache. The global cache properties are displayed.
  4. Set the cache policy to none, default, disabled, or the fully qualified name of an XML policy file.
    • If you set this property to default, the default global cache topology is used.
    • If you set this parameter to none, you must set the execution group properties explicitly.
    • If you set this parameter to disabled, all cache components in the broker are disabled. The cache is disabled by default.
    • If you specify the fully qualified name of a policy file, the brokers listed in the policy file are configured to share the data in the global cache. The path must be absolute, not relative. For more information, see Configuring the global cache for multiple brokers.
  5. Set the port range to generate or to a specific range of ports.
    • If you specify a range of ports, the value of this parameter must be in the format xxxx-yyyy, and the range must contain at least 20 ports.
    • If you specify generate, the brokers generates a range of ports that are not being used by another brokers on that computer. The broker chooses a range that starts from 2800. If, for example, another broker is using ports 2800 to 2819, the broker generates a range from 2820 to 2839.
  6. Set the host name or IP address that the cache components use to listen.
  7. To save your settings, click OK.
  8. To use the new settings, restart the broker.

Execution group properties

Before you start:
  1. 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.
  2. For the change in policy to take effect, you must restart the broker.
One execution group in the broker hosts a catalog server, and up to three other execution groups in that broker host container servers. If you stop the execution group 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 execution group that hosts the catalog server, it can no longer communicate with the container servers in other execution groups. 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 execution groups that host the container servers. Alternatively, restart the broker to reset all cache components.

To set cache manager properties for an execution group by using WebSphere Message Broker Explorer, complete the following steps.

  1. Open WebSphere Message Broker Explorer.
  2. In the Navigator view, expand the Brokers folder, then expand the broker that contains the execution group for which you want to set properties.
  3. Right-click the execution group, then click Properties. The broker properties are displayed.
  4. Click Global Cache. The global cache properties are displayed.
  5. Set the properties as appropriate. For a description of the properties that you can set, see Parameter values for the cachemanager component.
  6. To save your settings, click OK.
  7. 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.)
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:19


Task topicTask topic | Version 8.0.0.7 | bn23782_