What do the settings in "Include Event Type" drop down in your destination mean and do they help supress _ns_, _nm_ in messages going out of TIBCO BusinessEvents (BE) 5.2.
Article ID: KB0093271
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
The four settings for "Include Event Type" control the behavior for the HTTP, EMS and RV channels.
1). "When Serializing and Deserializing" is the original behavior which always includes _ns_ and _nm_ fields.
2). "Only when Serializing" is for BE event to JMS message conversion for
an outgoing JMS messages BE will set the ns and nm headers in the JMS
message. If receiving messages with this setting, the ns and nm fields
will be ignored.
3). "Only when Deserializing" the ns and nm fields will be suppressed when sending messages. When receiving messages if the fields are present in the incoming message, they will be used.
4). "Never" behavior is incorrect and BE-22481 has been filed to correct this behavior. Ideally, when you set "Never", the _ns_ and _nm_ should be suppressed/not used when sending and receiving messages.
Note: These settings will work as above with Pattern.IO.toDestination() . If all BE systems use "Only when Deserializing", then no messages will contain the _ns_ and _nm_ properties.
Issue/Introduction
Feedback
