Baseline™ Track and Trace

Tracking messages through an integration platform without some kind of tooling is extremely complex, since it will typically involve sifting through various log-files on different machines. Correlating all those log-entries to determine e.g. why a particular message got stuck can be very tedious and time consuming.



Baseline Track and Trace puts a common framework across all components involved in mediating a message (typically various adapters and ESB middleware). Each component will be configured to create Baseline metadata events in the form of messages. Those messages will be centrally collected using the common connectivity infrastructure (typically WebSphere MQ) and read into a database. The Baseline Track and Trace web application will then present all events collected into transactions. A transaction will contain all events relating to a specific message that is being sent through the platform, even if the message is duplicated and/or split. Using Baseline Track and Trace you can query the database with questions like "What happened to order number 1234?". You will be able to determine exactly what component in the whole chain caused the message to fail.



You can configure Baseline Track and Trace to only show failed transactions, thus making it easy for support personnel to determine the status of the whole integration platform at a glance.