|
|
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Page 4 of 7
I use the Mule framework to demonstrate the concepts and ideas discussed in this article.
The Mule architecture consists primarily of the following elements:
The UMO API defines the services and interactions of objects to be managed by Mule.
UMO components can be any component in the Mule system that receives, processes, and sends data as event messages.
The Mule server component is a server application launched to bootstrap the Mule environment.
The descriptor components describe a Mule UMO's attributes. New Mule UMOs can be initialized as needed from their associated descriptor. A descriptor consists of:
Connectors are components that provide the implementation for connecting to an external system or protocol and managing the session for that system or protocol. A connector is responsible for sending data to an external message receiver and for managing the registration and deregistration of message receivers.
Providers are components that manage the sending, receiving, and transformation of event data to and from external systems. They enable connections to external systems or other components in Mule. A provider acts as a bridge from the external system into Mule and vice versa. It is, in fact, a composite of a set of objects used to connect to and communicate with the underlying system. The elements of a provider are:
Endpoint resolvers determine what method to invoke on a UMO component when the component receives an event.
Transformer components transform message or event payloads to and from different data formats. Transformers can be chained together to perform successive transforms on an event before an object receives it.
Message adapters provide a common manner in which to read disparate data from external systems.
Message receivers are listener-endpoint threads that receive data from an external system.
Message dispatchers send (synchronous) or dispatch (asynchronous) events to the underlying technology.
Message routers are components that can be configured for a UMO component to route a message to deferent providers based on the message or other configuration.
Agents are components that bind to external services such as Java Management Extension servers.
Archived Discussions (Read only)