Recreating the FileNet domain and object store

If you have a problem with running the ccmDomainTool automation tool to create the FileNet® P8 domain and Object Store, perform the following refresh steps and then rerun the tool.

About this task

All the ccmDomainTool automation tool's scripts perform several steps simultaneously to configure the FileNet objects. However, if one of these steps encounters an error even though the script itself completes, then the objects might not be properly configured. For more information, see Configuring libraries automatically. If you encounter a problem in the initial domain or object store configuration, you might need to refresh your system. Refresh your system by clearing out CCM content to a state where you can rerun all of the ccmDomainTool scripts. Perform the following steps:

Procedure

  1. Stop the FileNetEngine and FileNet Collaboration Services (FNCS) WebSphere® Application Server applications in the WebSphere Application Server console.
  2. Delete and re-create the IBM® Connections Content Manager databases. Rerun the Connections database wizard to re-create the IBM Connections Content Manager databases. For more information, see Creating databases with the database wizard, Creating databases with SQL scripts and Uninstalling: delete databases with the database wizard.
  3. Delete the content in <WAS directory>\profiles\AppSrv01\FileNet
    Note: You must carry out this step to prevent failure when executing createGCD.sh/bat.
  4. Delete all of the content inside the CCM content directory, which, by default, is set to <Connections_Install_Root>/data/shared/ccm.
  5. Restart the FileNetEngine and FileNet Collaboration Services (FNCS) WebSphere Application Server applications in the WebSphere Application Server console.
  6. Rerun the post installation steps for configuring IBM Connections Content Manager for Libraries. For more information, see Configuring IBM Connections Content Manager for Libraries.