Facade Operation Requests

Overview of transports for the facade operation.

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 the 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 the Core Engine is not exposed to the external HTTP client. Usage of RV module requires each instance of the 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.