Troubleshooting
Problem
If Navigator is deployed as a container in a Cloud Pak for Business Automation (CP4BA) deployment, an error can occur when uploading files that are larger than 2GB.
The same issue does not occur with
- A stand-alone Content Navigator container
- A Content Navigator container in a FileNet Content Manager or IBM Content Foundation deployment.
Cause
Resolving The Problem
To resolve the issue set the following custom JVM parameter, and then restart the Navigator pod:
-Dcom.ibm.ecm.icn.system.action.upload.largeFile.chunked=true
Once the JVM parameter is set, files are broken into chunks and the chunks are saved in a temp file on the icn-vw-cachestore PVC. Then the content is sent to the Content Platform Engine.
To set the new parameter, add the following to the list of Navigator parameters in the custom YAML. The change is picked up by the Content Operator, and the Content Navigator pod is updated automatically with the JVM parameter.
spec:
navigator_configuration:
icn_production_setting:
jvm_customize_options: "-Dcom.ibm.ecm.icn.system.action.upload.largeFile.chunked=true"
For more information on the available Navigator parameters: https://www.ibm.com/docs/en/filenet-p8-platform/5.5.12?topic=operators-content-navigator-parameters
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
15 December 2023
UID
ibm17086135