Monitoring BPEL PM and BPEL processes

In the previous sections, we learnt how to discover BPEL PM and BPEL processes. We saw that the discovery process is different for BPEL PM running on different J2EE containers. The good news is that the monitoring aspect is the same, irrespective of the underlying J2EE container.

Monitoring BPEL PM

We know that BPEL PM runs on top of a J2EE container, uses Oracle database as a dehydration store, and that traffic to BPEL PM is routed through some HTTP gateways. To effectively monitor BPEL PM, we need to monitor all related components along with BPEL PM. Performance and availability of any related component can affect the performance and availability of BPEL PM. Collectively, we refer to BPEL PM and related components such as the BPEL eco system.

We learnt in Chapter 5,Managing Oracle Application Server, about System and Service constructs. Using system construct, we can group all such related targets as one system. To monitor the system we can also define...