Explanations of several rankings in the mule Architecture

1 Connectors: a connector that supports different protocols. For example, Http, FTP, Mail, Soap, JMS, and MQ. There are usually three types of connectors: for receiving only, for sending only, and for both.

2 EndPoints Address: terminal Address, something similar to jms: // topic: myTopic. The previous jms is the connector type. Each connector can recognize other addresses. This address can be the address recognized by the receiver. For example, jms: // topic: myTopic indicates listening to the queue of myTopic. It can also be the address identified by the sender. For example, pop3: // user: The password@mail.mycompany.com sends a message to a remote mailbox.

Note that the address here is your own name. Generally, different applications have different addresses. For example, an application is jms: // topic: myTopic. The other is jms: // topic: myTopic2.

3 UMO Components: As you can imagine, this is a chip and a controller on the ESB bus. In the Mule, they are some POJO responsible for receiving messages, processing them, and sending them out. For example, an UMO listens to messages in jms: // topic: myTopic. If yes, it is sent to pop3: // user: password@mail.mycompany.com after processing.

Obviously, UMO simply calls EndPoints Address to receive and forward messages. It does not need to know what protocol it uses to receive and send messages. This is the role of the ESB, that is, to provide a unified Bus Interface

Trackback: http://tb.blog.csdn.net/TrackBack.aspx? PostId = 482128