Integration considerations for Alfresco Community
IBM BPM supports the ECM integration with Alfresco Community 4.2 and 5.0.
When you define the ECM server properties for an Alfresco
Community server, the default CMIS web service context path is "/alfresco/cmisws".
You can contact your Alfresco Community administrator for complete
connection information.
Other integration considerations for Alfresco Community are described in the following sections:
- CMIS capabilities
- Deviations from the CMIS standard
- Reference
Capabilities
Alfresco Community supports the optional CMIS capabilities that are described in the following table:
| CMIS Capability | Alfresco Community | BPM Considerations |
|---|---|---|
| ACL | manage | Not applicable |
| AllVersionsSearchable | false | |
| Changes | none | Not applicable |
| ContentStreamUpdatability | anytime | |
| GetDescendants | true | |
| GetFolderTree | true | |
| Join | none | Queries cannot include any JOIN clauses |
| Multifiling | true | |
| PWCSearchable | false | Private working copies of a document are not searchable |
| PWCUpdatable | true | |
| Query | bothcombined | |
| Renditions | read | Not applicable |
| Unfiling | false | Documents are always filed in a folder |
| VersionSpecificFiling | false |
Deviations from the CMIS standard
Alfresco deviates from the OASIS CMIS standard in the following ways:
- The ECM operation Remove Document From Folder (CMIS removeObjectFromFolder) requires the specification of the Parent Folder Id (CMIS folderId) parameter even though the CMIS standard defines it as optional.
- When a new version of a document is being created, Alfresco requires a new unique document name to be specified.
Reference
For information about the Alfresco implementation of the OASIS CMIS standard, see the Alfresco topic Alfresco CMIS.