...
This is the recommended way to configure server roles . because the changes done through the console cannot be overridden by the other methods. Server roles are stored in the registry when they are configured through the management console. Values in the registry are always given priority over others.
- Log in to the management console of your product and click Server Roles menu under the Configure menu.
- Click Add New Server Role, enter the Role Name and click Add. You can add any textual name as a server role without special characters except underscore.
The newly added server role is displayed in the server roles list.
You can delete the server role using the Delete icon associated with it.Info You cannot undo a deletion once performed. Users can even delete a default server role. Once deleted, the server role manager will not pick up the deleted server role from the
carbon.xmlfile, next time the server starts.
...
In the above example, before setting the two ServerRole properties, ensure that the server has capability to deploy both Axis2 services and data services. When you deploy a C-App, all only the artifacts that have the above two server roles will be are deployed on the current instance. Others are ignored.
...
You can use the system property ServerRoles to specify the server roles that can be acted by of the current product instanceserver. When you start the server, pass the server roles ServerRoles as a comma separated list. For example,
| Code Block |
|---|
sh wso2server.sh -DserverRoles=appserver1,dataservices1 |
| Info |
| Once you use the management console to set server roles, you can't change that configuration using the other two methods. Server roles are stored in the Registry when they are configured through the management console. Values in the Registry are always given priority over others. |