IBM Integration Bus (WebSphere Message Broker) policies
This section provides details of the supplied WMB policies for monitoring of the IBM Integration Bus (or WebSphere Message Broker as older versions are called) to enable you to customize them for your specific environment.
If you simply want to get started using the policy as quickly as possible (with no customization), see Getting started with policies. In order to gain a better understanding of policies, see Policy architecture.
As is typical for the supplied agent policies, the Minimal level for WMB monitoring references the basic monitoring for the BMM agents and extensions and then turns on historical collection at the top level.
Because IBM Integration Bus is about the connection of different applications, this information is more extensive than for most minimal level policies.
The WMB_Agents_Minimal agent policy references one Object Policy Group (WMB_POLICY_Minimal) which, in turn, references a nested Object Policy Group called WMB_ResourceManagers_Minimal that turns on history collection using the SAMPLE History Template at the Summary level for all Resource Managers (as shown below), which provides you trending data on the use of each of the major communication pools from the Broker (MQ, JMS, SOAP, FTP, and so on).
Note that in order to be standard, the WMB_ResourceManagers_Minimal Object Policy Group contains an Object Policy for all supported Resource Manager types. Of course, you can remove the Object Policies for types that you do not use from your copy of the Object Policy Group (select the Object Policy that you do not want to use and click the Remove button).
The WMB Agents_Basic agent policy contains a WMB_ResourceManagers_Basic Object Policy Group. This is more extensive than the WMB_ResourceManagers_Minimal. While it activates history using the SAMPLE History Template for each Resource Manager type, it does so not just at the Summary level for the type, but also for each instance of the type. In addition, the WMB_POLICY_Basic adds three Object Policies to turn on history collection using the SAMPLE History Template for Execution Groups, Message Flows, and Nodes, respectively, as shown below.
The Standard level of Integration Bus (WMB) monitoring contains an Object Policy Group to reference all instances of all Resource Manager types and sets events for those. In addition to adding history on those resource managers as with the Basic level, it registers event templates against each type. While those types are too numerous to walk through individually here, the idea should be clear so that you can add or remove Policy Actions from the individual Object policies in that Group (or remove the whole object policy from the Group) according to your needs.
The WMB_POLICY_Standard_EventTarget Object Policy Group also includes Object Policies referencing all of the Broker and all of its key descendant types (Applications, Libraries, Execution Groups, and Message Flows). Each of those Object Policies sets up history on all objects of the type using the SAMPLE History Template and registers the a set of events notifying of key conditions.
For example, as shown above, you can see that the WMB_MessageFlow_Standard_BEM Object Policy adds associates each message flow with alerts when a Backout occurs, when the Message Flow uses High CPU, when the message flow is disabled by an administrative action, when an Error occurs, when Flow Stats are turned off (so that performance statistics from the flow will not be reporting), when the flow is using all of its available instances (MaxThreadsReached) or more than a threshold percentage (PoolUsageHigh), when the flow appears active but no performance data is arriving (Non-Responsive), when someone has turned Service or User Trace on, or when the time to process messages exceeds a threshold.
Clicking the Select button allows you to add additional Policy Actions to this Object Policy while selecting an existing Policy Action and clicking the Remove button will no longer apply that Policy Action. You can also change the individual thresholds for events.
The ALL level of IBM Integration Bus monitoring contains everything done by the Standard level, and then adds two additional Event Templates to Message Flows (Node Level Statistic are on, which might create a high load on BMM, and one to separate MQ Errors from other message flow errors).