B2B Integration 10.2 | Administering and Monitoring B2B Transactions | Trading Networks Built-In Services Reference | Doc Folder | Summary of Elements in this Folder | wm.tn.doc.xml:routeXml
 
wm.tn.doc.xml:routeXml
Recognizes an XML document and submits it for processing.
This service does not check the identity of the sender against the currently logged in user. Only invoke this service from within processing rules or services; do not expose directly to trading partners. Trading partners should use wm.tn:receive.
Input Parameters
node
Object An XML document to process (must be an instance of com.wm.lang.xml.Document).
TN_parms
Document (optional) An IS document (IData object) that holds “hints” that Trading Networks uses when performing document recognition for a flat file document. For information about using recognition hints in gateway services, see webMethods Trading Networks Administrator’s Guide.
Output Parameters
bizdoc
Document The XML document. For the structure of bizdoc, see wm.tn.rec:BizDocEnvelope.
sender
Document The profile summary for the sender of the document. For the structure of sender, see wm.tn.rec:ProfileSummary.
receiver
Document The profile summary for the receiver of the document. For the structure of receiver, see wm.tn.rec:ProfileSummary.
TN_parms
Document (optional) An IS document (IData object) that holds “hints” that Trading Networks uses when performing document recognition for a flat file document. For information about using recognition hints in gateway services, see webMethods Trading Networks Administrator’s Guide.
Usage Notes
*This service is protected by the TNAdministrators ACL.
*To submit a document externally, use the wm.tn:receive service.
*If you are invoking this service from a Java program, in addition to returning bizdoc, sender, and receiver as IS documents (IData objects), the service returns bizdoc as an instance of com.wm.app.tn.doc.BizDocEnvelope and the returned sender and receiver as instances of com.wm.app.tn.profile.ProfileSummary.
*This service returns after Trading Networks completes processing for the document. That is, after Trading Networks executes the preprocessing and processing actions for the document. If the processing actions instruct Trading Networks to execute a service asynchronously, the asynchronously invoked service may not complete.

Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.