Use this panel to view or change the advanced properties of the selected queue connection factory for use with the WebSphere® MQ messaging provider. These advanced properties control the behavior of connections made to WebSphere MQ messaging provider destinations.
Make any required changes to these groups and then click Apply to return to the queue connection factory.
A WebSphere MQ queue connection factory has the following advanced properties:
An option that enables the compression of message headers.
Data type | Check box |
Default | Cleared |
Range |
|
The compression algorithm that is used to compress message payloads.
Data type | Drop-down list |
Default | NONE |
Range |
|
The model queue that is used as a basis for temporary queue definitions.
Data type | String |
Default | SYSTEM.DEFAULT.MODEL.QUEUE |
The prefix that is attached to the beginning of the names generated for temporary queues.
Data type | String |
An option that determines whether messages for which there is no matching consumer are retained on the input queue or dealt with according with their disposition options.
Data type | Check box |
Default | Selected |
Range |
|
This setting is applicable in the client container only. When using a WebSphere MQ version 6 queue manager (or WebSphere MQ version 5.3 for z/OS®), this setting configures the mechanism used to dispatch messages to JMS asynchronous consumers.
This setting is used when the set of WebSphere MQ queues that is being asynchronously consumed from exceeds the number of threads that are available internally to synchronously get messages from the WebSphere MQ queue. The setting determines how long a thread waits for a message to arrive at a WebSphere MQ queue before polling another WebSphere MQ queue in the set.
Data type | Integer |
Units | Milliseconds |
Default | 5000 |
Range | A value greater than zero. |
When using a WebSphere MQ version 6 queue manager (or WebSphere MQ version 5.3 for z/OS), this setting configures the mechanism used to dispatch messages to JMS asynchronous consumers.
This setting is used when the set of WebSphere MQ queues that is being asynchronously consumed from exceeds the number of threads that are available internally to synchronously get messages from the WebSphere MQ queue. The setting determines how long a thread retrieves messages from a WebSphere MQ queue before switching to consume messages from another WebSphere MQ queue in the set.
Data type | Integer |
Units | Milliseconds |
Default | 5000 |
Range | A value greater than zero. |
The maximum number of messages that can be removed from a queue before at least one must be delivered to an asynchronous consumer.
Data type | Integer |
Default | 10 |
Range | A value greater than zero. |
The character set to use when you are encoding strings in the message.
Data type | Integer |
Default | 819 |
Range | A value greater than zero. The coded character set identifier (CCSID) must be one of the CCSIDs supported by WebSphere MQ. |
For more information about supported CCSIDs, and about converting between message data from one coded character set to another, see the WebSphere MQ System Administration and the WebSphere MQ Application Programming Reference sections of the WebSphere MQ library.
When sending a reply message to the reply-to queue obtained from a message, select this option to append an RFH version 2 header to the reply message regardless of whether the original message had a RFH version 2 header.
Data type | Check box |
Default | Cleared |
Range |
|
An option that enables selected JMS operations to fail when the queue manager is put into a quiescing state. Selecting this option enables the queue manager to quiesce successfully and shut down.
Data type | Check box |
Default | Selected |
Range |
|