Defining Your Own Internal TN XML Document Types
When you import a PIP or a PIP archive, the internal and external TN XML document types for the PIP or PIP archive are automatically created in Trading Networks. However, you may want to create your own internal TN XML document types or customize one of the internal TN XML document types provided with Trading Networks.
Important:
Do not modify any of the provided external TN XML document types. If you do, Trading Networks will not be able to join an incoming business document with a conversation.
When you define an internal TN XML document type, specify the following:
The root tag from the business document that must match the TN XML document type.
The XML queries that
Trading Networks uses to extract the
SenderID and
ReceiverID attributes from the business document.
Trading Networks uses XML queries to extract the SenderID and ReceiverID attributes from business documents that are sent to RosettaNet Module from an internal system. The SenderID and ReceiverID indicate the sender and receiver of the business document, respectively.
For more information on defining TN XML document types, see webMethods Trading Networks Administrator’s Guide.
Note:
You can determine if a TN XML document type is external by the description and the pipeline. If the document type is external, it will always have a pipeline matching variable of processVersion. Internal TN XML document types do not have a matching variable in the pipeline.