Mule技术入门指南英文版

下载需积分: 9 | PDF格式 | 1.7MB | 更新于2024-08-02 | 138 浏览量 | 举报

"Mule2.xGettingStartedGuide" Mule 是一个开源的企业服务总线（Enterprise Service Bus，简称 ESB）和集成平台，它提供了一种简单而强大的方式来连接各种应用、系统和服务。该资源是Mule技术的入门手册，英文版，适用于初学者和希望了解Mule 2.x 版本的开发者。手册涵盖了以下关键知识点： 1. **基本使用**：这部分内容可能介绍了Mule的基本概念，如如何启动和停止Mule服务器，以及如何配置和管理Mule项目。 2. **示例**：手册包含多个示例项目，如`BookstoreExample`、`EchoExample`和`LoanBrokerExample`，这些示例旨在帮助用户理解Mule的工作原理和实际应用，通过实际操作来学习Mule的各种功能。 - `BookstoreExample` 可能是一个模拟书店业务流程的应用，展示了如何处理订单、库存管理和支付等集成场景。 - `EchoExample` 可能是一个简单的回显服务，用于演示Mule如何接收和转发消息。 - `LoanBrokerExample` 可能涉及贷款审批流程，展示Mule在业务流程管理（BPM）中的应用，可能包括与不同服务交互，如信用评估、风险分析等。 3. **错误处理**：`ErrorHandlerExample`部分讨论了如何在Mule中处理和恢复错误，这对于构建健壮和高可用性的集成解决方案至关重要。 4. **脚本支持**：`ScriptingExample`解释了如何在Mule中使用脚本语言，如Groovy或JavaScript，进行动态数据处理和逻辑控制。 5. **股票报价示例**：`StockQuoteExample`可能展示了如何集成到实时股票报价服务中，从而获取和处理市场数据。 6. **迁移指南**：手册还提供了从不同版本的Mule迁移到2.x的指南，如`MigratingfromCommunitytoEnterprise`、`MigratingMule1.xto2.0`等，这对于已有Mule项目的用户升级和维护非常有用。 7. **教程**：`LessonOne`至`LessonFive`构成的教程部分，逐步引导用户了解Mule的核心概念和技术，帮助他们快速上手。 8. **新特性介绍**：`WhatsNewinMule2.0`和`WhatsNewinMuleEE2.1`章节，分别列出了Mule 2.0和Mule Enterprise Edition 2.1版本引入的新特性和改进，对于跟踪Mule的最新发展很有帮助。 9. **安装与集成**：手册还包括如何安装Mule以及如何将其集成到开发环境中，如使用Eclipse和Maven的配置说明。这个Mule技术开始手册是全面了解和学习Mule 2.x 版本的宝贵资源，无论你是刚开始接触Mule，还是已经有一定经验的开发者，都能从中找到有价值的信息。通过实践手册中的示例和教程，可以深入理解Mule的集成能力，掌握如何构建和部署高效的企业级服务和应用。

Document generated by Confluence on Sep 30, 2009 14:02 Page 16

Echo Example

This page last changed on Sep 14, 2009 by jwheeler.

Echo Example

[ Running the Application ] [ The Echo Component ] [ Configuring the Service ] [ Invoking the Service ] [

Exposing the Service as a Web Service with Axis ] [ Exposing the Service as a Web Service with CXF ]

Some of the links on this page go to the Mule User Guide, which requires that you log in to

see the links. Registration is free and takes only a few moments.

The example demonstrates how to expose a Mule ESB component over multiple transports. In this

example, the component is exposed as an Axis web service that receives messages via System.in

(request) and sends them via System.out (response).

Cannot resolve external resource into attachment.

Running the Application

1. Make sure you have met the prerequisites and installed Mule according to the Installing Mule

instructions.

2. At the command line, navigate to the examples/echo directory under your Mule home directory.

3. Type echo.bat on Windows or ./echo on UNIX.

4. Follow the on-screen prompts.

5. To stop Mule, type 'CTRL-C' in the Mule console window.

The Echo Component

The Echo service is based on a POJO component that implements the EchoService interface:

public interface EchoService

{

public String echo(String echo);

}

The component looks like this:

package org.mule.components.simple;

public class EchoComponent extends LogComponent implements EchoService

{

public String echo(String echo) {

return echo;

}

Configuring the Service

To configure the service, you add a <service> element to your Mule XML configuration file and provide

the name attribute. You specify the class of the service component with the <component> element. To

reference objects from the Spring registry, you would use the nested <spring-object> element instead.

Document generated by Confluence on Sep 30, 2009 14:02 Page 17

</service>

The class attribute must be the fully qualified path name to the class. The name attribute must be a

unique name for the service.

You can also use the shortcut for the Echo service component by simply specifying the following element:

<echo-component/>

Invoking the Service

Next, you need to configure endpoints on the service so that it can be invoked. When you ran the

example, you were prompted to enter something at the command line. When you entered something,

you were invoking the EchoUMO service by providing input data from System.in, and then the data you

entered was echoed back to you via System.out. The Mule STDIO transport manages this interaction.

Following is the configuration for the EchoUMO service with the endpoints included. Note that you can

have multiple inbound endpoints.

<stdio:inbound-endpoint system="IN"/>

<vm:inbound-endpoint path="echo"/>

</inbound>

<echo-component/>

<pass-through-router>

<stdio:outbound-endpoint system="OUT"/>

</pass-through-router>

</outbound>

</service>

</model>

The <inbound> element allows one or more inbound endpoints to be configured for a service. In this

example, one endpoint uses the STDIO transport, and the other uses the VM transport.

The <inbound-endpoint> element specifies both the transport to use and the address, path, or resource

from which this component will receive events. This example uses transport-specific endpoints, so the

STDIO endpoint just specifies IN to receive messages on System.in, and the VM endpoint specifies a

path. Generic endpoint configuration can also be used by specifying a URI, such as vm://echo or http://

locahost:8080. For more information, see Configuring Endpoints in the Mule User Guide.

The <outbound> element allows one or more outbound router elements to be configured that control

how and where message are sent once they have been processed by the component. In this example, all

message are sent via System.out using the pass-through router.

Lastly, you can configure a connector if you want to override the default configuration used by the

transport specified on an inbound endpoint. In this example, let's override the STDIO transport's default

connector configuration so that it will prompt the user for input:

<stdio:connector name="SystemStreamConnector"

promptMessage="Please enter something: "

Document generated by Confluence on Sep 30, 2009 14:02 Page 20

Error Handler Example

This page last changed on Sep 14, 2009 by jwheeler.

Error Handler Example

The error handler example demonstrates using Spring beans as Mule ESB service component

implementations and how to publish messages to multiple outbound endpoints. The sample consists of

two services: ExceptionManager and BusinessErrorManager. The BusinessErrorManager is a simple service

used to log a message to the console when a message is received. In this example, it is used to receive

BusinessException message over JMS to simulate a real-world exception processing application.

The ExceptionManager is a service that receives exception messages and performs some action

depending on the type of exception. For example, if a fatal exception is received, an email is sent to the

system administrator. If a standard system exception is received, it is logged to a file on the local file

system. The purpose of this example isn't to implement an exception handler, but to demonstrate the

following features:

• All the service components in the error handler are configured as Spring beans in the same Mule

configuration file.

• The error manager has multiple outbound endpoints configured on it, and the example

demonstrates how to dispatch to different endpoints.

• The messages in the system are Java objects and need to be converted to and from XML. The

example demonstrates chaining multiple transformers together.

Cannot resolve external resource into attachment.

Running the Application

Prerequisites

Prior to running the example, you must download several JARs using the supplied build scripts with either

Ant (version 1.6.5 or later) or Maven (version 2.0.9 or later). This means you must have an Internet

connection available and have set up your environment correctly as described in Installing Mule.

Preparation

1. At a command prompt/shell, navigate to the examples/errorhandler directory under the Mule

distribution root.

2. If you are running this example for the first time, run either the Ant command ant or the Maven

command mvn, depending on which tool you want to use.

3. When you see output indicating that the required JARs have been downloaded to the MULE_HOME/

lib/user directory, proceed with the "Running" section below.

Running the Example

1. At a command prompt/shell, navigate to the examples/errorhandler under the Mule distribution

root.

2. Edit the conf/email.properties file with the SMTP settings for your environment. These settings

are required for the Error Handler example to send an alert email.

3. Run the errorhandler script. The Mule startup screen displays.

4. Open another console window and navigate to the examples/errorhandler/test-data/out

directory. This directory contains three files : MuleException.xml, BusinessException.xml, and

FatalException.xml.

5. Move each of these files into the ../in directory one by one to see what happens. Each exception

type will trigger a different endpoint. Note that the FatalException.xml file will cause Mule to send an

email using the properties you specified in conf/email.properties.

6. To stop Mule, type 'CTRL-C' in the Mule console window.

剩余158页未读，继续阅读

wlystrong

粉丝: 0

Mule技术入门指南英文版

Mule_入门、介绍及架构理解

mule esb开发手册

MuleStudio用户手册

MuleStudio开发手册：入门与核心技术

muleesb开发手册

MuleStudio用户手册.doc

MuleESB用户手册第一章.pdf

mule esb 企业版说明

Mule in Action

emule用户手册，英文版本

最新资源