1. Advancing Integration Competency and Excellence with the WSO2 Integration Platform Kasun Indasiri Software Architect, WSO2 Miyuru Wanninayaka Technical Lead, WSO2

2. Agenda Fundamentals of WSO2 ESB Cloud Connectors RESTful Integration Cloud Connector – Scenarios RESTful Integration – PizzaShop Scenario Discussion

3. Software in Enterprise Large enterprises have many software systems in their “line of business” Enterprise Resource Planning systems (ERP) Management Information Systems (MIS) Decision Support Systems (DSS) Data stores Legacy systems These systems are often independent and controls one or more related business activities But they are all parts of a single business process

4. Need for Enterprise Integration Individual software applications cannot achieve much Systems should be integrated to work together Enables free data flow across the organization Improves production and management efficiency Application users can make better decisions

5. Easier Said Than Done! Integrating a multitude of complex software applications is no child's play Systems are diverse Different platforms Different programming languages Different protocols and messaging standards Different QoS requirements Not everyone adhere to standards

6. Point-to-Point Connections?

10. Bus

12. What is an ESB? A piece of software that resembles a data bus used in computers Provides a uniform approach for connecting systems Monitor and control routing of message exchange between services Software applications communicate via the bus The service bus acts as a carrier or a message broker Replaces direct contact between applications – Reduces coupling http://en.wikipedia.org/wiki/Enterprise_service_bus

13. WSO2 Enterprise Service Bus A lightweight, high performance ESB Configuration driven over coding REST, SOAP and WS-* support Domain specific protocol support (eg: SAP, FIX) Extensible to support custom protocols / message formats Cloud enabled Supports all EIP patterns http://www.eaipatterns.com

14. KEY FEATURES

15. Routing Simple proxy Header-based Routing Content-based Routing XPath/Property/Regular Expression Rules If/Then/Else Router mediator for complex routing

16. Traffic Filtering Xpath and regex based filtering Script based filtering Schema based filtering and validation foo bar foo

17. Service Orchestration Service chaining Split/Aggregate/ Clone/Merge Parallel/Serial execution If/Then/Else

18. Transformation XSLT Payload Factory Smooks XQuery

19. Protocol & Message Format Switching Message Formats SOAP, REST, JSON, Binary Protocols HTTP(S), JMS, VFS(File), TCP, SAP, FIX, HL7, SMTP

20. Business/Cloud Connectors Connectors

21. Load Balancing

22. QoS : Security, Throttling, Caching WS-Security / REST Security Throttling Concurrency Rate Caching Local Replicated Suitable for idempotent operations

23. REST Capabilities Expose any service as RESTful APIs URL Mapping URL Templates REST http://www.infoq.com/articles/webber-rest-workflow http://wso2.org/library/articles/2012/09/get-cup-coffee-wso2-way/

24. Store and Forward Store incoming request in message store In memory, JMS queue, Database Forward to backend using message processor Guaranteed delivery Message Store

25. WSO2 ESB NUTS AND BOLTS

26. WSO2 ESB – Messaging Architecture

27. Runtime

28. Mediator Configuration Data Input MessageOutput Message

29. Sequences A sequential arrangement of mediators – A mediator chain When a message is handed to a sequence it is given to the first mediator of the chain - The outcome of that will be handed to the second mediator of the chain and so on… The messages are sent through the chain while mediators perform various actions on it along the way Pipelining

30. More on Sequences… Consider the example sequence shown above  Messages are first logged by the log mediator  The property mediator sets a property on the messages  Then they are sent to a specified endpoint by the send mediator  It is a simple log-and-forward message flow

31. Endpoints Defines an endpoint reference (EPR) to which messages can be sent/forwarded from the ESB  The send mediator takes an endpoint as an argument Various operational constraints can be enforced on an endpoint  Timeout duration  Message format (POX, SOAP 1.1, SOAP 1.2) QoS expectations can be set on an endpoint  WS-Security

32. Proxy Services / API Acts like a virtual service that can receive requests from clients Received client requests are processed and routed to a specified endpoint (usually to an actual service – backend service) Responses coming back from the backend service are further processed and forwarded to the clients Resembles traditional HTTP proxy servers

33. Proxy Service – Abstract View

34. With complex business requirements, ESB config can grow bigger.. Need a way to reuse the configuration WSO2 ESB 4.0 introduces – Templates An analogy… classes vs instances Templates

35. Sequence Templates Templates

36. Templates Call Template Mediator – Invoking a Template

37. WSO2 ESB Cloud Connectors

38. Cloud to Cloud

39. WSO2 ESB Cloud Connectors Cloud to Cloud

40. WSO2 ESB Cloud Connectors Cloud to Enterprise

41. Cloud Connector Architecture Objectives  Connect with any cloud API  Supporting diverse APIs (REST, SOAP, SDKs)  Dynamic configuration (No predefined configuration language)  Development methodology (config, java code, javascript, pojo)  Reduce development time(100+ connectors)  Dynamic Tooling with DevStudio  Performance

42. Dynamic Synapse Configuration based on Templates WSO2 ESB config language is predefined – Mediator Factories and Serializers Eg: Property Mediator Serializer/Factory – So, dynamic synapse config language is not possible? Custom Mediators/Mediator per each connector? – Won’t scale and it will be tedious task to write a connector A new approach… – Inspired from Templates and Mediation Library

43. Structure of a Cloud Connector Connector Structure A connector can have Synapse config as templates Custom Mediators External Libararies (eg: twitter4j) Java Script (or any other scripting lang.) – Connector Deployer Loading required libraries

44. Structure of a Cloud Connector Templates External Libs Connector custom code

45. New Secure Vault No hardcoded secrets or passwords in the ESB Config wso2:vault-lookup xx {wso2:vault-lookup('my_secret')} {wso2:vault-lookup('my_token')} {wso2:vault-lookup('my_key')}

46. Cloud Connectors – Use Case (I) Salesforce + Twilio – Lead Generation

47. Cloud Connectors – Use Case (II) Salesforce + Google Spread Sheet – Opportunity Management

48. Cloud Connectors – Use Case (III) Salesforce + JIRA + Twilio – Account Management

49. Cloud Connectors – Use Case (IV) Twitter + Salesforce – Lead Monitor

50. Advanced RESTful Integration HTTP Endpoint <http uri-template= "http://localhost:8080/{uri.var.servicepath}/restapi/{uri.var.servic ename}/menu?category={uri.var.category}&type={query.param.type}" method="GET">

51. Advanced RESTful Integration JSON Payload Factory {"purchaseInformation": {"amount": "$1","cc": "$2"}}

52. Advanced RESTful Integration Pizzashop Scenario

53. Discussion

54. THANK YOU