Link code for page
The RosettaNet Business Message is the container for exchanging the individual business documents involved in RosettaNet PIP messages (new window) and is the basic unit of exchange between two RosettaNet end-points. Below is the basic structure and components of the RosettaNet Business Message.
The RosettaNet Business Message contains two parts:
- 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.
-
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 ebXML Message Service Specification (MSS).
Organization: RosettaNet
More information: RNIF page on the RosettaNet website (new window)
More on the general topic: Messaging specifications
- Asynchronous Application Service Protocol (ASAP) for SOAP
- Message Service Specification (MSS)
- Representational State Transfer (REST)
- SOAP
- Web Distributed Data Exchange (WDDX)
- Web Services Addressing (WS-Addressing)
- Web Services Eventing (WS-Eventing)
- Web Services Notification (WSN)
- Web Services Reliability (WS-Reliability)
- Web Services Reliable Messaging (WS-ReliableMessaging)
- XML Protocol (XMLP)
