...
- Caching support is added to event table implementation. This improves performance. See Event Table Definitions.
- Capability to send events as HTTP requests using any HTTP client. Events can be of XML, JSON or TEXT formats. See Input HTTP Event AdaptorAdapter.
- Improvements to the debugging logs of CEP: when events are sent to streams that are configured with log adaptor, they get printed as INFO logs. For information, see /wiki/spaces/PS/pages/10518594Output Logger Adapter.
- Improvements to the debugging and monitoring functionality : graphical views to see the systematic flow of events in the CEP system. See CEP Event Flow.
- You can now quickly define event builders and event formatters without having to fill lengthy forms. Capability to pass events without doing mappings manually. You just need to send events that matche the defined stream definition in the event builder. If you select the default mapping for event formatters, the CEP sends events in a pre-defined format. For information, see Event Builders and Event Formatters.
- Introduction of the Kafka Input and Output event adapters. See Input Kafka Event AdaptorAdapter and Output Kafka Event AdaptorAdapter.
- Capability to process SOAP messages using a simple SOAP input/output adapter. See /wiki/spaces/PS/pages/10518553 and /wiki/spaces/PS/pages/10518558 Input SOAP Event Adapter and Output SOAP Event Adapter.
- Supports high availability by continuing event processing even when the active CEP node is down. Lets one CEP node be active while the redundant CEP node drops all notifications till the active node is processing. See
- Enhanced JMS output notifications with header properties. For information, see /wiki/spaces/PS/pages/10518559 Output JMS Event Adapter.
Improved real-time monitoring by creating and managing real-time gadgets in the CEP Dashboard. See an end-to-end usecase in Getting Started with CEP.
- Capability added to CEP to store realtime outputs in an RDBMS (MySQL, H2) in addition to the Cassandra based persistence store. See Event Table Definitions and Event Tables.
Compatible WSO2 product versions
The following products were tested for compatibility with WSO2 CEP 34.10.0:
- BAM 2.4.1
- ESB 4.8.1
- Message Broker 2.1.1
- Identity Server 4.6.0
WSO2 CEP 34.10.0 is based on WSO2 Turing Chunk 8 and is expected to be compatible with any other WSO2 product that is based on Carbon 4.2.0. If you get any compatibility issues, please contact team WSO2. For information on the third-party software required with CEP 34.10.0, see Installation Prerequisites.