This documentation is for WSO2 Enterprise Integrator version 6.5.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

All docs This doc

Versions Compared


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



  1. In Go to Getting Started page in WSO2 Integration Studio, and click on Miscellaneous → Add New Server to add a new server..
  2. In the Define a New Server dialog box, expand the WSO2 folder, and select the respective product and version.
  3. Click Next, click Browse that is next to CARBON_HOME, and select the WSO2 EI distribution directory, to define the server runtime environment and click Next.


    If you are running on a linux-based system (MacOS, Ubunto, or CentOS), be sure that your WSO2 EI distribution is a binary distribution downloaded from the website. If you use a product distribution that was set up using the product installer, you will require special permissions to start the product through WSO2 Integration Studio.

  4. Review the default port details for the ESB profile of WSO2 EI. Typically, you can leave these unchanged, but if you are already running another server on these ports, specify unused ports here. See Default Ports of WSO2 Products for more information. Click Next
  5. To deploy the CApp project in the ESB server that we just added, select SampleServicesCompositeApplication from the list, click Add to move it into the Configured list, and then click Finish.
    The ESB server of WSO2 EI is now added inside Eclipse tooling.

  6. On the Servers tab, you see that the server is currently stopped. Click  on the Servers tab's toolbar to start the server.

    If you are prompted to save changes to any of the artifact files, click Yes
    As the server starts, the Console tab appear. You should see messages indicating that the C-App was successfully deployed. The C-App will now be available in the ESB profile's management console (Manage -> Carbon Applications -> List).


    You can also deploy the artifacts to the ESB server using a Composite Application Archive (CAR) file.