The below section describes how to configure cloud to cloud integration with WSO2 ESB Connectors using WSO2 Developer Studio.
Query new (open) high severity issues created in JIRA system and alert them by a SMS.
The latest version of Developer Studio can be downloaded from 
Before you start creating ESB artifacts with connector operation, the necessary connectors should be imported into your workspace. You can download the ESB connectors from 
- Create a new ESBConfig project (SampleConnectorProject)
- Right click on the created ‘SampleConnectorProject’ project and select ‘Import Connector’ from the context menu.
- Then browse the location of the connector zip and select the relevant connectors zip (jira-connector.zip, twilio-connector.zip) to import.
- Create Sequence, Proxy or REST API and the imported connectors will be appeared in the tool palette.
Create ESB Artifacts with Connector Operations
The detailed configurations on how to perform various operations on Jira Connector and Twilio connector can be found in  and  respectively.
- Create a Sequence with name ‘AlertSequence’
- Connect to Jira
Drag and drop the ‘init’ JIRA operation from the tool palette before use any other Jira connector operations.
This configuration authenticates with Jira system by configuring the user credentials and login url. Provide username and password and url for Jira System.
- Get high severity issues created.
Drag and drop ‘searchJira’ operation from the tool palette to retrieve data from Jira system.
Set query to get open , highest severity issues in property window.
priority = Highest AND resolution = Unresolved AND status = Open
- Loop through retrieved issues
Jira system response have following format.
According to response there are two issues in high priority and open. To loop through them Drop Iterator mediator.
Set ‘Iterate Expression’ property to “//issues”of Iterator mediator.
- Extract the issue link from iterated issue.
Drop a Property mediator into the iterator. Set values as follows. It will concat issue link and “WSO2 ALERT” message.
- Connect to Twilio
Drop Twilio Init operation from palette and provide required account details to authenticate.
- Send extracted issue link as a SMS alert
Drop a Twilo sendSMS mediator.
Set ‘To’ value to receiver phone number . (‘From’ value needs to be find in your Twilio account).
Simply place the ‘body’ with property value.
- It might be useful to add Log mediators for log sequence status intermediately.
- Triggering sequence in periodically
ESB Scheduled Task component can be use to invoke the sequence we created. Create a Shedule Task name “AlertTask” in same project.
In properties, get the ‘Task Properties’ pop-up configuration window. Set ‘sequenceName’ to “AlertSequence” , ‘injectTo’ to “sequence” and ‘message’
In AlertTask properties change ‘interval’ to 900, which is 15 minutes, and ‘count’ to -1 .
Create the deploy archive to deploy in WSO2 ESB
- Create a Composite Application Project (SampleCAPP) from Developer Studio and include the SampleConnectorProject as Dependencies.
Deploying in WSO2 ESB
After install connectors in ESB server make sure to activate them.
- Deploy the ‘SampleCAPP’ in Developer Studio
Check issues intermittently by client REST application
This issues review scenario completely time synchronized. If someone needs to check whether are there high priority issues immediately, we should be able to invoke the sequence.
Considering user makes request from REST client.
- Create REST API artifact in Sample SampleConnectorProject
A REST API allows you to configure REST endpoints in the ESB by directly specifying HTTP verbs (such as POST and GET), URI templates, and URL mappings through an API.
- Drop AlertSequence into insequence from pallet Defined Sequences section.
Make sure to set value ‘true’ for Continue Parent property in AlertSequence, Iterator mediator.
- Drop ‘Respond’ mediator. (this will redirect results to user)
Now deploy the SampleCAPP. In management console, REST api menu page will show the SampleRESTAPI, and API Invocation URL. Using this url, we can simply check the issues created with high priority intermittently.