Troubleshooting
Problem
When the ViewONE.exportDocument() JavaScript API is used to save large TIFF documents containing annotations or redactions, the export operation may take several minutes to complete.
The delay becomes more noticeable as the number of pages and document size increase. For documents containing thousands of pages, the API callback may not be triggered for 20 minutes or longer.
Symptom
Users may observe the following behavior:
- The
onStatusUpdate()callback reports that pages are being processed slowly. - The export percentage increases gradually for large TIFF files.
- The API takes several minutes to generate the
downloadLocationURL. - A document containing more than 4,000 pages may require approximately 22–27 minutes before the export callback begins.
- Smaller documents complete successfully within an acceptable time.
- The issue is especially noticeable when saving redacted or annotated TIFF documents.
Cause
The original exportDocument() implementation uses the print and export processing pipeline to create a new document containing the applied annotations and redactions.
For a large TIFF file, the viewer processes the document page by page and embeds the annotations and redactions into the exported output. In the reported workflow, the TIFF document was exported as a PDF and then converted back to TIFF by the application:
TIFF source document
↓
ViewONE exportDocument()
↓
Temporary PDF output
↓
Application converts PDF back to TIFF
↓
Final TIFF documentThe additional TIFF-to-PDF-to-TIFF conversion and page-by-page processing caused the performance delay. Increasing JVM memory improved performance in testing, but it did not remove the underlying conversion overhead.
Environment
Daeja Virtual Viewer
Diagnosing The Problem
Investigate the performance issue with the exportDocument() API in ViewONE.
Reproduce the issue with a large document (over 4000 pages) and observe the slow processing.
Identify that the PDF-to-TIFF conversion step which can cause additional processing time.
Enhance the exportDocument() API to support direct TIFF output with annotations burned in.
Test the new API with the TiffOutput parameter set to true, which will improve performance.
Resolving The Problem
The issue was caused by the performance delay in the exportDocument() method when handling large documents. To resolve this, the exportDocument() API was enhanced with an optional 'tiffOutput' parameter to support direct TIFF output with annotations burned in.
The steps to resolve the issue are as follows:
1. The exportDocument() API was updated to include an optional 'tiffOutput' boolean parameter.
2. When 'tiffOutput' is set to true, the API exports the document in TIFF format with annotations burned in.
3. The code can be updated to use the new API signature.
4. The fix was included in the formal iFix release under known issue DT465815.
Apply IBM Daeja ViewONE Virtual 5.0.15 iFix 6 or a later supported release containing the fix for known issue DT465815.
The updated exportDocument() JavaScript API includes an optional tiffOutput Boolean parameter:
exportDocument(fileUrl, annotationUrl, callback, tiffOutput);
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
05 June 2026
UID
ibm17275229