X hits on this document

111 views

0 shares

0 downloads

0 comments

27 / 48

London Market Implementation of ACORD DRI Messages and Data

response to confirm a package has been received and subsequent Repository[Operation]Rs. The sender must receive the initial system response to confirm successful delivery before any subsequent package can be issued by the same sender to the same receiving URL.

Recovery and Retransmission

This section supplements the information supplied in the London Market Accounting and Settlement Technical Information with respect to ACORD DRI messages.

In the event of a failure scenario where ACORD DRI messages are lost due to a system failure and an inability of recovering from the log of received/sent ACORD DRI messages, the following is recommended:

1.

Retry and Resend

A retry is a re-transmission before the synchronous response has been received. The UUID’s of both the SOAP envelope and the message(s) will remain as per the original.

A resend is a re-transmission after the synchronous response has been received. The UUID of the DRI message will remain as for the original, but the SOAP envelope will have a new UUID. The <resend> indicator in the SOAP envelope will indicate a resend.

2.

Duplicate transmissions

A duplicate transmission is identified by the repetition of a package UUID with the same creation date. These should be given a positive synchronous response but should not be re-delivered to the application.

3.

Duplicate ACORD DRI messages (not part of a duplicate message)

These should be given a positive synchronous response.

London Market Implementation of ACORD DRI Messages v1.doc

Page 27 of 48

Document info
Document views111
Page views111
Page last viewedMon Dec 05 12:35:47 UTC 2016
Pages48
Paragraphs1101
Words9338

Comments