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

Logged errors

If you configured logging for IBM® Content Management Interoperability Services for FileNet® Content Manager (IBM CMIS), all errors are logged in WebSphere® Application Server and returned in a response.

The following code is an example of the message format:

INVALID_OBJECT_ID_1=CIL1148: The service cannot be completed because the 
following object ID or path is not valid: {object ID or object path}
INVALID_OBJECT_ID_1_E=The object ID or path might contain invalid characters or 
use invalid syntax.
INVALID_OBJECT_ID_1_A=Ensure that a valid object ID or path is retrieved from 
HTTP responses, or the RESTful AtomPub binding service document, or the Web 
Services binding document.

The OASIS Content Management Interoperability Services API specification requires applications to throw exceptions when certain errors occur.

The following code is an example of the information that is written to the log file when an exception occurs:

MM/DD/YY HH:MM:SS] 00000017 DALP8Exceptio E 
com.ibm.ecm.cmis.dal.p8.DALP8ExceptionHandler handleException null
com.ibm.ecm.cmis.app.exceptions.InvalidArgumentException: 
CIL1145: The service cannot be completed because the value that was specified 
for the following input parameter is not valid. 
Input parameter: repositoryId 
Value: bad-dog
Explanation: No additional explanation is required.
Action: For information about implementing the argument, 
see the OASIS CMIS API specification. 
Stack trace...

If you use REST services, server-side stack trace information is logged and returned. If you use Web Services, server-side stack trace information is logged but not returned. The client application sees only the client-side stack trace information.