Real-timeInput node

Use the Real-timeInput 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.

This topic contains the following sections:

Purpose

The Real-timeInput node handles messages in the following message domains:
  • JMSMap
  • JMSStream

An output node in a message flow that starts with a Real-timeInput node can be any of the supported output nodes, including user-defined output nodes. You can create a message flow that receives messages from real-time clients and generates messages for clients that use all supported transports to connect to the broker, because you can configure the message flow to request the broker to provide any conversion that is required.

If you create a message flow to use as a subflow, you cannot use a standard input node; you must use an instance of the Input node as the first node to create an In terminal for the subflow.

If your message flow does not receive messages from JMS applications, choose one of the supported input nodes.

The Real-timeInput node is contained in the Additional Protocols drawer of the palette, and is represented in the workbench by the following icon:

Real-timeInput node icon

Using this node in a message flow

Look at the following sample to see how you can use this node: You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.

Terminals and properties

When you have put an instance of the Real-timeInput 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 Real-timeInput node terminals are described in the following table.

Terminal Description
Out The output terminal to which the message is routed if it is successfully retrieved from JMS. If this routing fails, the message is retried.

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

Property M C Default Description
Node name No No The node type: Real-timeInput 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-timeInput node Basic properties are described in the following table.

Property M C Default Description
Port Yes Yes   The port number on which the input 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. No default value is provided for this property; you must enter a value.
Authentication Yes No Cleared To authenticate users that send messages on receipt of their messages, select this check box. If you clear the check box (the default setting), users are not authenticated.
Tunnel through HTTP Yes No Cleared Select the check box to indicate that users use HTTP tunneling. 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 use this feature, 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.
Read Threads No Yes 10 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.
Write Threads No Yes 10 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.
Authentication Threads No Yes 10 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 properties of the General Message Options for the Real-timeInput node are described in the following table.

Property M C Default Description
Parse Timing No No On Demand This property controls when an input message is parsed. Valid values are On Demand, Immediate, and Complete.

Parse timing is, by default, set to On Demand, which causes parsing of the message to be delayed. To cause the message to be parsed immediately, see Parsing on demand.

Notices | Trademarks | Downloads | Library | Support | Feedback

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

ac09200_