...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
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.
Given below are the different profiles available in WSO2 API Manager.
| Tip |
|---|
Note the following:
|
...
| Profile | Command Option with Profile Name | Description |
|---|---|---|
| Gateway manager | -Dprofile=gateway-manager | Starts only the components related to the API Gateway. You use this when the API Gateway acts as a manager node in a cluster. This profile starts |
front end/UI features such as login as well as backend services that allow the product instance to communicate with other nodes in the cluster. | ||
| Gateway worker | -Dprofile=gateway-worker | Starts only the components related to the API Gateway. You use this when the API Gateway acts as a worker node in a cluster. This profile only starts the backend features for data processing and communicating with the manager node. |
| Key Manager | -Dprofile=api-key-manager | Starts only the features relevant to the Key Manager component of the API Manager. |
| API Publisher | -Dprofile=api-publisher | Starts only the front end/backend features relevant to the API Publisher. |
| API Store | -Dprofile=api-store | Starts only the front end/backend features relevant to the API Store |
...
| . |
Execute the following commands to start a product on any profile:
| OS | Command |
|---|---|
| Windows | <PRODUCT_HOME>/bin/wso2server.bat -Dprofile=<preferred-profile> --run |
| Linux/Solaris | sh <PRODUCT _HOME>/bin/wso2server.sh -Dprofile=<preferred-profile> |
How multi-profiling works
...