Transaction monitoring
When monitoring transactions, the goal is to achieve two purposes:
Identifying transactions that have not been completed successfully to determine further action
Ensuring that the transactions do not experience poor performance
When a payload is received by the SOA Infrastructure, it may pass through multiple components within your infrastructure and may even traverse multiple external systems as well. For example, a sales order may be received by a BPEL process, which in turns places it into a queue. Afterwards, it may be consumed by some third-party application that processes the sales order, before sending it back to another Mediator service, which routes it to the final order management application. If any one of the above steps in this particular integration fails, how can you identify where the message is? What would also be important to you is to know the time taken by each component to determine if it is inline with your predefined SLAs.
In this section, we will...
