IBM BPM supports ECM integration with IBM FileNet 5.1 Content Manager.
When you define the ECM server properties for IBM FileNet Content Manager, the default CMIS web service context path is "/fncmis". You can contact your IBM FileNet Content Manager administrator for complete connection information.
Other integration considerations for IBM FileNet Content Manager are described in the following sections:
- CMIS capabilities
- Best practices
- Reference
CMIS capabilities
IBM FileNet Content Manager supports the optional CMIS capabilities that are described in the following table:
| CMIS Capability | IBM FileNet Content Manager | BPM Considerations |
|---|---|---|
| ACL | none | Not applicable |
| AllVersionsSearchable | true | |
| Changes | none | Not applicable |
| ContentStreamUpdatability | pwconly | Documents must be checked out for updates |
| GetDescendants | true | |
| GetFolderTree | true | |
| Join | innerandouter | |
| Multifiling | true | |
| PWCSearchable | true | |
| PWCUpdatable | true | |
| Query | metadataonly | The CONTAINS() predicate function is not supported |
| Renditions | none | Not applicable |
| Unfiling | true | |
| VersionSpecificFiling | false |
Best practices
The best practices for developing
client applications for IBM CMIS for FileNet Content Manager are described
in the topic 
Best practices for developing client applications.
Reference
Information about the IBM CMIS
for FileNet Content Manager implementation of the OASIS CMIS standard
is found in the topic IBM CMIS for FileNet Content Manager implementation
of the OASIS CMIS specification.