X hits on this document





31 / 48

London Market Implementation of ACORD DRI Messages and Data


At the SOAP level, a synchronous SOAP Fault may be identified and returned. Different fault code <FaultCode> and string <FaultString> values are recommended to be used in the London Market.


At the ACORD Messaging Service level, a synchronous Post Response is returned to indicate receipt of a Post Request message. Different message processing status code <MsgStatusCd> values (success or error) are sent according to the extent that validation has been carried out.  


Thereafter, all responses are to be delivered as asynchronous messages. In the case of DRI messages, these are Repository[Operation]Rs messages.

The ACORD SOAP Implementation Guide describes compliant options to define the extent of validation to be carried out at each level, whilst also giving consideration to minimising the risk of SOAP response time out.

SOAP Faults

A SOAP fault is used to report on any error on the messaging service invocation. A SOAP fault is returned, with <FaultCode>, <FaultString> and <FaultDetails> populated as indicated in the London Market ACORD DRI Messages Completion and Validation Rules v1 if any of the values operations noted in the matrix fail.

This recommended set is not exclusive and other combinations of <FaultCode>, <FaultString> and <FaultDetails> values can be used if required, in compliance with the ACORD SOAP conventions.

In circumstances where the SOAP handler does not provide the implementer with programmatic control the exact <FaultCode>, <FaultString> and <FaultDetails> returned by the SOAP handler cannot be prescribed.  

Post Response

At this stage, a valid <MsgItem> aggregate is available in the SOAP Body for reference in the Post Response messages.  At this level, the

London Market Implementation of ACORD DRI Messages v1.doc

Page 31 of 48

Document info
Document views155
Page views155
Page last viewedThu Jan 19 15:01:08 UTC 2017