Proxy Server

TIBCO API Exchange Gateway acts as a proxy server for facade operation requests and target operation responses. When you use the TIBCO API Exchange Gateway as proxy server, TIBCO API Exchange Gateway does not process or validates the incoming facade operation request. TIBCO API Exchange Gateway just forwards the facade operation request to the appropriate target operation. Similarly, for any response message from the target service, TIBCO API Exchange Gateway passes the response message to the client. For example, when an error response is returned from the target service, TIBCO API Exchange Gateway sends the error response to the client without modifying or customizing the error code and message. Using the proxy feature improves the performance of the request processing in TIBCO API Exchange Gateway.

Note: When TIBCO API Exchange Gateway is used as a proxy server and the user has not explicitly configured the response caching for a facade operation on the Config UI , TIBCO API Exchange Gateway provides the response caching with the default caching parameters, as follows:

Cache Type: SimpleCache

Time To Live: 1 day (24 hours)

You can configure the headers of the request message to be forwarded to the target operation.

To use TIBCO API Exchange Gateway as a proxy server, enable the proxy functionality as follows:

Procedure

  1. Start the Config UI, if not running.
  2. Log in to the Config UI using your credentials.
  3. Select the project under Projects.
  4. On the ROUTING tab, click Facade Operations on the top menu.
  5. Select an existing facade operation to be used by proxy server. If the facade operation does not exist, add a new facade operation.
  6. Select Operation Features field. Enter Proxy.
  7. Save changes to the configuration.