During run time, your internal systems sends a business document to RosettaNet Module. RosettaNet Module processes the business document, that is, it invokes a Trading Networks service to recognize the TN XML document type, creates the BizDocEnvelope, and sends the BizDocEnvelope to Process Engine.

In this scenario, your internal system could send either a small or large business document to RosettaNet Module. For example, in the PIP 3D8 Large Document Sample, the internal system sends a small document that includes a file name that references the large business document.

Alternatively, the internal system could send a large business document. After Trading Networks creates the BizDocEnvelope and opens a reservation to TSpace, Trading Networks invokes wm.tn.doc:getContentPart to retrieve the document content and writes the content to TSpace.

The better option of these two methods is to use the small business document to initiate a RosettaNet transaction for a large business document. This improves performance because RosettaNet Module does not need to load the entire large document into memory.