Each A&E Eventtype (e.g. Simple, Tracking, Condition) has an associated set of Eventcategories which are intended to define groupings of A&E Events. For example, Level and Deviation are possible Eventcategories of the Condition Eventtype for an A&E COM Server. However, since A & C does not explicitly support Eventcategories, the A&E COM UA Proxy uses A & C Eventtypes to return A&E Eventcategories to the A&E COM Client. The A&E COM UA Proxy builds the collection of supported categories by traversing the type definitions in the address space of the UA A & C Server. Figure D.3shows the mapping as follows:

  • A&E Tracking categories consist of the set of all Eventtypes defined in the hierarchy of subtypes of AuditEventType and TransitionEventType, including AuditEventType itself and TransitionEventType itself.
  • A&E Conditioncategories consist of the set of all Eventtypes defined in the hierarchy of subtypes of ConditionType, including ConditionTypeitself.
  • A&E Simple categories consist of the set of Eventtypes defined in the hierarchy of subtypes of BaseEventTypeexcluding AuditEventTypeand ConditionTypeand their respective subtypes.

image045.png

Figure D.3– Example mapping of UA Event Types to COM A&E categories

Category name is derived from the display name Attributeof the Nodetype as discovered in the type hierarchy of the UA A & C Server.

Category description is derived from the description Attributeof the Nodetype as discovered in the type hierarchy of the UA A & C Server.

The A&E COM UA Proxy assigns Category IDs.