Skip to content

RTGOV-605 Add eventProcessingMode and clockType Drools event processor d... #247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectiser merged 1 commit into from
Dec 5, 2014
Merged

RTGOV-605 Add eventProcessingMode and clockType Drools event processor d... #247

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/userguide/en-US/UGAnalyzingEvents.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -399,9 +399,9 @@ As previously mentioned, all EventProcessor implementations can define the follo
| Field | Description
| services | The optional map of names to services. The current service types are listed at the bottom of this section.
| parameters | The optional map of names to parameters. These parameters can be used to customize the behaviour of an event processor.
| asynchronous | This optional and *experimental* boolean flag enables an event processor to produce its results asynchronously. This has been added to support CEP, and currently means any results are processed as individual events which may be less efficient.
|=======================


Although custom event processors can be defined, there are some "out of the box" implementations. These are discussed in the following sub-sections.

==== Drools Event Processor
Expand All @@ -412,6 +412,8 @@ The Drools Event Processor implementation (+org.overlord.rtgov.ep.drools.DroolsE
|=======================
| Field | Description
| ruleName | The name of the rule, used to locate the rule definition in a file called "<ruleName>.drl".
| eventProcessingMode | This optional field identifies the event processing mode. Valid values are _cloud_ (default) and _stream_. If _stream_ is chosen, then you will also need to set the _asynchronous_ property to _true_.
| clockType | The optional clock type. Valid values are _realtime_ (default) and _pseudo_.
|=======================

An example of such a rule is:
Expand Down