Copyright © Cloud Software Group, Inc. All Rights Reserved

Overview

TIBCO API Exchange Gateway supports various transports for inter-component communications, as follows:

Facade Operation Requests

For the facade operation requests, TIBCO API Exchange Gateway supports the following transports:

HTTP

The Core Engine has the native HTTP Channel, which can receive requests out of the box. The native HTTP Channel can be used in conjunction with Apache HTTP server as described in Configure Apache HTTP Server as Reverse Proxy section. The native HTTP Channel is the most straight forward configuration option for handling the HTTP requests.

Rendezvous (RV)

The HTTP requests can be sent to the Apache HTTP server, which communicates with the Core Engine using the RV module. The RV communication between the Apache RV module and the Core Engine can be configured to initiate the connection from Core Engine to the RV module to provide securer network topology. The RV transport used internally between RV module and Core Engine is not exposed to the external HTTP client. Usage of RV module requires each instance of Core Engine to be pairs with a dedicated Apache server.

JMS

The client can send either SOAP or non-SOAP requests over the JMS transport. Use the JMS transport to send the requests to the Core Engine when the reliable messaging is important.

Central Logger

The Central Logger component of the TIBCO API Exchange Gateway supports the following transports:

Rendezvous (RV)

When the RV transport is used for the Central Logger, the Core Engine sends the log reports to the Central Logger using RV channel. The log reports are lost if the Central Logger is not running.

JMS

When the JMS transport is used for the Central Logger, the Core Engine sends the log reports to the Central Logger using JMS channel. The log reports are retained if the Central Logger is not running.

AS

When the AS transport is used for the Central Logger, the Core Engine sends the log reports to the Central Logger using ActiveSpaces channel.

Global Throttle Manager

The Global Throttle Manager component of the TIBCO API Exchange Gateway supports the following transports:

Rendezvous (RV)

When the RV transport is used for the Global Throttle Manager, the Core Engine communicates with the Global Throttle Manager using RV channel.

AS

When the AS transport is used for the Global Throttle Manager, the Core Engine communicates with the Global Throttle Manager using AS Channel. When AS transport is configured for Global Throttle Manager, the Central Logger must use the AS transport.

The following table summarizes the supported transports for the components of TIBCO API Exchange Gateway:

Table 18 Transports For Intercomponent Communication

Transport	Engine	CL	GTM
HTTP	X
JMS	X	X
RV	X	X	X
AS		X	X

Copyright © Cloud Software Group, Inc. All Rights Reserved