Channel Types

One project can have multiple channels of different types with multiple destinations.

You can choose from the following types of channels:

TIBCO Rendezvous channels
They connect TIBCO BusinessEvents to TIBCO Rendezvous sources and sinks.
Local channels
They connect co-located agents at runtime.
JMS channels
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.
HTTP channels, 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).
Hawk channels
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.
ActiveSpaces channels
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.
TCP channels
They connect to data sources not otherwise available through channels, using a catalog of functions.