186 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1
Figure 6-38 Successful completion message
6.4.4 WebSphere MQ channel monitoring
Here are some highlights of WebSphere MQ channel monitoring:
򐂰 The channel status attribute specifies the current status of a channel. If the
channel is retrying, then a previous attempt to establish a connection has
failed. The MCA will re-attempt a connection after the specified time interval.
If the MCA reaches its limit of retry attempts, then the channel will stop and
need to be restarted manually.
򐂰 If the channel is indoubt status, then the sending MCA is waiting for an
acknowledgement that a batch of messages, which it has sent, has been
successfully received and committed. The detection of an indoubt channel
status could indicate network related problems.
򐂰 If the channel is stopped, it is not necessarily a problem with the network,
because it may have been manually stopped for a specific reason. Therefore,
in addition to checking whether the channel is stopped or not, what also
needs to be checked is if the channel stopped because of an error. If this is
the case, and the channel is stopped due to an error, then some action needs
to be taken to remedy the situation.
Again, let us walk you thorough an example:
1. For example, if the monitored channel is down, a critical alert will appear in
the Enterprise Event Console (Figure 6-39 on page 187).
Chapter 6. WebSphere MQ Monitoring 187
Figure 6-39 WebSphere MQ channel stopped alert
2. It is a good practice to acknowledge the alert first.
3. Select the Channel Performance workspace, which provides performance
information about the monitored channels on each monitored queue
manager, as shown in Figure 6-40 on page 188. Included is whether or not
each channel is in-doubt, current, or inactive, as well as the channel type. Use
the information in the Channel Performance workspace to examine and
compare channel performance among the selected channels. Look for
patterns in resource activity, traffic, or time of day.
188 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1
Figure 6-40 Channel Performance workspace
4. To view the Recent Channel Performance workspace, right-click the Channel
Performance workspace and select Workspace Recent Channel
Performance, as shown in Figure 6-31 on page 180.
Chapter 6. WebSphere MQ Monitoring 189
Figure 6-41 Channel Performance workspace
5. Use the information in the Recent Channel Performance workspace to
investigate recent trends in the performance of the selected channels. Look
for patterns in time of day, channel type, or transmission rate.
6. You can take advantage of Take Action feature. From the Channel
Performance workspace, click the link to Channel Performance
workspace. Select the channel you want to start and right click it. Select Take
Action (Figure 6-42 on page 190).
190 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1
Figure 6-42 Taking actions to restart the channel
7. In the next panel, select MQ Start Channel from the drop down Name list,
select the Destination System, and click OK (Figure 6-43).
Figure 6-43 Restarting a channel

Get Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.