Newletter Sign Up
Posts on the
Design Decomposition Blog
Iridium Satellite Collision in Space
You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
(The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
Atomicity
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
Well-Formed Business Process Diagrams
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram. To start, here are three criteria from [...]
November 18, 2008
Recent Business Process Modeling Books
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good. The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog
is written by Doug Barry.

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.

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 ebXML Message Service Specification (MSS).

Organization: RosettaNet

More information: RNIF page on the RosettaNet website (new window)

Related content for: RosettaNet Business Message

More on the general topic: Messaging specifications

Read more free articles on this site

There are nearly 400 pages of articles on this site with over 130 pages on Web services and service-oriented architecture.

Search this site for more articles

Custom Search

Browse this site for more articles

Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current article: RosettaNet Business Message.

Related recent articles from Google News

Eckpunkte für die Universalbank 2015
Die Bank
Beispiele derartiger Referenzmodelle sind das Y-Modell für Industriebetriebe, das H-Modell für Handelsbetriebe, RosettaNet sowie Modelle einer Bank sowie ...

1 Mar 2010 at 3:44am
More related news on: RosettaNet

Related books at Amazon.com

ZapNote: RosettaNet ZapNote: Aiming Towards Global Implementation
ZapNote: RosettaNet ZapNote: Aiming Towards Global Implementation
by ZapThink, Ronald D. Schmelzer
Publisher: ZapThink, LLC
Publication Date: December 2001
More related books: Search Amazon.com for RosettaNet