Working with Rendezvous Channels

Warning: TIBCO Rendezvous channel has been deprecated and might be removed in the future release.

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.

Basic Serializer

The basic TibRvMsgSerializer serializer is used for efficient handling of events and messages that do not have payloads. It ignores payloads in messages and in events if any exist.

Serializer for Use with Payloads

To include a payload in a Rendezvous message, ensure that the message has a _payload_ field. To pass contents between the Rendezvous message _payload_ field and an event payload, use the TibRvMsgSerializerWithXMLPayload serializer.