When a CBE event is mapped to a Enterprise Console event class in the rule base, each context data element is mapped to two attributes in the resulting Enterprise Console event.
If both names of these two attributes do not match the name of an attribute in the the Enterprise Console event class definition, the context data element is discarded.
Table 1 illustrates the mapping of an CBE context data element to attributes in a Enterprise Console event.
Context Data Element sub-field |
Enterprise Console attribute |
---|---|
used on both attribute names |
|
value for one of the attributes created from the context data element |
|
contextDataElement.contextId |
value for one of the attributes created from the context data element |
Table 1. Mapping of CBE context data elements to Enterprise Console attributes.
The following sections explain in details how a CBE context data element is mapped to attributes in the Enterprise Console event:
A context data element is mapped to two attributes in the resulting Enterprise Console event:
ctx.contextDataElement.name=contextDataElement.value ctx.contextDataElement.name.type=contextDataElement.type
As an example, consider a CBE event with the following context data elements
<CommonBaseEvent ...> <contextDataElements name="myContext" type="String"> <contextValue>contextValue</contextValue> </contextDataElements> ... </CommonBaseEvent>
The resulting attributes, and corresponding values, in the Enterprise Console event would be:
ctx.myContext=contextValue ctx.myContext.type=String
If the mapped name of a context data element conflicts with the name of another attribute in the Enterprise Console event, the context data element is discarded. Refer to the topic "Name conflicts for context data elements" for more details.
Notes:As described in "Name", the type attribute in a context data element is used as the value of the second attribute created from the context data element.
As described in "Name", the contextValue and contextId attributes in a context data element are used as the value of the second attribute created from the context data element.
An event in CBE format can only have a contextValue or a contextId, and contextValue takes precedence over contextId. For that reason, if the original context data element has both values set (illegal according to the CBE specification), the conversion algorithm discards the contextId sub-field.
Name conflicts for context data elements
Converting an event in the Common Base Event format to Enterprise Console event format