TN_parms | Document (Optional) An IS document (IData object) that you can use to provide parameters that govern how Trading Networks recognizes and processes a document. TN_parms is primarily used for flat file processing. The document gateway service adds “hints” to TN_parms that Trading Networks uses when performing document recognition for a flat file document. See information about document gateway services in webMethods Trading Networks Administrator’s Guide for details on providing recognition hints. For both XML and flat files, you can optionally add the TN_parms/DoctypeID or TN_parms/DoctypeName fields. The TN_parms/DoctypeID and TN_parms/DoctypeName fields identify the TN document type to use, thus bypassing document recognition and eliminating the overhead of searching for the TN document type. If you specify both variables, DoctypeID is used.  TN_parms/DoctypeID is a string that identifies the internal identifier of the TN document type. To determine the identifier use the wm.tn.doctype:list service. Using DoctypeID rather than DoctypeName is more stable because the internal identifier cannot be changed.TN_parms/DoctypeName is a string that identifies the name of the TN document type. Be sure to use the exact combination of upper- and lowercase letters. |
Note: You can add a flat file document as an Object with the name ffdata in the pipeline | |
For XML documents you can optionally add a node (Object). The document to process must be an instance of com.wm.lang.xml.Document. The typical way to get an XML document into the pipeline is by posting an XML document to Integration Server. | |
For EDI documents, you can add an EDI document as an Object with the name edidata in the pipeline. |