Receiving a file using IBM Sterling Connect:Direct
Use the CDInput node to receive files from an IBM® Sterling Connect:Direct® network.
Before you begin
- Read IBM Sterling Connect:Direct overview and concepts.
- Ensure that WebSphere® MQ is installed on the same machine as your integration node. Information about file transfers is held on storage queues that are controlled by WebSphere MQ, so you must install WebSphere MQ on the same computer as your integration node if you want to use the capabilities provided by the CDInput node.
- Ensure that a queue manager has been specified on the integration node; this queue manager will own the system queues that store information about the file transfer. For information about specifying a queue manager on the integration node, see mqsicreatebroker command.
- Create the system queues that will store the file transfer information. For more information about creating the system queues, see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
About this task
Multiple CDInput nodes can be deployed to the same integration server, or to different integration servers in the same integration node. 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 integration node, and that you are using the default ports.