The Event Bus streams event data from the Short Term Canister, the in-memory database, to your Tealeaf pipeline. The pipeline can then deliver the event data to any system configured to receive it. The ability to send the event data as a stream in real time makes the event bus useful for integrating with real-time systems.
The Event Bus runs out-of-band and does not affect the core Tealeaf processes.
Complex Event Processing (CEP) engines can receive the event bus data as a stream and run computations on the data to observe patterns and sequences on the data outside of the Tealeaf event infrastructure. The event bus data can be correlated against other enterprise data to create new and insightful correlations.
DecoupleEx session agent > Complex Event Processing engineDecoupleEx session agent > Socket session agent
If more processing is required on the Event Bus data, it should be forwarded to another pipeline, which by definition runs out-of-band of the Event Bus.
Event Bus pipeline
The default Event Bus pipeline includes DecoupleEx and Null as active session agents. You can configure the Event Bus through TMS.
The Null session agent ends delivery of event data. Nothing happens until an appropriate destination is enabled in the pipeline.
The configuration file is TealeafEventBus.cfg and is in the Tealeaf installation directory (<Installed drive>\Tealeaf). You can modify this file as needed to send the event bus data to the appropriate session agent for further processing and transmission of the data to a receiving system.
Sending events to the Event Bus
For event data to be delivered to the event bus, you must select Send to Event Bus in the More Options step of the event definition in the Event Manager. This check box must be selected for each event that you want to send to the Event Bus.