Queue uniform resource identifiers (URIs)

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

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

queue://<queue.manager.name>/WC_MQCONN.IN?targetClient=1&priority=5

The following table shows property names for queue URIs.

Table 43. WebSphere MQ-specific connector property names for queue URIs

Property name Description Values
expiry

The lifetime of the message in milliseconds.

0 = unlimited

positive integers = timeout (in ms).

priority

The 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

Indicates whether the message should be

hardened

to the 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

The character set of the destination.

Integers: Valid values are listed in the documentation for the Adapter for WebSphere MQ User Guide.
targetClient

Indicates whether the receiving application is JMS compliant or not.

0 = JMS (MQRFH2 header)

1 = MQ (MQMD header only)

encoding

Indicates how to represent numeric fields.

Integers: Valid values are listed in the documentation for the Adapter for WebSphere MQ User Guide.

The adapter 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 adapter 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 adapter has no control over differences or failures in the conversion process. The adapter 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 adapter passes this information to WebSphere MQ, which (via the JMS API) uses the information when encoding data for MQMessage delivery.

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. If problems specific to CCSID and encoding persist, contact Technical Support to discuss the possibility of using an alternate Java Virtual Machine to run the adapter.

Configuring Queue URIs

To configure queues for use with the connector:

Note:
If your target application expects an MQMD header only and cannot process the extended MQRFH2 headers used by JMS clients, append ?targetClient=1 to the queue URI.

Copyright IBM Corp. 1997, 2004