/
Deploying and Clustering the API Manager
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.
Deploying and Clustering the API Manager
- Former user (Deleted)
Owned by Former user (Deleted)
Last updated: Jan 10, 2016
In a typical production environment, you set up the different API Manager components (API Publisher, Gateway, Store and Key Manager) in separate servers so that you can scale them independently. You also install multiple instances of a component in a cluster to ensure proper load balancing. When one node becomes unavailable or is experiencing high traffic, another node handles the requests.
- For information on clustering, see Clustering WSO2 API Manager.
- For information on deployment patterns, see API Manager Deployment Patterns.
, multiple selections available,
Related content
Deploying and Clustering the API Manager
Deploying and Clustering the API Manager
More like this
Deploying and Clustering the API Manager
Deploying and Clustering the API Manager
More like this
Distributed Deployment of API Manager
Distributed Deployment of API Manager
More like this
Distributed Deployment of API Manager
Distributed Deployment of API Manager
More like this
Distributed Deployment of API Manager
Distributed Deployment of API Manager
More like this
Deploying WSO2 API Manager
Deploying WSO2 API Manager
More like this
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.