Bridge rules

Whilst Queue Rules can also be applied to Bridge Queues, you can also apply the following other types of rules to the Bridge:
UndeliveredMessageRules
These rules can be applied to the Bridge Listener and can be used to determine what action is to be performed when an MQ Message can't be delivered to the MQe Gateway. The default rule used by MQe will stop the Bridge Listener after a set number of attempts to deliver the message. Two example rules are provided:
examples.mqbridge.rules.MQeUndeliveredMessageRule
Copy of the default rule
examples.mqbridge.rules.UndeliveredMQMessageToDLQRule
Will either discard the message or move it to MQ's Dead Letter Queue depending on the report field of the original MQ Message
StartUp Rules
These rules can be used to control startup of the objects held in the bridge so that, for example, the bridge is in a stopped state when the MQe Gateway is started. An example is provided: examples.mqbridge.rules.MQeStartupRule.
SyncQueuePurger Rules
These rules can be used for administrative purposes to clear up old records that can sometimes be left on the MQ Queue manager. However, this typically only occurs if the corresponding MQe message has been deleted. Two examples are provided:
examples.mqbridge.rules.MQeSyncQueuePurgerRule
Calls trace with an info statement when it discovers messages older than a specified time
examples.mqbridge.rules.DestructiveMQSyncQueuePurgerRule
Deletes any message that is older than a specified time

Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.