Configuring a new FileNet® deployment for the first time

A "new" FileNet® deployment refers to any IBM® Connections installation where you chose to create a FileNet® deployment when you installed IBM® Connections Content Manager. Follow this procedure only if you installed IBM® Connections Manager for the first time and are ready to set up the required data storage. The procedure does not apply to a new FileNet® deployment that was migrated from an earlier version of IBM® Connections, which already has the required components nor does it apply to an existing FileNet® deployment that was installed independently of IBM® Connections.

Before you begin

If you set the value of login properties in your LDAP configuration to be other than uid or if uid is not the first value in the list of values, then the first <loginAttribute> in the section of <loginAttributes> in profiles-config.xml needs to match with the value that FileNet® uses to look up a user. Since by default, the uid value is used and if the security principal for FileNet® is not uid, then you must modify the 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:
Note: Make sure that the CCM shared file system is readable/writeable before running the tool.
If you are unaware of the login properties settings, from the application server's administrative console navigate to Security > Global security > Federated repositories > {YOUR LDAP} > Federated repository properties for login to find the settings or contact your administrator.
Find the JVM argument by navigating to Servers > Server Types > WebSphere application servers > <YOUR SERVER> > Java and Process Management > Process definition > Java Virtual Machine > Generic JVM arguments. The JVM argument needs to match the first value that is specified in <loginAttributes> as follows:{YOUR PROPERTY}

About this task

This procedure creates a new domain and object store for the FileNet® deployment. Do not create a new domain or object store if you are migrating from a previous version of Connections Content Manager.


  1. (Microsoft SQL on Windows only) FileNet® Collaboration Services users need special permissions for the createGCD batch file to work. Grant SQL Server permissions by adding the users to the SqlJDBCXAUser role.

    For more information, see Understanding XA Transactions on the Microsoft Developer's Network.

  2. To create a P8 domain and Global Configuration Data (GCD), perform the following steps:
    1. Locate the ccmDomainTool automation tool under the connections_root\ccmDomainTool.
    2. Start the server where the Connections Content Manager is deployed or start the Connections Content Manager cluster.
    3. (Non-Windows only) Set the executive permission by running the command: chmod 755 *.
    4. Create the P8 domain and GCD as follows:
      • For Windows platform, run the command: createGCD.bat
      • For non-Windows platforms, run the command: ./

      Click Y to regenerate a new file.

      Note: You can specify a group name for administrative access.
  3. To create an Object Store and AddOns, perform the following steps:
    1. Find the ccmDomainTool automation tool under the connections_root\ccmDomainTool directory.
    2. Confirm that you created the domain and FileNet Global Configuration Database (GCD) either by completing Step 2 or by creating them manually.
    3. Create the Object Store by completing the following steps.
      1. Run the following command:
        • Windows: createObjectStore.bat
        • AIX or Linux: ./
      2. When prompted for the Deployment Manager administrator user ID, type the WebSphere administrator's user name.
      3. When prompted for the Deployment Manager administrator password, type the WebSphere administrator's password.
      4. When prompted to Regenerate file, type Y.
      5. When prompted to enter the Activity Stream HTTP endpoint URL, follow the on-screen instructions and be sure to specify the SSL URL for the Connections server.

      Input the Connections administrator password (which is the FileNet® Domain administrator).

      Click Y to regenerate a new file.

  4. Be sure to restart the FileNet® Engine application from the WebSphere® Application Server Integrated Solutions Console.
  5. Optional: If you shut down IBM Docs clusters, restart them.


If one of the scripts ends abnormally or your 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.

What to do next

Refer to Configuring collaborative features in FileNet to learn about how to set up and maintain FileNet® collaborative features.

Many aspects of the FileNet® configuration are set up with defaults entered during your installation. You may need to reconfigure some aspects of your FileNet® deployment later, especially if user information, authentication, or host names change after your initial installation. For more information, see Administering Libraries.