MQOptimizedFlow node

Use the MQOptimizedFlow node to provide 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, ensure that you have installed WebSphere MQ Version 5.3 Fix Pack 10 for distributed systems. See the release notes for this fix pack, which are accessible through the WebSphere MQ support Web page, for details of the JMS configuration that is required.

Restriction: z/OS platform You cannot use an MQOptimizedFlow node in message flows that you deploy to z/OS® systems.

This topic contains the following sections:

Purpose

Use the MQOptimizedFlow node to replace a publish/subscribe message flow that consists of an MQInput node that is connected to a Publication node and that uses the Java Message Service (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 contained in the WebSphere MQ drawer of the palette, and 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.

The MQOptimizedFlow node has no terminals, so you cannot connect it to any other message flow node.

Terminals and properties

When you have put an instance of the MQOptimizedFlow node into a message flow, you can configure it; see Configuring a message flow node. The properties of the node are displayed in the Properties view. To display the properties of the node in the Properties dialog, either double-click the node, or right-click the node and click Properties. All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.

The MQOptimizedFlow node has no terminals. It is a complete message flow and you cannot connect it 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 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 MQOptimizedFlow node Description properties are described in the following table.

Property M C Default Description
Node name No No MQOptimizedFlow The name of the node.
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.

The MQOptimizedFlow node Basic properties 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 MQOptimizedFlow node Advanced properties are described in the following table.

Property M C Default Description
Transaction mode Yes No Yes This property controls whether the incoming message is received under syncpoint. Valid values are Automatic, Yes, and No.
Related reference
MQInput node
Publication node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:28

ac20804_