Overview

This section gives an overview and configuration setup of the deployment of runtime components with multiple instances for load balancing and high availability.

The administrators deploy two or more instances of the Core Engines in production to achieve high availability through load balancing. That is, a load balancer routes request messages to multiple Core Engine instances. The Core Engines together can handle more messages than just one Core Engine instance running. Also, such deployment makes the runtime components highly available to process the requests with minimum or no down time. The Core Engine instances, thus, share the load of requests when large number of requests are received from the clients.

All the runtime components of the TIBCO API Exchange Gateway are deployed in the same cluster except the Central Logger component. The Central Logger instance must be running in a separate cluster.

Overview Of Deployment

Figure Overview of Runtime components For High Availability shows a high level overview of a deployment model of runtime components in a cluster for high availability setup.

Overview of Runtime components For High Availability