Configure IBM Connections Content Manager with a new FileNet deployment

Many aspects of the FileNet configuration are set up with defaults entered during the installation. You may need to reconfigure some aspects of the FileNet deployment later, especially if user information, authentication, or host names change after the initial installation. Refer to Administer Libraries for additional information.

For migrations from a previous version of Connections Content Manager, we will reuse our domain and object store from the previous installation. Do not create a new domain or object store.

1. Verify CCM shared file system is readable/writeable.

2. If the value of login properties in the LDAP configuration is not uid, or if uid is not the first value in the list of values, then the first <login> attribute in the section of <loginAttributes> in profiles-config.xml needs to match with the value that FileNet uses to look up a user.

   To determine login properties, from the dmgr...

   Security | Global security | Federated repositories | myLDAP | Federated repository properties for login

   By default, the uid value is used. If the security principal for FileNet is not uid, modify profiles-config.xml to move the attribute that matches up with the principal to be the first attribute in the <loginAttributes> section. For example, if email is used as the principal, then the <loginAttributes> section should look like this:

       <loginAttributes>
           <loginAttribute>email</loginAttribute>
           <loginAttribute>uid</loginAttribute>
           <loginAttribute>loginId</loginAttribute>
       </loginAttributes>

3. Go to...
   Application servers | servername | Process definition | Java Virtual Machine | Generic JVM arguments

   ...and verify the following JVM argument matches the first value specified in <loginAttributes>

   -Dcom.ibm.connections.directory.services.j2ee.security.principal={YOUR PROPERTY}

4. Start the cluster where the Connections Content Manager is deployed.

5. Create a P8 domain and Global Configuration Data (GCD)...
   cd connections_root/addons/ccm/ccmDomainTool
   chmod 755 *
   ./createGCD.sh

6. Create an Object Store and AddOns.
   cd connections_root\addons\ccm\ccmDomainTool
   ./createObjectStore.sh

   You will be required to input the Connections administrator password (which is the FileNet Domain administrator).

7. Restart the FileNet Engine application from the WAS console.

Results

If one of the scripts ends abnormally or the object store is not functional immediately after creation, refer to Troubleshooting the ccmDomain tool. Also, refer to Recreating the FileNet domain and object store if you encounter a problem in the initial domain or object store configuration. Refer to Configure collaborative features in FileNet to learn about how to set up and maintain FileNet collaborative features.

Parent topic:
Configure IBM Connections Content Manager for Libraries