This documentation is for WSO2 API Manager 1.8.0 View documentation for the latest release.
Page Comparison - Product Profiles (v.1 vs v.2) - API Manager 1.8.0 - WSO2 Documentation

Versions Compared


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

When a WSO2 product


starts, it starts all features and related artifacts bundled


with it. Multi-profile support allows you to run the product on a selected profile so that only features specific to that profile along with common features start up with the server. This enables better resource utilization.

Execute one of the following commands to start a product on a preferred profile.

<PRODUCT_HOME>/bin/wso2server.bat -Dprofile=<preferred-profile> --run

sh <PRODUCT _HOME>/bin/ -Dprofile=<preferred-profile>

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


ProfileCommand Option with Profile NameDescription
Gateway manager
Used 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 back-end services that allow the product instance to communicate with other nodes in the cluster.
Gateway worker
Used when API Gateway acts as a worker node in a cluster. This profile only starts the back-end features for data processing and communicating with the manager node.
Key Manager
Starts only the features relevant to the Key Manager component of API Manager.
API Publisher
Starts only the front-end/back-end features relevant to the API Publisher Web interface.
API Store
Starts only the front-end/back-end features relevant to the API Store Web interface.

How multi-profiling works

Starting a product on a preferred profile starts only a subset of features bundled in the product. In order to identify what feature bundles apply to which profile, each product maintains a set of files in <PRODUCT_HOME>/repository/components/<profile-name>/configuration/org.eclipse.equinox.simpleconfigurator directories. The files contain references to the actual bundles. Note that <profile-name> in the directory path refers to the name of the profile. For example, when there's a product profile named webapp, references to all the feature bundles required for webapp profile to function are in a file saved in <PRODUCT_HOME>/repository/components/webapp/configuration/org.eclipse.equinox.simpleconfigurator directory.