WebSphere MQ messaging provider queue connection factory advanced properties

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.

To view WebSphere MQ queue connection factory advanced properties, use the administrative console to complete the following steps:
  1. In the navigation pane, click Resources > JMS->Queue connection factories to display existing queue connection factories.
  2. If appropriate, in the content pane, change the Scope setting to the level at which the queue connection factories are defined. Setting the scope in this way restricts the set of queue connection factories displayed.
  3. Select the name of the queue connection factory that you want to work with.
  4. In the content pane, under Additional properties, click Advanced properties to view a list of the advanced properties of the WebSphere MQ queue connection factory.
Under General Properties there are six groups of advanced properties:
  • Client reconnect
  • Message compression
  • Temporary destinations
  • Connection consumer
  • Message format
  • Additional

Make any required changes to these groups and then click Apply to return to the queue connection factory.

Notes: When specifying WebSphere MQ properties, the following restrictions apply:
  • Names can have a maximum of 48 characters, except for channels, which have a maximum of 20 characters.
  • The property values that you specify must match the values that you specified when configuring JMS resources for WebSphere MQ. For more information about configuring JMS resources for WebSphere MQ , see the Using Java™ section of the WebSphere MQ documentation.

A WebSphere MQ queue connection factory has the following advanced properties:

Client reconnect options

This property specifies whether a client mode connection reconnects automatically, or not, in the event of a communications or queue manager failure. This parameter is ignored unless the connection factory is being used in a thin or managed client environment.

Information Value
Data type Drop-down list
Default DISABLED
Range
DISABLED
Client reconnection does not automatically occur.
ASDEF
The value from the DefRecon attribute from the channels stanza of the client configuration file is used. If there is no DefRecon value specified in the client configuration file, ASDEF has the same effect as DISABLED.
QMGR
Reconnection occurs only to the queue manager to which the connection was originally connected.
RECONNECT
Reconnection occurs to any queue manager that is consistent with the value of the queue manager attribute. This queue manager might be a different queue manager from the one to which the connection was originally connected.

For more information about automatic client reconnection, see the WebSphere MQ information center.

Client reconnect timeout

The maximum number of seconds that a client mode connection spends attempting to automatically reconnect to a queue manager after a communications or queue manager failure. This parameter is ignored unless the connection factory is being used in a thin or managed client environment. Whether this parameter is used or not depends on the value of the client reconnect options parameter.

Information Value
Data type Integer
Units Seconds
Default 1800 (30 minutes)
Range A value greater than zero and up to 2147483647

For more information about automatic client reconnection, see the WebSphere MQ information center.

Compress message headers

An option that enables the compression of message headers.

Information Value
Data type Check box
Default Cleared
Range
Cleared
Do not compress message headers.
Selected
Compress message headers.

Compression algorithm for message payloads

The compression algorithm that is used to compress message payloads.

Information Value
Data type Drop-down list
Default NONE
Range
RLE
Message data compression is performed using run-length encoding.
ZLIBFAST
Message data compression is performed using ZLIB encoding with speed prioritized.
ZLIBHIGH
Message data compression is performed using ZLIB encoding with compression prioritized.
NONE
No message data compression is performed.

WebSphere MQ model queue name

The model queue that is used as a basis for temporary queue definitions.

Information Value
Data type String
Default SYSTEM.DEFAULT.MODEL.QUEUE

Temporary queue prefix

The prefix that is attached to the beginning of the names generated for temporary queues.

Information Value
Data type String

Retain messages, even if no matching consumer is available

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.

Information Value
Data type Check box
Default Selected
Range
Cleared
Do not retain messages.
Selected
Retain messages.

Polling interval

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.

Information Value
Data type Integer
Units Milliseconds
Default 5000
Range A value greater than zero.

Rescan interval

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 use messages from another WebSphere MQ queue in the set.

Information Value
Data type Integer
Units Milliseconds
Default 5000
Range A value greater than zero.

Maximum batch size

The maximum number of messages that can be removed from a queue before at least one must be delivered to an asynchronous consumer.

Information Value
Data type Integer
Default 10
Range A value greater than zero.

Coded character set identifier

The character set to use when you are encoding strings in the message.

Information Value
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 System Administration and the Application Programming Reference sections of the WebSphere MQ information center.

Append an RFH version 2 header to reply messages

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.

Information Value
Data type Check box
Default Cleared
Range
Selected
Append an RFH version 2 header to reply messages regardless of whether the original message had an RFH version 2 header.
Cleared
Append an RFH version 2 header to reply messages only if the original message had an RFH version 2 header.

Fail JMS method calls if the WebSphere MQ queue manager is quiescing

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.

Information Value
Data type Check box
Default Selected
Range
Cleared
Do not fail JMS operations if the queue manager is quiescing.
Selected
Fail JMS operations if the queue manager is quiescing.