Setting up the Collector Node sample

Change your IBM Integration Toolkit preferences

You must change your IBM Integration Toolkit preferences for the Test client from 120 seconds to 300 seconds:

1. Click Window > Preferences. The Preferences window opens.
2. In the left preferences pane, expand Integration Development.
3. Select Unit Test Client.
4. Change the value of the Seconds to wait for the test client to stop field from 120 seconds to 300 seconds.
5. Click Apply.

Create the directory and files that are read by the FileInput node

When configuring a FileInput or FileOutput node you must set the location of the directory from which to read or write files. In the node you can set an absolute path or set a relative path. If you set a relative path, you must set the MQSI_FILENODES_ROOT_DIRECTORY environment variable.

In this sample a relative path name of fileinput is set in the FileInput node fileinput. This property is set in the Input Directory property of the node, which is found in the Basic page when the node is configured in the Message Flow editor.

The root directory in this sample is:

• On Windows: c:\MQSIFileInput
• On Linux: /tmp/MQSIFileInput

You can choose a different root directory and set the environment variable MQSI_FILENODES_ROOT_DIRECTORY to your chosen directory instead.

1. Create the directories:
   • On Windows: Create the following directory structure: c:\MQSIFileInput\fileinput
   • On Linux: Create the following directory structure: /tmp/MQSIFileInput/fileinput
2. Set the environment variable MQSI_FILENODES_ROOT_DIRECTORY to the root directory.
   1. Follow the instructions at Setting up a command environment to create a command environment and a command file that contains the following line (ensuring that there is no white space around the equal (=) sign):
      • On Windows:

        SET MQSI_FILENODES_ROOT_DIRECTORY=c:\MQSIFileInput

      • On Linux:

        export MQSI_FILENODES_ROOT_DIRECTORY="/tmp/MQSIFileInput"

   2. Stop and restart your integration node. See Starting and stopping a broker.

You can now import and deploy the message flow to run the sample.

Note: When you import the sample, you might see error messages similar to Node has an unconnected Catch terminal in the Problems view of the IBM Integration Toolkit. This error message does not affect the behavior of the sample at runtime.

Back to sample home