Best Practice / Strategy to back-up interfaces
I wanted to reach out to you to get an opinion on the best practice / strategy to back-up interface messages.
Our client wants to back-up interface messages both at source and target for a few critical interfaces.
Some of these interface are File to File, File to Proxy, Proxy to SOAP.
- File to File: We are having archiving at source - using standard option to archive in file source directory / PI server too.
- Target - Client wants to archive the target file too - option to request target application to archive after processing - any other options?!
- File to Proxy: Source File archiving same as the above scenario - how to archive proxy message - standard retention period is set as 30 days for successful messages - how do we archive apart from retention period beyond 30 days ?!
- Proxy to SOAP: How do we archive source side & target side payloads?!
Alternate archive approach for all the above 3 cases:
- Option # 1: On the file/FTP Is it best to add receiver and have the receiver messages routed to specific FTP folders - We still need an answer for Proxy / SOAP messages.
- Option # 2: Can we take regular period back-up's of the PI back-end system tables which store these messages - is this a possibility?! IF yes, how do we retrieve the data from these back end tables.
- Option # 3: ANY OTHER OPTIONS?!
Your help is greatly appreciated!!