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

See information about the latest product version

Monitoring the global cache

You can use the mqsicacheadmin command, resource statistics, and the activity log to monitor the global cache. You can use resource statistics and the activity log to monitor external grids.

The following tools provide information about the global cache and how it is performing.

mqsicacheadmin command: The mqsicacheadmin command provides information about the global cache that is embedded in a broker. For example, you can find out the size of a map and list the hosts that are participating in the cache. You can also use this command to clear data from a map. See Running the mqsicacheadmin command.
Activity log: Activity logs provide a high-level overview of how IBM® Integration Bus interacts with external resources, therefore helping you to understand what your message flows are doing. See Viewing the activity log.
Resource statistics: Resource statistics are collected by a broker to record performance and operating details of resources that are used by integration servers. See Collecting resource statistics.

Running the mqsicacheadmin command

To use the command to find information about the global cache that is embedded in a broker, complete the following steps.

Before you run the mqsicacheadmin command, ensure that the broker is running and that the global cache is available.
The cache is disabled by default. To use the cache, select a broker-level cache policy (see Configuring the embedded global cache).
Run the mqsicacheadmin command, specifying the appropriate parameters, as described in mqsicacheadmin command. Use the -c parameter to run a WebSphere® eXtreme Scale command.
For example, to list all container servers and their shards in the embedded cache, run the WebSphere eXtreme Scale command, showPlacement:
```
mqsicacheadmin myBroker -c showPlacement
```
To clear all data from the map called myMap in the broker myBroker, run the following command:
```
mqsicacheadmin myBroker -c clearGrid -m myMap
```
The data is cleared immediately; you do not need to restart the broker for this action to take effect.
You do not have to specify a broker name with this command. For example, use the -cep parameter to connect to a catalog server and show the routing table for each WebSphere eXtreme Scale shard:
```
mqsicacheadmin -cep server.company.com:2800 -c routetable
```
Examine the output and usage information that is returned by the command.

Viewing the activity log

To open the activity log view in IBM Integration Explorer, complete the following steps.

Ensure that the global cache is available.
The cache is disabled by default. To use the cache, select a broker-level cache policy (see Configuring the embedded global cache).
In the WebSphere MQ Explorer - Navigator view, expand the Integration Nodes folder, then expand the folder for the relevant integration server.
To view the activity log for either a message flow or the global cache resource type, complete one of the following steps.
- To open the activity log for a message flow, right-click the message flow and click Open Activity Log.
- To open the activity log for the global cache, expand the Resource Managers folder, right-click the global cache resource type, then click Open Activity Log.
Activity information is displayed for the cache or the message flow. For more information about the activities that are recorded for the global cache, see Global cache Activity log.
You can save or copy information in the activity log; for more information, see Working with Activity logs in IBM Integration Explorer.

Collecting resource statistics

To view resource statistics for the global cache, complete the following steps.

Ensure that the global cache is available.
The cache is disabled by default. To use the cache, select a broker-level cache policy (see Configuring the embedded global cache).
To start collecting resource statistics, use one of the following methods.
For more information about working with resource statistics, see Analyzing resource performance.
- Ensure that the broker is running, then run the mqsichangeresourcestats command, setting the -c parameter to active.
  For example, to start collecting resource statistics for integration server myIS on broker myBroker, run the following command.
```
mqsichangeresourcestats myBroker -c active -e myIS
```
  For more information about this command, see mqsichangeresourcestats command.
- In the WebSphere MQ Explorer - Navigator view of IBM Integration Explorer, expand the Brokers folder. Right-click one or more integration servers and click Statistics > Start Resource Statistics.
To view the statistics, use IBM Integration Explorer.
For more information about the data that is collected for the global cache, see Resource statistics data: global cache.
1. In IBM Integration Explorer, click Window > Show View > Resource Statistics. The Resource Statistics and Resource Statistics Graph views open.
2. In the Resource Statistics view, click the global cache tab.
  If you are displaying statistics for this integration server for the first time, the views might be empty until the first data is received. Update messages are sent every 20 seconds, and the views refresh automatically.

bn23786_.htm |

Last updated Friday, 21 July 2017