9.5 System design overview

 < Day Day Up > 



9.5 System design overview

With the design guidelines in mind, ABC Electronics decided to implement their solution in three stages using WebSphere Business Integration Message Broker V5 as the broker.

9.5.1 Stage 1: Internal "Get earliest delivery date" solution

In the first stage of the solution, the Retail department will use a broker to access the internal Wholesale departments.

Figure 9-10 shows a high-level design view of the solution.

click to expand
Figure 9-10: Aggregation design

The solution will consist of the following elements:

  • A Retail application that requests delivery dates from Wholesale applications using the part number as input. This application invokes a Web service in order to get the delivery date.

  • A message flow deployed on WebSphere Business Integration Message Broker that distributes the request to all the Wholesale systems that can provide that part. The message flow is built using aggregate nodes in order to make the fact that there are multiple Wholesale systems transparent to the client. The message flow will collect the responses from the Wholesale systems, examine them to determine which date is the earliest, and send that date back to the client.

    This message flow is available to the client as a Web service.

  • A Wholesale system that returns a delivery date for a part it contains in its inventory. The application is implemented using an EJB and has been Web-service enabled.

To simplify and standardize the access to the broker process, the WebSphere MQ Web Services Transport features of WebSphere Business Integration Message Broker will be used. The requests for delivery dates are non-critical to the business and if a response is not received in a reasonable amount of time, the request can be easily sent again.

In this scenario, we are combining two aspects of Web service support provided by WebSphere Business Integration Message Broker:

  • The message flow is available to clients as a Web service and is accessed using HTTP.

  • The message flow sends a message to a Web service to get a reply for the client. This also uses the HTTP protocol.

The primary message flow uses the aggregator node to send the request to multiple Wholesale systems. It is important to note that the aggregator node is designed for MQ message input so in this stage you will see examples of converting messages from one format to another.

9.5.2 Stage 2: Internal sales forecast publish/subscribe

Stage 2 will use a publish/subscribe model to allow the Retail systems to publish their sales forecast information to large numbers of Wholesale system subscribers (Figure 9-11).

click to expand
Figure 9-11: Real-time flow design

The solution will consist of a publish/subscribe mechanism to allow the Retail clients to distribute sales information to the Wholesale applications

Because a large number of messages need to be published and persistent delivery is not required, this design will use the WebSphere MQ Real-time Transport features of WebSphere Business Integration Message Broker.

9.5.3 Stage 3: External "Get earliest delivery date" solution

Stage 3 will extend the solution in stage 1 to allow the Retail departments to access external Wholesale suppliers. The addition of a gateway will allow the internal Retail departments to access the external Wholesale processes through a standard interface (Figure 9-12).

click to expand
Figure 9-12: Aggregation design

A gateway will be used to minimize the impact of using external services. It will provide the mapping between the internal clients and the external services.

Note 

A variation of this is the situation where you want to make the Broker processes available to external clients. For an example of exposing WebSphere Business Integration Message Broker message flows to external clients as Web services, see Using Web Services for Business Integration, SG24-6583.



 < 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