When using the One-Way/Pull MEP, use the com.ip.estd.as4.msh.submit service to package the submitted payload(s) as a user message and submit it to an MPC. The submit service uses the values of the toPartyId, toPartyIdType, fromPartyId, fromPartyIdType, and pmodeID. If pmodeID is empty, then a tuple of toPartyId, toRole, fromPartyId, fromRole, Service, Action, and AgreementRef input parameters to fetch the appropriate TPA. The values in the TPA are then used to identify the messaging parameters. Instead of transferring the message to the initiating MSH, the module stores the message in the MPC specified in the legs/businessInfo/mpc TPA parameter of the requestUM leg.

When a pull signal is received, the module determines which TPA to use to process the pull signal by matching the MPC named in the pull signal with the MPC named in the requestSM leg of each TPA that is configured in Trading Networks. The matching MPC is used to process the pull signal. The module retrieves the user message from the MPC specified in the pull signal and sends it to the initiating MSH. If no MPC is specified in the pull signal, the module uses the default MPC to pull the user message.

Module for AS4 uses the Trading Networks database as the MPC queue. When a user message is queued, the message is stored in Trading Networks with a UserStatus of QUEUED, and the corresponding bizDocId is cached. When a pull signal is received, the module first retrieves the bizDocId from the cache First In, First Out, and then retrieves the user message that corresponds to this bizDocId from Trading Networks. The retrieved message is then sent to the initiating MSH.

For more information about configuring the module to use the One-Way/Pull MEP, see Configuring Trading Partner Agreements. For more information about the submit service, see Built-In Services.