This topic describes the Real-timeInput node.
This topic contains the following sections:
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.
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:
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.
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-timeInput node as follows:
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. |
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 | 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 | 0 | The port number on which the input node listens for publish or subscribe requests. |
Authentication | Yes | No | Cleared | If you select this check box, users are authenticated. |
Tunnel through HTTP | Yes | No | Cleared | Select the check box to indicate that users 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 properties of the General Message Options for the Real-timeInput node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Parse Timing | Yes | No | On Demand | This property controls when an input message is parsed.
Valid values are On Demand, Immediate, and Complete. For a full description of this property, see Parsing on demand. |