Channel Types
One project can have multiple channels of different types with multiple destinations.
You can either create an custom channel using the provided custom channel API or choose from the following types of channels:
- ActiveSpaces 3.x channel
- TIBCO ActiveSpaces software is a distributed in-memory data grid product. It can notify applications like TIBCO BusinessEvents of changes to the rows stored in a table which can be transformed into TIBCO BusinessEvents events. For more information, see the TIBCO ActiveSpaces documentation.
- ActiveSpaces channel
- They connect TIBCO BusinessEvents to TIBCO ActiveSpaces metaspace to enable it to monitor the activities in the metaspace, receive events from TIBCO ActiveSpaces and convert them into events in TIBCO BusinessEvents. A set of catalog functions are provided to control the type of the TIBCO ActiveSpaces events.
- FTL channel
- TIBCO FTL® messaging product is used for sending messages from one point to another. TIBCO BusinessEvents can send and receive events using TIBCO FTL as the medium. Using the FTL channel, TIBCO BusinessEvents can receive incoming TIBCO FTL messages and send TIBCO FTL messages across TIBCO BusinessEvents. You can use catalog functions in BusinessEvents to communicate with FTL.
- Hawk channel
- They connect TIBCO BusinessEvents to TIBCO Hawk domain to enable it to receive events from the Hawk monitor and transform them into events. A set of catalog functions are also provided which are used to control the Hawk microagents through Hawk APIs.
- HTTP channel, including SOAP support
- An HTTP channel acts as an HTTP server at runtime. This enables TIBCO BusinessEvents to serve requests from clients, and to act as a client of other servers. Support for SOAP protocol is provided by these features (using SOAP over HTTP):
- A specialized event type with a payload is configured as a skeleton SOAP message.
- A set of functions for extracting information from SOAP request messages and constructing response messages.
- A utility that constructs project resources based on the SOAP service’s WSDL file (document style WSDLs with literal encoding are supported).
- JMS channel
- They connect TIBCO BusinessEvents to TIBCO Enterprise Message Service provider sources and sinks.
- Kafka channel
- To send and receive messages from a Kafka broker TIBCO BusinessEvents uses Kafka channel. The Kafka channel converts the incoming Kafka messages to the BusinessEvents events and output BusinessEvents events to outgoing Kafka messages.
- Kinesis channel
- Amazon Kinesis Data Streams helps in real-time collection and processing of data records. By using the Amazon Kinesis channel, TIBCO BusinessEvents can convert Kinesis data streams to TIBCO BusinessEvents events.
- Local channel
- They connect co-located agents at runtime.
- MQTT channel
- MQTT is a machine-to-machine connectivity protocol that enables remote connections for IoT applications. By using the MQTT channel, TIBCO BusinessEvents can receive MQTT messages and transform them into TIBCO BusinessEvents events.
- StreamBase channel
- Using the StreamBase Channel a BusinessEvents application (StreamBase client) can connect to a StreamBase server. The BusinessEvents application can subscribe to StreamBase streams to receive (dequeue) messages from the StreamBase server and send (enqueue) messages to the StreamBase server.
- TCP channel
- They connect to data sources not otherwise available through channels, using a catalog of functions.
- TIBCO Rendezvous channel
- They connect TIBCO BusinessEvents to TIBCO Rendezvous sources and sinks.
See TIBCO BusinessEvents Developer's Guide for more information on how to create a custom channel for your project.
Copyright © Cloud Software Group, Inc. All rights reserved.