API-M Distributed Deployment - Overview

Before deploying WSO2 API Manager (WSO2 API-M), let's understand how the WSO2 API-M distributed deployment works. According to the recommended deployment patterns, a distributed deployment includes API-M server nodes that separately run the API-M profiles. An API-M profile is a server instance that only runs specific components of the API-M server.

API-M Profiles

Listed below are the different profiles available in WSO2 API Manager.

Profile Description
Gateway Profile

Only starts the components related to the API Gateway.

Use this when the API Gateway acts as a worker node in a cluster. This profile starts the backend features for data processing and communicates with the management node.

Control Plane Profile Starts all the API-M components (Traffic Manager, Key Manager, Publisher, Developer Portal) excluding the Gateway.
Traffic Manager Profile Only starts the Traffic Manager component.

Databases used by API-M profiles

When you run the API-M server as separate profiles, databases are used as shown below.


API Manager
database

apimgtdb

WSO2_AM_DB

Shared Database

shareddb

WSO2_SHARED_DB

Control Plane profile

Used

Used

Gateway profile

Not used

Used (in multi-tenancy mode/ in multiple gateway mode when Google Analytics is used)

Traffic Manager profile Used Used

API-M Components

Listed below are the five components in the API-M server. When you run the recommended API-M profiles, the components (from the below list) that are required for operating the functionalities related to each profile are used.

Component Description
Gateway Responsible for securing, protecting, managing, and scaling API calls.
Key Manager Responsible for all security and key-related operations.
Traffic Manager Used to make a decision on throttling. It also works as an event hub for broadcasting controller events such as throttling events, block conditions, revoke token retrieval events, API events, API policy events, application events, application policy events, application keys events, subscription events, and subscription policy events.
Publisher Enables API providers to easily publish their APIs, share documentation, provision API keys, and gather feedback on API features, quality, and usage.
Developer Portal Enables consumers to self-register, discover API functionality, subscribe to APIs, evaluate them, and interact with API publishers.

What's Next?

Top