This topic applies only to the IBM Business Process Manager Advanced configuration.

Troubleshooting Service Component Architecture and WebSphere MQ communications

Communication between Service Component Architecture (SCA) modules and WebSphere® MQ queue managers depends on the binding between the imports and exports within the SCA module and the queues in WebSphere MQ servers. Use this information to determine the servers that are not processing WebSphere MQ messages.

Before you begin

This task assumes that you have noticed requests dependant on WebSphere MQ are not being processed and that you have access to the administrative console. You should also either have the ability to make changes to the WebSphere MQ queue manager or be in contact with the WebSphere MQ administrator.

About this task

Service Component Architecture (SCA) modules depend on the bindings between the server and the WebSphere MQ queue manager. Communications between the two entities could keep messages from processing completely. The following steps should help you discover the cause of the disruption and what to do to get the messages processed again.

Procedure

Display the SCA module communicating with WebSphere MQ to make sure it is still processing. Navigate to this page using Applications > SCA Modules.
Display the queue manager to make sure it is still operational. Use WebSphere MQ administrative tools to perform this task.
Display the bindings between the SCA module and the queue manager to make sure the binding is correct. If the binding is incorrect, change the binding. Navigate to this page using Applications > SCA modules >moduleName > Imports|Exports > importName|exportName > Bindings > bindingName [type].
Locate any messages that may indicate failed transactions. You will have to investigate system, SCA-specific message areas, WebSphere MQ-specific message areas, the failed event queue and other locations to determine what has failed.
1. Examine SystemOut.log for any messages that would indicate processing failures.
  If there is a WebSphere MQ error, there will be an MQException linked somewhere in the stack trace with a WebSphere MQ reason code (for example, 2059 is "queue manager unavailable").
2. Check AMQERRxx.LOG and the WebSphere MQ FFDC files to determine the cause of a WebSphere MQ error.
3. Examine the application queues to determine if there are any unprocessed messages. Make sure you examine both WebSphere MQ and Service Integration Bus (SIB) queues.
4. Examine the WebSphere MQ dead letter queue and the SIB exception destination.
5. Examine the failed event queue to determine if there are any messages related to the applications of interest.