Message Service Specification (MSS)

Message Service Specification (MSS) is a communications-protocol neutral method for exchanging electronic business messages. It supports reliable, secure delivery of business information and a flexible enveloping technique. This flexible enveloping technique is being used to incorporate features of SOAP and RosettaNet Business Message messages.

Message Service Specification (MSS)

The Message Service Specification contains two parts:

  1. Header container. This is the first MIME part, containing One SOAP message. The SOAP message is an XML document consisting of a SOAP Envelope element. The SOAP Envelope element consists of:

    SOAP-ENV:Header. This is a generic mechanism for adding features to SOAP message, including ebXML specific header elements.

    SOAP-ENV:Body. This is a container for message service handler control data and information related to the payload parts of the message.

    See SOAP Header and Body information.

  2. Payload containers. There can be zero or more additional MIME parts containing application specific payloads. See RosettaNet Business Message payloads.

MSS can use HTTP, but other protocols such as HTTPS, and Simple Mail Transfer Protocol (SMTP) may by used.

You may use this material for your work or classes. Reprint Policy. Be sure to check the menu at the left for other articles available on this site.

The Savvy Manager's Guide

Douglas K Barry is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide (Second Edition)

by with David Dick

This is a guide for the savvy manager who wants to capitalize on the wave of change that is occurring with Web Services, service-oriented architecture, and—more recently—Cloud Computing. The changes wrought by these technologies will require both a basic grasp of the technologies and an effective way to deal with how these changes will affect the people who build and use the systems in our organizations. This book covers both issues. Managers at all levels of all organizations must be aware of both the changes that we are now seeing and ways to deal with issues created by those changes.