WSO2 Enterprise Integrator v6.1.1 was explored through a pilot study and proof of concepts. Key capabilities tested included: - Mediating between external clients and endpoints like Axis2, WSO2 Broker, and Spring Boot using ESB proxy services. - Connecting to external systems like ActiveMQ and an LDAP server. - Deploying BPEL and BPMN processes on the Business Process Services runtime. - Implementing a two node vertical cluster with load balancing. - Applying security policies to authenticated ESB services using an LDAP backend. The study validated core integration and mediation capabilities of the product.

1. PILOT STUDY
ESB MIDDLEWARE
WSO2 ENTERPRISE INTEGRATOR V6.1.1
CAPABILITY DETAILS
&
PROOF OF CONCEPT
PREPARED BY : GANESH NAGALINGAM

2. Subject Areas Explored
First cut PPT shared.
Product download, Product Bug fix, Setup, Configurations.
As part of PoC,
Explore and Design ESB runtime artifacts in Graphical Assembly area to connect to endpoints within WSO2 EI standalone produ
Capability check to see whether Binding external endpoint instances could be connected and communicated through WSO2 EI fro
external clients.
As part of PoC,
Explore ESB proxy services, API Resources, Data Mapper, WSO2 Broker profile for messages, Endpoints, Gmail Connectors.
Connect Wso2 EI and mediate with Axis2 WS Engine
Connect Wso2 EI and mediate with WSO2 Broker profile Engine
Connect Wso2 EI and mediate with MS4J Framework Engine
Connect WSO2 EI with External Tomcat Instance (External Endpoint)
Connect WSO2 EI and mediate with Spring Boot REST API services (External Endpoint)
Explore BPEL / BPMN process with BPS Engine.
As part of PoC,
Explore Dynamic Endpoint connections and advantages over Static Endpoint connections.
Collate information in Final PPT viz product screen shots, PoC screen shots, terminology etc.
Prepare Agenda for Demo.

3. PRODUCT DETAILS
• Product Size
• WSO2 EI v6.1.1 607 MB
• developer-studio-ei-eclipse-jee-mars-2-win64-x86_64-1.1.0 501 MB

4. WSO2 ENTERPRISE INTEGRATOR V6.1.1
SUITE OF PRODUCTS IN
CARBON PLATFORM
• Capabilities Available Capabilities Unavailable
• Axis2 WS Engine Application Server
• Enterprise Service Bus Integrator Engine
• BPEL, BPMN - Business Process Services Engine
• WSO2 Message Broker profile runtime
• MS4J Framework runtime
• Analytics Engine (Not explored in this PoC)

5. WSO2 ENTERPRISE INTEGRATOR V6.1.1
TERMINOLOGY AT GLANCE
• .aar (axis2 archive) deployed in Axis2 WS Engine
• .bar (business archive) deployed in Business Process Services runtime (BPMN applications)
• .car (composite archive) deployed in ESB runtime.
• .zip deployed in Business Process Services runtime (BPEL applications)

6. SCREEN CAPTURE - WSO2 EI - PRODUCT MANAGEMENT CONSOLE
• Local setup – As part of PoC, Applications deployed in Carbon Platform

7. SCREEN CAPTURE - ECLIPSE MARS.2 DISTRIBUTION DEVELOPER STUDIO
• Local setup – As part of PoC, Applications Design and Development

8. SCREEN CAPTURE – BUSINESS PROCESS SERVER – BPEL APPS
• Local setup – As part of PoC, Applications deployed in Carbon Platform

9. SCREEN CAPTURE – BUSINESS PROCESS SERVER – BPMN APPS
• Local setup – As part of PoC, Applications deployed in Carbon Platform

10. SCREEN CAPTURE – BPMN EXPLORER – BPMN APPS
• Local setup – As part of PoC, Applications deployed in Carbon Platform

11. PROOF OF CONCEPT : 1
• SOAP UI Client sending message via WSO2 EI (ESB) to AXIS2 WS Engine

12. PROOF OF CONCEPT : 2
• SOAP UI Client sending message via WSO2 EI (ESB) to External Tomcat Endpoint Instance

13. • Proof of concept : 3
• Postman Client sending message via WSO2 EI (ESB) to MS4J Framework runtime
• Message Transformation and Routing (If Client message format is different from message format of Backend service.

14. • Proof of concept : 3 (continued)
• Data Mapping

15. • Proof of concept : 4
• Postman Client sending message via WSO2 EI (ESB) to MS4J Framework runtime
• Message Transformation, Routing, Store and Forward Messaging, Gmail Connector (Send email)

16. • Proof of concept : 4 (continued)
• Postman Client sending message via WSO2 EI (ESB) to MS4J Framework runtime
• Message Transformation, Routing, Store and Forward Messaging, Gmail Connector (Send email)

17. • Proof of concept : 5
• Postman Client sending message via WSO2 EI (ESB) to Spring Boot Rest API Services (External)

18. • Proof of concept : 6
• SOAP UI Client sending message via WSO2 EI (ESB) to connect Dynamic Endpoint

19. • Proof of concept : 6 (continued)
• SOAP UI Client sending message via WSO2 EI (ESB) to connect Dynamic Endpoint

20. • Proof of concept : 7
• SOAP UI Client sending message via BPEL (BPS runtime) to connect External Tomcat Endpoint Instance

21. Proof of concept : 8
Messaging infrastructure – ActiveMQ
Purpose
Connect WSo2 EI v6.1.1 to external ActiveMQ Messaging Infrastructure
Issues
The existing StorableMessage class in synapse-core_2.1.7.wso2v15.jar of WSo2 EI v6.1.1 product
stores message in ActiveMQ in unreadable format as shown in Slide 23.
Fix
To overcome the issue StorableMessage class in synapse-core_2.1.7.wso2v15.jar of WSo2 EI v6.1.1
product has been modified, re-compiled, and re-packaged. Slide 24 shows the readable format.
Exact location where the StorableMessage class is modified, re-compiled and re-packaged is given
below.
synapse-core_2.1.7.wso2v15.jarorgapachesynapsemessagestoreimplcommons

22. Proof of concept : 8 (continued)
• Postman Client sending request via WSO2 EI (ESB) to store message in external Messaging infrastructure - ActiveMQ

23. Proof of concept : 8 (continued)
• Messaging infrastructure – ActiveMQ console

24. Proof of concept : 8 (continued)
Messaging infrastructure – ActiveMQ console - Message format in ActiveMQ
(Hard to Read)

25. Proof of concept : 8 (continued)
Messaging infrastructure – ActiveMQ console - Message format in ActiveMQ

26. Proof of concept : 9
Vertical Clustering
• Clustering are of 2 types. Horizontal and Vertical.
• To check the capability and for the purpose of Proof Of Concept demo, Vertical Clustering is
implemented in a Single Machine.
• Two instances of WSO2 EI product (EI1, EI2) are used as cluster members.
• HazelcastClusteringAgent is used in WSO2 EI product to create clusters.
• NGINX v1.13.12 (LB) Load Balancer , Windows distribution (zip) is configured to test Load
Balance and High Availability.

27. Proof of concept : 9 (continued)
Vertical Clustering
• Cluster members – EI1, EI2
Node EI1- Screen captures from command line console
Node EI1, listens at port 4100.
Screen capture shows Node EI2 has joined at port 4200.
Accepts HTTP request at port 8280.

28. Proof of concept : 9 (continued)
Vertical Clustering
• Cluster members – EI1, EI2
Node EI2 Screen captures from command line console
Node EI2, listens at port 4200.
Accepts HTTP request at port 8281.
When a node leaves the cluster, the other node will be notified as shown below.

29. Proof of concept : 9 (continued)
Vertical Clustering (Load Balancer)
• Cluster members – EI1, EI2
When Load Balancer is not configured :-
a. Node EI1 accepts HTTP request at port 8280.
b. Node EI2 accepts HTTP request at port 8281
When Load Balancer is configured :-
a. Load Balancer accepts HTTP request at port 80 and would route to 8280, 8281 based on Load and
Availability.

30. Proof of concept : 9 (continued)
Vertical Clustering (Load Balancer)
Screen captures of Load Balancer
a. Configure Load Balancer
b. Start Load Balancer
c. Send request to
Load Balancer at
port 80, that will
Route to 8280, (or)
8281 and response is
Received.

31. Proof of concept : 9 (continued)
Vertical Clustering (Load Balancer)
Screen captures of Load Balancer
d. When a node is shut down, the Load Balancer would route to available Node that is up and running.
e. The above screen shot shows that Node receiving request at port 8281 is shut down. But still a request is
able to fetch the response from port 8280, through port 80 (LB). See screen shot below;

32. PROOF OF CONCEPT : 10
WSO2 ENTERPRISE INTEGRATOR
INTEGRATION WITH
LDAP (APACHE DIRECTORY STUDIO)
Overview
WSO2 EI by default uses H2 Embedded Database as User Store. This PoC will demonstrate by
connecting WSO2 EI with External LDAP User Store. For PoC purpose, Apache Directory Studio is
downloaded and installed.
Integration steps
In the User-mgmt.xml, (wso2ei-6.x.xwso2ei-6.x.xconf) perform the following to integrate.
a. The JDBCUserStoreManager has to be commented out.
b. The ReadWriteLDAPUserStoreManager should be configured to connect with external LDAP
server. Slide 33 shows the LDAP Server running in local machine. The properties should be
configured as shown in slides 34, and 35.

33. PROOF OF CONCEPT : 10 (CONTINUED…)
WSO2 ENTERPRISE INTEGRATOR
INTEGRATION WITH
LDAP (APACHE DIRECTORY STUDIO)
• LDAP server

34. PROOF OF CONCEPT : 10 (CONTINUED…)
WSO2 ENTERPRISE INTEGRATOR
INTEGRATION WITH
LDAP (APACHE DIRECTORY STUDIO)

35. PROOF OF CONCEPT : 10 (CONTINUED…)
WSO2 ENTERPRISE INTEGRATOR
INTEGRATION WITH
LDAP (APACHE DIRECTORY STUDIO)
WSO2 EI
integrated
with LDAP
successfully
can be seen in
the command
console. (See
the underline
in blue)

36. PROOF OF CONCEPT : 11
APPLYING SECURITY POLICY
IN
ESB APPLICATION DEPLOYMENT
Overview
a. An application deployed in ESB (.car) can be secured. This PoC will show through screen shots the
following aspects:
1. Configure WS Policy, Username Token.
2. Apply the Security policy to ESB Proxy Service.
3. Invoke the Proxy Service URL providing Authentication.
4. As WSO2 EI is integrated with LDAP, the credentials will be authenticated in LDAP server.
5. WSO2 EI Management console will take LDAP user credentials to login, and also allow to create
Users and Roles. (see slides 32-35 on ESB – LDAP Integration (PoC :10)
6. Users created through WSO2 EI Management console will get stored in LDAP server.

37. PROOF OF CONCEPT : 11 (CONTINUED…)
APPLYING SECURITY POLICY
IN
ESB APPLICATION DEPLOYMENT
1. Configure WS Policy, Username Token in ESB Proxy Service.

38. PROOF OF CONCEPT : 11 (CONTINUED…)
APPLYING SECURITY POLICY
IN
ESB APPLICATION DEPLOYMENT
2. Apply Security Policy in ESB Proxy Service. (Configured area highlighted)

39. PROOF OF CONCEPT : 11 (CONTINUED…)
APPLYING SECURITY POLICY
IN
ESB APPLICATION DEPLOYMENT
3. Invoke Proxy Service URL providing Authentication from Soap UI.
4. As WSO2 EI is integrated with LDAP, the credentials will be authenticated in LDAP server and response will be
returned..

40. PROOF OF CONCEPT : 11 (CONTINUED…)
APPLYING SECURITY POLICY
IN
ESB APPLICATION DEPLOYMENT
5. WSO2 EI Management console will take LDAP user credentials to login, and also allow to create Users and
Roles.
6. Users created through WSO2 EI Management console will get stored in LDAP server.

41. THANK YOU