|Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search|
|Implementation Options | Technical Basics | Internet Commerce Model | Architecture ||
3c - Integrated B2B via the Internet, Point-to-Point (PTP, No VAN or Hub) -
RosettaNet XML Using RNIF
|Business User View|
|When to Use this Implementation Option|
|What You Need for this Implementation Option|
|How it Works - Design Time (Initial Implementation, New Partner, New Business Process/New Business Document)|
|How it Works - Run Time, Outbound|
|How it Works - Run Time, Inbound|
|In Order Model 1 Section:|
|UML Activity Diagram - Inventory Report Example|
This is a technology where the both sending and receiving partners are using the RosettaNet standard, which includes business process standards called Partner Interface Processes (PIPs), which include specifications for business documents using RosettaNet's XML vocabulary, and a specification for transport and routing, called the RosettaNet Implementation Framework (RNIF).
In RosettaNet's early days, the business processes were expected to be fully integrated for all partners. As with legacy EDI, some alternatives have been emerging, such as a PC front-end, and web-based applications.
In this implementation option, all connections with trading partners are point-to-point, via the internet. Again, because point-to-point connections are expensive to maintain, as with EDI, modern VANs have been emerging to handle RosettaNet traffic.
Business User View
Compare with Basic Implementation Options User View.
When to Use This Technology
This technology is appropriate wherever you would use legacy EDI; see When to Use This Implementation Option - Implementation Option 1. Since RosettaNet is business-process based and uses XML syntax, its potential for extensibility and scalability is somewhat higher than for the legacy EDI standards, ASC X12 and EDIFACT.
Some companies have adopted a strategy of eventually replacing their legacy EDI implementations with RosettaNet implementations. Other companies are leaving existing EDI partnerships in place, and using RosettaNet for business processes for which legacy EDI standards are not as robust as they need to be. Some companies implement RosettaNet with trading partners who also have a RosettaNet strategy, or trading partners who have not yet invested in legacy EDI standards.
|Legacy EDI Standards||RosettaNet|
Transport and Routing
Transport and Routing
Options for Connecting with Partners
For a point-to-point RosettaNet connection, both partners must be using the same RNIF version at both ends.
Last updated 02 March 2003