Uninstalling CP4BA FileNet Content Manager from the OCP console

You can uninstall Cloud Pak resources and components from your platform deployment from the OCP console.

About this task

If you installed the IBM operator catalog, and used an IBM CP4BA FileNet Content Manager operator instance to create an ICP4ACluster then you must use the OCP user interface to uninstall it. Uninstalling involves four separate high-level tasks.

Uninstalling the Cloud Pak deployment.
Uninstalling the operators.
Deleting PVs and PVCs. If you do delete the PVs/PVCs, the persistent data along with configuration and log files are also deleted. Delete the PVCs before you delete the PVs.
Dropping the databases.
Deleting the secrets created by the Cloud Pak deployment. Go to the CP4BA project, click Workloads > Secrets, then right-click each secret and click Delete secret.
If you do delete all of the secrets that you created for Cloud Pak for Business Automation, then you must create them again if you want to install another CP4BA deployment.
Deleting the CP4BA project.
Uninstalling the Cloud Pak foundational services is necessary only if you want to completely clean up the cluster. The uninstallation of CP4BA uninstalls Cloud Pak foundation services only and does not remove the Cloud Pak foundation services operators and some of its resources. To completely remove Cloud Pak foundational services, see Uninstalling foundational services.

Procedure

Log in to your OCP or ROKS cluster.
Click Administration > Namespaces, and click the namespace that you used to install the Cloud Pak deployment.
Click Operators > Installed Operators > IBM CP4BA FileNet Content Manager, and then click the CP4BA deployment tab.

The name of the deployment is shown in the list of Content clusters. The default name is content.
To the right of the Content operator name, click > Delete Content.

The action deletes the resources and the instance is no longer seen in the Content list.

Note: Deleting the ICP4ACluster and uninstalling the CP4BA and Content operators does not delete the existing PVs/PVC, or the databases that are used by the various components. Check the persisted data before you delete the PVs/PVCs manually to make sure you no longer want to keep them. Likewise, if the data no longer needs to be retained or reused you can delete the databases.
Check whether the Client and ZenExtension resources are fully deleted because some resources get stuck in the Terminating state. Click Home > Search and select the CP4BA project.
1. Click Resource and enter Client. Select Client and check whether the resource shows as Resource is being deleted.
2. Click Resource and enter ZenExtension. Select ZenExtension and check whether the resource shows as Resource is being deleted.
If the Client and ZenExtension resources are remaining, you must run the following commands to clean up the resources:
1. Change the directory to the extracted cert-kubernetes/scripts folder.
```
cd ${PATH_TO_EXTRACTED_FILES}/cert-kubernetes/scripts 
```
2. Run the following command to clean up the resources:
```
./cp4a-uninstall-clean-up.sh 
```
Optional: If you want to uninstall the IBM CP4BA FileNet Content Manager operator as well, then click Operators > Installed Operators. To the right of the IBM CP4BA FileNet Content Manager operator, click > Uninstall Operator.

The action deletes the operator and the instance is no longer seen in the Installed Operators list.

What to do next

If you now plan to install another instance of the Cloud Pak on the same cluster, check if the dependencies like Namespaces and OperandRequests are properly deleted. If you are sharing the project with another Cloud Pak, then do not delete the dependencies.

Deleting PVCs

If you uninstalled all the operators, then you can delete the PVCs from the project. Click Storage > PersistentVolumeClaims for each PVC, and then click Delete PersistentVolumeClaim. If you deleted only CP4BA and its related operators, then you can click Storage > PersistentVolumeClaims, change the "Filter" to Label and enter "release=24.0.0" in the Search by label field. You can then delete the listed PVCs by clicking Actions > Delete PersistentVolumeClaim.

Optional: Deleting PVs

To identify which PV can be removed, check the status of the PV. If the status is “Available”, then the PVs can be deleted.

Get a list of all the PVs.
```
oc get pv
```
Delete a PV.
```
oc delete pv <PV name>
```

For more information about cleaning up your data, see Cleaning up data.

Deleting secrets

Remove the foundation subscription in the CP4BA namespace by clicking Home > Search, selecting Subscription for operators.coreos.com/v1alpha1 in the Resource list, and then selecting Remove Subscription from the icp4a-foundation-operator menu. Now, all of the CP4BA secrets can be deleted.
To delete the secrets from the project click Workloads > Secrets, and then click Delete Secret.
The CP4BA secrets include the strings ibm-cp4a or icp4a in the names. The custom secrets can also be deleted, for example ibm-fncm-secret, ibm-ban-secret, and ldap-bind-secret.

Deleting the databases

For more information about the databases used by FileNet® Content Manager, see Deleting a domain and Preparing an object store database or tablespace for reuse.
If you plan to reinstall the Application Engine database, you must drop the database and database objects (buffer pool and table spaces) after you delete Application Engine.
For more information about cleaning up your data, see Cleaning up data.

Deleting the CP4BA project

Note: If deleting a project fails and the project is stuck in the Terminating state, some objects may still exist in the namespace after a force deletion. Do not use the same project name to rebuild instead use a new project name.

Click Home > Projects, identify the project, and then click Delete Project.

The project might not terminate successfully until you uninstall the Cloud Pak foundational services.

Note: If foundational services are installed in a namespace-scoped instance in the same namespace as the CP4BA deployment, then delete the CP4BA project after you uninstalled the foundational services and Automation foundation. For more information, see Uninstall foundational services.

Deleting the catalog sources

If you decide to remove CP4BA completely, then remove the related catalog sources.

Click Administration > Cluster Settings, click the Configuration tab, scroll down the list, and then click OperatorHub.
Select the Sources tab.
Delete the following sources:
- ibm-cp4a-operator-catalog
- bts-operator
- cloud-native-postgresql-catalog
- ibm-cs-flink-operator-catalog
- ibm-cs-elastic-operator-catalog
- ibm-fncm-operator-catalog

Uninstall foundational services

If you plan to remove all of the Cloud Pak dependencies, the custom resource definitions (CRD) for both Cloud Pak for Business Automation and the Cloud Pak foundational services can be deleted. Delete the following CRDs from the cluster.

contentrequests.icp4a.ibm.com 
contents.icp4a.ibm.com 
foundationrequests.icp4a.ibm.com 
foundations.icp4a.ibm.com 
icp4aclusters.icp4a.ibm.com 
processfederationservers.icp4a.ibm.com 
wfpsruntimes.icp4a.ibm.com

Click Administration > CustomResourceDefinitions, search by the name and click Delete CustomResourceDefinition.

For more information about uninstalling foundational services, see Uninstalling foundational services.

Note: You can also run a script if the foundational services uninstallation does not remove all the components. For more information, see Uninstallation is not successful.