A conversation starts when the internal system on the initiator’s side invokes pub.estd.rosettaNet:processDocument. An outbound mapping service must convert the business document received from the internal system into a RosettaNet object (RNO), that is the standard format used by both trading partners to exchange business documents. The outbound mapping service on the initiator’s side includes a Send to Seller step. This step invokes a service that sends the document, now in RNO format, to the trading partner.

The conversation starts on the fulfiller's side when the pub.estd.rosettaNet:receive service, which has a Wait for RNO step, receives the document. The pub.estd.rosettaNet:receive service invokes wm.tn.doc:recognize service to recognize the document by matching it against the TN XML document types. Next, the fulfiller’s custom-created mapping service converts the RNO document into the format used by the internal system. The Send PO step of the custom-service sends the business document to the internal system.

Both the pub.estd.rosettaNet:processDocument and pub.estd.rosettaNet:receive services invoke wm.tn.doc:recognize to recognize the document by matching it against the TN XML document types.

On each side, a BizDocEnvelope is created. Both the pub.estd.rosettaNet:processDocument and pub.estd.rosettaNet:receive services send the BizDocEnvelope to Process Engine.

Throughout this process, Process Engine determines if a ConversationID exists for the conversation. If not, Process Engine creates a new instance of the process model and assigns the ConversationID to the process model. Process Engine executes the conversation based on the steps defined in the process model.