BICC Extract: No way to correlate MANIFEST.MF file to specific request
Summary:
When submitting multiple BICC extract offerings in parallel via the ESSWebService (submitRequest), each completed job produces a MANIFEST.MF file in UCM under the OBIAImport security group. However, there is no reliable way to associate a specific MANIFEST.MF file with its corresponding request.
Business Impact:
We are building an automated data extraction pipeline that submits multiple BICC offerings concurrently. Without a reliable way to correlate the manifest file to a specific ESS request ID, we cannot:
- Verify data integrity (MD5 checksums) per run
- Ensure complete file downloads per offering
- Safely clean up UCM files after processing
Current Workaround:
Tagged:
0