A Carbon Application, abbreviated as a cApp, is a collection of artifacts deployable on a Carbon instance. These artifacts are usually java-based or xml configurations, designed differently for each product in the Carbon platform. Users have to deploy these artifacts to generate services. In a single Carbon-based solution, there can be numerous artifacts used, such as Axis2 services, data services, synapse configurations, endpoints, proxy services, mediators, registry resources, BEPL BPEL workflows etc. Usually, these artifacts are created in a development environment and then moved one by one into staging/production environments. When moving a Carbon solution from one setup to another, the user has to manually configure these artifacts to build up the entire solution. This is a time-consuming process.
Alternatively, bundling configuration files and artifacts in a cApp makes it easy for users to port their Web service based solutions across environments. Carbon Applications save time by providing the facility to export your entire solution as a single cApp artifact and simply deploy it in the server. WSO2 Web services development tooling environment (Carbon Studio) Developer Studio can be used to develop your individual artifacts and export them as a single cApp artifact. You can then deploy it on any Carbon server which has cApp deployment capabilities.
...
This is the easiest and the most recommended way to configure your server roles. For more information, please refer to section: Configuring Server Roles for Carbon Applications.
Using carbon.xml File
You can find the ServerRoles element in <PRODUCT_HOME>/repository/conf/carbon.xml file. For example,
...
Before setting the above, ensure that the current server has capability to deploy Axis2 services and data services. When you deploy a cApp artifact on this server, all artifacts which have the above two server roles will be deployed on the current instance. Others will be ignored.
Using a
...
System Property
You can use the system property ServerRoles to specify the server roles that can be acted by the current Carbon instance. When you start the server, pass the server roles as a comma separated list. For example,
...
| 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. |
| Excerpt | ||
|---|---|---|
| ||
Introduction to WSO2 Carbon applications. |