CMIS Setup in FileNet
To enable CMIS with FileNet there are few mandatory classes and properties that must be defined in the object stores.
To enable CMIS functionality, the FileNet Object store MUST have these base document classes:
It is recommended the following naming be used. This naming can be altered but must then be reflected in the mapping section contentServer.cmis.documentColumns section in the INI configuation file (see CMIS Setup in Docuflow documentation node)
cmis:objectId cmis:baseTypeId cmis:objectTypeId cmis:secondaryObjectTypeIds cmis:name cmis:description cmis:createdBy cmis:creationDate cmis:lastModifiedBy cmis:lastModificationDate cmis:changeToken cmis:isImmutable cmis:isLatestVersion cmis:isMajorVersion cmis:isPrivateWorkingCopy cmis:versionLabel cmis:versionSeriesId cmis:isVersionSeriesCheckedOut cmis:versionSeriesCheckedOutBy cmis:versionSeriesCheckedOutId cmis:checkinComment cmis:contentStreamLength cmis:contentStreamMimeType cmis:contentStreamFileName cmis:contentStreamId
cmis:objectId cmis:baseTypeId cmis:objectTypeId cmis:secondaryObjectTypeIds cmis:name cmis:description cmis:createdBy cmis:creationDate cmis:lastModifiedBy cmis:lastModificationDate cmis:changeToken cmis:parentId cmis:path cmis:allowedChildObjectTypeIds
To enable archivelink document management, the document classes sapbo:basedocument and sapbo:Archivelink are required
- sapbo:baseDocument
sapbo:basedocument:synchronized sapbo:basedocument:Document sapbo:basedocument:DocumentComponentID
- sapbo:ArchiveLink
sapbo:ArchiveLink:ArchiveLinkDocument
To enable DMS document management, the document classes sapbo:basedocument and sapbo:KnowledgeProvider are required
- sapbo:baseDocument
sapbo:basedocument:synchronized sapbo:basedocument:Document (Index field for better retrieval performance) sapbo:basedocument:DocumentComponentID
- sapbo:KnowledgeProvider
sapbo:KnowledgeProvider:LogicalDocument
FileNet does not allow the metadata property internal (symbolic) name to have special characters. So map all the properties to the custom ones as explained in CMIS Setup in Docuflow middleware.
We have ACCE JScript to create CMIS properties. Please reach out if you would like to use the script.
mapping json overview (pretty print)
The hierarchy of the cmis properties is as follows:
Depending on Docuflow configuration setting : If xxx.contentServer.cmis.enableSAPFolderFormat is enabled
This requires to add a new class sapbo:baseFolder
- sapbo:baseFolder
sapbo:basefolder:multiBoReference sapbo:basefolder:synchronized

if xxx.contentServer.cmis.enableSAPFolderFormat is disabled

The service account/technical user used by docuflow to connect to FileNet P8 requires:
- On Domain:
- Permission Group “Use stores and services”
- On Object Store:
- Permission Group “Use object store”
- On used Document classes and Folder classes:
- Security of the class
- View all Properties
- Read Permission
- Create instance
- Default Instance Security access control list (ACL)
- Permission Group “Full Control”
If for compliance or other reasons "Full Control" cannot be granted certain actions will fail. E.g. if no 'Delete' rights granted and SAP request a delete of a document the request would fail (error code 500)