Real-timeOptimizedFlow node

This topic contains the following sections:

Purpose

Use the Real-timeOptimizedFlow node to receive messages from clients that connect 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 taken by this node are all internalized; you cannot influence its 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. If you want to modify the input message, or if you want to send messages or make publications available to applications that use other communications protocols, you must use the Real-timeInput node.

The Real-timeOptimizedFlow node is represented in the workbench by the following icon:

Real-timeOptimizedFlow node icon

Using this node in a message flow

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.

Configuring the Real-timeOptimizedFlow node

When you have put an instance of the Real-timeOptimizedFlow node into a message flow, you can configure it. Right-click the node in the editor view and select Properties. The node's basic properties are displayed.

All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk on the properties dialog.

Configure the Real-timeOptimizedFlow node as follows:

  1. In Port, identify the number of the port on which the node listens for publish or subscribe requests from JMS applications. Ensure that the port number that you specify does not conflict with any other listener service. There is no default for this property; you must enter a value.
  2. If you want users to authenticate that send messages on receipt of their messages, select the Authentication check box. If you clear the check box (the default setting), users are not authenticated.
  3. If you want clients to use HTTP tunneling, select the Tunnel through HTTP check box. If you clear the check box (the default setting), messages do not use HTTP tunneling. If you select the check box, all client applications that connect must use this feature. If they do not, their connection is rejected. The client application cannot use this option in conjunction with the connect-via proxy setting, which is activated from the client side.
  4. In Read Threads, enter the number of threads that you want the broker to allocate to read messages. The broker starts as many instances of the message flow as are necessary to process current messages, up to this limit. The default setting is 10.
  5. In Write Threads, enter the number of threads that you want the broker to allocate to write messages. The broker starts as many instances of the message flow as are necessary to process current messages, up to this limit. The default setting is 10.
  6. In Authentication Threads, enter the number of threads that you want the broker to allocate to user authentication checks. The user authentication check is performed when a message is received. The broker starts as many instances of the message flow as are necessary to process current messages, up to this limit. The default setting is 10.
  7. Select Description in the properties dialog navigator to enter a short description, a long description, or both.
  8. Click Apply to make the changes to the Real-timeOptimizedFlow node without closing the properties dialog. Click OK to apply the changes and close the properties dialog.

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

Terminals and properties

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 on the properties dialog 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 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 Select the check box to authenticate users.
Tunnel through HTTP Yes No Cleared Select the check box to indicate that 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.

The Real-timeOptimizedFlow node Description properties 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
Real-timeInput node