This documentation is for WSO2 Enterprise Service Bus version 4.7.0 . View documentation for the latest release.
Skip to end of metadata
Go to start of metadata

When developing solutions using WSO2 Carbon platform, there can be many artifact types used in it. For example, Axis2 services, Synapse artifacts (endpoints, proxy services, mediators, etc.), registry resources, data services, etc. Normally these artifacts are developed in a development environment and then moved one by one into the staging and production environments. On each and every setup, you have to manually configure these artifacts in order to build up the entire solutions.

A Carbon Application (C-App) is a collection of artifacts, which can be deployed on a Carbon instance to easily port your Web services solution from one environment to another. You can use WSO2 Developer Studio to develop your artifacts and C-Apps. You can then deploy the C-Apps as Carbon Application Archive (CAR) files on any Carbon server that has C-App deployment capabilities. For more information, see the following topics:

Deploying applications

When deploying CAR files that have dependencies on other CAR files, be sure to deploy the independent CAR files first and the dependent CAR files next to avoid deployment issues.

When you deploy an application to the ESB and start the server, the artifacts are initialized in the following order:

  1. Endpoints
  2. Sequence templates
  3. Sequences
  4. Proxy services
  5. Priority executors
  6. Message stores
  7. Message processors
  8. APIs
  • No labels