A broker operates in between an event source and the CEP Engine, facilitating their connection. There are four types of broker adapters configured in the CEP by default as WS Event, Local, JMS and Agent. WSO2 CEP also supports custom brokers through its pluggable architecture.
WS-Event Broker
Can be used to send and receive XML/SOAP messages as WS-Events. Follow Configuring WS-Event Broker for configuration details.
Local Broker
A type of WS-Event Broker that is shipped within the CEP. When the local broker is used, CEP uses the local transport to receive events from the broker and send events to the broker. Follow Configuring Local Broker for configuration details.
JMS Broker
Can be any JMS broker. Using the JMS broker, any type of XML, Text and Map events can be sent as JMS events via the JMS transport. Follow Configuring JMS Broker for configuration details.
Agent Broker
Handles WSO2 common events. Agent broker can receive events over Thrift using TCP, SSL, HTTP, and HTTPS, and it can also receive JSON events via HTTP and HTTPS. WSO2 CEP is shipped with an Agent Broker which is used to receive fired events and handover them to CEP using Local Transport. From CEP, we can send output events to any Agent Broker using Thrift over TCP, SSL, HTTP, or HTTPS. Follow Configuring Agent Broker for configuration details.
Note
Only the Agent Broker that is shipped with CEP (internal Agent broker) can be used to receive incoming events, but CEP can send output events to any (including external) Agent brokers.
E-mail Broker
Email broker can send Text Messages via a configured e-mail account. This cannot be used to receive incoming messages. Follow Configuring E-mail Broker for configuration details.