Exercise 3.6 – Transaction Monitors

Create the Routes

1. 1. From the eiConsole File Management screen, select the Add Route button.
   2. In the dialog that appears, enter the name Error1 – Main Route and select OK.
   3. Select the Add Route button again, enter the name Error2 – Error Route, and select OK.
   4. Both Routes should now be in the table in the File Management screen.

Configure Error Route (The Second Route)

1. 1. The second Route needs to be configured first, since it is referenced in the first Route.
   2. Double-click on Error2 – Error Route to open it to edit.

Error Route – Document Source System

1. 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 PilotFish Route
   3. Leave the icon alone.

Error Route – Configure the Listener

1. 1. Select the Listener stage in the Route Editing Grid. The configuration panel will appear at the bottom.
   2. Select Programmable (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. Change the Listener Name to ErrorRoute.Trigger.

Error Route – Configure the Transport

1. 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 selector.
   4. Set error as the Target File Name.
   5. Set xml as the Target File Extension.

Error Route – Document the Target System

1. 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.

Configure Main Route (The First Route)

1. 1. Save all changes and go back to the File Management.
   2. Double-click on Error1 – Main Route to open it to edit.

Main Route – Document Source System

1. 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

Main Route – Configure the Listener

1. 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:

Main Route – Configure the Transport

1. 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 selector.
   4. Set good-output as the Target File Name.
   5. Set xml as the Target File Extension.

Main Route – Document the Target System

1. 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

Main Route – Configure Exception Processor

1. 1. Select the Transport stage from the Route Editing Grid. From the top of the configuration panel, select the Processor Configuration tab.
   2. Click the Add Processor button in the new configuration panel. The Add Processor dialog will appear.
   3. Select the Exception Thrower Processor from the Processor 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. After clicking Add, the configuration panel will be updated. The processor will appear in the table in the middle, and its configuration items will appear in the bottom panel.
   5. Fill in the Message configuration field with Transaction failed.

Main Route – Configure Transaction Monitor

1. 1. Select the Route stage from the Route Editing Grid. The configuration panel will appear below.
   2. Select the Transaction Monitoring tab to bring up the Transaction Monitor configuration panel.
   3. Select the Add Transaction Monitor button to open the Add Transaction Monitor dialog.
   4. Select the Error Route Trigger monitor from the Transaction Monitor 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.
   5. After clicking Add, the configuration panel will be updated. The monitor will appear in the table in the middle, and its configuration items will appear in the bottom panel.
   6. Select the … button next to the Error Listener Name configuration field to open the Listener Dialog.
   7. From the selection box in the dialog, select the Listener called Error2 – Error Route::ErrorRoute.Trigger. Click OK to save the changes.

Prepare to Test

1. 1. Save all changes and return to the File Management screen.
   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 Tools -> 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.

Perform the Test

1. 1. Select the Start Emulator button from the eiPlatform Emulator Management dialog. The main panel should start displaying log output.
   2. In the log output, an exception stack trace should appear. The transaction should continue running after the exception, as it enters the error route.
   3. In the output directory, there should be a file called error.xml. This contains the default PilotFish error report.