Skip to main content


developerWorks  >  SOA and Web services  >

An approach to moving industry business messaging standards to Web services

Comparing business messaging and Web services

developerWorks

Level: Introductory

Contributors: IBM

21 Dec 2004

Get the download

The authors of this whitepaper show you how you can integrate various industry standards-based business messaging systems such as CIDX, OAGi, PIDX, and RosettaNet Web services technology at both the message and document levels.

You can adapt various Industry Standards-based Business Messaging Systems to leverage the benefits of Web services. Review the current functionality of Industry Standards such as CIDX, OAGi, PIDX, and RosettaNet that use the RosettaNet Implementation Framework (RNIF) and learn the benefit of adapting them to a Web services environment. With this foundation established, you can learn an approach that achieves existing functionality using Web services tools, methods, and standards that are available today or in the near future. The authors do not presume that this is the only solution. nor that there will be no further improvements to Web services. They only offer a recommendation that matches those standards and technologies that are available in the near term that you can use to develop a solution. A future paper will explore the deeper benefits that you can gain by fully leveraging Web services.


Download

DescriptionNameSizeDownload method
Whitepaper in PDF formatws-move2wswp.pdf392KBHTTP
Information about download methodsGet Adobe® Reader®

The approach that the authors outline in this whitepaper applies to both the business messages and documents that contain business content and to the RNIF which provides the messaging infrastructure needed to exchange the business messages. For business content, the authors propose that each business message package consist of a set of XML Schemas, WSDL definitions, WS-Policy assertions, and abstract BPEL processes. They also propose that the processes and infrastructure embodied within the RNIF be handled by the abstract BPEL processes along with other elements of a Web services stack, including:

  • WS-Security
  • WS-ReliableMessaging
  • WS-Addressing
  • WS-Policy
  • WS-PolicyAttachment

All Web services-related sub-systems are expected to comply with Web Services Interoperability (WS-I) profiles and specifications to ensure the maximum level of interoperability.


Resources

  • Learn how BPEL works by reading the column Business Processes with BPEL4WS (developerWorks)

  • Explore the core specifications and the RosettaNet Implementation Frameworks at the RosettaNet Web site. RosettaNet is an industry standard for business messaging.

  • Learn more about the Web Services Interoperability Organization (WS-I), which publishes profiles on how different Web services can interact with each other in a practical manner.

  • Visit our Standards and specifications page for a full list of links to many of the documents mentioned in this paper.

  • Want more? The developerWorks SOA and Web services zone hosts hundreds of informative articles and introductory, intermediate, and advanced tutorials on how to develop Web services applications.

Back to top


Document options

Document options requiring JavaScript are not displayed