Log out?

Exercise 3.5 – Triggering Listeners

Purpose:

To practice triggering a Listener that’s not currently running to run from a previous Route.


Steps:

  1. Create the Routes
    1. From the eiConsole File Management screen, select the “Add Route” button.
    2. In the dialog that appears, enter the name “Trigger1 – Send Trigger” and select “OK”.
    3. Select the “Add Route” button again, enter the name “Trigger2 – Receive Trigger”, and select “OK”.
    4. Both Routes should now be in the table in the “File Management” screen.


  2. Configure “Receive Trigger” (The Second Route)
    1. The second Route needs to be configured first, since it is referenced in the first Route.
    2. Double click on “Trigger2 – Receive Trigger” to open it to edit.


  3. Receive Trigger – Document Source System
    1. Select the “Source System” stage in the “Route Editing Grid”. The configuration panel will appear at the bottom.
    2. Change the “System Name” to “XML File”
    3. Select the “Choose Source Icon” button, and scroll down to select one of the XML icons


  4. Receive Trigger – 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. Change the “Listener Name” to “ReceiveTrigger.Listener”.
    4. Assign a polling directory, using the “…” button to open the file chooser. The polling directory should NOT be the directory with all the sample files, since files will be moved/deleted by the listening process.
    5. Select the “Advanced” tab, and check the box that says “Initialize on trigger only”.


  5. Receive Trigger – Configure the 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. Select the “Target Directory”, using the “…” button to open the file chooser.
    4. Set “output” as the “Target File Name”.
    5. Set “xml” as the “Target File Extension”.


  6. Receive Trigger – Document the 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 “XML File”.
    3. Select the “Choose Target Icon” button, and scroll down to select one of the XML icons.


  7. Configure “Send Trigger” (The First Route)
    1. Save all changes and go back to the File Management.
    2. Double-click on “Trigger1 – Send Trigger” to open it to edit.


  8. Send Trigger – Document Source System
    1. Select the “Source System” stage in the “Route Editing Grid”. The configuration panel will appear at the bottom.
    2. Change the “System Name” to “None”.
    3. Leave the icon alone.


  9. Send Trigger – Configure the Listener
    1. Select the “Listener” stage in the “Route Editing Grid”. The configuration panel will appear at the bottom.
    2. Select “Null (Empty/Trigger)” 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. Set a “Trigger Interval” of 1 minute.


  10. Send Trigger – Configure the Transport
    1. Select the “Transport” stage in the “Route Editing Grid”. The configuration panel will appear at the bottom.
    2. Select “Listener Trigger” 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 configuration panel, select the “…” button next to the “Target Listener” field to open the “Listener Dialog”
    4. Find the listener called “Trigger2 – Receive Trigger::ReceiveTrigger.Listener” from the selection box, and choose it. Click OK to save and close the dialog.


  11. Send Trigger – Document 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 “None”.
    3. Leave the icon alone.


  12. Prepare to Test
    1. Save all changes.
    2. Copy the file called “people.xml” from the “Samples” directory provided into the directory chosen as the polling directory.
    3. Open the “eiPlatform Emulator” by going to the menu bar at the top of the screen, and selecting “Route” -> “Local eiPlatform Emulator”.
    4. In the “eiPlatform Emulator Management” dialog, select the “Configure Emulator” option.
    5. In the “EIP Emulator Settings” dialog, select the “Disable All” button at the bottom of the left hand table panel. Nothing should be checked in the left-hand “Run” column.
    6. Find the two Routes created in this exercise in the left hand table panel. Select the “Run” checkbox to the far left of their rows, so that those two are the only ones with checkmarks in that column.
    7. Click the “Apply and Close” button in the bottom right of the dialog to save the changes.


  13. Perform the Test
    1. Select the “Start Emulator” button from the “eiPlatform Emulator Management” dialog. The main panel should start displaying log output.
    2. The log output should stop shortly after it begins, and for the first minute very little should happen. The “people.xml” file should remain untouched in the polling directory.
    3. After a minute, the first Route should execute. When it finishes, it triggers the listener of the second Route. When this happens, the “people.xml” file should be removed from the polling directory.
    4. When log output stops, the emulator has finished processing the two Routes.
    5. In the OS File Explorer, open the directory selected as the “Target Directory”. The file “output.xml” should be there, with contents identical to the “people.xml” input file.


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


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

Thanks!

Our editors are notified.

Close