Step | Description |
1 | You invoke the wm.EDIINT:send service to send a document to Module for EDIINT to be packaged as an EDIINT document and delivered to the receiving trading partner. |
2 | Using the input information that you provide, the wm.EDIINT:send service creates the EDIINT document (that is, an EDIINT MIME or S/MIME message). |
3 | The wm.EDIINT:send service uses the TN document types to determine the type of document. The document matches the EDIINT TN document type that is installed into Trading Networks when you install Module for EDIINT. After determining the TN document type, the wm.EDIINT:send service forms a BizDocEnvelope for the inbound document and places it in the pipeline in the bizdoc variable. A BizDocEnvelope contains the original document and includes additional information that Trading Networks requires for routing and processing the document. One piece of information that Trading Networks can use in the selection of a processing rule is the user status. The EDIINT recognizer sets the user status to “SendMsg.” After forming the BizDocEnvelope, the wm.EDIINT:send service sends BizDocEnvelope to Trading Networks for processing. |
4 | Trading Networks determines the processing rule to use for the document. For outbound EDIINT documents, Trading Networks uses the EDIINT Send Message processing rule that is installed into Trading Networks when you install Module for EDIINT. Trading Networks selects this processing rule because the TN document type is EDIINT and the user status is “SendMsg.” This processing rule performs the Execute a Service action to invoke the wm.EDIINT.rules:sendMsg service. |
5 | The wm.EDIINT.rules:sendMsg service delivers the document by invoking the wm.EDIINT.delivery:deliveryDocument service, which in turn delivers the document to the appropriate trading partner. |