The document discusses using Mule MMC for event tracking. It recommends that every flow have entry and exit events, and each business condition/state have a business event specific to the service implementation. MMC can be configured with an event-tracking database to persist events and metadata. The database design stores event data in tables for transaction summaries, events, and event properties. This allows auditing of transactions and retrieval of event metadata through MMC's user interface.

1. Event Tracking using Mule MMC
Events
Author:GDS Sashidhar Rao
Email: gdssrao@gmail.com
Twitter: gdssrao

2. Auditing Implementation using DB
component

3. Purposed Event characteristics
• Every flow should have entry and exit events.
• For each and every business condition/state of the
flow, we need a business event.
• All this Business events are specific to one Service
Implementation.
• All the Business events used within in one particular
flow should have the same event name.
• Mete data keys that needs stored against an event
within one Service Implementation are same.
• Event Name specific to a flow should be unique.

4. Mule Application
How Business event data will stored
MMC
configured with event-tracking DB
event-tracking
DB
MMC persists event and it’s meta-data
Custom Business Event Component

5. MMC used DB Design for persisting
events with PostgreSQL

6. Sample Business Event Configuration
in Mule flow

7. Auditing Implementation using
Business Events

8. MMC Transaction Summary Tab
Transaction
Id

9. Transaction Specific Events Tab
Event meta data

10. Event specific Meta Data
Meta data for
Fields specified in
“Custom Business
Component”

11. Data in “transaction_summaries”
table

12. Data stored in “event” table specific
to transaction

13. Data stored in “event_properties”
table specific to an event
Meta-key and
Value records

14. Thank You