Step | Description |
1 | The wm.EDIINT:receive service accepts the inbound document. |
2 | The wm.EDIINT:receive 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:receive 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 “ProcessMsg.” After forming the BizDocEnvelope, the wm.EDIINT:receive service sends BizDocEnvelope to Trading Networks for processing. |
3 | Trading Networks determines the processing rule to use for the document. For inbound EDIINT documents, Trading Networks uses the EDIINT Process Message processing rule that is installed into Trading Networks when you install Module for EDIINT. It selects this processing rule because the TN document type is EDIINT and the user status is “ProcessMsg.” This processing rule performs the Execute a Service action to invoke the wm.EDIINT.rules:processMsg service. The service processes the message by opening the MIME or S/MIME package and then decrypting and/or verifying the signature of the message. |
Step | Description |
4 | The wm.EDIINT.rules:processMsg service determines whether the sender of the EDIINT document requested an MDN. ![]() ![]() |
5 | The wm.EDIINT.rules:processMsg service invokes the wm.EDIINT.rules:processPayload service, which determines whether you want to send the payload of the EDIINT document to Trading Networks for processing. You define whether you want Module for EDIINT to send EDIINT payloads to Trading Networks for processing when you configure the module. |
6 | If the payload is to be sent to Trading Networks for processing (for example, to perform business-level logic), submit the payload. The payload can be either an EDI document or a non-EDI document (for example, an XML document). ![]() ![]() |