Once event data is acquired, it is converted into a native EPN (Event Processing Network) event and processed by one or more Occurrence EPN nodes. Occurrence EPN node features can be enabled independently on each node within the EPN depending on the deployment and processing requirements.

Event Zero has created three predefined EPN roles to address the most common implementation scenarios: Director, Edge Collector and Relay

• Edge Collectors are used to collect and process events from one or more agents.Typically deployed in situations involving high throughput or remote locations, edge collectors pre-process raw events from agents and relay the resulting event to another node for processing
• Relays are used to offload event encryption and compression processing to a dedicated node in extremely high throughput scenarios.
• Directors are top level EPN nodes designed to manage subordinate nodes, archive events, and analyze events using CEP rules. Event data is made available to external applications via the publish/subscribe interface.

Regardless of the deployment scenario, all Occurrence nodes utilize the following services:

• Persistent event queue – store and forward for all events being processed by the node
• Configuration – framework for remote node configuration
• Security – network, system, event, and user security

The following services may also be enabled on any Occurrence Node depending on the desired function or role for the node:

• Event Relay – to/from other EPN nodes
• Profile Engine – convert raw event data into a native event using conversion rules contained in the event profile
• Enrichment Engine – add data to the event based using enrichment rules contained in the event profile
• CEP Engine – perform event analysis, state management, and summarization on incoming events
• Event storage – archive incoming events
• Publish/Subscribe API – communication channel for external applications

>> return to top