Reinitializing FileNet Content Manager

If you want to uninstall and redeploy FileNet Content Manager, you need to clean up the allocated storage and the databases.

About this task

Before you redeploy FileNet Content Manager, you need to clean up the existing allocated storage and databases. If the allocated storage and the databases contain production data, you do not want to follow this procedure unless you intend to delete your production data.

Removing the custom resource YAML file does not remove the PVs and PVCs that were set up for your environment. This prevents the loss of any data that might be included in the storage structure. You determine when you are ready to remove the persistent volumes and claims, and to reclaim your databases for another use. These steps assume that you already analyzed your data to make sure you are ready to delete.

Procedure

  1. Determine the database or table space that the domain's global configuration database uses by reviewing the data sources information in the custom resource YAML for the Content pattern deployment.
  2. Determine the database or table space that is used by the object stores by reviewing the data sources information in the custom resource YAML used for the Content pattern deployment.
  3. Determine the database or table space that is used for the Business Automation Navigator (BAN) configuration database by reviewing the data sources information in the custom resource YAML for the Content pattern deployment.
  4. Delete the contents of the cpe-fnlogstore persistent volume.
  5. Delete content from any advanced storage devices or fixed storage devices for the object store that contain content for that object store only.
    1. Delete all content on the devices that belong to the object store you are deleting.
    2. Delete the device.txt file that is located in the root directory of the deleted advanced storage device.
  6. Delete the directories that hold any full text indexes that are created by Content Search Services or indexes that are managed by Elastic Search that is associated with the deleted object stores.
  7. Delete or reuse the databases or table spaces for the object stores and BAN configuration information. To delete the database or table space, see the documentation that is provided with your database application. For more information about reusing the database or table space for another object store, see Preparing an object store database or tablespace for reuse.
  8. Drop the tables in the global configuration database.
    1. Open the appropriate tool for your database vendor to access the database or table space.
    2. In the database provider tool, find the database or table space for the global configuration database.
    3. In the database or table space for the global configuration database, drop the tables with names that begin with FNGCD.
      If your FileNet P8 domain included managed users or local groups, also drop these tables:
      • managedusers
      • localgroups
      • localgroupmembers