Overview of the elastic deployment process and an example containerized topology.
Deploy API Gateway in containers
Understand the differences between container deployments (API Gateway 7.6.0 and later) and classic deployments (API Gateway 7.5.3 and earlier) and get answers to frequently asked questions (FAQ) about deploying API Gateway in containers.
Prerequisites and steps you must follow to set up your Docker environment.
Create a base Docker image containing an operating system and an API Gateway installation.
Steps to build an Admin Node Manager Docker image and start an Admin Node Manager container.
Steps to build an API Gateway Docker image and start an API Gateway Docker container.
Enable usage tracking for on-premise API management products purchased on a subscription basis.
Customize a container’s behavior at runtime.
Configure the API Gateway logging system to redirect the trace and traffic logs to
stdout instead of to separate files, allowing the logs to be read directly from each container by an external logging service (for example, Elastic Stack or Splunk).
Deploy API Manager or OAuth services in your API Gateway containers.
Create an API Gateway Analytics Docker image and start an API Gateway Analytics Docker container.
Use the API Gateway Manager web UI to operate and monitor API Gateways running in containers.
Develop and test APIs and policies in a development environment, and promote and deploy them in other environments (for example, preproduction and production).
Migrate an API Gateway or API Manager classic deployment to an elastic container deployment.
Upgrade your API Gateway or API Manager container deployment from 7.6.2 or later.
Apply a patch, update, or service pack (SP) to an API Gateway or API Manager container deployment.
Problems you might encounter when running API Gateway and API Manager in Docker containers, and possible solutions.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.