Event handling in Interlok consists of a single component default-event-handler which is responsible for publishing AdapterLifecycleEvents and MessageLifecycleEvents events when appropriate. default-event-handler wraps other standard components to fulfil its specialised role within Interlok, so where the event eventually goes is up your configuration.
When a standard lifecycle happens (e.g.
close()) then an associated AdapterLifecycleEvent is generated and published. These events are generated regardless of how the lifecycle is invoked, so JVM startup and JMX operations (e.g. via the UI) will cause the lifecycle event to be published.
As a message passes through a workflow and has various services operating on the contents, each Service will generate a marker event which is added to a MessageLifecycleEvent; this marker event captures the name of the Service and whether it was successful or not. At the end of the Workflow, this event is published as a record of the operations that happened on the Message in that workflow.
The default-event-handler may only be configured as part of the Adapter object; but will be injected into any Services that implement the EventHandlerAware interface. For our example we will configure a default-event-handler that publishes events to a JMS Topic called
<adapter> <event-handler class="default-event-handler"> <connection class="jms-connection"> .. skipped for brevity. </connection> <producer class="jms-topic-producer"> <destination class="configured-produce-destination"> <destination>events</destination> </destination> </producer> </event-handler> ... Other configuration skipped. </adapter>
- In this example the event is marshalled using the default marshaller (as defined by your bootstrap.properties; which is generally XML.
- You could explicitly configure an xstream-json-marshaller implementation, if you wanted your events to be JSON format
Adapter Lifecycle Events
The following list of standard AdapterLifecycleEvents are built into a standard distribution. Of these, standard-adapter-start-up-event and heartbeat-event may be overridden in configuration at the adapter level.
|adapter-shutdown-event||Fired when the adapter is terminated (usually by CTRL-C).|
|standard-adapter-start-up-event||Fired when the
|heartbeat-event||Fired on a periodic schedule and contains some information about various states|
|license-expiry-warning-event||Fired on a periodic schedule to indicate that the license is about to expire.|
Message Lifecycle Events
A MessageLifecycleEvent is always created whenever the message is created and will contain the message’s unique id. Marker Events are added to the MessageLifecycleEvent as services work on it; the MessageLifecycleEvents is published asynchronously at the end of the workflow, and errors during the publishing phase are simply logged and will not cause a failure of the message. If you have multiple workflows acting upon the same message then MessageLifecycleEvents can be correlated together via the message unique-id.
Each marker event will have a creation time (ms since the epoch) associated with it; and also a sequence number. Using the creation time is the preferred method of sorting, but we know that clocks are never in sync, so the sequence number is available as a fallback. Note that the sequence number will be unreliable if the message is retried; or if you publish the message to multiple other workflows simultaneously.
If you do not care about these types of events, then you can turn them off on a per workflow basis by setting
send-events=false on the workflows. Doing this may have a marginal performance improvement as the act of turning the internal object into a
String has some cost associated with it.