Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# 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 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.
Legacy ActiveSpaces channel
They connect TIBCO BusinessEvents to Legacy ActiveSpaces metaspace to enable it to monitor the activities in the metaspace, receive events from Legacy ActiveSpaces and convert them into events in TIBCO BusinessEvents. A set of catalog functions are provided to control the type of the Legacy 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.
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.
Note: Each JMS Input Destination Runs a Session. Every JMS destination that is configured to be an input destination runs in its own JMS Session. This provides good throughput on queues and topics for processing, and less connections.
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.
Pulsar channel
To send and receive messages from a Pulsar broker, use the Pulsar channel. The Pulsar channel converts the incoming Pulsar messages to BusinessEvents events and transforms BusinessEvents events as outgoing Pulsar messages.
Local channel
They connect co-located agents at runtime.

See TIBCO BusinessEvents Developer Guide for more information on how to create a custom channel for your project.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.