Deployment Architecture

This section describes the various options to deploy the Core Engine and other components.

TIBCO API Exchange Gateway is deployed as a cluster of engines that act as a single logical gateway. The engines in the cluster can run on a single server or in a distributed environment across multiple physical or virtual servers, providing fine-grained control over the cluster deployment topology.

TIBCO Rendezvous/TIBCO ActiveSpaces is used for communication between most of the runtime components of both the gateway operational layer and the gateway management layer. The gateway operational layer and all its components share a single set of configuration files. Therefore, the configuration files should be stored on a shared storage device that is accessible to each of the runtime components.

When multiple instances of the Core Engine are deployed in a cluster, multiple instances of cache-agents are also instantiated. This deployment has a single distributed cache that is shared across all the core engines to support association and response cache functionality.