An event processor can be used to monitor events within STEP. Each event processor has many parameters but most notably the collective configuration of a processing plugin, a processor queue, and event triggering definitions. These allow for the collected events to be logically processed, and actions automatically performed, based upon each event processor's specific configuration.
Event processors can be used to automatically perform actions based on triggering events, however much of what an event processor can do is controlled by the processing plugin. Before creating an event processor, you should know the processing plugin to be used. For a complete list of STEP processing plugins, see the Processing Plugins documentation here.
Before an Event Processor can be created / configured the one-time setup tasks described in the Initial Setup for Event Processors (here) must be completed to allow for the creation of event processors.
It is expected that anyone configuring an event processor is familiar with how and when events are generated. For more information, see the Events section of the System Setup / Super User Guide documentation here.
Setting up and using an event processor involves the following steps:
An event processor has no delivery method, but is otherwise similar to an event-based outbound integration endpoint (OIEP). Event processors can be used alone when the results are only required internally to STEP. However, if the delivery of the results of the event processor is required externally, the event processor can be used in conjunction with an OIEP. For more information, see the Outbound Integration Endpoints section within the Data Exchange documentation here.
Monitoring the progress of an event processor from an external system is available by way of a STEP Monitoring Sensor. For details, see the Monitoring an Event Processor via External System documentation here.
2018, Stibo Systems – Confidential