Network Deployment (Distributed operating systems), v8.0 > Reference > Administrator best practices


Performance for WebSphere MQ queues

To optimize performance, configure the queue destination properties to best fit your message-driven bean (MDB) or other applications that use the queue destinations.

For example:

To ensure that there are enough underlying WebSphere MQ resources available for the queue, ensure that you configure the queue destination properties adequately for use by your message-driven beans or other applications that use the queue.

We must also consider the queue attributes associated with the queue name you created with WebSphere MQ. Inappropriate queue attributes can reduce the performance of WebSphere operations. We can use WebSphere MQ commands to change queue attributes for the queue name.

BOQNAME

The excessive backout requeue name. This attribute can be set to a local queue name that can hold the messages that were rolled back by the WebSphere applications. This queue name can be a system dead letter queue.

BOTHRESH

The backout threshold and can be set to a number when the threshold is reached, the message is moved to the queue name specified in BOQNAME.

INDXTYPE

Set this attribute to MSGID to cause an index of message identifiers to be maintained, which can improve WebSphere MQ retrieval of messages.

DEFSOPT

Set this attribute to SHARED (for shared input from the queue).

SHARE

This attribute must be specified (so that multiple applications can get messages from this queue).

For more information about using these properties, see the following sections of the WebSphere MQ information center:


Configure a queue for the WebSphere MQ messaging provider
Tune messaging destinations for the WebSphere MQ or V5 default messaging providers


Related


WebSphere MQ library

+

Search Tips   |   Advanced Search