IBM MQ messaging provider activation specification broker properties

Use this panel to view or change the broker settings of the selected activation specification for use with the IBM MQ messaging provider. These broker settings determine how the IBM 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 view IBM MQ activation specification broker properties, use the administrative console to complete the following steps:
  1. In the navigation pane, click Resources > JMS->Activation specifications to display existing activation specifications.
  2. If appropriate, in the content pane, change the Scope setting to the level at which the activation specifications are defined. This restricts the set of activation specifications displayed.
  3. Select the name of the activation specification that you want to work with.
  4. In the content pane under Additional properties, click Broker properties to view a list of the broker properties of the IBM MQ activation specification.
Under General Properties there are four groups of properties:
  • Queues
  • Capabilities
  • Tuning
  • Additional

Make any required changes to these groups and then click Apply to return to the activation specification.

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

An IBM MQ activation specification has the following broker properties.

Broker control queue

The queue to which broker control messages are sent.

Information Value
Data type String
Default SYSTEM.BROKER.CONTROL.QUEUE

Broker subscriber queue

The queue from which subscription messages are received.

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

Broker connection consumer subscription queue

The queue to receive subscription messages for connection consumers from.

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

Broker connection consumer durable subscription queue

The queue to receive subscription messages for durable connection consumers from.

Information Value
Data type String
Default SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE

Version

The version of the broker that is 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.

Information Value
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 you select this option, you must also complete Specify where message selection occurs.

Specify where message selection occurs

The process in which message selection is performed. This property is enabled only if Version 2 broker was selected.

Information Value
Data type Drop-down list
Default CLIENT
Range
CLIENT
Message selection is performed in the application server process.
BROKER
Message selection is performed in the broker process.

Subscription store

The process for tracking subscriptions.

Information Value
Data type Drop-down list
Default MIGRATE
Range
MIGRATE
Any information that is held on 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 IBM 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.

Information Value
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.

Information Value
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.

Information Value
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.

Information Value
Data type Drop-down list
Default character wildcards
Range
character wildcards
You can 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
You can 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.

Optimize for sparse subscription patterns

An option to specify whether this activation specification is anticipated to receive a high proportion of messages that match its selection criteria. This information can be used to optimize message delivery.

Information Value
Data type Check box
Default Cleared
Range
Cleared
Subscriptions frequently receive matching messages.
Selected
Subscriptions do not frequently receive matching messages.