IBM Connections Suite
IBM® Connections Suite Version 4.5 now includes IBM Connections Content Manager V4.5 and IBM Connections V4.5. IBM Connections Content Manager V4.5 adds content management capabilities to Communities in IBM Connections V4.5. Together, IBM Connections Content Manager V4.5 and IBM Connections V4.5 combine an enterprise grade social software platform with embedded content management capabilities designed to help make corporate content available for use across the enterprise.
CCM adds the following new capabilities:
Community Content Libraries expanded with new rich content management capabilities
Access to content management functions through an embedded experience in the activity stream
Social capabilities such as likes, tags, comments, and download counts integrated into Content Libraries
Connections Content Manager integration
As mentioned above, IBM Connections 4.5 is now capable of integrating with Connections Content Manager (CCM), The underlining platform of CCM is FileNet Content Manager.
When considering CCM integration, you have two options.
Obviously, using the embedded FileNet Content Manager instance is an easier migration scenario. However, if customer already have an instance of FileNet in their organization, they have the choice to utilise this as their content manager in IBM Connections. You must consider the following when planning for integration:
Required version: Base FileNet Content Manager is required to be at Version 5.2 Fixpack 1. If your existing installation is not at this level, you must upgrade and migrate existing content to the new version before integrating with IBM Connections. In most cases, the effort to complete this task might outweigh the benefits in using the existing instance.
Directory Repository: You must consider how the directory severs that support IBM Connections and FileNet are going to be consolidated or kept in synch.
Migration tools to assist with CCM migration
The Quickr Document Library migration tool was created to facilitate the migration of data in Quickr Domino and Quickr J2EE to CCM. As with any migration, proper planning is required for migrating the Quickr Domino to CCM. A proper testing environment is equally as important. Before actually performing an in-place migration, there are some preparations that must must be considered. The primary consideration is the directories used by both Quickr Domino and IBM Connections. Refer to 5.0 Using the Quicker Document Library migration tools
for further details on the tools available to migrate Quickr Domino/Java Document Library content to CCM.