In TIBCO Business Events (BE), how to map the external messages from a non-BE application to a specified event type in BE?
Article ID: KB0092075
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
In TIBCO Business Events (BE), how to map the external messages from a non-BE application to a specified event type in BE?
Environment:
===========
BusinessEvents 3.x,4.x,5.x
All Operating Systems.
Resolution:
========
The external messages can be mapped to a specified event type by adding two fields in a message header.
The field named _ns_ takes a namespace as a value. The namespace points to the event type. Example: www.tibco.com/be/Ontology/Events/MyEvent .
The field named _nm_ takes the name of the event itself. Example: MyEvent .
These fields are added and filled automatically for events arriving from ActiveMatrix BusinessWorks using a Send Event activity and for events created using BusinessEvents rules.
Description:
===========
In TIBCO Business Events (BE), how to map the external messages from a non-BE application to a specified event type in BE?
Environment:
===========
BusinessEvents 3.x,4.x,5.x
All Operating Systems.
Resolution:
========
The external messages can be mapped to a specified event type by adding two fields in a message header.
The field named _ns_ takes a namespace as a value. The namespace points to the event type. Example: www.tibco.com/be/Ontology/Events/MyEvent .
The field named _nm_ takes the name of the event itself. Example: MyEvent .
These fields are added and filled automatically for events arriving from ActiveMatrix BusinessWorks using a Send Event activity and for events created using BusinessEvents rules.
Issue/Introduction
In TIBCO Business Events (BE), how to map the external messages from a non-BE application to a specified event type in BE?
Feedback
Yes
No
Powered by
