Introduction to Enterprise Application Integration and Open-Source ESB products ServiceMix and mule

Introduction to Enterprise Application Integration and Open-Source ESB products ServiceMix and mule

Agenda

• Internal requirements of enterprises for Application Integration
• Problems faced by enterprise IT facilities
• Architecture solution for Enterprise Application Integration
• Roles and Responsibilities of ESB
• ServiceMix Introduction
-ServiceMix Architecture
-ServiceMix component Overview
-ServiceMix practice
-Demo
• Mule Introduction
-Mechanism of mule
-Mule component Overview
-Mule practices
-Demo

Internal requirements of enterprises for Application Integration

• At the initial stage of most enterprises, most of their applications were used to replace isolated and repetitive work links without considering the integration of business and data.
• When enterprises develop to a certain stage, they begin to realize the value and necessity of application integration. All departments of an enterprise, as well as enterprises and partners, must coordinate and cooperate closely. The original isolated applications within the enterprise cannot meet this requirement. This prompted enterprises to start looking for application integration solutions.

Problems faced by enterprise IT facilities

• Multiple isolated systems
-The collaboration between departments is weakened.
-Integration of affected resources
• Inconsistent Data Formats

• Unable to communicate effectively with the partner's System

Architecture solution for Enterprise Application Integration

• Point-to-point Solution
• Hub-and-spoke Solution
• Enterprise message bus Integration
• Enterprise Service Bus Integration

Point-to-Point Architecture

 

 

Architecture of the ESB Style

Roles and responsibilities of ESB

• Providing connectivity (supporting cross-Protocol)
• Data Transformation (including data format conversion)
• (Intelligent) routing
• Dealing with security
• Dealing with reliability
• Service Management
• Monitoring and logging

Introduction to ServiceMix

ServiceMix is an ESB product built based on jbi (JSR 208) specifications. As a member of ASF, it integrates activemq, camel, cxf, Ode, A series of excellent ASF products and tools, including Karaf.
Advantages of ServiceMix: fully compliant with jbi specifications; well integrated with other excellent ASF products and tools
Disadvantages of ServiceMix: the expansion components are not rich enough; the documents are not updated timely and comprehensive (I personally feel that there is a big gap between the product maturity and mule)

ServiceMix Architecture

 

ServiceMix component Overview

ServiceMix functions are provided by components, so it can be said that the number of components determines the number of ServiceMix functions, the following is the list of ServiceMix components: http://servicemix.apache.org/components-list.html

 

ServiceMix practice

• Use the mavenarchetype tool provided by ServiceMix to quickly create a ServiceMix Project
• ServiceMix project package structure:

• Example:
1. Create SA: mvnarchetype: Create-darchetypeartifactid = ServiceMix-service-assembly-darchetypegroupid = org. Apache. ServiceMix. tooling-dgroupid = net. SF-dartifactid = demo-sa
2. create su: mvnarchetype: Create-darchetypegroupid = org. apache. serviceMix. tooling-darchetypeartifactid = ServiceMix-http-provider-service-unit-dgroupid = net. SF-dartifactid = demo-su

Demo

This demo shows a basic function of ESB: connecting two systems. Source code can be checked out from SourceForge, SVN address https://mydemolib.svn.sourceforge.net/svnroot/mydemolib

The demo steps are as follows:

1. Start cxfdemo-server to publish the service: mvnclean jetty: Run
2. Start cxfdemo-client and directly connect to the Service released by cxfdemo-server to confirm that both the server and client work properly: mvncompile Exec: Java
3. build and deploy the project servicemixdemo-http-sa to ServiceMix
4. Modify the connection configuration of the cxfdemo-client, connect it to ServiceMix, restart the cxfdemo-client, and still access the required services through the ESB.

Introduction to mule

Mule: currently the most mature ESB product in the open-source community, which is robust in terms of connectivity, data transmission, and routing. Its maturity is manifested in: It has a rich set of extension components, complete documentation, and is supported by most application servers. In particular, mule provides a series of cloud connectors so that mule can be integrated with cloud platforms such as amasonec2.

Mechanism of mule

 

Mule component Overview

Like ServiceMix, mule provides and extends functions in the form of components. mule has two main types of components: Transport and module. Transport is a component related to a specific transmission protocol, while module is a component unrelated to the protocol and does not transmit or receive data.
Official transport components: http://www.mulesoft.org/documentation/display/MULE3USER/Transports+Reference
Module components: http://www.mulesoft.org/documentation/display/MULE3USER/Modules+Reference
Components provided by the community:
Http://www.mulesoft.org/community-transports-modules

Mule practice

Use the mavenarchetype tool provided by mule to quickly create a mule project.
Example:
Mvnmule-project-archetype: Create-dartifactid = muledemo-dmuleversion = 3.1.2
Note: When transport or module is not specified, the archetype tool always introduces the default transport or module to manually delete unwanted components from the generated mule-config.xml.

Demo

This demo shows a basic function of ESB: connecting two systems. Source code can be checked out from SourceForge, SVN address https://mydemolib.svn.sourceforge.net/svnroot/mydemolib
The demo steps are as follows:
1. Start cxfdemo-server to publish the service: mvnclean jetty: Run
2. Start cxfdemo-client and directly connect to the Service released by cxfdemo-server to confirm that both the server and client work properly: mvncompile Exec: Java
3. build and deploy the project muledemo-Bridge to mule
4. Modify the connection configuration of the cxfdemo-client, connect it to the mule, restart the cxfdemo-client, and still access the required services through the ESB.

Summary

• ESB is the core component of enterprise application integration. It is mainly responsible for connecting various applications that use different protocols for communication.
• ServiceMix is the implementation of jbi specifications
• Mule is currently the most mature Open-Source ESB product, backed by commercial support, powerful functions, and rich plug-ins
• Overall Evaluation: mule is better than ServiceMix