David,
persistDuration applies in this case. It specifies how long an
MSH will keep the necessary information (usually MessageId)
in persistent storage so that idempotency checks can be assured.
As for some additional parameter in the CPA that indentifies
the NRR archival parameters (how long will I keep messages,
not just the artifacts for business/legal reasons) I think that
should be taken up by the CPP/A team.
I don't think that it is the MSH responsibility to perform
the archive-for-nrr-audit function. That could be handled
at a level above the MSH.
Cheers,
Chris
David Fischer wrote:
>
> Chris,
>
> Yes, I agree. Should we specify something here rather than leave it as
> implementation dependant? Making a note about minimum times between GC might
> help with Interoperability. Unfortunately, I can see this as a site parameter
> rather than a CPA value -- could be a problem. Any ideas what to do?
>
> Regards,
>
> David Fischer
> Drummond Group.
>
>
