Developing a Web service using an industry-specific messaging standard
From the developerWorks archives
Date archived: January 5, 2017 | First published: July 05, 2007
Web services are a key ingredient of service-oriented computing and Service-Oriented Architecture (SOA). Interactions between service consumers and service providers are primarily message-based. The structure of these messages is defined in a serviceâs interface definition, specified in Web Services Description Language (WSDL). Organizations are increasingly moving toward supporting industry-specific messaging standards. This article describes an approach to developing a Web service that uses the ACORD messaging standard for an insurance industry client. With the help of an example, you can see how a Web service definition is created based on business process decomposition, including mapping data elements to their respective standard schema elements. You can also see considerations when dealing with schema maintenance, data binding, and data typing during runtime and build time. While this article offers only a glimpse into what is needed to fully utilize a standard message model, it tries to describe one key aspect of it and serves as a starting point for further discussion.
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.