wm.tn.route:routeBizdoc
Submits for processing a document that has already been recognized by
Trading Networks; that is, submits a bizdoc (
wm.tn.rec:BizDocEnvelope).
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:submit.
Input Parameters
bizdoc | Object The recognized document that you want Trading Networks to process. The document must be an instance of com.wm.app.tn.doc.BizDocEnvelope. |
TN_parms | Document (optional) If either of the nested elements processingRuleID or processingRuleName are present, Trading Networks bypasses the processing rule matching process and instead uses the specified rule to process the bizdoc. If both processingRuleID and processingRuleName are present, Trading Networks uses the processingRuleID to determine which rule to use. If neither are present, Trading Networks executes the rule matching process as described in the chapter about processing rules in webMethods Trading Networks Administrator’s Guide. The following are the pipeline variables for this document.  processingRuleID- String (optional) The internal identifier of the processing rule that should be used to process this bizdoc. processingRuleName- String (optional) The name of the processing rule that should be used to process this bizdoc. |
Output Parameters
bizdoc | |
sender | |
receiver | Document The profile summary for the receiver of the document. For the structure of receiver, see wm.tn.rec:ProfileSummary. |
Usage Notes
This service is protected by the TNAdministrators ACL.
To submit a bizdoc externally, use the
wm.tn:submit 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 has executed the pre-processing and processing actions for the document. If the processing actions instructed
Trading Networks to execute a service asynchronously, the asynchronously invoked service may not be complete.
If you are submitting documents to
Trading Networks from an internal application, that application might know which processing rule should be used to process the document. In this case, you might improve the performance of your
Trading Networks application (reduce latency and/or increase document throughput) by explicitly stating which processing rule should be used to process the document. To do this, specify
processingRuleID or
processingRuleName in the
TN_parms document in the pipeline when you submit the document to
Trading Networks from the internal application. See the description of the input signature for details.
