PI 7.1 Archiving - Delete

Question

hi Team,
We have PI 7.1 production environment and planning to implement ARCHIVING & DELETE for Integration Engine, Adapter Engine and Business Process Engine based messages.
I had referred to 'How to arhive & delete' doc that highly available in SDN but few question after going through the doc.
1. If a interface flagged for ARCHIVING then all messages in complete message status gets automatically Archived
2. And if interface not flagged for ARCHIVING then all messages of those interfaces gets automatically Deleted
Ofcourse on these both the cases, the corresponding action takes place only provided the retention period candition meets.
1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
4. Either Archiving or Delete mechanism has any dependance or functional variations on Synchronous and Asysnchronous?
I highly appriciate all those add their knowledge here to clarify
Regards
Sekhar

Answer 1

Dear Sekhar,
let me go through your questions step by step...
1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
This is almost correct. Canceling is required for asynchonous messages in error state only. By canceling a message its state changes from error to final and this it is allowed to be archived. In contrast synchronous messages are final right when processing fails.
Please note: archiving applies to asynchronous messages only. It is a general decision by SAP to not archive synchronous messages.
2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
Once an asynchronous message enters the central Intergation Server(IS) or the local Integration Engine(IE) XI/PI takes over responsibility for this message. Canceling a message means a serious violation of the EO/EOIO protocol. This violation needs to be documented in productive environments for the purpose of tracebility.
3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
I am not quite sure that I got the point. For each message entering the IS/IE SAP has to provide a guided procedure to reorganize this message. For successfully processed messages this is done by standard house-keeping jobs for archivng and deletion. For messages in error state there are basically two ooptions:
(1) restert message after error has been fixed;
     -   if message processing is sucessful this time, we are back to normal
     -   if message processing fails again, we are in the very same siutation as before
(2) cancel messages; this males the message 'final' and then it is treated like sucessfully processed messages.
Thus, this is all about defining an end point in the lifecycle of each message.