5.2 Application Integration patterns

 < Day Day Up > 



5.2 Application Integration patterns

In the following topics, we take a look at basic Runtime patterns for the Application Integration Broker and Router patterns. Each Runtime pattern is shown overlayed with its underpinning Application pattern. The location of the tiers in the Application pattern correspond to the location in the Runtime pattern that provides the function of that tier.

Following the Runtime pattern will be a product mapping that shows one way of implementing the Runtime pattern.

5.2.1 Runtime pattern and product mapping for the Broker

Figure 5-1 shows the basic Runtime pattern for the Broker application pattern.

click to expand
Figure 5-1: Broker Runtime pattern

The Broker tier in the application pattern is implemented in this Runtime pattern with a Broker node. The Broker node is responsible for the routing and distribution of incoming messages to the target applications. It has the ability to decompose and recompose messages.

The Application Server/Services nodes execute the logic of the target and source applications.

Figure 5-2 shows a product mapping for this Runtime pattern using WebSphere Business Integration Message Broker.

click to expand
Figure 5-2: Product mapping for Application Integration--Broker

WebSphere Business Integration Message Broker provides all the function needed for this solution. Among the many features of this product are:

  • Point-to-point publish/subscribe and multi-cast models

  • Support for MQSeries®, mobile, telemetry, real-time, and reliable IP multi-cast models

  • Content and table-driven routing capabilities

  • Powerful engine for message/data transformation and database integration

  • XSLT engine for XML transformation

  • Message filtering and message warehousing

  • Web services (SOAP/HTTP) protocol support

5.2.2 Runtime patterns and product mappings for Router

Figure 5-3 shows the basic Runtime pattern for the Router variation of the Broker.

click to expand
Figure 5-3: Application Integration--Broker- Router variation Runtime pattern

The Router node provides the logic to perform intelligent routing of messages to one target application at a time. It does not include the simultaneous distribution or decomposition capabilities that the Broker node provides.

Figure 5-4 shows a product mapping for this Runtime pattern using Web Services Gateway.

click to expand
Figure 5-4: Product mapping for Router

Note that WebSphere Business Integration Message Broker can also provide Router functionality.



 < Day Day Up > 



Patterns. Broker Interactions for Intra- and Inter-Enterprise
Patterns. Broker Interactions for Intra- and Inter-Enterprise
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 102

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net