IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Receiving a file using IBM Sterling Connect:Direct

Use the CDInput node to receive files from an IBM® Sterling Connect:Direct® network.

Before you start:

Read IBM Sterling Connect:Direct overview and concepts.

Multiple CDInput nodes can be deployed to the same integration server, or to different integration servers in the same broker. Multiple CDInput nodes can read files transferred to the same directory without contention. Each file is processed only once, even if the nodes are deployed to separate integration servers.

On z/OS®, when the CDInput node receives notification of the arrival of a dataset that it should process, the node copies that dataset into Unix System Services temporarily, before processing.

Complete the following steps to create a CDInput node message flow using the default settings. The task includes some optional steps for additional configuration, but detailed information about configuring the CDInput node is given on the property panels for the node, in the IBM Integration Toolkit. The default settings assume that you have a Connect:Direct server running on the same machine as the broker, and that you are using the default ports.

Drag a CDInput node onto a message flow and wire its Out terminal to an output node of your choice.
Optional: To process only a defined subset of files, configure the Basic panel. This action allows multiple CDInput nodes in the same integration server to receive specific files, depending on the directory or file filters specified.
You can also specify whether, after processing, the file is left in its directory, renamed, or deleted.
To change how the node handles a message flow failure, configure the Retry panel.
Optional: To change how records are identified in the input file, configure the Record detection property on the Records and Elements panel. For example, you might want to specify that a record is fixed length, and set the record length.
1. If you set the Record detection property to anything other than Whole File, drag an additional output node to the flow, such as the MQOutput node. Wire the End of Data terminal on the CDInput node to the In terminal of the MQOutput node. The node connected to the End of Data terminal receives an empty message when the last record in the file is read.
Optional: To process the file based on details of the transfer, place a node such as the Route node after the CDInput node. Details of the transfer are stored in the local environment, at LocalEnvironment.CD.
Setup the username and password that is required for the CDInput node to connect to the primary Connect:Direct server using the mqsisetdbparms command.
Add the flow to a broker archive (BAR) file and deploy the BAR file.
For information on how to use configurable services with IBM Sterling Connect:Direct, see Advanced configuration properties when using IBM Sterling Connect:Direct nodes.
Use IBM Sterling Connect:Direct to send a file to the local Connect:Direct server. The CDInput node processes this file.

bc14050_.htm |

Last updated Friday, 21 July 2017