The new publish/subscribe based Dynamic Event Framework (DEF) event transport mechanism since Business Monitor v 8.5.5 exposes REST and JMS interfaces to receive BAM (Business Activity Monitoring) events instead of the earlier CBE format (Common Base Events) events required by Common Event Infrastructure (CEI) server. The purpose of this project is to expose an ESB service that can connect to Monitor server on REST and JMS interfaces. Advantage of this approach include a common reusable BAM emitter service that can be invoked by all transaction/technology components while minimizing the changes required if underline monitor model changes. We have a common ESB service developed in IBM Integration Bus (IB) which is exposed as a REST API. The REST service can receive events in JSON and XML content types.
The scenario in discussion here is: we receive customer information verification request through ESB (IB). After, request is received by IB, a new process application instance is created in BPM (using IBM Process Designer - PD) so that information verification team can view, verify and provide suitable feedback/remarks against the specific request. For verifying customer’s information an existing service developed using IBM Integration Designer (ID) is used. A business transaction starts when the request is received by ESB (IB) and ends when response (remarks) is received back by IB from BPM application (PD). The three involved sub systems developed in IB, PD and ID invoke common IB service to send their start and end BAM events to Monitor server which helps to track current transaction progress/status. The Remarks provided by Verification team are also updated in BAM for record.

If you are interested to read further, you can read full post here:
https://www.linkedin.com/pulse/business-activity-monitoring-ibm-monitor-flows-using-bus-haider-raza?trk=pulse_spock-articles