Event Framework Components
- Last UpdatedJun 10, 2024
- 1 minute read
The following table describes the main components of AVEVA Work Tasks Event Framework
|
Event Framework Components |
Description |
|---|---|
|
EventProviders |
This is the main component of Event Framework. This component is used to handling specific events. You need to create different event providers to handle your events. All event providers need to implement an interface called IEventClientServiceProvider. There are two types of event providers. First type is hosted inside the Engine. You need to implement additional interfaces as follows:
|
|
EventPorts |
EventPorts can be considered as an endpoint for EventProviders. For example, for a wait for email event provider email need to be received from different sources such as POP3, or forwarding from Exchange Server. In each of this source EventPorts can be implemented. For a file watcher event provider, there will be different EventPorts which are watching different Folders. User can use IEventPort interface to implement EventPort. |
|
EventBinding |
This client side component is responsible for consuming events and alert workflow. You need to create an EventBinding for each interested events. EventBindings are stored in SKEventBinding table. |
|
EventParameter |
This is the correlation parameter which filters events and its interested EventBindings. Every event provider has a set of EventParameters. Using these parameters, it will filter eventbindings interested to the specific provider events. |
|
EventItem |
This is an event message container component. The Event Framework is designed to support any type of events such as file system event provider, share point event provider, email event provider, and so on. |