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.
This topic contains the following sections:
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:
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.
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.
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. |