The mapping rule for extended data elements in a CBE could cause them to have the same attribute name in the Enterprise Console event, which is not allowed by the event server. The mapping mechanism eliminates that possibility by discarding extended data elements with names that collide with the name of Enterprise Console attribute names or with the name of another extended data element that has already been mapped into the Enterprise Console event.
As an example, consider a CBE event with the following extended data elements
<CommonBaseEvent ...> <extendedDataElements name="msg" type="string"> <values>my value</values> </extendedDataElements> <extendedDataElements name="slot1" type="string"> <values>my value</values> <children name="def" type="int"> <values>123</values> </children> </extendedDataElements> <extendedDataElements name="slot1.def" type="string"> <values>456</values> </extendedDataElements> ... </CommonBaseEvent>
The resulting attributes, and corresponding values, in the Enterprise Console event would be:
slot1.def=456
The extended data element named "msg" is not mapped because the Enterprise Console attribute "msg" is already mapped from other attribute in the CBE event.
The extended data element "slot1.def" is not mapped because the extended data element named "def" inside the extended date element named "slot1" is already mapped to a Enterprise Console attribute named "slot1.def".
Mapping extended data elements to Enterprise Console event class attributes