ebxml-msg — archive

[System]

At this stage of the game functions like NRR archiving belong in the BPSS instance document, not in the CPA. The CPA has not even begun to get into business-level information though it may some day. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com ************************************************************************************* christopher ferris <chris.ferris@Sun.COM>@Sun.COM on 09/20/2001 11:50:38 AM Sent by: Chris.Ferris@Sun.COM To: David Fischer <david@drummondgroup.com> cc: Dan Weinreb <dlw@exceloncorp.com>, arvola@tibco.com, ebxml-msg@lists.oasis-open.org Subject: Re: T2, Proposed solution for ... Re: SyncReply andReliableMessagingMethod in QualityOfServiceInfo 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. > >