This topic contains the following sections:
Use the Real-timeOptimizedFlow node to receive messages from clients that connect to the broker using the WebSphere MQ Real-time Transport or the WebSphere MQ Multicast Transport, and that use JMS application programming interfaces.
The Real-timeOptimizedFlow node is a complete message flow that provides a high performance publish/subscribe message flow. The actions that are taken by this node are all internalized; you cannot influence the node's operation except by configuring its properties, and you cannot connect it to any other node.
This node also supports publication to, or subscription from, standard WebSphere MQ applications, but its performance for these applications is not as good as the performance achieved for JMS applications.
You cannot affect the message content in any way when you use the Real-timeOptimizedFlow node. To modify the input message, or to send messages or make publications available to applications that use other communications protocols, use the Real-timeInput node.
The Real-timeOptimizedFlow node is represented in the workbench by the following icon:
Include the Real-timeOptimizedFlow node in a message flow when you want to distribute messages through a broker to and from client applications that use JMS.
When you have put an instance of the Real-timeOptimizedFlow node into a message flow, you can 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.
Configure the Real-timeOptimizedFlow node as follows:
The Real-timeOptimizedFlow node has no terminals. It is a complete message flow and cannot be connected to other nodes to extend the message processing.
The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined), the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).
The Real-timeOptimizedFlow node Description properties 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 Real-timeOptimizedFlow node Basic properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Port | Yes | Yes | The port number on which the node listens for publish or subscribe requests. You must provide a value for this property. | |
Authentication | Yes | No | Cleared | If you select this check box, users are authenticated. |
Tunnel through HTTP | Yes | No | Cleared | If you select this check box, clients use HTTP tunneling. Clear the check box to indicate that HTTP tunneling is not used. |
Read Threads | No | Yes | 10 | The number of threads used for reading. |
Write Threads | No | Yes | 10 | The number of threads used for writing. |
Authentication Threads | No | Yes | 10 | The number of threads used for accepting connections and authenticating users. |