This slide deck discusses how you can use the lean, enterprise-ready, high performing WSO2 integration platform to solve integration and innovation challenges that organizations face when carrying out brownfield integration.
Watch video: https://wso2.com/library/conference/2018/07/wso2con-usa-2018-up-leveling-brownfield-integration/
4. Brownfield vs Greenfield
Source :
https://commons.wikimedia.org/wiki/File:Greenfield
_California.JPG
Source :
https://commons.wikimedia.org/wiki/File:A_classic_bro
wnfield_site_-_geograph.org.uk_-_728293.jpg
VS
5. Why is Brownfield Integration Important ?
● Reuse of existing systems
● Cutdown the time it takes for digital transformation
● Cut down cost
● Not all existing systems are replaceable
6. Types of Systems in Brownfield
● Systems based on standard protocols
● Systems based on non standard or proprietary protocols
● File based systems
● Systems that doesn’t provide any integration points
○ Databases
16. WSO2 Enterprise Integrator
Single integrated packaging of
● ESB and DSS as a single runtime
● Business Process Server
● Message Broker
● EI Analytics (primarily ESB analytics)
● MicroESB (New..!)
17. Service Integration - Integrator Runtime
A lightweight, high performance service bus
● Comprehensive REST, SOAP, and WS-* support
● SAP, FIX, and HL7 - Domain specific solutions
● Configuration driven
● Extensible and scalable
● 100% coverage of all EIPs
18. Data Integration - Integrator Runtime
Building service abstractions on top of disparate data sources
SQL
SOAP/REST/OData
XML/JSON
19. Business Processes - BPS Runtime
● Define and execute business processes - WS-BPEL 2.0,
BPEL4WS 1.1, BPMN 2.0, long running stateful processes
● Define workflows interacting with people - BPMN user tasks,
WS-HumanTask 1.1, BPEL4People 1.1
● Graphical process modeling
20. MicroESB
● Startup time reduced
● Distribution size reduced
● Supports all key features
● Removed features that are not useful for MSA
● Container-friendly
21. MicroESB vs ESB Profile
ESB MicroESB
Startup Time 40s 5s
Distribution size 814 MB 379 MB
Mediation (ESB) Features ✅ ✅
Data Integration Features ✅ ✅
Built-in Clustering ✅ ❌
Tooling ✅ ✅
Management Console ✅ ❌
Dep-Sync ✅ ❌
Multitenancy ✅ ❌
CAR Deployment ✅ ✅
Hot deployment ✅ ❌
28. Protocol Switching
New System Brown-Field
Existing
SystemHTTP
JMS
Receive over
any protocol
and
deliver over
any protocol
29. Brownfield Integration with Different Types of
Systems
● Integration with systems that talk in standard protocols
● Integration with systems that talk in non-standard/
proprietary protocols
● Integration with file-based systems
● Integration with systems that use databases
30. Integration with Systems That Talk in Standard
Protocols
Support for wide range of
standard protocols
● HTTP/HTTPS
● JMS
● AMQP
● FTP/SFTP/FTPS/SMB
● SMTP/IMAP
● MQTT
● KAFKA
● And many more
SMTP
HTTP
JMS
FTP
Websocket
31. Integration with Systems That Talk in
Standard Protocols
HTTP/API
Public Private Organization
Existing
System
FTP
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
33. Integration with Systems That Talk in
Non-standard/ Proprietary Protocols
HTTP/API
Public Private Organization
Existing
System
Non Standard
Protocol
Connector
34. Extending the Functionality
● Extension points are available in each layer of the ESB
architecture
● Extensions can be written using Java and plugged into the
runtime
36. Connectors
● Add-ons for ESB runtime
● Over 150 ready-made connectors
available in WSO2 store
● Can build your own connector
easily
- Using SDKs
- Using web APIs
37. Integration with Files-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
38. File Handling Use Cases
Listen to a location, pick files, and invoke a web API using the
content of the files
File HTTP
Web API
Invocation
Existing Legacy
System
39. File Handling Use Cases
Expose a file-based system as an API over HTTP protocol
FileHTTP
Existing Legacy
System
40. Integration with Systems That Use Databases
Expose databases or other data sources as services
HTTP