Setting up queues

Note:
Before setting up specific queues, be sure that you have defined the queue manager, server connection channel, and listener that you will use to communicate with Peer-to-Peer Agent.

A typical implementation of the connector requires the creation of at least one outbound queue for delivering messages to Peer-to-Peer Agent, and at least three inbound queues that the connector will poll for business data events, MDNs, and notifications:

In addition to creating the queues, you must also configure the connector to use the queues that you create. See Configure connector propertiesfor information about the properties that configure the connector to use the queues.

Queue Uniform Resource Identifiers (URI)

To configure queues for use with the connector:

The URI for a queue begins with the sequence queue:// followed by:

For example, the following URI connects to queue IN on queue manager crossworlds.queue.manager and causes all messages to be sent as WebSphere MQ messages with priority 5.

queue://isoft.queue.manager/ISOFT.IN?targetClient=1&priority=5
 

The table below shows property names for queue URIs.

Property name Description Values
expiry Lifetime of the message in milliseconds. 0 = unlimited. positive integers = timeout (in ms).
priority Priority of the message. 0-9, where 1 is the highest priority. A value of -1 means that the property should be determined by the configuration of the queue. A value of -2 specifies that the connector can use its own default value.
persistence Whether the message should be 'hardened' to disk. 1 = non-persistent 2 = persistent A value of -1 means that the property should be determined by the configuration of the queue. A value of -2 specifies that the connector can use its own default value.
CCSID Character set encoding of the outbound message. Integers - valid values listed in base WebSphere MQ documentation. This value should match that of the CCSID connector-specific configuration property; see CCSID
Note:
The connector has no control of the character set (CCSID) or encoding attributes of data in MQMessages. Because data conversion is applied as the data is retrieved from or delivered to the message buffer, the connector relies upon the IBM WebSphere MQ implementation of JMS to convert data (see the IBM WebSphere MQ Java client library documentation). Accordingly, these conversions should be bi-directionally equivalent to those performed by the native WebSphere MQ API using option MQGMO_CONVERT. The connector has no control over differences or failures in the conversion process. The connector can retrieve message data of any CCSID or encoding supported by WebSphere MQ without additional modifications. To deliver a message of a specific CCSID or encoding, the output queue must be a fully-qualified URI and specify values for CCSID and encoding. The connector passes this information to WebSphere MQ, which (via the JMS API) uses the information when encoding data for MQMessage delivery. Not all platforms support all CCSIDs. Often, lack of support for CCSID and encoding can be resolved by downloading the most recent version of the IBM WebSphere MQ Java client library from IBM's web site.

For more information about URIs, see the WebSphere MQ programming guide.

Copyright IBM Corp. 1997, 2003