This documentation is for WSO2 API Manager 2.0.0 View documentation for the latest release.
Page Comparison - Deploying API Manager as an All-in-One Instance (v.19 vs v.20) - API Manager 2.0.0 - WSO2 Documentation
Provide Feedback

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Setting up on WSO2 API Cloud, which is a subscription based API Management solution. You can access this service by creating an account in WSO2 API Cloud.

  2. If you are interested in setting up an all-in-one API Manager instance on-premise, you can download the latest version of API Manager and follow the instructions given below to set up the instance.

Prerequisites

HardwareEnsure that the minimum hardware requirements mentioned in the hardware requirements section are met. Since this is an all-in-one deployment, it is recommended to use a higher hardware specification. You can further fine tune your operating system for production by tuning performance. For more information on installing the product on different operating systems, see Installing the Product.
Software

Oracle JDK 1.8

You can deploy API Manager in 3 different ways, 

...

In this setup, API traffic is served by one all-in-one instance of WSO2 API Manager.

 


ProsCons
  • Production support is required only for a single API Manager node (you receive 24*7 WSO2 production support).
  • Deployment is up and running within hours.
  • Can handle up to 43 million API calls a day (up to 500 API calls a second)
  • Minimum hardware/cloud infrastructure requirements (only one node).
  • Suitable for anyone new to API Management.
  • Deployment does not provide High Availability.
  • Not network friendly. Deploying on DMZ would require a Reverse Proxy.

Active/passive deployment

In this setup, API traffic is served by one active all-in-one instance of WSO2 API Manager and one passive all-in-one instance of WSO2 API Manager.

ProsCons
  • The system is highly available.
  • Production support is required only for a single API Manager node (you receive 24*7 WSO2 production support).
  • Can handle up to 43 million API calls a day (up to 500 API calls a second).
  • Deployment is up and running within hours.
  • Not network friendly. Deploying on DMZ would require a Reverse Proxy.
  • Switch over time from active node to passive node, in case of a failover.

Active/active deployment

In this setup, API traffic is served by two all-in-one instances of WSO2 API Manager.

 


ProsCons
  • The system is highly available.
  • Production support is required for 2 API Manager nodes (you receive 24*7 WSO2 production support).
  • Can handle up to 86 million API calls a day (up to 1000 API calls a second)
  • Deployment is up and running within hours.
  • Not network friendly. Deploying on DMZ would require a Reverse Proxy.

Deploying an all-in-one API Manager instance to serve external API traffic

...

For information on how to manually configure production servers, see Configuring a Single Node, Configuring an Active-Active Deployment and Configuring an Active-Passive Deployment.For information on how to configure production servers using Puppet scripts, see Configuring Production Servers Using Puppet.