Intro to Mule ESB and the Elegant 'Endpoint' Data Channel
The Integration Zone is brought to you in partnership with Red Hat. Download the IDC Report: The Business Value of Red Hat Integration Products to learn more about Red hat Integration.
This is a core concepts example that demonstrates how to invoke a Mule application using HTTP. The example introduces two key concepts in Mule:
- Flow - A Mule flow is a flexible way to build integrations by simply choosing building blocks from Mule's wide range of functionality and gluing them together.
- Endpoint - An endpoint is a channel to receive or send data in Mule. An endpoint has a specific protocol such as HTTP or JMS and a set of elements for configuring filters, transactions, transformations and more. There are 2 types of endpoints: inbound or outbound. An inbound endpoint allows a flow to be called by an external client. In this particular example, we will use an HTTP inbound endpoint, but most endpoints in Mule can be used for inbound and outbound communication. Conversely, an outbound endpoint is used to publish data to a service, application or resource.
Read more in the Mule Endpoint Docs