Scribd
Upload
26 views3 pages

Event Processor Quick Reference Guide

Uploaded by

Ravindra Sarang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
26 views3 pages

Event Processor Quick Reference Guide

Uploaded by

Ravindra Sarang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

QUICK REFERENCE GUIDE

Event Processor R106.1

1.1 Overview
About
Event Processor component is used for creating an Event, processing the event against expressions, and
triggering the corresponding action, which can be one of the following:
 Send the event to the Notification component
 Send the event to a Windows client application.
 Take any customized action.
Event Processor component comprises of:
 Event Processor Model
 Event Service
 Event Processing Service
Event Processor Model is a standard Intuition Model, which contains entities for storing events, event
schema, and the expressions and rules against which the events are processed. All supported Create,
Update, Read and Delete (CURD) operations for all entities are exposed through the Data Access Service
and OData Service.
Event Service is WCF service used for Read & Write events, event types, expression and rules, and so on.
Event Processing Service is a Windows service, which runs in the back ground and processes the events
created in the Event Processor Model in a scheduled frequency. The scheduled time is configurable and by
default, the background process is scheduled to run for a scan frequency of 20 seconds.

1.2 Installation
Prerequisites
 .NET Framework 4.0
 Core System 280.1
Note: Compatible with custom database name feature of core system
Procedure
Double-click the Setup.exe for the component and follow the onscreen instructions to install the
component.
Note: If Intuition Core System is installed in https mode, then the Event Processor component is also
installed in https mode automatically. For more details about installing Intuition Core System in https
mode, refer to “Pre Installation Tasks - Enable HTTPS for Core System (Optional)” in Intuition Core
System User’s Guide.

1.3 Expression Formation and Supported Operators


Following section has the details about the supported operators and expression with examples:
Event Processor Supported Operators
 ‘>’ (eg: NumericField1>4)
 ‘< ‘(eg: NumericField2<4)
 ‘=’ (eg:Asset=Plant)
 ‘>=’ (eg: NumericField1>=4)
 ‘<=’ (eg: NumericField2<=4)
 ‘.Like’ (eg: StringField.Like* )
Event Processor Supported Expression
 Single Expression (Eg: Asset=Plant1)
 Multiple Expression with And Clause (Eg:
[Asset=Plant1]&&[NumericField1>4]&&[KPIName=Utilization])
 Multiple Expression with OR Clause (Eg:
[Asset=Plant1]||[NumericField1>4]||[KPIName=Utilization])
 Multiple Expression with both AND & OR Clause (Eg: [Asset=Plant1|Asset.Like
Plant23*]&&[NumericField1>4&NumericField2>10]||[KPIName=Utilization])

1.4 Integrating with the application


Overview
Applications need to define their Event Schema in the “Event Type” entity of Event Processor Model for
using the event processing capability against their schema. The steps for integration are detailed in the
following sections.
Steps involved
1. Create an Event Type for the application in XML format. Sample schema shown below
<?xml version="1.0" encoding="utf-8"?><xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:element
name="Events"><xs:complexType><xs:sequence><xs:element
name="Event"><xs:complexType><xs:sequence><xs:element
name="Category"><xs:simpleType><xs:restriction base="xs:string"><xs:enumeration
value="Alarm"/><xs:enumeration value="OperatorAction"/><xs:enumeration
value="System"/><xs:enumeration value="OperatorMessage"/><xs:enumeration
value="ProcessAlert"/></xs:restriction></xs:simpleType></xs:element><xs:element
name="Condition" type="xs:string" /><xs:element name="EventID" type="xs:string" /><xs:element
name="ExtendedData"><xs:complexType><xs:sequence><xs:element name="FromValue"
/><xs:element name="ToValue" /><xs:element name="LimitValue" /><xs:element
name="ColorType" /><xs:element name="Comment" /><xs:element name="CommentedBy"
/><xs:element name="Parameter" /><xs:element name="UnitOfMeasure" /><xs:element name="Area"
type="xs:string" /><xs:element name="Plant" type="xs:string" /><xs:element name="Unit"
type="xs:string" /><xs:element name="TagDescription" type="xs:string" /><xs:element
name="DASEntitySet" type="xs:string"
/></xs:sequence></xs:complexType></xs:element><xs:element
name="Severity"><xs:simpleType><xs:restriction base="xs:string"><xs:enumeration
value="Low"/><xs:enumeration value="High"/><xs:enumeration value="Urgent"/><xs:enumeration
value=""/></xs:restriction></xs:simpleType></xs:element><xs:element name="SeverityNumber"
type="xs:string" /><xs:element name="Source" type="xs:string" /><xs:element name="Time"
type="xs:string" /><xs:element name="Location" type="xs:string"
/></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element>
</xs:schema>
2. Define an Event Subscription and its Rule with the Expression through the Event Service.
3. Create Events through the Event Service.
4. Event Processing Service will process the events and evaluate the Rule Expressions.
5. The processed events that match the expressions are notified as per their Event Subscription Type
(for example, for EventSubscriptionType ‘MESNotification’ a corresponding Notification will be
triggered).
Overriding the default values
The character limit restriction in the Event Service parameters is configurable. To override the default
value, update the respective entry of application setting in the Event Service web config file available in the
following path:
$Installpath\Honeywell\MES\EventProcessor\Service\EventService\1.0 \Web.config
For Example:
<add key="MaxLengthEventData" value="20000"/>
Table Sql columns Default value App setting name
Events EventData 15000 MaxLengthEventData

Events KeyContextName 100 MaxLengthKeyContextName

Events KeyContextValue 100 MaxLengthKeyContextValue

EventSubscriptions Subscriber 500 MaxLengthSubscriber

EventSubscriptions SubscriberName 200 MaxLengthSubscriberName

EventSubscriptions Context 100 MaxLengthContext

EventSubscriptions ParentSubscriber 500 MaxLengthParentSubscriber

EventTypeSubscriptionRules Expression 8000 MaxLengthExpression

Events &
DirectSubscriptionID 500 MaxLengthDirectSubscriptionID
EventTypeSubscriptionRules

1.5 Localization
Event Processor Component has a Translation Tool Project file (TTP) named “EventProcessor.ttp”
available in the media under the Localization folder.
Output Location of Resource files
Toolkit Resource DLL Target Location
Project
[install path]\Honeywell\
EventProcess Honeywell.MES.Service.EventProcessor.EventServ
MES\EventProcessor\Service\EventService\
or.ttp ice.Resource.dll 1.0\Bin\<lang>

You might also like