Use the TCPIPServerOutput node to create a server connection to a raw TCP/IP socket, and to send data over the connection to an external application.
The TCPIPServerOutput node listens on a TCP/IP port and waits for a client node to make a connection with the port. When the client node connects to the port, the server node creates a connection for the client. The connections are not made directly by the node but are obtained from a connection pool managed by the IBM® Integration Bus integration server.
The integration server uses the default TCPIPServer configurable service to determine which attributes are used for the socket connection. However, if the configurable service is set on the node, the configurable service is used for all the properties, including the host and port number.
When the connection has been established, the data is sent. If the data is not sent successfully within the time limit specified by the node's Timeout sending a data record property, an exception is thrown.
You can configure the broker to use SSL for TCP/IP nodes; see SSL and the TCP/IP nodes.
Properties in the local environment can override the TCP/IP connection used by the node.
Location in local environment | Description |
---|---|
$LocalEnvironment/Destination/TCPIP/Output/Hostname | The host name used to make a connection. |
$LocalEnvironment/Destination/TCPIP/Output/Port | The port number used to make a connection. |
$LocalEnvironment/Destination/TCPIP/Output/Id | The ID of the socket being used. This ID is an internal identifier used by IBM Integration Bus to uniquely identify a connection. |
$LocalEnvironment/Destination/TCPIP/Output/ReplyId | The Reply ID that is stored on this connection. It can be any text string. |
$LocalEnvironment/Destination/TCPIP/Output/Timeout | The timeout value used when sending data to the TCP/IP server connection. This value overrides the Timeout sending a data record property specified on the node. |
You can dynamically select the connection details (host name and port number), and the connection used (ID), using these properties. The Reply ID can also be set on the connection, which enables a string to be stored in the connection and to be displayed in the local environment. This behavior can be used to store Reply IDs from other TCPIP nodes or from other transports such as WebSphere® MQ.
The output of the node contains the same information as the input, and any fields that are missing from the input are updated with details from the connection used. For example, if the Id property is not provided as input (because you want to create a connection or reuse a pool connection), the output local environment contains the ID of the connection that is used.
Location in local environment | Description |
---|---|
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/Hostname | The host name used to make a connection. |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/Port | The port number used to make a connection. |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/OpenTimestamp | The time stamp when the connection was first opened. |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/CloseTimestamp | The time stamp when the connection was closed (null if not yet closed). |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/SequenceNumber | The sequence number of the message received on this connection. The first record has a sequencing number 1, the second record has a sequencing number 2, and so on. |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/Id | The ID of the socket being used. This ID is an internal identifier used by IBM Integration Bus to uniquely identify a connection. |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/ReplyId | The Reply ID that is stored on this connection. It can be any text string. |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/ClientDetails/Hostname | The fully qualified domain name of the computer from which the client connected. |
$LocalEnvironment/WrittenDestination/TCPIP/Output/ConnectionDetails/ClientDetails/Address | The IP address of the computer from which the client connected. |
If the connection closes (or any other type of exception occurs) while using the TCP/IP transport, an exception is thrown. This exception goes to the Failure terminal if it is connected, otherwise the exception goes back down the message flow.
The node also has a Close input terminal. If a message is sent to this terminal, the connection is closed using a combination of the details provided in the node and the local environment.
The TCPIPServerOutput node is contained in the TCPIP drawer of the palette and is represented in the workbench by the following icon:
You can view information about samples only when you use the product documentation that is integrated with the IBM Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration Toolkit.
When you have put an instance of the TCPIPServerOutput node into a message flow, you can configure it (for more information, 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 in that view.
To configure the TCPIPServerOutput node:
The TCPIPServerOutput node terminals are described in the following table.
Terminal | Type | Description |
---|---|---|
In | Input data | The input terminal that accepts a message for processing by the node. |
Close | Input control | The input terminal to which a message is routed when the connection given in the local environment is closed. |
Out | Output data | The output terminal to which the message is routed if it is successfully sent to an external resource. The message received on the In terminal is propagated to the Out terminal and is left unchanged except for the addition of status information. |
Close | Output control | The output terminal to which a message propagated from the Close input terminal is routed. |
Failure | Output data | The output terminal to which the message is routed if a failure is detected in the node. |
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 for deployment).
Property | M | C | Default | Description |
---|---|---|---|---|
Node name | No | No | TCPIPServerOutput | 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 TCPIPServerOutput node are described in the following table:
Property | M | C | Default | Description | mqsiapplybaroverride command property |
---|---|---|---|---|---|
Connection details | Yes | Yes | A string containing the port number to be used, or the name of a configurable service. | connectionDetails | |
Timeout sending a data record (seconds) | Yes | Yes | 60 | Specifies how long the node waits when trying to send data. You can specify any length of time in seconds. | timeoutSendingData |
The Advanced properties of the TCPIPServerOutput node are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Close connection | Yes | No | No | Controls when the connection is closed, or if
it remains open. Valid options are:
|
Close output stream after a record has been sent | Yes | No | Cleared | Specifies whether to close the output stream as soon as the data has been sent. By default, this property is not selected. |
Output Stream Modification | No | No | Leave unchanged | Specifies whether to reserve this output stream
or release it and return it to the pool for use by any output node.
Valid options are:
|
Input Stream Modification | No | No | Leave unchanged | Specifies whether to reserve the input stream
for use only by input and receive nodes that specify the connection
ID, or to release the input stream at the end of the flow. Valid options
are:
|
Send to: | Yes | No | One connection | Specifies whether the data is to be sent to
one connection or to all available connections. Valid options are:
|
The Request properties of the TCPIPServerOutput node are described in the following table:
Property | M | C | Default | Description |
---|---|---|---|---|
Data location | Yes | No | $Body | The location in the input message tree that contains the record to be written. |
Port location | Yes | No | $LocalEnvironment/Destination/TCPIP/Output/Port | The message element location that contains the port. |
ID | Yes | No | $LocalEnvironment/Destination/TCPIP/Output/Id | The message element location that contains the ID. |
Reply ID location | Yes | No | $LocalEnvironment/Destination/TCPIP/Output/ReplyId | The message element location that contains the Reply ID. |
The Records and Elements properties of the TCPIPServerOutput node are described in the following table:
Property | M | C | Default | Description |
---|---|---|---|---|
Record definition | Yes | No | Record is Unmodified Data | This property controls how the
records derived from the message are written. Valid options are:
|
Length (bytes) | Yes | No | 0 | The required length of the output record. This property applies only when Record definition is set to Record is Fixed Length Data. |
Padding byte (hexadecimal) | Yes | No | 20 | The two-digit hexadecimal byte to be used to pad short messages when Record definition is set to Record is Fixed Length Data. |
Delimiter | Yes | No | Broker System Line End | The delimiter to be used when Record definition is set to Record is Delimited Data. Valid
options are:
|
Custom delimiter (hexadecimal) | No | No | None | The delimiter byte sequence to be used when Record definition is set to Record is Delimited Data and Delimiter is set to Custom Delimiter (Hexadecimal). |
Delimiter type | Yes | No | Postfix | This property specifies the way
in which the delimiters are inserted between records when Record definition is set to Record is Delimited Data. Valid
options are:
|
The Validation properties of the TCPIPServerOutput node are described in the following table.
For a full description of these properties, see Validation properties.
Property | M | C | Default | Description | mqsiapplybaroverride command property |
---|---|---|---|---|---|
Validate | No | Yes | Inherit | This property controls whether validation takes
place. Valid values are:
|
validateMaster |
Failure action | No | No | Exception | This property controls what happens if validation
fails. You can set this property only if you set Validate to Content or Content and Value. Valid values
are:
|
Property | M | C | Default | Description |
---|---|---|---|---|
Events | No | No | None | Events that you have defined for the node are
displayed on this tab. By default, no monitoring events are defined
on any node in a message flow. Use Add, Edit,
and Delete to create, change or delete monitoring
events for the node; see Configuring monitoring event sources using monitoring properties for details. You can enable and disable events that are shown here by selecting or clearing the Enabled check box. |