BAW has two document homes and a set of content controls in the toolkits:
- BPM document store - the built-in store (the server definition IBM BPM document store exists in every process app): zero configuration, documents belong to the process instance and are deleted with it; fine for attachments that have no life outside the process.
- External ECM - FileNet Content Manager or any CMIS 1.0 / 1.1 repository (Alfresco, Documentum, SharePoint through CMIS): a Server definition of type Enterprise Content Management server with URL and credentials (a system user, or the current user's identity), then the Content Integration service steps (create document / folder, get document, search, update properties) and the coach controls work against it.
- Coach controls (Content Management toolkit): Document List (folder or search based, with upload and delete), Document Viewer (in-page viewer), Document Explorer (folder tree), plus Document Attachment for the BPM document store.
// service flow "Create claim folder": Content Integration > Create Folder on server "FileNet PROD" -> tw.local.folderId (run before the coach)
// coach: Document List bound to tw.local.folderId; configuration: ECM server = FileNet PROD, allow upload, document class = ClaimDoc,
// properties mapping ClaimNumber <- tw.local.claim.number
// after the coach: list what was uploaded (Content Integration > Search, CMIS query)
tw.local.query = "SELECT cmis:objectId, cmis:name, cmis:contentStreamMimeType FROM ClaimDoc WHERE ClaimNumber = '" + tw.local.claim.number + "'";
// CMIS AtomPub endpoint of FileNet for the server definition: https://cpe-host:9443/fncmis/resources/Service
Permissions: with the current user option on the ECM server, FileNet's own ACLs apply (users need FileNet access - on CP4BA the same LDAP through Zen makes this seamless); with a system user BAW acts as one identity and you control visibility in the coach (which folder / query the user sees). For the BPM document store, access follows the instance: users who can see the instance see its documents. Add virus scanning at the ECM or with a service between upload and the final folder, and keep uploads reasonably small (a large file goes through the BAW JVM on its way to the repository).
Migration to CP4BA: the BPM document store maps to the object store the operator creates for Workflow; external ECM server definitions are re-created with the new URLs and credentials (Zen user or FileNet service account); process apps that used the classic document attachment controls keep working.
References