API Gateway 10.3 | Configuring API Gateway | Docker Configuration | Configuring an API Gateway Docker Container Cluster
 
Configuring an API Gateway Docker Container Cluster
You can combine API Gateway Docker containers to form a cluster.
*To configure an API Gateway Docker container cluster
1. Configure loadbalancer on the docker host.
The custom loadbalancer is installed on the docker host. For more details on setting up the loadbalancer, see Configuring an API Gateway Cluster.
2. Configure Terracotta Server Array
API Gateway requires a Terracotta Server Array installation. For details, see webMethods Integration Server Clustering Guide and Terracotta documentation ( https://www.terracotta.org/generated/4.3.4/pdf/bigmemory-max/BigMemory_Max_Installation_Guide). The Terracotta Server Array on its own can be deployed as a Docker container.
3. Create the basic API Gateway docker image.
For details on creating the API Gateway docker image, see Building the Docker Image for an API Gateway Instance .
4. Create cluster API Gateway docker image and enhance it with the cluster configuration.
a. Adapt Integration Server configuration (SoftwareAG\IntegrationServer\instances\default\config\server.cnf).
b. Adapt the wrapper configuration (SoftwareAG\profiles\IS_default\configuration\custom_wrapper.conf).
c. Adapt the Internal Data Store configuration (SoftwareAG\InternalDataStore\config\elasticsearch.yml).
For more details about the above configurations, see API Gateway Cluster Configuration
The resulting docker file is used to create a docker image is_apigw_cluster.
5. Run API Gateway docker cluster
Each container represents a cluster node. Ensure to start all containers together so that Internal Data Store instances running in the Docker containers can form a cluster.