Mapping Incoming Messages to Non-default Events

Incoming messages can be mapped to default events or to specified event types.

The fields in a message header instruct TIBCO BusinessEvents to map the incoming message to a specified event type:

• The field named _ns_ takes a namespace as a value. The namespace points to the event type, for example, www.tibco.com/be/ontology/Events/MyEvent
• The field named _nm_ takes the name of the event, for example, NewMyEvent
• The field named _extid_ takes the unique external id of the event.

These fields are added and filled automatically for events created using TIBCO BusinessEvents rules. You can also add these fields to the incoming messages from other sources if you have control of those messages. You can also use the Include Event Type field in the destination of channel to suppress the original behavior of including _ns_ and _nm_ fields during serialization and deserialization.