WSO2 Enterprise Integrator (EI) Tooling/ Developer Studio Project Types

WSO2 Enterprise Integrator (EI) Tooling also known as Developer Studio is a plugin developed by WSO2, and it is based on Eclipse IDE. It is a FREE Open Source download and it allows developers to build their integration artifacts and deploy them into WSO2 EI ESB.

Since WSO2 EI is a combination/ bundle of many earlier WSO2 products, we need to use different projects to target Enterprise Service Bus (ESB), Data Services Server (DSS) and Business Process Server (BPS) profiles.

Below is the list of different projects which you can create using WSO2 Developer Studio targeting WSO2 EI.

WSO2 Developer Studio

It’a always better to know when to use which project type and below is a high-level overview of each project type in Developer Studio and when to use them:

• ESBConfig project — This project contains all artifacts related to the functionality you are developing targeting the ESB profile. This type of project is focused on web services and REST artifacts. Proxy services, REST APIs, Sequences and Endpoints are some of the artifacts we can create inside this project.
• Registry Resource project — This project will be used to add resources such as XSL transformations, WSDL files, and XSD files to the underlying EI registry. Most of our custom developments require some supporting artifacts such as XSL/ XSD/ WSDL to be stored in the EI registry. This project type will take care of deploying them to the underlying EI registry.
• Data Service project — There are many cases where we need to work with a backend database system within our EI development artifacts. Data Service project template will be used to add data services that allow us to access multiple data sources and expose their data in a very simple way.
• Composite Application project — All the artifacts should be packages as Carbon Application Archive (.CAR) files before deploying to the EI. This project generates the deployable artifact by detecting the existing artifacts in the projects within the workspace and allows us to select which ones will be packaged.
• ESB Solution project — Creating a custom EI solution typically involved in creating many projects. Grouping all those related projects into a single unit of work make the developer’s life easier. Rather than having to create required projects one by one, ESB Solution project walks us through a wizard which will create required dependant project and group them together. We can choose to include ESBConfig project (mandatory), Registry Resource project (optional), Composite Application project (optional) and Create Connector Exporter project (optional) when we are creating a new ESB Solution project.