See information about the latest product version
Data caching overview
WebSphere® eXtreme Scale provides WebSphere Message Broker with data caching capability.
A global cache is a repository for data that you want to reuse. For example, you can use a global cache in WebSphere MQ message flows to store correlation information for use beyond a specific node, instance of a message flow, execution group, or broker. The cache facilitates sharing of data across processes (both in the same broker, and across brokers) and eliminates the need for an alternative solution, such as a database. You can use one node to store data in the global cache, then a second node (in the same message flow or a separate flow), can retrieve that data from the global cache.
You can use a message flow node to interact with the global cache. Interactions with the cache happen outside the message flow transaction, and are committed immediately. If an exception is thrown downstream of the node that interacts with the cache, the cache interactions are not rolled back.
For an example of how to use the global cache, see the Coordinated Request Reply sample. You can view information about samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit or the online information center. You can run samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit.
You can use the global cache that is supplied with WebSphere Message Broker, and you can configure WebSphere Message Broker to connect to an external WebSphere eXtreme Scale grid. You can work with multiple remote grids, and the embedded grid, at the same time.
Interacting with the global cache or external grid
You can interact with the global cache or external grid by using a JavaCompute node. The node can put data into a map, retrieve data, and create a map if one does not exist. For more information, see Accessing the global cache with a JavaCompute node.
Monitoring the global cache or external grid
- The activity log
- Resource statistics
For more information, see Monitoring the global cache.