You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 64 Next »

The purpose of an Enterprise Service Bus (ESB), also known as a Java Business Integration (JBI) bus, is to provide a mechanism for different applications to exchange messages in a protocol neutral manner and provide services for processing those messages such as message transformation and dynamic routing. Although not a requirement, messages exchanged between business applications are typically done asynchronously. ServiceMix is an implemenation of JSR 208, the JBI specification.

The Basic example demonstrates how external 1 applications communicate via the ESB. Similar techniques could be used to plug any external application or service into ServiceMix (e.g. SAP, Peoplesoft, spreadsheets, POJOs, Webservices and EJBs) and allow it to communicate with other external applications or components within ServiceMix itself.

A common business scenario, which extends the Basic Example, is that of a large department store distributor. This distributor sells products from many wholesalers to many retail outlets (i.e., department stores). The distributor presents a common interface for product ordering to each of its department store customers. However, each wholesaler presents a different ordering interface to the distributor for the product the wholesaler supplies.

Using an ESB, the distributor has developed a number of components to receive department store orders and dynamically route and transform these orders to the appropriate wholesaler. The order flow is described as follows:

  1. Using the distributor's web interface, a department store buyer submits an order for multiple products. An HTTP request is sent to the OrderReceiver, an HTTP binding component (BC). 3
  2. The OrderReceiver sends the message to an OrderRouter service engine (SE) 4 component. This SE is responsible for parsing the order and deciding, based on the message content, which OrderTransformer should receive which part of the message (i.e., an order for a product).
  3. The OrderRouter publishes the orders to the appropriate message topics based on the message content. Specifically, the OrderRouter publishes the messages based on which wholesaler sells the item.
  4. The OrderTransformer is a service engine component, which modifies the message and puts it in a format which is readable by the wholesaler interface that will fulfill the order.
  5. Each OrderTransformer sends the modified message to the OrderProcessor.
  6. The OrderProcessor is a binding component that has two functions:
    a. It places an order to the appropriate wholesaler through the wholesaler's Webservice or proprietary interface.
    b. It also publishes a message about the order on a topic.
  7. The message on the topic is subsequently picked up by the BusinessMonitor component via the jmsTrace component.
  8. The BusinessMonitor component monitors the orders for quality assurance and business analytics, such as data mining.

The following diagram illustrates this:

Department Store Distributor's Order Processing System

  1. External means the application is outside of the enterprise service bus.
  2. Resource Adapter: a resource adapter provides connectivity between a specific external application and the ESB. In the Basic example the jencks container provides a JMS resource adapater.
  3. Binding Component (BC): a BC provides connectivity to applications that are external to the ESB.
  4. Service Engine (SE): a service engine provides business logic and transformation services to other components within the enterprise service bus.
  • No labels