RosettaNet Business Message

The RosettaNet Business Message is the container for exchanging the individual business documents involved in and is the basic unit of exchange between two RosettaNet end-points. Below is  the basic structure and components of the RosettaNet Business Message.

RosettaNet Implementation Framework (RNIF)

The RosettaNet Business Message contains two parts:

  1. Headers. All three types of headers use XML. All headers are required and there is only one header of each type per message. The overall purpose of these headers is for the recipient to be able to:
    • Identify the message as a RosettaNet Business Message
    • Identify the context of the message
    • Identify the sender for authentication and authorization.

    Preamble Header: Identifies the standard with which this message structure is compliant.

    Delivery Header: Identifies message sender and recipient and message instance information.

    Service Header: Identifies the PIP, the PIP instance, the activity, and the action to which this message belongs.

  2. Payload. These messages are defined using XML. For Service Content, an example of an Action is a purchase order request. An example of a Signal it the acknowledgement of a purchase order request.

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

Also see how RNIF is used in the .


More information: RNIF page on the RosettaNet website

Context for RosettaNet Business Message

Related Articles for RosettaNet Business Message

The Savvy Manager's Guide

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

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.