B2B Integration 10.2 | Administering and Monitoring B2B Transactions | webMethods Module for EDIINT | Concepts | Inbound EDIINT Processing with AS1 and AS2 | Processing Inbound EDIINT MDNs
 
Processing Inbound EDIINT MDNs
The following diagram illustrates how Module for EDIINT processes an inbound EDIINT MDN.
Step
Description
1
The wm.EDIINT:receive service accepts the inbound MDN.
2
The wm.EDIINT:receive service uses the TN document types to determine the type of document. The MDN matches the EDIINT MDN 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 MDN and places it in the pipeline in the bizdoc variable. A BizDocEnvelope contains the MDN 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 “ProcessMDNMsg.”
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 MDN. For inbound MDNs, Trading Networks uses the EDIINT Process MDN 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 MDN and the user status is “ProcessMDNMsg.”
This processing rule performs the Execute a Service action to invoke the wm.EDIINT.rules:processMDN service, which processes the EDIINT MDN.
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.