This document discusses building an integration agile digital ecosystem using WSO2 Enterprise Integrator. It covers brownfield vs greenfield integration, the key functionality of WSO2 EI like transformation, routing, orchestration and protocol switching. It demonstrates integration with different types of systems including standard protocols, databases, files and proprietary protocols. It also discusses ensuring guaranteed delivery, containerized deployments using Docker and Kubernetes, and the Micro Integrator CI/CD workflow.

1. Building an Integration Agile Digital
Ecosystem
May 8, 2021

2. Hello!
Rohitha Liyanagama
Rohithal@wso2.com
Director - Solutions Architecture, WSO2
● More than 17 years experience in software industry .
● AWS Certified Solutions Architect - Associate

3. Agenda
1. Brownfield vs Greenfield Integration
2. WSO2 Enterprise Integrator
3. Integration with systems that talk in standard protocols and non-standard/
proprietary protocols
4. Integration with legacy systems using techniques such as file-based integration
5. Sharing existing data from different sources as services
6. How to ensure guaranteed delivery of messages
7. Future proof your integrations by leveraging containerized CI/CD driven
deployments using Docker and Kubernetes
3

4. 4
Half of All Digital Platform Development Will Be Integration

5. Brownfield vs Greenfield
Source :
https://commons.wikimedia.org/wiki/File:Greenfield_C
alifornia.JPG
Source :
https://commons.wikimedia.org/wiki/File:A_classic_brown
field_site_-_geograph.org.uk_-_728293.jpg
VS
5

6. Why is Brownfield Integration Important?
● Reuse of existing systems
● Cut down the time it takes for digital transformation
● Cut down cost
● Not all existing systems are replaceable
6

7. ● Systems based on standard protocols
● Systems based on non-standard or proprietary protocols
● File based systems
● Systems that don’t provide any integration points
⦿ Databases
7
Types of Systems in Brownfield

8. Key Functionality Requirements
● Transformation
● Routing
● Orchestration
● Protocol Switching
● Parallel Processing
8

9. Transformation
New System Brownfield
9
Existing System

10. Routing
10
New System Brownfield
Existing System
A
Existing System
B

11. Orchestration
11
New System Brownfield
Existing
System
A
Existing
System
C
Existing
System
B
1
2
3

12. Protocol Switching
12
New System Brownfield
Existing System
HTTP JMS

13. Parallel Processing
13
New System Brownfield
Existing System
A
Existing System
B

14. WSO2 Enterprise Integrator

15. 15
What is WSO2 Enterprise Integrator?
An open-source, cloud-native, distributed, hybrid integration platform for integrating APIs, and data
using microservices, cloud-native or centralized ESB style architectures.
Enterprise Integrator

16. 16
WSO2 EI
Connectors
Web services
APIs
Filesystems
Messaging
systems
Business
Applications
Partners’
systems
Data
public cloud | private cloud | on-premise
A Hybrid Integration Platform
Connectivity / Integration : anything-to-anything
Typical Use Cases
● A system of systems: connect
multiple systems together
● Better consumer experience with
connected data and business
processes
● Digitize legacy systems: mediate
legacy with modern architecture
paradigms
● Hybrid integration by taking
on-premise data and processes into
the cloud and back

17. Connect with WSO2 Enterprise Integrator
○ Mediator: A component
that represents an action
(enrich, split, aggregate,
send, log)
○ Sequence: A logical
container of a set of
sequentially arranged
mediators/ actions
○ Endpoint: A
representation of an
external destination for
messages
17
Sender
Sender
Synapse
MR
Proxy
MR
Callback
Receiver
Sequence A
Sequence B
End Point
End Point
Request to
Service
From
Synapse
Request to
Synapse
From
Service
Synapse Environment
Client
Request
To Synapse
Request to
Client
From
Synapse
Client Service

18. Connect with WSO2 Enterprise Integrator
Basic Mediators
18
Name Description
Log Mediator Logs full or part of the message, at various severity levels (Trace, Debug, etc.)
Sequence Mediator Invokes existing sequence - Sequence name can be static or dynamic
Send Mediator Sends a message out, using static information or endpoint definition
Callout Mediator Performs a blocking external service invocation
Switch Mediator
Evaluates message contents against regular expression and invokes the
corresponding mediator (switch-case-default)
Validate Mediator
Validates message or parts of message against XML schema (schema can
be local or in registry)
Drop Mediator Stops processing of current message
Fault Mediator Transforms current message into custom Fault message

19. 19
Visual Tooling - Integration Studio
● Provides graphical and source
view editing of integration
artifacts
● Debugging support on
mediation flows
● Eclipse-based
● Packaging / archiving artifacts
for deployment

20. Brownfield Integration
with
WSO2 Enterprise Integrator
20

21. Implementation of Key Functionality Requirements
● Transformation
● Routing
● Orchestration
● Protocol Switching
21

22. Transformation
Data Mapper,
Enrich,
Payload Factory,
XSLT Mediators
22
Enterprise
Integrator
New System Brownfield
Existing System
● Ability to transform any
format to any format
● Data mapping
● Enrich Payload
● XSLT

23. Transformation - Visual Data Mapping
23

24. Routing
Routing Based on
● Content
● Headers
● A property of the message
● Environment
Switch, Filter
Mediators
24
New System Brownfield
Existing
System
A
Existing
System
B
Enterprise
Integrator

25. Orchestration
Synchronous service
invocations with
underlying
asynchronous
non-blocking thread
model
Call
Mediator
25
New System Brownfield
Existing
System
A
Existing
System
C
Existing
System
B
1
2
3
Enterprise
Integrator

26. Protocol Switching
Receive over any
protocol and deliver
over any protocol
26
New System Brownfield
Existing
System
HTTP JMS
Enterprise
Integrator

27. Demo - Integration
27

28. Brownfield Integration with Different Types of Systems (Demo
Scenarios)
● Demo 1 - Integration with systems that talk in standard protocols
● Demo 2 - Integration with systems that use databases
● Demo 3 - Integration with file-based systems
● Demo 4 - How to ensure guaranteed delivery of messages
● Demo 5 - Micro Integrator CI/CD workflow
28

29. Integration with File-based Systems
● A lot of legacy systems still use files as the medium to integrate with other
systems
● WSO2 Enterprise Integrator supports a wide range of file transferring protocols
such as FTP, SFTP, FTPS, and SMB
29

30. Demo 3 - Channel Collection Center
Listen to a location, pick files, and invoke a web API using the content of the files
30
Grand Oak
Pine Valley
Discount Payment
Channel
Collection
Legacy System
Enterprise Integrator Data Mapper,
Property,
Payload Factory,
Call,
Log

31. Expose File as an API
Expose a file-based system as an API over HTTP protocol
31
Existing Legacy
System
Enterprise Integrator
File
HTTP

32. Integration with Systems that Talk in Non-standard/ Proprietary
Protocols
● Built in support for well-known proprietary protocols
E.g. SAP
● Easy to extend the functionality to introduce new protocols
32

33. Integration with Systems that Talk in Non-standard/ Proprietary
Protocols
33
Public Private Organization
Existing System
Non
Standard
Protocol
HTTP/API
Enterprise Integrator
Connector

34. ● To connect and integrate with common systems and platforms
● Connector Store: More than 230+ enterprise connectors
● No additional cost, just download and install
● Can build your own connector easily, using SDKs and web APIs
Connectors
● Salesforce
● SAP
● Google
● PeopleHR
● SugarCRM
● Twilio
Connectors to Connect The Enterprise
34
● Youtube
● eBay
● Bugzilla
● Zuora
● Nest
● ...

35. Demo 4 - Connect to Salesforce with WSO2 SF Connector.
35
Enterprise Integrator
Connector

36. There is a possibility of payment system unavailability
36
Demo 4 - How to Ensure Guaranteed Delivery of Messages
Grand Oak
Pine Valley
Discount Payment
Check System
Availability and
Reinitialize the
Process
Enterprise Integrator
X

37. Cloud-native integration with microservices
37
Support for Containerized Deployments Using Docker and Kubernetes

38. Micro Integrator CI/CD Workflow
38

39. Demo 5 - Micro Integrator CI/CD Workflow
39
Enterprise
Integrator
Integration
Studio (IDE)
Commit
Changes
Git hook
trigger
Automated
Testing
Push docker
image
Pull docker
image
Deployed to
K8S
Integration
Developer

40. Question Time!
40

41. wso2.com
Thanks!