Charge Workflow implemented as a Fiorano ESB Application

BTI Canada's first Fiorano ESB Workflow enabled them to track commitments made to their internal cards by the travel counsellors in Real Time BTI Canada built XML configuration files listing Credit Card numbers and made the booking applications parse these files Each time a card usage was detected.

BTI Canada captures the current screen or web page as well as the following two pages so that they are able to track back who the booking was for and how much was spent. All this is placed into an XML document and sent to Fiorano ESB through a "ChargeListener" running as a servlet on a web server Chargelistener Fiorano ESB Service

This receives the XML messages sent by BTI Canada Booking applications (Custom 4GL application and/or customized browser). LogActivity1 Fiorano ESB Service – It is responsible for tracking for whom and when exactly a charge was created (Ghost Card used). It then transfers this data into a database "log". In this case, BTI Canada mostly logs Travel Counsellor Activity to build accountability.

ChargeWorklist Fiorano ESB Service – BTI Canada needed to gather all the incoming messages into one Fiorano ESB service so that their business users could verify them one by one (through a web page) and eventually validate each of them. They therefore defined a new Component called a Worklist.

A "Worklist" is a servlet running on a J2EE web server and acts as a "message accumulator". The Accumulator is queried through an XML API over HTTP. The XML API allows building customized Web pages to hide XML details from the users. Users can then verify the accuracy of the data, make comments and changes and finally let the message go to the next task. Here is a "Business User Interface" with the list of charges recently captured by BTI Canada booking applications and sitting in the worklist:

LogActivity2 Fiorano ESB Service

This service once again checks the messages and tracks who and when the previous operation was performed. In this case, BTI Canada logs QA people and supervisors responsible for verifying the accuracy of the information entered in the system. The messages are transferred into a database for reporting purposes. Further reporting web pages were build for the Finance Department and BTI Canada Call Center Division. Once again, changes to BTI Canada applications were very easy to achieve. This was achieved by downloading the list of credit cards, capturing three screens (terminal screens or web pages), building an XML message and sending it to the "ChargeListener". To handle errors BTI Canada attached mail and display components to each RDBMS. (For Adapters ON_EXCEPTION out port.) This way the system administrator is notified as soon as the Database link encounters any problem. This functionality is later added to the custom made Fiorano ESB Components. In this first Phase, Fiorano ESB is not used to perform processing but is used to monitor the work being done by Travel Counsellors and Applications. This non-intrusive approach provides a great value by reporting inconsistencies within existing Business Processes.

a. Booking Workflow implemented as a Fiorano ESB Application

b. Sample of a Document sent to Fiorano ESB by the booking Application