Working with Rendezvous Channels
The type of the event from which the outbound message is serialized is added to the Rendezvous message header using _nm_ and _ns_ fields so that if the message is used in TIBCO BusinessEvents again, the correct event type is used to deserialize the message (ignoring the default event specified for the destination).
Note that the Rendezvous serializers use UTF8 encoding for XML payloads.
For TRA file updates required for Rendezvous and JMS channels that use TIBCO Enterprise Message Service, see TIBCO BusinessEvents Administration.
Rendezvous Message Header
For Rendezvous messages, the only header that TIBCO BusinessEvents interprets is _sendsubject_ of type String. It is a read-only property. The event has to define this property to receive the value. The value is the actual Subject on which the message was sent.
- Deserializing from Rendezvous Message to Event
First level Rendezvous property values are used as values for matching event properties. Any additional (non-matching) Rendezvous properties are ignored. - Serializing from Event to Rendezvous Message
Event properties are transformed to first level Rendezvous message properties. - Avoding REGISTRATION COLLISION RVCM Advisory Messages
REGISTRATION COLLISION RVCM Advisory Messages should be avoided.