Cloud to Cloud and Cloud to Enterprise Integration

1. Cloud to Cloud and
Cloud to Enterprise Integration
S.Uthaiyashankar
VP Engineering
WSO2
shankar@wso2.com

2. Why Cloud Integration?
• Many useful cloud services
• Enterprises have started using SaaS for their needs
Images from : http://www.sfdcstatic.com/common/assets/img/logo-company.png, http://www.mgitsol.com/wp-content/uploads/Google-Apps-Transparent.png, http://www.sunnysea-residence.
com/img/facebook.png, http://aweebitirish.com/wp-content/uploads/2014/04/linkedin-transparent-background.png, http://www.justfreestuff.com/wp-content/
uploads/dropbox-300x300.png

3. Integration Scenarios
• Cloud to Cloud
• Cloud to Enterprise
Images from : http://www.sfdcstatic.com/common/assets/img/logo-company.png, http://www.boldkiln.com/Images/tr/135.png,
https://openclipart.org/detail/13272/-by--13272, http://hlgstudios.com/wp-content/uploads/2012/09/sap-logo.png

4. Challenges in Integration
• Different protocols
• Different message/data
formats
• Different APIs
• Point to point integration
mess
Image: http://www.nyceestinoored.com/wp-content/uploads/2013/01/how-to-organize-cable.jpg

5. Cloud Integration Challenges
• Enterprise applications should work with cloud applications
• Cloud applications has their own data storage, user accounts
– Relieve users from
• Re-enter data to different applications
• Re-enter their credentials
• Cloud applications should abide by enterprise policies
– Governance
– Security
– Provision/de-provision users in various applications
• Overlapping functionalities of applications

6. iPaaS
• Integration Platform as a Service
• “…is a suite of cloud services enabling development,
execution and governance of integration flows
connecting any combination of on premises and
cloud-based processes, services, applications and
data within individual or across multiple
organizations.” : Gartner Research
http://www.gartner.com/it-glossary/information-platform-as-a-service-ipaas/

8. Characteristics of iPaaS
• Integration Flows
– Prepackaged
– Custom developed
• Integration Flow Marketplace
– Collaboration
– Self Service
• Monitoring
• Development & Lifecycle Management
Reference : Gartner iPaaS Reference Model

9. Integration Flows
• Connectors
• Data Mapping & Transformations
• Recipes
• Dishes

10. Connectors
• Connects to a specific cloud or enterprise application
• Configuration driven
• We have about 100 connectors upto now, and
increasing
– Can write your own custom connectors

11. Connector Catalog
https://storepreview.wso2.com/store/assets/esbconnector

12. Data Mapping & Transformations
• XSLT
• XQuery
• Smooks
• Visual Data Mapping

13. Recipes
• Providing high level abstractions for connector
interactions
• Commonly used integration scenarios between any
publicly available services/APIs
– E.g. Salesforce->Google spread sheet
• Take data from Salesforce using connector
• Do the data mapping / conversion
• Push data to google spread sheet using a connector
• Can have methods
– E.g: syncContacts, syncLeads

14. <template name=”SyncLeads" xmlns=http://ws.apache.org/ns/synapse>
<parameter name="googlespreadsheet.username"/>
<parameter name="googlespreadsheet.password"/>
<parameter name="googlespreadsheet.spreadsheetName"/>
<parameter name="googlespreadsheet.worksheetName"/>
<parameter name="googlespreadsheet.batchEnable"/>
<parameter name="googlespreadsheet.batchSize"/>
<parameter name="salesforce.username"/>
<parameter name="salesforce.password"/>
<parameter name="salesforce.batchSize"/>
<sequence>
<salesforce.init>
<username>{get-property('func','salesforce.username')}</username>
<password>{get-property('func','salesforce.password')}</password>
<loginUrl>https://login.salesforce.com/services/Soap/u/27.0</loginUrl>
</salesforce.init>
<salesforce.query>
<batchSize>{get-property('func','salesforce.batchSize')}</batchSize>
<queryString>select id,name from Account</queryString>
</salesforce.query>
<xslt key="csvConverter2.xslt"/>
<googlespreadsheet.usernameLogin>
<username>{get-property('func','googlespreadsheet.username')}</username>
<password>{get-property('func','googlespreadsheet.password')}</password>
</googlespreadsheet.usernameLogin>
<googlespreadsheet.importCSV>
Convert Data
<spreadsheetName>{get-property('func','googlespreadsheet.spreadsheetName')}</spreadsheetName>
<worksheetName>{get-property('func','googlespreadsheet.worksheetName')}</worksheetName>
<batchEnable>{get-property('func','googlespreadsheet.batchEnable')}</batchEnable>
<batchSize>{get-property('func','googlespreadsheet.batchSize')}</batchSize>
</googlespreadsheet.importCSV>
</sequence>
</template>
Parameters
Recipes
Read Data
Write Data

15. Recipes

16. Creating a Recipe
• From scratch
• Take an existing one and modify it
• Take an existing ESB flow and make it as a recipe

17. Dishes
• A user can prepare multiple dishes from single recipe
– Different parameters
– Different connector configurations
• A dish will be triggered periodically to perform the
operation

18. Dishes
<task xmlns="http://ws.apache.org/ns/synapse" name="CarbonTask"
class="org.wso2.carbon.recipeexecutor.RecipeMessageExecutor" group="synapse.simple.quartz">
<trigger count="1" interval="100"/>
<property xmlns:task="http://www.wso2.org/products/wso2commons/tasks" name="recipeParams">
<salesforceGooglespreadsheet.syncContacts xmlns="">
<salesforce.username>xxxxxxxx</salesforce.username>
<salesforce.password>xxxxxx</salesforce.password>
<salesforce.batchSize>200</salesforce.batchSize>
<googlespreadsheet.username>xxxx</googlespreadsheet.username>
<googlespreadsheet.password>xxxxx</googlespreadsheet.password>
<googlespreadsheet.spreadsheetName>RecipeDemo</googlespreadsheet.spreadsheetName>
<googlespreadsheet.worksheetName>Recipe1</googlespreadsheet.worksheetName>
<googlespreadsheet.batchEnable>true</googlespreadsheet.batchEnable>
<googlespreadsheet.batchSize>10</googlespreadsheet.batchSize>
</salesforceGooglespreadsheet.syncContacts>
</property>
<property xmlns:task="http://www.wso2.org/products/wso2commons/tasks" name="regKey"
value="gov:/recipes/TestRecipe.xml"/>
</task>
Trigger
Parameters

19. Dishes

20. Characteristics of iPaaS
• Integration Flows
– Prepackaged
– Custom developed
• Integration Flow Marketplace
– Collaboration
– Self Service
• Monitoring
• Development & Lifecycle Management
Reference : Gartner iPaaS Reference Model

21. Integration Flow Marketplace
• Connector Store • Recipe Store

22. Monitoring
with WSO2 Business Activity Monitor & WSO2 Complex Event Processing

23. Development & Lifecycle Management

24. Development & Lifecycle Management

25. Other Technologies used in Integration
• Stateful, long-lived processes
– WSO2 Business Process Server
– BPEL, BPMN
• Messaging
– WSO2 Message Broker
– JMS, AMQP, MQTT

26. SSO and Identity Federation

27. Identity Provisioning

28. Cloud Gateway

29. Thank You