Based on Apache Camel, Fuse ESB Enterprise's embedded routing and integration service is a framework for building integration and routing solutions using enterprise integration patterns (EIPs). Using Fuse ESB Enterprise's routing and integration service, you can quickly define and implement routes. A route defines an integration path between endpoints—between an input source (consumer) and one or more output destinations (producers). While data is in route between endpoints, you can manipulate it using enterprise integration patterns or custom processors such that the data arrives at each target destination in the format each requires.
Fuse ESB Enterprise's routing and integration service provides two DSLs—one based on Java and one based on XML—which you can use to specify routing rules. The DSLs contain methods named after the EIPs described in Enterprise Integration Patterns—Designing, Building, and Deploying Messaging Solutions (Hohpe and Woolf).
Fuse ESB Enterprise's routing and integration service makes it easy to develop integration solutions. Some of its features are:
Routing and mediation engine
The routing and mediation engine is the core feature of the service. It moves messages from point to point, according to routes configured using EIPs.
Enterprise integration patterns
Within routes, you can use the supported enterprise integration patterns (EIPs) to implement processors, or create your own using plain old Java objects (POJOs). EIPs provide proven solutions for specific integration design problems. The patterns have evolved over time, having been tested and refined through serious use. Out of the box, Fuse ESB Enterprise supports over sixty EIPs. (See Routes and processors.)
For more details, see Implementing Enterprise Integration Patterns.
Modular and pluggable architecture
Fuse ESB Enterprise's routing and integration service has a modular architecture, which enables you to load any component into it, whether the component is provided by Fuse ESB Enterprise, a third party, or custom-built by you.
Convention Over Configuration
Fuse ESB Enterprise's routing and integration service adheres to the convention over configuration design paradigm whenever possible to minimize configuration requirements. For example, the routing and integration service uses an easy and intuitive URI scheme to configure endpoints directly within routes.
Automatic type converters
Fuse ESB Enterprise has a built-in type-converter mechanism and provides over 150 converters. This mechanism enables Fuse ESB Enterprise's routing and integration service to easily adapt to many protocols, and it also eliminates the need to configure type-converter rules. If you need to convert unsupported types, you can create your own type converter.
 |  |  |
 |
