This chapter describes all the steps required to install and configure Connections Content Manager with IBM Connections. We use an existing FileNet deplyment to connect to the Connections Content Manager.
IBM Connections Content Manager provides a rich social networking and content management experience inside IBM Connections communities. This add-on software to IBM Connections liberates organizational content and engages people to collaborate as part of the content creation process. Now your organization can improve decision-making and business results.
Before you begin
If you want to use Connections Content Manager, you must configure IBM Connections and FileNet with the same WebSphere federated repositories. This can be checked in the WebSphere Application Server administration consoles in the security -> global security
When IBM Connections is installed, the installer provides a user name and password for a system user account that is created by the installer to handle feature-to-feature communication. The Connections installer also creates a J2C authentication alias name connectionsAdmin. This alias is filled with the specified user and maps that user to a set of application roles.
For many advanced security scenarios (especially Tivoli Access Manager and Siteminder) and in cases where an existing FileNet server is used with IBM Connections Content Manager, the connectionsAdmin user should be located in an LDAP directory or a common directory that is available to all services.