IBM Content Navigator, Version 2.0.3 Supports: CMIS for Content Manager, CMIS for FileNet P8, CMIS for OnDemand

Troubleshooting problems with IBM CMIS

Troubleshoot problems and errors that occur when administering and using IBM® CMIS applications.

Verifying whether IBM CMIS for Content Manager uses WebSphere Application Server connection pooling
Check the dklog.log trace file to verify that IBM CMIS for Content Manager uses WebSphere® Application Server connection pooling.
Getting authorization failed error when connecting from CMIS applications
If you get an Authorization failed, user ID or password invalid error when you try to connect from CMIS applications, review the checklist below and implement as many steps as is necessary to resolve the issue.
The properties view of a document does not display the correct file size and MIME type
If the properties view of a document displays the incorrect file size or MIME type, use the resource item type types classification to retrieve the correct metadata of multiple part documents.
Cannot find the changes made to the Content Manager EE definitions
If you do not see the changes that you made to the Content Manager EE definitions, restart IBM CMIS for Content Manager for the changes to take effect.
Composite path information is displayed instead of file names
If IBM CMIS for Content Manager displays the composite path information of a file instead of the file name, you must disable the access path configuration option to disable the display of the composite information.
Configuration program fails for Content Manager for z/OS
If you are using DB2 z/OS Version 9, the IBM CMIS for Content Manager configuration program fails because there is a query feature that requires DB2 z/OS Version 10. You must update the advanced configuration parameter searchInTree and run the configuration program again.
Cannot save document with properties because the total size of the metadata property values exceeds the size limit
If the total size of the metadata property values exceeds the repository capacity to save properties, the document cannot be saved in the repository. Reduce the size of the property values so that the total size of the metadata values is within the repository metadata size limit. Depending on your repository configuration, an administrator might be able to extend the metadata capacity limit.
Java core dump error
If you receive a Java core dump error in IBM CMIS for Content Manager, increase the heap size setting in WebSphere Application Server to accommodate your workload.
Getting error messages from RESTful AtomPub bindings
The RESTful AtomPub binding of the IBM CMIS interface reports errors back to the application by using a MIME type of text/plain. If you get error messages that include the syntax similar to HTML, use HTML Encoding for the IBM CMIS error messages before inserting it in your HTML web page.

Parent topic: Troubleshooting IBM Content Navigator components