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


Chapter 4 Channels and Destinations : Selecting a Serializer

Selecting a Serializer
For each type of channel (except local channels), TIBCO BusinessEvents uses a serializer to convert events to messages and a deserializer to convert incoming messages to events. Local channels do not require serializers. HTTP channels also provides you the option of using action rule functions on the message instead of converting messages to event using deserializer.
Figure 1 Serializer and Deserializer Behavior
When you configure a destination, you select the appropriate serializer. (It actually includes the serializer and deserializer).
For JMS and Rendezvous messages, different serializers are available for different needs. For details see Selecting a JMS Serializer and Working with Rendezvous Channels.
For HTTP, and SOAP, specific serializers are used. See Mapping of HTTP Requests to Events, with the REST serializer for HTTP channel configuration. See Configuring TIBCO BusinessEvents as a SOAP Server and Client for more on SOAP.
For TIBCO ActiveSpaces tuples, the AS Serializer is used. See Working with ActiveSpaces Channels for ActiveSpaces channel configuration.
For TIBCO Hawk, see Working with the Hawk Channel for details.
Deploy-time Configuration
In the Cluster Deployment Descriptor, you specify what destinations an agent listens to at runtime, and you configure the destinations with an event preprocessor (as needed) and threading options. See the section Configuring Collections of Rules, Rule Functions, and Destinations.

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