Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Channels and Destinations : Mapping Incoming Messages to Non-default Events

Mapping Incoming Messages to Non-default Events
Incoming messages can be mapped to a default event that you specify when you configure the destination. (See Default Destinations and Default Events in TIBCO BusinessEvents Architect’s Guide for more details). You can also map incoming messages to specified event types.
Two 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
These fields are added and filled automatically for events created using TIBCO BusinessEvents rules. You can also add these fields to messages coming in from other sources, if you have control of those messages.
See also:
Mapping of HTTP Request URI to Destination
Mapping of SOAP Request URI to Destination
Specifying Default and Non-Default Destinations

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved