Today, transforming a conventional business into a digital one is essential to increase revenue and productivity. Integrating heterogeneous systems and building an ecosystem with integrated components is a fundamental requirement for this.
Most modern systems support integration with other systems through APIs that are exposed to well-known protocols and standards. However, it is hard to expect all existing systems of an organization to be capable of integrating with other systems. Certain legacy systems will only be replaced a few years down the line.
Therefore, the challenge is to drive all these existing systems towards integration in quick succession while ensuring the agility to make any changes in the future. In this meetup, we will discuss how you can use the lean, enterprise-ready, high performing WSO2 Integration Platform to solve integration and innovation challenges that organizations face when performing brownfield integration.
Discussion topics include
Integrating with systems that talk in standard protocols and non-standard/ proprietary protocols
Integrating with legacy systems using techniques such as file-based integration
Sharing existing data from different sources as services
Ensuring guaranteed delivery of messages
Future-proofing your integrations by leveraging containerized deployments using Docker and Kubernetes
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
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
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
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. 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
This is an important Gartner observation…. That Development will become Integration.
This also implies that Development organizations must also become Integration organizations.
Lastly, if Agility is important to development organizations, then agility is important to integration as well.
In general, Brownfield land is an area of land previously used or built upon.
In urban planning - previously used for commercial or industrial purposes,
Green field is a fresh land
In software
Brownfield integration means integrating these already existing systems with the rest of the world
Modern systems supports integration through APIs
Hard to expect all systems are like that in an organization
Most systems will get replaced, but nobody wants to wait.
Building everything from scratch may not be cost effective too.
Similar to rebuilding a brownfield land brownfield integration has to be done carefully
File Handling Capabilities
Pick and read files from a location periodically
Pick and read files from a location on demand
Write data to files