A back-end system or client sends an internal-format document to the webMethods Integration Server, invoking the wm.tn:receive service to send the document to Trading Networks.

Trading Networks matches the internal-format document to its TN document types. You need to create a TN document type that will match your internal-format. For more information about creating TN document types, see the webMethods Trading Networks Administrator’s Guide.

After selecting the appropriate TN document type, Trading Networks forms the BizDocEnvelope that contains the internal-format document as the content and places the BizDocEnvelope in the pipeline in the bizdoc variable.

Trading Networks searches its processing rules to find the appropriate rule to use to process the internal-format document. You should create a processing rule that uses the Execute a Service processing action to invoke a service that you create to form the EDI document. For more information about creating this service, see Creating a Service for Forming an Outbound EDI Document.

The service you create to form the EDI document executes. After forming the EDI document, your service creates a BizDocEnvelope that contains the EDI document and places it in the pipeline in the bizdoc variable (overwriting the previous bizdoc variable).

Your service then invokes the wm.tn.route:routeBizDoc service to send the BizDocEnvelope that contains the EDI document back into Trading Networks to select a different processing rule.

Trading Networks searches its processing rules again to find the appropriate rule to use to deliver the EDI document. You need to create a processing rule for the EDI document that does one of the following: