Choose and Book Compliance Document (PDF, 850Kb)

The main points of interest are:• ebXML ACK will be received much quicker with this pattern because:1. It will come from the TMS, not the PAS.2. It will come synchronously (in the HTTP response to the original message).• This has an implication for the receiving MHS, which must be supported by allNASP, LSP, and ESP systems; it must now do two things on receipt of a message:1. Persist the message (to guarantee delivery to the next layer – EIS6.x section6.2);2. Return the ebXML on the same connection (i.e., in the HTTP response), notas before as an asynchronous message.• ebXML retries (contract properties) will be applied by all sending MHS. Therefore,there is potentially double the number of retries as specified in the contractproperties. However, in practice it is unlikely that both MHS’ will be down.• The TMS may also apply slow retry logic if it cannot deliver the messageimmediately, and it may ultimately give up and put the message in a deadmessage queue. It will not notify the sender of this situation. This is defined in theMHS Interaction Behaviour section of EIS6.x.Implications for applications:1. All receiving MHS’ must persist a message before sending the ebXML ACK.2. All receiving MHS’ must send the ebXML ACK synchronously on the sameconnection as the message being acknowledged.3. ebXML duplicate elimination must be implemented by the “to” party.Choose and BookAtos Origin - Commercial In ConfidenceChoose and Book ComplianceVersion: 8 (final)Reference EBS-AN\BA\BA011 9 May 2007Page 116