Queue Uniform Resource Identifiers (URI)

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://crossworlds.queue.manager/MQCONN.IN?targetClient=1&priority=5

Table 11 shows property names for queue URIs.

Table 11. FIX-specific connector 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 of the destination. Integers - valid values listed in base WebSphere MQ documentation. The value of this property should match that of the CCSID connector-specific property (see CCSID.
targetClient
 
Whether the receiving application is JMS compliant or not. 0 = JMS (MQRFH2 header) 1 = MQ (MQMD header only)
encoding
 
How to represent numeric fields. An integer value as described in the base WebSphere MQ documentation.
Note:
The connector has no control of the character set (CCSID) or encoding attributes of data in FIX messages. 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 FIX 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 connector.

Copyright IBM Corp. 1997, 2003