WSO2 Enterprise Integrator (EI) Connectors are extensions to WSO2 EI runtime (compatible with both 6.x and 7.x) that allows you to interact with SaaS applications on the cloud, databases, and popular B2B protocols.
Connectors are hosted in a connector store and can be added to integration flows in WSO2 Integration Studio, which is the tooling component of WSO2 EI. Once added, the operations of the connector can be dragged onto your canvas and added to your sequences and proxy services.
Each connector provides a set of operations, which you call from your proxy services, sequences, and APIs to interact with the specific third-party service.
This documentation provides an example of how to use each connector and a reference of each of its operations and their properties.
Types of connectors¶
There are three types of connectors available in WSO2 EI.
Cloud Connectors: These connectors enable you to integrate with the APIs of external cloud systems (SaaS Applications) such as Salesforce, ServiceNow, Gmail, Amazon S3, etc.
Technology Connectors: You can send and receive information over standard protocols using connectors like File Connector, ISO8583 Connector, etc.
Database Connectors: You can integrate with databases and perform actions using connector operations.
Advantages of connectors¶
Using connectors provide the following advantages:
|Integrate fast||Let's say you need to get some data from Salesforce and return some of it back to users. If you want to do it, first you need to find and analyze the available APIs from Salesforce. Then you need to code to interfaces or use a SDK provided to communicate with the third party. Designing such a module from ground up takes a lot of time. WSO2 EI Connectors make this process simple as you can easily add the connector via WSO2 Integration Studio and drag and drop your connector’s operations onto the canvas and use them to design your integration flow with the help of our detailed documentation.|
|Easy to use||Connector operations are designed to hide complexities in communication and expose what is required for the users for integration. Connectors are fully supported by WSO2 Integration Studio so that you can just drag and drop operations and configure the integration flow. There is less code complexity when using connectors as most of the intricacy has already been dealt with. It is also very easy to authenticate with external systems as you only need to configure credentials and access URLs in most cases.|
|150+ available connectors||There are numerous connectors available in the store. This provides multiple options on SAAS providers and popular APIs for you to build your integration use cases as required.|
|Less domain knowledge required||When integrating with different APIs, WSO2 EI Connector documentation provides detailed information. Less domain knowledge is required when integrating with systems since all the information about operations are available to you and you do not need to know elaborate details of the system you are integrating with. You can spend less time studying the APIs and focus more on business use cases..|
|Dynamically added to the runtime||Connectors and most of the extensions can be directly added to and removed from the runtime. It is not required to restart the servers for deployments.|
|Easy maintenance||Connectors act as a bridge between main integration logic and the third party application. Even if the application needs to be updated to support new features, the main integration logic of the API version does not need to be changed.|
How to use connectors¶
When configuring the integration logic, you need to use Integration Studio. When ready, you can export the project along with dependency connectors to the WSO2 EI runtime. See documentation on adding connectors for more information.
Note: You can also access the connectors directly from the connector store if required.
Connectors in Integration Studio¶
You can search and import the required connectors to your integration project in WSO2 Integration Studio. Once imported the supported operations are displayed on the design palette.
You need to start using the connector by dragging and dropping the
init operation to the place where you need to use the connector in the message flow. Every connector has this operation. The parameters needed for init will usually be authentication parameters.
An operation of a particular connector represents a function that can be executed using that connector. The input parameters of an operation can be hard coded or fed into the connector programmatically using Properties. You can use any property (custom or internal) set to the message flow before the connector operation is used. Sometimes, the payload in the message context is considered by the connector for its operation as the payload to be sent over the connector. You can manipulate this payload using mediators like enrich, payloadfactory etc. After the connector operation is used in the message flow, response received by invoking that operation will be available in the message context for the next mediator to be used.
As described above input for the connector operations would be:
- Hard coded values
- Values of properties set to the message flow before the connector operation is used
- Payload that is in message context (message flow) at the place he connector operation is used
Inbound endpoints are used to listen or poll for messages from external systems like Kafka and NATS. These are also used to trigger events into WSO2 EI and start a message flow upon changes made to external systems (i.e., RDBMS Database).
The configurations are made using Integration Studio for inbound endpoints as well. When configuring, you need to define it as an inbound endpoint of type “custom”. The parameter “class” has the fully qualified name to the Java class implementing message pooling functionality.
You need to download the required libraries from the connector store and import them to WSO2 EI runtime. Usually the inbound endpoint is co-hosted with the associated outbound connector.
Exporting to runtime¶
Once the integration logic is done, you can export it along with the dependency connectors as a CApp. CApp is the deployable unit for WSO2 EI runtime. However, when you are using inbound endpoints, you need to place corresponding libraries in WSO2 EI runtime.
Example scenarios and operations¶
Within this documentation, each connector has an example scenario associated with it that illustrates how a simple use case can be done using the connector. It also has a detailed reference guide that lists out the operations and the respective properties of each of these operations, highlighting sample values, required configurations, and even sample requests and responses.
Empowering the developer¶
We have to be honest; we would really like to encourage developers who want to solve integration problems. If you have a use case that requires you to customize one of our connectors, we encourage you to go ahead and make the changes you need.
Report an issue¶
You can report issues for any connector under the Micro Integrator repository. Once you have reported the issue, do the following:
- Add the label
- Add to the project
For an example, please refer to this issue.
Contribute to the connector project¶
Search for the connector you want to customize in the WSO2 Extensions GitHub repository and clone it.
Use the following command to build the connector.
mvn clean install
Make the changes you need and send in a pull request.
Write your own custom connector¶
There may be instances where the product you want to integrate with does not have a connector as yet. In this case, you can build your own connector. Please refer to the document here for detailed instructions.
- Custom connector
- Custom inbound endpoint