WebSphere MQ Browse
The Browse activity is used to retrieve a message nondestructively from a configured queue. Messages can be retrieved based on filter criteria specified in the input document.
The queue is opened in browse mode, and the results of the first message are returned. To retrieve subsequent messages, the activity must be placed in a loop. If no more messages on the queue satisfy the filter criteria, the activity fails with fault message code
50217. Interception of this fault by a fault handler allows the process to gracefully exit the browse loop.
The Browse activity can be used to check the queue with or without a wait interval. The activity waits on the queue for the specified interval, then returns whether or not a message is received.
General
The General tab of the Browse activity contains the following fields:
Input
The following table lists the input items for the Browse activity:
Output
The following table lists the output items for the Browse activity:
Fault
The Fault tab lists the possible exceptions that occur in the Browse activity:
Error Schema Element | Data Type | Description |
---|---|---|
msg | String | The descriptive text provided by this exception object. |
msgCode | String | If the message has a BW message code, it is mapped to this field. |
mqCompCode | String | If the message originates as a WebSphere MQ API exception, then that exception's completion code is here. |
mqReasonCode | String | If the message originates as a WebSphere MQ API exception, then that exception's reason code is here. |
mqErrorCode | String | If the message originates as a WebSphere MQ API exception, then that exception's error code is here. |
Copyright © Cloud Software Group, Inc. All rights reserved.