This article describes three different ways to archive processed documents in the Boomi platform to assist with troubleshooting and auditing purposes.
| Runtime Archiving | When you want to archive processed documents for all of your integration processes |
| Connector Archiving | When you want to archive documents for specific processes at any point during the integration process |
| Archive Anywhere | When you want full control over what, when and where to store your archived documents. |
Option 1: Runtime Archiving
Best for
- When you want to archive processed documents for all of your integration processes for troubleshooting and auditing purposes. This can be useful for auditing EDI transactions that may extend over multiple months.
How it works
- Documents are archived into a user-specified directory for all deployed processes for a particular basic runtime, runtime cluster or private runtime cloud according to the configured purge schedule. When the scheduled purge occurs, processed documents are archived into the user specified directory. Archived documents can also be retrieved from Process Reporting for up to 30 days. If you want to retrieve documents beyond 30 days using the Process Reporting UI, see Optional “Extended Process Reporting Archive” feature below.
Configuration
- Runtime Archiving requires several configurations depending on your particular setup. For instructions, visit Process document archiving on our help site.
Optional “Extended Process Reporting Archive” feature
- By default, you can retrieve documents for up to 30 days using the Process Reporting UI (including archived documents). This timeframe can be increased from 30 days to 18 months by purchasing the “Extended Process Reporting Archive” feature. When used in conjunction with basic runtime Archiving it allows customers to utilize the Process Reporting page UI to manage and retrieve their archived documents. This can be useful for troubleshooting and auditing long running transactions that may span several months without needing to manually inspect the documents in the archive directory.
- This feature is not available for integrations running on the Boomi public runtime clouds. Document data process on Boomi's public runtime clouds is only retained for up to 14 days.
- The feature is provisioned by the Boomi team after purchase. Once enabled, Boomi will start to store execution meta-data older than 30 days from that day forward. Historical data (i.e. data older than 30 days) will not be displayed as it has already been purged from the platform. In addition to using the Process Reporting UI for querying execution history, customers may utilize the Boomi Enterprise Platform API. More info here.
Option 2: Connector Archiving
Best for
- When you want to archive documents for specific processes at any point during the integration process. This can be useful to see a document “history” as it flows through an integration process.
How it works
- Documents are archived into a user specified directory on a per connector basis. Connector Archived documents are not retrievable from the Process Reporting UI.
Configuration
Option 3: Archive Anywhere
Best for
- When you want full control over where and how to store documents. This can be useful if you want custom file naming and the ability to store a copy of the document in long term storage such as Amazon S3.
How it works
- First configure basic runtime or Connector Archiving depending on your use case. Then build an integration process that retrieves your archived documents, renames them and then stores them in their final destination.
Configuration