[SOA] Mule ESB Linux deployment

This article describes how to deploy mule ESB on Linux. Mule is a lightweight messaging framework and integration platform centered on java. It is implemented based on EIP (Enterprise integeration patterns, a book written by hohpe And Woolf. The core component of mule is UMO (universal message objects, which has been replaced by componse since mule2.0). UMO implements the integration logic. UMO can be pojo or JavaBean. It supports over 30 transmission protocols (such as file, FTP, UDP, TCP, email, HTTP, soap, and JMS) and integrates many popular open-source projects, such as spring, activemq, cxf, axis, drools, etc.

By the way, the concept of ESB (Enterprise Service Bus) is as follows:

Let's talk about mule. mule studio is a powerful eclipse-based development tool () with user-friendly interfaces (). Users can easily create, edit, and test the mule ESB process within minutes without having to have a deep understanding of the XML configuration Syntax of mule. Based on Eclipse technology, mule studio consists of three main components: the project structure tree, toolbox, and canvas. The project structure tree contains the directory structure of the entire project. After creating a mule project, you will see the mule project name and the following file and directory structure:

Path	Description
Src/main/Java	Stores custom Java classes
Src/main/Resources	Storage Flowchart
Src/test/Resources	Stores custom Java test classes
Application	Stores mule deployment attribute files
SRC	Main/APP contains the XML file of the process; Main/test contains the file related to the process test.
Mule-project.xml	Project metadata file. You can edit the name, description, and running version of the server.
JRE system library	Java runtime libraries.
Mule Runtime	Mule runtime libraries.

Is the project structure tree in mule studio:

In test. mflow, you can drag and drop to control the service process. Is a simple example of HTTP-Inbound/HTTP-outbound.

In this example, the forwarding function is actually implemented. mule ESB will expose the Internal Service http: // localhost: 8090 through http: // localhost: 8080 for XML Schema validation. View the original xml configuration as follows:

    <flow name="proxyFlow" doc:name="proxyFlow">      
Next, let's take a look at how to deploy the ESB (of course, you have to prepare a web service first)
1. Export the mule Application: Right-click the mulestudio project and choose export to save a. ZIP file.
 
2. Deploy mule manage Console (MMC) in Linux)
First, make sure that Java 1.6 is installed in Linux. Download MMC:Tar-xvzf mmc-distribution-mule-console-bundle-3.3.2.tar.gzAfter decompression, run mule in the/mule-enterprise-standalone-3.3.2/bin directory, which starts the mule MMC. Next, you can deploy the Service on the web page of mule.

3. Deploy the mule application (flow) through web pages)
Http: // localhost: 8585/MMC

Add the previously generated ZIP file for release.

4. Post-release monitoring
You can monitor published mule applications in sequence, such as the service running status, request, response, and other information.


Next, we will continue to introduce the configurations of mule flow in several typical scenarios.