Developing a Service Oriented Solution

The service oriented solution demonstrates a credit account balance system for Woodgrove Bank. Information about an account comes from three legacy systems: an SAP system that provides the credit limit, a pending transactions system running on a mainframe, and a payment tracking system using MQSeries. Balance check requests come through a Web service or an Interactive Voice Response (IVR) system. For more information about the scenario, see Understanding the Service Oriented Solution.

This Developer's Guide presents one approach to building a service oriented architecture solution for the Woodgrove Bank scenario. The Guide begins by considering a possible solution in terms of industry-standard patterns. "Patterns in the Service Oriented Solution" begins the translation of that pattern into the appropriate artifacts of a BizTalk application. The next section, "Components of the Service Oriented Solution," summarizes the various parts of the application and their relationships. The Implementation Highlights section discusses areas—such as using Enterprise Single Sign-On—that required special work to meet the criteria of the scenario. "Monitoring the Service Oriented Solution with BAM" describes how the solution uses the BAM API to track progress of requests and results. The "Versioning the Service Oriented Solution" and "Scaling the Service Oriented Solution" sections suggest ways of extending or modifying the solution. The reference section lists the files in the solution and provides a reference to the messages.

In This Section

• Patterns in the Service Oriented Solution

• Components of the Service Oriented Solution

• Implementation Highlights of the Service Oriented Solution

• Monitoring the Service Oriented Solution with BAM

• Versioning the Service Oriented Solution

• Scaling the Service Oriented Solution

• Service Oriented Solution Reference