The promised business value of Service-Oriented Architecture (SOA) is driving many enterprises to purchase key SOA-related technologies, such as an Enterprise Service Bus (ESB), in advance of the forthcoming architecture. However, the road to SOA is not always clear, and many enterprise architects, developers, and project leaders require guidance to understand the steps to SOA success. Such guidance must include clear, interactive, and adaptive process that ensures that team members understand all requirements, document all details, and plan all testing and implementation tasks.

The purpose of this manual is to walk those charged with designing and building their SOA implementation through the issues, steps, and procedures they require to create their first iteration of SOA, and how to build on that experience to drive a more systemic change within their enterprise. We’re going to take you through this journey assuming that you have the technology on hand, whether that is an integration server, application server, or an ESB, and focus on the best practices and architectural patterns for that particular category of technology. Since SOA is by nature heterogeneous, strategies for resolving architectural challenges earlier in the lifecycle using well-defined semantics will be discussed.

Systemic to this manual is how to approach testing in the context of SOA. While many consider testing as something that is at the end of the process, it’s actually a part of each step. Thus, as part of this manual we will teach you about testing approaches and key enabling technology.Download File