Modeling SOA, Part 3. Service realization
From the developerWorks archives
Date archived: February 23, 2017 | First published: October 16, 2007
This third article of this five-part series explains how SOA-based Web services are actually implemented. The service realization starts with deciding what component will provide what services. That decision has important implications in service availability, distribution, security, transaction scopes, and coupling. After these decisions have been made, you can model how each service functional capability is implemented and how the required services are actually used. Then you can use the UML to SOA transformation feature included in IBM® Rational® Software Architect to create a Web services implementation that can be used in IBM® WebSphere® Integration Developer to implement, test, and deploy the completed solution.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.