Adding a Destination to a Channel
Destinations in a channel represent listeners to messages from that channel. They can also send messages to the resource. One channel can have multiple destinations. Each is shown in the Destinations section of the Channel editor.
- Procedure
- If it is not already open, open the editor for the channel to which you want to add a destination. To open the channel editor, double-click the channel name in the BusinessEvents Studio Explorer view.
- In the Destinations section, click Add.
- Enter a Name and Description for the destination.
- In the Default Event field, browse to and select the event to be created (by default) from incoming messages received by this destination. If you have not yet created the event, you can select the default event later.
- In the
Serializer/Deserializer field, select the appropriate class. See the following sections for more details:
For JMS destinations, see TIBCO BusinessEvents Architect’s Guide.For Rendezvous destinations, see TIBCO BusinessEvents Architect’s Guide.For HTTP and SOAP destinations, Adding a Destination (Destination configuration is the same for SOAP and HTTP destinations). See Manually Creating Resources to Work with SOAP Services and Creating Resources Using the WSDL Import Utility for more information about creating SOAP channels and destinations)For Hawk destinations, The Hawk channel allows TIBCO BusinessEvents to receive events from the Hawk monitor and transform them to events in TIBCO BusinessEvents.For StreamBase destinations, see StreamBase ChannelFor Kafka destinations, see Kafka Channel Serializers.For Kafka Streams destinations, see Kafka Streams Channel SerializersFor Legacy ActiveSpaces destinations, Working with Legacy ActiveSpaces Channels.
Various fields appear, depending on your selection.
For FTL destinations, select com.tibco.cep.driver.ftl.serializer.FTLSerializerFor MQTT destinations, see MQTT ChannelFor ActiveSpaces destinations, see ActiveSpaces ChannelFor Kinesis destinations, see Kinesis Channel - (For Rendezvous, JMS, and HTTP only)
In
Include Event Type, select when to use the
_ns_
and_nm_
fields from the following options:When serializing and deserializingOnly when serializingOnly when deserializingNeverFor more details about this property, see Destination Resource Common Properties. - Complete the rest of the properties for the type of destination you are creating. See Destination Resource Reference for details.
- Save the project.