...
| 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 frontend/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 -DworkerNode=true | 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 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. |
Note that the WSO2 products platform currently doesn't block/allow Web applications depending on profiles. 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 api-store for example, you will still be able to access the API Publisher Web application.
Execute the following commands to start a product on any profile:
...