When a WSO2 product starts, it starts all components, features and related artifacts bundled with it. Multi-profile support allows you to run the product on a selected profile so that only the features specific to that profile along with common features start up with the server.
| Tip | |||||
|---|---|---|---|---|---|
Starting a product on a preferred profile only blocks/allows the relevant OSGI bundles. As a result, even if you start the server on a profile such as the
|
| Table of Contents |
|---|
API-M Profiles
...
| Profile | Command Option with Profile Name | Description |
|---|---|---|
| Gateway worker | -Dprofile=gateway-worker -DworkerNode=true | Only starts the components related to the API Gateway. You use this when the API Gateway acts as a worker node in a cluster. This profile starts the backend features for data processing and communicating with the manager node. |
| Key Manager | -Dprofile=api-key-manager | Only starts the features relevant to the Key Manager component of the API Manager. |
| Traffic Manager | -Dprofile=traffic-manager | Only starts the features relevant to the Traffic Manager component of the API Manager. The Traffic Manager helps users to regulate API traffic, make APIs and applications available to consumers at different service levels, and secure APIs against security attacks. The Traffic Manager features a dynamic throttling engine to process throttling policies in real-time, including rate limiting of API requests. |
| API Publisher | -Dprofile=api-publisher | Only starts the front end/backend features relevant to the API Publisher. |
| Developer Portal (API Store) | -Dprofile=api-store | Only starts the front end/backend features relevant to the Developer Portal (API Store). |
...