The Error Route Trigger Transaction Monitor is used when you would like to call another interface in the case of an error. This allows you to build arbitrarily complex error handling directly into an eiConsole or eiPlatform Interface. To configure an Error Route Trigger, select this option from the Transaction Monitor Type dropdown and click Add. It will appear in the main route grid.
On the Basic tab, you will see the Error Listener Name configuration item. This name should correspond to a programmatic or triggerable Listener in another interface or route that should be invoked any time an exception occurs. You can also select whether you would like to include the data of the Transaction as it appeared when the error occurred and the Transaction Attributes with that message. You can also decide whether or not you would like to pass the data along unaltered as the message itself.
On the Exception tab you can specify information that is used to filter when this particular Transaction Monitor will be invoked. For instance, you can enter the Exception Class Name in the Exception Class Name configuration item. This is the name of the Java exception that will trigger this particular Transaction Monitor. You can also enter information about text that the Exception Message must include or must not include. As well as the level of that exception.
On the Stage tab, you can choose to make this Transaction Monitor only applicable to certain stages within the route. To configure this, click the button … to the right of the Only Valid for Stage textbox.
Input the names of the stages for which this should be invoked. Then click OK.
Now that you’re familiar with the Error Route Trigger, take a moment to review the other two Transaction Monitors, if you haven’t already.