London Market Implementation of ACORD DRI Messages and Data
Where the London Market Accounting and Settlement Technical Information states different time out and file size specifications for a SOAP message, the following definitions take precedence (the London Market Accounting and Settlement Technical Information will be updated in due course):
HTTP time-out period (t1): 3 minutes
For a single transfer:
Maximum size of attachments: 20 Mbytes
Maximum size of SOAP message: 20.5Mbytes
There is no limit specified on the number of messages and/or attachments allowed within a single SOAP message other than that implied by the message size limit. Within the context of ACORD DRI, there is only ever one message per SOAP transmission.
The initiator of the sequence that results in the transmission of documents is responsible for ensuring that the maximum sizes are not exceeded.
If the sender is unable to obtain a synchronous response to a message within the HTTP time-out period (t1), the sender will retry the transfer at intervals of 15-20 minutes until either it succeeds or three failed attempts have been made. If three fail, an out of band process (e.g. phone call) is recommended to be initiated within one hour of the final re-try if the failure occurs within either parties’ supported hours or, the commencement of supported hours if the failure occurs outside supported hours.
London Market error handling rules of ACORD RLC and DRI messages are detailed in the London Market Accounting and Settlement Technical Information (section 5, subsection 4.4). These rules are summarised below.
At the stage at which the SOAP handler is invoked, the ACORD SOAP Implementation Guide specifies three (3) levels of responses senders may expect when using the ACORD Messaging Service Inbox/Post operations.
London Market Implementation of ACORD DRI Messages v1.doc
Page 30 of 48