High availability for the REST client

A minimum HA configuration for REST clients can be implemented with just two IBM® z/OS® Connect servers that run in a single LPAR.

High availability can be achieved with IBM z/OS Connect by the workload distribution of HTTP and HTTPS API and service requests from clients across several servers with shared configuration. For more information, see Connectivity for high availability and Sharing server configuration. To ensure that workload distribution can route requests to any configured IBM z/OS Connect server, the servers must be maintained as clones of each other. That is, the servers must have the same configuration with the same IBM z/OS Connect APIs, services, or API requesters deployed.

This scenario is built on the Create a server and connect to a System of record (SoR) scenario and implements high availability for IBM z/OS Connect by adding a second IBM z/OS Connect server. To simplify the configuration, the scenario describes how to define a configuration that is used by both servers.

Diagram showing a REST client requests passed to a Sysplex Distributor, and Port Sharing being used to connect to a z Subsystems Address Space via multiple IBM z/OS Connect servers

For a step-by-step example of how to implement high availability for inbound requests to two IBM z/OS Connect servers that use port sharing and shared configuration data, see Configure HA for connections to IBM z/OS Connect.

You can also design a more complex parallel sysplex solution with many IBM z/OS Connect servers that are spread across multiple LPARs. Such a configuration is described in High availability of IBM z/OS Connect servers.