A WebSphere MQ bridge queue definition can contain the following
attributes.
Table 24. WebSphere MQ bridge queue properties
Property | Explanation |
---|---|
Alias names | Alternative names for the queue |
Authenticator | Must be null |
Class | Object class |
Client connection | Name of the client connection service to be used |
Compressor | Must be null |
Cryptor | Must be null |
Expiry | Passed to transformer |
Maximum message size | Passed to the rules class |
Mode | Must be synchronous |
MQ queue manager proxy | Name of the WebSphere MQ queue manager to which the message should first be sent |
WebSphere MQ bridge | Name of the bridge to convey the message to WebSphere MQ |
Name | Name by which the remote WebSphere MQ queue is known to WebSphere MQ Everyplace |
Owning queue manager | Queue manager owning the definition |
Priority | Priority to be used for messages, unless overridden by a message value |
Remote WebSphere MQ queue name | Name of the remote WebSphere MQ queue |
Rule | Rule class used for queue operations |
Queue manager target | WebSphere MQ queue manager owning the queue |
Transformer | Name of the transformer class that converts the message from WebSphere MQ Everyplace format to WebSphere MQ format |
Type | WebSphere MQ bridge queue |
More detail of each property can be found in the WebSphere MQ Everyplace Java Programming Reference, in the administration class com.ibm.mqe.mqbridge.MQeMQBridgeQueueAdminMsg.
Example code which manipulates a bridge queue can be found in the java class examples.mqbridge.administration.programmingAdminHelperBridgeQueue.
WebSphere MQ bridge queues are synchronous only. Asynchronous applications must therefore use either a combination of WebSphere MQ Everyplace store-and-forward and home-server queues, or asynchronous remote queue definitions as an intermediate step when sending messages to WebSphere MQ bridge queues.
Applications make use of WebSphere MQ bridge queues like any other WebSphere MQ Everyplace remote queue, using the putMessage, browseMessages, and getMessage methods of the MQeQueueManager class. The queue name parameter in these calls is the name of the WebSphere MQ bridge queue, and the queue manager name parameter is the name of the WebSphere MQ queue manager. However, in order for this queue manager name to be accepted by the local WebSphere MQ Everyplace server, a connection definition with this WebSphere MQ queue manager name must exist with null for all the parameters, including the channel name.
Administration of the WebSphere MQ bridge is handled in the same way as the administration of a normal WebSphere MQ Everyplace queue manager, through the use of administration messages. New classes of messages are defined as appropriate to the queue.