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 webMethods API Gateway containers and Elasticsearch containers.

Clustered API Gateway containers and Elasticsearch containers

To run clustered webMethods API Gateway containers and Elasticsearch containers

Set the environment variables to define image for the webMethods 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 webMethods API Gateway Docker image. You can create the webMethods API Gateway image through webMethods API Gateway scripting.

Specify the webMethods API Gateway image by changing the .env file. webMethods API Gateway uses the .env file when the working directory is .../samples/docker-compose, else you must specify the environment variables.
Run the following command to start clustered webMethods API Gateway and Elasticsearch containers using the Docker Compose sample file:
```
cd InstallDir/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 webMethods API Gateway Docker container and the Elasticsearch container using the Docker Compose sample file with the following command:

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