It has been out for a little while now, but the Connections 5 install process included some significant updates for CCM. As we get more and more adoption on 5.0, we've been getting more questions on this. In Connections 5, you'll see a much shorter list of post install steps for CCM.
There is now one task for Configuring IBM Connections Content Manager with a new FileNet deployment. This task has no subtasks. Compare this to what we had in Connections 4.5 where the similar task had 5 dependent subtasks.
We previously had this as a list of "post install" steps specific to new CCM deployments. What happened to these? Let's go one by one through the old post install steps and see what we did to improve in 5.0.
Configuring Libraries automatically
This task was mostly configuring the FileNet domain and object store through a post install script we provided - something we called the ccmDomainTool. The step remains with IC 5, but we've rolled it up into the parent document in the Knowledge Center since it's the only required post install step now. The parent topic used to be a table of contents for the subtasks, but with no subtasks remain, the table of contents is no longer necessary, so the documentation was simply reorganized here. You can read more in the documentation about what a domain is and how it relates to CCM.
We've also made quite a few improvements to the ccmDomainTool itself. The tool now sets up a Collaboration Configuration document inside FileNet to enable the Activity Stream. If an anonymous user was specified during the Installation Manager process, the ccmDomainTool will complete the anonymous setup. The ccmDomainTool also has improved input and output, better logging and prompt to confirm all information it is using to configure the system before it proceeds.
Generating Security identifiers to be used in configuration
This step was just a helper task to enable other steps. Specifically, you needed to get FileNet's internal security identifiers to set up anonymous access fully and to set up the Activity Stream config. Since anonymous setup and Activity Stream config are now included in the ccmDomainTool, we've moved this task to the Administering > Administering Libraries > Configuring the FileNet deployments used by Libraries > Generating Security Identifiers to be used in the configuration. You might need to reference this is you change something in the config, and it's useful reference, but isn't required for initial installation anymore.
Configuring FileNet to be an Activity Stream producer with a new deployment
This task previously instructed you how to manually set up the Collaboration Configuration object in FileNet to enable the Activity Stream. This step was basically telling FileNet how to find the Connections Activity Stream and how to connect to it. Activity Stream configuration is now automated in the ccmDomainTool. The task may still be useful especially for altering configuration in some situations, so it remains for reference in the Administering section. The task is now moved to Administering > Administering Libraries > Configuring the FileNet deployments used by Libraries > Configuring collaborative features in FileNet.
There are a couple other improvements worth noting to the Collaboration Configuration. If you look at the Collaboration Configuration object in FileNet which is created by the ccmDomainTool in Connections 5, you will notice that config2 and config1 and the Activity Stream Extended Settings are empty. This is not a mistake. As of FileNet 5.2 FP 3 which we use in Connections 5, these fields may be left blank. As explained in the new documentation, if config2 and config1 are blank, FileNet will use the connectionsAdmin J2C authentication alias to post stories to the Activity Stream. This J2C authentication alias is a way of storing a user and password in WebSphere's configuration, instead of directly in FileNet. The alias is also required for the rest of Connections to function, and is created by the installation, so it will already be set up if you have a functioning Library widget.
There is one known character encoding issue on Windows when config2 and config1 are empty. When users create Community or File Names with NLS characters they appear corrupted in the Activity Stream. This impacts only Windows deployments of Connections Content Manager version 5.0 where config2 and config1 are empty. This is resolved with FileNet CPE 220.127.116.11 IF002.
Setting an LDAP group to be domain administrator in addition to, or instead of, a specific user
The ccmDomainTool now prompts for a group to be used and will set up the group's access to the domain and object store. Since you could still do this after the installation, the old documentation remains for reference under Administering > Administering Libraries > Configuring the FileNet deployments used by Libraries > Setting an LDAP group to be domain administrator in addition to, or instead of, a specific user. One way or another, you must add an LDAP group to the administrator access of the system, but we've now included this in the ccmDomainTool.
Changing the bootstrap admin password
While this wasn't a step in the initial installation, you previously had to use this to change the password of the FileNet admin in FileNet's configuration. Now with Connections 5, the out of the box bootstrap config for a newly installed CCM system will use the filenetAdmin J2C alias here (similar to how we use the Connections alias for the Activity Stream and for the rest of Connections), so this step will be used less and less. With this change we will no longer need to store any user passwords in FileNet's own configuration. They were stored encrypted before, but now we're move consistent with the rest of Connections and WebSphere. There are still user IDs stored in FileNet though, so IDs of users and administrators should be kept consistent throughout the user's lifecycle.
We know there is always room for constant improvement, and so we always love being able to remove steps from our documentation. Our install team is focused on constant improvement.