Running Clustered API Gateway Containers and external Elasticsearch Containers

In this deployment scenario you can use the sample Docker Compose file apigw-elasticsearch-cluster.yml.

The following diagram depicts a set-up that has clustered API Gateway containers and external Elasticsearch containers.

To run clustered API Gateway containers and external Elasticsearch containers

1. Set the environment variables to define image for the API Gateway Docker container as follows:

export APIGW_DOCKER_IMAGE_NAME=image name or filepath location of an existing image

The composite file requires the API Gateway Docker image. You can create the API Gateway image through API Gateway scripting. For details on creating a Docker image, see Building the Docker Image for an API Gateway Instance .

Specify the API Gateway image by changing the .env file. API Gateway uses the .env file when the working directory is .../samples/docker-compose, else you must specify the environment variables.

2. Run the following command to start clustered API Gateway and external Elasticsearch containers using the Docker Compose sample file:

cd SAG-Root/IntegrationServer/instances/default/packages/WmAPIGateway
/resources/samples/docker-compose
docker-compose -f apigw-elasticsearch-cluster.yml up

In the Docker Compose sample file apigw-elasticsearch-cluster.yml ensure that you have specified the required information such as image name, name and port of the Elasticsearch host, server port, and UI port. This creates and starts the containers. Run the docker ps command to view the details of the containers created.

To run it in the detached mode, append -d in the docker-compose command.

Note:
You can stop the API Gateway Docker container and the external Elasticsearch container using the Docker Compose sample file with the following command:

docker-compose -f apigw-elasticsearch-cluster.yml down