com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.
Deploying WSO2 API Manager
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
Owned by Former user (Deleted)
In a typical production environment, you set up the different WSO2 API Manager (WSO2 API-M) components (API Publisher, Store, Gateway, Key Manager, and Traffic 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.
The following topics explain the deployment aspect of WSO2 API Manager in detail.
- Deployment Patterns
- Deploying API Manager using Single Node Instances
- Using Puppet Modules to Set up WSO2 API-M
- Distributed Deployment of API Manager
- Configuring the Proxy Server and the Load Balancer
- Installing and Configuring the Databases
- Configuring rsync for Deployment Synchronization
- Configuring WSO2 Identity Server as a Key Manager
- Deploying API Manager with Kubernetes or OpenShift Resources
- Configuring Admin App Event Publishing for Traffic Manager HA Setup
- Minimum High Availability Deployment for WSO2 APIM Analytics
- Deploying WSO2 API Manager with Multiple Datacenters
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.