Routing Overview

Overview of the routing functionality of TIBCO API Exchange Gateway

The routing capabilities of TIBCO API Exchange Gateway determine the target operation to process a facade request. TIBCO API Exchange Gateway uses the routing key to route a facade request to either one of the following:

  • Target Operation

    A target operation is an external operation which is called by the gateway to process a facade request.

  • Target Operation Group

    A target operation group is used to group multiple target operations, which helps the Core Engine to balance the load of requests processing across target operations. See Target Operation Group.

When the Core Engine routes the facade request to a target operation group, an appropriate target operation within the target operation group is selected, based on the type of the target operation group. See Types of Target Operations Group for details.

A routing key is used to determine the target operation or a target operation group to process an incoming facade request. See Routing Key for the details.

TIBCO API Exchange Gateway provides options to derive a routing key.

Content Based Routing

When the routing key is generated from the content (data) of the request message, the routing is defined as content based routing. The generated routing key is used to route the client request to a target operation or target operation group.

Context Based Routing

When the routing key is derived from the HTTP or JMS header fields in the request context message, the routing is defined as context based routing. The generated routing key is used to route the client request to a target operation or target operation group.