Event Tracking using Mule MMC Events

Author:GDS Sashidhar Rao

Email: gdssrao@gmail.com

Twitter: gdssrao

Auditing Implementation using DB component

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.

Mule Application

How Business event data will stored

MMC configured with event-tracking DB

event-tracking DB

Event Notification with meta-data

MMC persists event and it’s meta-data

Custom Business Event Component

MMC used DB Design for persisting events with PostgreSQL

Sample Business Event Configuration in Mule flow

Auditing Implementation using Business Events

MMC Transaction Summary Tab

Transaction Id

Transaction Specific Events Tab

Event meta data

Event specific Meta Data

Meta data for Fields specified in “Custom Business

Component”

Data in “transaction_summaries” table

Data stored in “event” table specific to transaction

Data stored in “event_properties” table specific to an event

Meta-key and Value records

Thank You