WebSphere Message Brokers
File: ac20804_
Writer: Terry Cowling

Reference topic

This build: July 31, 2007 21:19:28

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.

Restriction: The MQOptimizedFlow node cannot be used on 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 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.

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

Configuring the MQOptimizedFlow node

When you have put an instance of the MQOptimizedFlow node into a message flow, you must configure it. To display its properties, 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.
  1. Optional: On the Description tab, enter a short description, a long description, or both. You can also rename the node on this tab.
  2. On the Basic tab, specify in the Queue Name property the name of the WebSphere MQ input queue from which messages are retrieved.
  3. On the Advanced tab, set the Transaction Mode property to Yes (the default) if you want the incoming message to be received under syncpoint.

Terminals and properties

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 Description properties of the MQOptimizedFlow node are described in the following table.

Property M C Default Description
Node name No No The node type 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 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 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, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:19:29

ac20804_ This topic's URL is: