This chapter focuses on how an existing instance of IBM FileNet Content Manager 5.2 could be integrated with IBM Connections 4.5. This will facilitate for the inclusion of IBM FileNet ECM repositories directly into the Connections community user experience as native components. The integration can be established in the following ways:
- In brand-new installations, such as those provided by IBM Connections Content Manager
- By adding a new IBM Connections system to an existing FileNet deployment
- By integrating existing but uncoupled FileNet and Connections deployment
Social collaboration and content management can be purchased and licensed through several different product offerings, including IBM Connections Content Manager (CCM), IBM Connections Enterprise Content Edition (CECE) and FileNet Social Content Manager. Regardless of which offering is used, the software components are the same.
- IBM FileNet Content Manager: provides the enterprise content management platform and repository. The server element is Content Platform Engine (CPE).
- IBM Connections: provides the social collaboration platform and user interface
- IBM Content Navigator (ICN): IBM ECM's latest user client application (not included with CCM)
- IBM FileNet Collaboration Services (FNCS): provides the REST service interface to Content Platform Engine (CPE)
The following diagram depicts the high-level component architecture.
Prerequisites for integration
- Upgrade IBM FileNet Content Manager to release 5.2 and the most recent Fixpack available (FP1 as of the writing of this book).
- If IBM FileNet Services for Lotus Quickr is installed, upgrade it to IBM FileNet Collaboration Services 2.0 and the most recent fixpack available (currently FP1). If IBM FileNet Services for Lotus Quickr is not present, install IBM FileNet Collaboration Services.
- Install IBM Connections 4.5 and the most recent fixpack available (CR1 as of the writing of this book).
- The P8 domain used by IBM Connections must use the new IBM Connections LDAP provide configured for IBM Connection integration. This can be a new domain, or can involve migrating an existing domain along with its object stores. Certain social features are available using linked libraries with other LDAP providers, as are described later.
IBM Connections CCM integration with FileNet Collaboration Services will need at least 5.2 FP1 version. Please make sure Fix Pack 1 has been installed on your FileNet 5.2 deployment.
At a high level, the integration procedure is:
- Set up the target FileNet domain and object store for IBM Connections integration as described in the subsequent sections.
- Create one or more teamspaces. Use IBM Connections to create a new, empty community library. Alternatively, use IBM Content Navigator to create a new, empty general-purpose teamspace that can be linked into a Connections community.
- Use tooling to import documents and folders into the new teamspaces. This tooling can use the native FileNet APIs, IBM FileNet CMIS, or IBM FileNet Collaboration Services