You can manage the event flow in your network topology by using the WebSphere® Sensor Events Administrative Console to work with event templates and output channels.
WebSphere Sensor Events uses an event format called the IBM® Sensor Event. When the Data Capture and Delivery controller captures an event from a device, the event is converted to the IBM Sensor Event format. That format is then converted to sensor event XML and sent to the WebSphere Sensor Events sensor event gateway. The WebSphere Sensor Events sensor event gateway pushes the event to the WebSphere Application Server service integration bus (SIBus), ibmsensorevent, where WebSphere Sensor Events task agents are listening for events.
WebSphere Sensor Events task agents are message-driven beans (MDBs). They process events by registering with WebSphere Application Server for the desired topics. When a topic arrives, the MDB receives the event and processes it. A Persistence Manager listens on the SIBus for all messages destined for WebSphere Sensor Events or the Data Capture and Delivery controller. When the Persistence Manager captures an event, it either persists the event to a local database or it can persist the event to the Electronic Product Code Information System (EPCIS) using the EPCIS Connector reusable component.
A Complex Event Processing (CEP) engine also listens on the SIBus for certain events. When it receives an event, the CEP engine responds either by generating a new event, which is pushed to the SIBus, or by calling actions that start processes on WebSphere Process Server.
You can use the WebSphere Sensor Events Toolkit to develop your own use case. For more information refer to the WebSphere Sensor Events Toolkit documentation.