Carbon servers have a notion called server profiles. Logical grouping of set of features/components is known as a server profilesprofile. Every Carbon server has a default shipped profile named 'default' profile. This default profile consists of the complete feature set corresponding to a particular product. For an example, the WSO2 Application Server's default profile has all the feature set that corresponds to an application server.
Apart from the default profile, a server can have several other server profiles depending on the use cases. Given below are the available profiles in WSO2 Application Server.
- default: default Default profile.
- worker: This profile only consists of the back-end feature set of the Application Server. That is it does not include the management console related features of Application Server. This profile is used to start the server as a worker node, in a worker-manager setup.
...
Creating a new server profile is equal to , materializing a new profile. Therefore, first we have to publish the product definition to a P2-repo and refer it while materializing a product.
...
Starting a specific server profile
Start You can generally start the server with the server profile name given as the input parameter as shown below.
| Code Block |
|---|
./wso2Server.sh -Dprofile=<profileName> |
However, if you want to start the server as a worker node (Worker profile), it is recommended to set the profile in the product startup script (stored in the <PRODUCT_HOME>/bin/ directory) as a system property as shown below.
| Code Block |
|---|
'-DworkerNode=false' |