MQOptimizedFlow node

The MQOptimizedFlow node is a complete message flow that provides a high-performance publish/subscribe message flow. The node supports publishers and subscribers that use Java Message Service (JMS) application programming interfaces and the WebSphere® MQ Enterprise Transport.

To take advantage of any performance gain that this node can provide, you must make sure that you have installed WebSphere MQ Version 5.3 Fix Pack 10 for distributed platforms. Refer to the memo.ptf file for Fix Pack 10 for details of the JMS configuration that is required.

Restriction: The MQOptimizedFlow node cannot be used on z/OS® platforms.

This topic contains the following sections:

Purpose

Use the MQOptimizedFlow node to replace a publish/subscribe message flow that consists of an MQInput node connected to a Publication node and that uses the JMS over WebSphere MQ transport.

Use the MQOptimizedFlow node to improve performance, particularly where a single publisher produces a persistent publication for a single subscriber

The MQOptimizedFlow node is represented in the workbench by the following icon:

MQOptimizedFlow node icon

Using this node in a message flow

Use an MQOptimizedFlow node in a message flow to publish a persistent JMS message to a single subscriber.

Because the MQOptimizedFlow node has no terminals, it cannot be connected to any other message flow node.

Configuring the MQOptimizedFlow node

You must configure each instance of an MQOptimizedFlow node that is present in a message flow.

To do this, right-click the node in the editor view of the message flow and click Properties. The Basic properties of the node are displayed.

Specify in the Queue Name property the name of the WebSphere MQ input queue from which messages are retrieved.

Select Advanced in the properties dialog navigator, and choose Yes as the value of the Transaction Mode property.

Select Description in the properties dialog navigator if you want to give a short description, a long description, or both.

Click Apply to make the changes to the MQOptimizedFlow node without closing the properties dialog.

Click OK to apply the changes and close the properties dialog.

Click Cancel to close the properties dialog and discard all the changes that you have made to the properties.

Terminals and properties

The MQOptimizedFlow node has no terminals. It is a complete message flow and cannot be connected to other message flow nodes to extend the message processing.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory; that is, whether you must enter a value if no default value is defined; an asterisk next to the name of the property in the properties dialog denotes this. The column headed C indicates whether the property is configurable; that is, whether you can change the value in the bar file.

The Basic properties of the MQOptimizedFlow node are described in the following table:

Property M C Default Description
Queue Name Yes Yes none The name of the WebSphere MQ input queue from which this node retrieves messages for processing by this message flow.

The Advanced properties of the MQOptimizedFlow node are described in the following table:

Property M C Default Description
Transaction Mode Yes No Yes Whether the incoming message is received under syncpoint. Valid values are Automatic, Yes, and No.

The Description properties of the MQOptimizedFlow node are described in the following table.

Property M C Default Description
Short Description No No   A brief description of the node.
Long Description No No   Text that describes the purpose of the node in the message flow.
Related reference
MQInput node
Publication node