WebSphere MQ messaging provider connection factory broker properties


 

+

Search Tips   |   Advanced Search

 

Broker settings determine how the WebSphere MQ messaging provider interacts with a broker for the purposes of publishing messages and subscribing to topics. Updates to the settings take effect when the server is restarted.

To set the broker settings of the selected connection factory, or topic connection factory, for use with the WebSphere MQ messaging provider.

  1. In the navigation pane, click...

    Resources | JMS | Connection factories

    ...to display existing connection factories, or click...

    Resources | JMS | Topic connection factories

    ...to display existing topic connection factories.

  2. Set the scope.

  3. Select the name of the connection factory, or topic connection factory, to work with.

  4. In the content pane, under Additional Properties, click Broker properties to display the broker properties of the WebSphere MQ connection factory, or topic connection factory.

Under General Properties there are four groups of properties:

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

When specifying WebSphere MQ properties, the following restrictions apply:

A WebSphere MQ connection factory, or topic connection factory, has the following broker properties:

Broker control queue

The queue to which broker control messages are sent.

Data type String
Default SYSTEM.BROKER.CONTROL.QUEUE

Broker publication queue

The queue to which publication messages are sent.

Data type String
Default SYSTEM.BROKER.DEFAULT.STREAM

Broker subscriber queue

The queue to which subscription messages are sent.

Data type String
Default SYSTEM.JMS.ND.SUBSCRIBER.QUEUE

Broker connection consumer subscription queue

Queue to which subscription messages that are destined for a connection consumer are sent.

Data type String
Default SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE

Version

Version of the broker used. This determines some of the capabilities that the broker is assumed to have. For example, whether to use an RFH version 1 or version 2 header in publications.

Data type Radio button
Default Version 1 broker
Range

Version 1 broker

Message selection cannot be specified.

Version 2 broker

Message selection can be specified. If we select this option, also complete Specify where message selection occurs.

Specify where message selection occurs

The process in which message selection is performed. Is enabled only if V2 broker was selected.

Data type Drop-down list
Default CLIENT
Range

CLIENT

Message selection is performed in the appserver process.

BROKER

Message selection is performed in the broker process.

Subscription store

The process for tracking subscriptions.

Data type Drop-down list
Default MIGRATE
Range

MIGRATE

Any information that is held using queues is migrated to the broker mechanism for persisting subscription information. If subscription information is already persisted using the broker mechanism then specifying a value of Migrate is equivalent to specifying a value of Broker.

BROKER

Internal broker mechanisms are used to track subscription information.

QUEUE

A designated WebSphere MQ queue is used to record information about current subscriptions.

Durable subscription state refresh interval

How often a long running transaction is recreated and used to clean up durable subscriptions, for some versions of the queue manager.

Data type Integer
Default 60000
Range Any positive integer

Subscription cleanup level

How aggressively messages are cleaned up if the subscriber that is expected to consume the messages terminates unexpectedly.

Data type Drop-down list
Default SAFE
Range

SAFE

A conservative algorithm is used to clean up subscriptions.

ASPROP

The cleanup algorithm is determined by a system property.

NONE

No cleanup of subscriptions is performed.

STRONG

An aggressive algorithm is used to clean up subscriptions.

Subscription cleanup interval

How often to check for orphaned subscriptions and clean up messages.

Data type Integer
Default 3600000
Range Any positive integer

Subscription wildcard format

The wildcard format used for subscribing to more than one topic in a topic hierarchy.

Data type Drop-down list
Default character wildcards
Range

character wildcards

Use an asterisk (*) or question mark (?) to represent characters, or strings of characters, in a topic name.

* is interpreted as matching many characters.

? is interpreted as matching a single character.

topic level wildcards

Use a plus sign (+) or number sign (#) to represent topics in a multilevel topic hierarchy.

+ is interpreted as matching a single topic name.

# is interpreted as matching many topics in the hierarchy. / is used to delimit topics.

Publish acknowledgement window

The number of messages to publish before publishing a message that requires broker acknowledgement

Data type Integer
Default 25
Range Any positive integer

Optimize for sparse subscription patterns

Option to specify whether this connection factory is anticipated to receive a high proportion of messages that match its selection criteria. This information can be used to optimize message delivery.

Data type Check box
Default Cleared
Range

Cleared

Subscriptions frequently receive matching messages.

Selected

Subscriptions do not frequently receive matching messages.

Broker queue manager

The name of the queue manager that is running the broker, if it is not the same as the queue manager to which the connection factory connects.

Data type String
Default The queue manager name that was specified in the connection factory.




 

Related

Connection factory collection
Mapping of admin console panel names to command names and WebSphere MQ names
WebSphere MQ messaging provider connection factory settings
WebSphere MQ messaging provider topic connection factory settings