Provides three communication methods: SOAP, HTTP, and Socket.
It can connect with input sources such as sensors, smartphones, and SOA systems.
Allows input events and events output by complex event processing to be recorded.
When developing rules, the output destination of logging can be a Hadoop system (Hadoop collaboration), or a CEP Server.
Outputting a log to a Hadoop system allows events to be analyzed in it, and this can be harnessed in monitoring event trends and adding or modifying rules.
Allows input events to be processed rapidly with the pre-registration of a "rule definition" that describes how to filter input events and perform high-speed matching of events with master data.
Allows continuously generated events to be analyzed and assessed in real time with the pre-registration of a "rule definition" that describes detection patterns for input events.
Allows external data to be referenced from complex event processing.
Allows cache data stored in Terracotta to be referenced as external data. It also enables cache data to be added, updated, or deleted when an event occurs.
Allows data registered in a relational database to be referenced as external data.
Allows events output by complex event processing to be sent to a user-developed Web service by using the SOAP listener, and to be processed by a user-developed Java class by using the custom listener.
There are also the logging listener (which can be used to store the events output by complex event processing in a Hadoop system), and the debug log listener (which can be used to output the results of complex event processing to a log, for debugging purposes).
