Integration Engine Solutions to Connect Anything to Anything

Log out?

Purpose:

To practice using routing to determine which Target systems a transaction is sent to



Create a Route

    1. From the eiConsole File Management screen, select the Add Route button.
    2. In the dialog that appears, enter the name Routing and select OK.
    3. The Route should now appear in the table on the screen. Double-click it to open it.

Configure the Listener

    1. Select the Listener stage in the Route Editing Grid. The configuration panel will appear at the bottom.
    2. Select Directory / File from the Listener Type selection box. Optionally, click the button to open the Module Search Dialog, which provides a faster way to find the module you’re looking for.
    3. Assign a polling directory, using the button to open the file selector. The polling directory should NOT be the directory with all the sample files, since files will be moved/deleted by the listening process.
    4. Go to the Post-Process tab and select Delete from Postprocess Operation:

Configure the First Transport

    1. Select the Transport stage in the Route Editing Grid. The configuration panel will appear at the bottom.
    2. Select Directory / File from the Transport Type selection box. Optionally, click the button to open the Module Search Dialog, which provides a faster way to find the module you’re looking for.
    3. In the Transport Name field, change the name to TransportA.
    4. Select the Target Directory, using the button to open the file selector.
    5. Set outputA as the Target File Name.
    6. Set txt as the Target File Extension.

Document the First Target System

    1.  Select the Target System stage in the Route Editing Grid. The configuration panel will appear at the bottom.
    2. Change the System Name to Output File.
    3. Select the Choose Target Icon button, and scroll down to select one of the generic File icons.

Configure the Second Transport

    1. Click the Add Target button at the top of the screen to add a second target path.
    2. Select the Transport stage in the Route Editing Grid for the second target. The configuration panel will appear at the bottom.
    3. Select Directory / File from the Transport Type selection box. Optionally, click the button to open the Module Search Dialog, which provides a faster way to find the module you’re looking for.
    4. In the Transport Name field, change the name to TransportB.
    5. Select the Target Directory, using the button to open the file selector.
    6. Set outputB as the Target File Name.
    7. Set txt as the Target File Extension.Configure Transport

Document the Second Target System

    1. Select the Target System stage in the Route Editing Grid for the second target. The configuration panel will appear at the bottom.
    2. Change the System Name to Output File
    3. Select the Choose Target Icon button, and scroll down to select one of the generic File icons.

Configure the Routing Module

    1. Select the Route stage from the Route Editing Grid. The configuration panel will appear at the bottom.
    2. In the configuration panel, select the tab that says Routing Rules, to open the configuration for routing to multiple Transports.
    3. Enable the use of Routing Rules by selecting the XPath/Attribute option from the Routing Module selection box. The rules configuration panel will now appear.
    4. The left-hand section of the panel is the Rules Tree. It has only one Node right now, which simply says Rules.Add Routing Rules
    5. Configure the first Rule.
      • Select Add Rule. A new node, called Rule, should appear under it.
      • Select the Transaction Attribute Query in the Expression Field.
      • Select TransportA in the Transport Field.
      • Select the new Attribute node. A new configuration panel will appear to the right.
      • For Attribute Name, enter com.pilotfish.FileName. For Operator, make sure that = is selected. Finally, for Attribute Value, enter A. The expression is now configured.
      • The rule is now configured.Add Expression
    6. Configure the second Rule.
      • Select Add Rule. A new node, called Rule, should appear under it.
      • Select the Transaction Attribute Query in the Expression Field.
      • Select TransportB in the Transport Field.
      • Select the new Attribute node. A new configuration panel will appear to the right.
      • For Attribute Name, enter com.pilotfish.FileName. For Operator, make sure that = is selected. Finally, for Attribute Value, enter B. The expression is now configured.
      • The rule is now configured.Configure Second Rule

Prepare to Test

    1. In the menu bar at the top, select Mode -> Testing Mode. Make sure the changes to the Route are saved.
    2. Find the two sample files called A.txt and B.txt. Do NOT copy them to the polling directory yet.

Execute Test

    1. Copy the A.txt file to the polling directory, and select the Execute Test button at the top of the Testing Mode screen.
    2. If the Route was configured successfully, green checkmarks should appear across the screen. However, the path of the green checkmarks should only go to TransportA. Nothing should reach TransportB.
    3. Stop the test. Copy the B.txt file to the polling directory, and then select Execute Test again.
    4. If the Route was configured successfully, green checkmarks should appear across the screen. However, this time, the path of the green checkmarks should only go to TransportB. Nothing should reach TransportA.

Output Files

    1. Compare the results from the exercise with the following example output files to see if they are correct.

This is a unique website which will require a more modern browser to work! Please upgrade today!