Redeploying Cloud Pak for Business Automation deployments

Redeploying a CP4BA deployment involves deleting the CP4BA custom resource (CR), running the cp4a-uninstall-clean-up.sh script, and then reapplying the CR. 

About this task

Use the following steps to clean up your CP4BA multi-pattern deployments and then reinitialize the storage and databases for each of the capabilities.

After you completed all the clean up steps and reinitialized your allocated storage and databases, apply the custom resource for your redeployment.

Procedure

  1. To clean up a CP4BA multi-pattern deployment, use the following steps.
    1. Backup your CR YAML file, and check the configuration and database information.
    2. Delete the ICP4ACluster instance in the OCP console or by using OCP CLI.

      To retrieve the names of the instances, run the get command.

      oc get ICP4ACluster

      To delete an instance, run the delete command.

      oc delete ICP4ACluster <MY-INSTANCE>

      Wait for all the pods to be terminated.

    3. Change the directory to the downloaded cert-kubernetes/scripts folder.
      cd ${PATH_TO_EXTRACTED_FILES}/cert-kubernetes/scripts
    4. Run the following command to clean up the resources:
      ./cp4a-uninstall-clean-up.sh
    5. Delete the CR YAML file for the ICP4ACluster instance in the OCP console or by using OCP CLI.
      Note: Removing the custom resource YAML file does not remove all the PVs and PVCs you set up for your environment. Determine when you are ready to remove the persistent volumes and claims, and to reclaim your databases for another use. The clean up steps assume that you already analyzed your data and you are ready to delete the PVs and PVCs or delete the content in the PVs.

      Before you redeploy your deployment, you need to clean up the existing allocated storage and databases. The following steps assume that the allocated storage and the databases do not contain production data that you want to keep.

    6. Follow the extra steps according to your included components.
  2. If Business Automation Application is included, see Reinitializing a CP4BA deployment with Business Automation Application.
  3. If Business Automation Workflow is included, see Reinitializing a CP4BA deployment with Business Automation Workflow.
  4. If Business Automation Workflow Authoring is included, see Reinitializing a CP4BA deployment with Business Automation Workflow Authoring.
  5. If FNCM is included, see Reinitializing FileNet Content Manager.
  6. If Enterprise Records is included, see Reinitializing a CP4BA deployment with Enterprise Records.
  7. If Automation Decision Services is included, see Reinitializing a CP4BA deployment with Automation Decision Services.
  8. If Business Automation Insights is included, see Reinitializing a CP4BA deployment with Business Automation Insights.
  9. If Workflow Process Service Authoring is included, see Reinitializing a CP4BA deployment with Workflow Process Service Authoring.
  10. Reapply your ICP4ACluster deployment CR to create a new instance.
    1. Check that all the capabilities that you want to install are configured.
      cat <custom-resource-file>.yaml
    2. Use the OpenShift CLI to deploy the configured capabilities and apply the custom resource.
      oc apply -f <custom-resource-file>.yaml
  11. To reconfigure a CP4BA deployment with IBM Content Collector for SAP Applications, use the following steps.
    1. Configure the IBM Content Collector for SAP Applications plug-in in IBM Enterprise Records and create a Desktop. For more information, see Configuring IBM Content Navigator for connecting to Content Collector for SAP Applications.
    2. Configure Task Manager. For more information, see Configuring Task Manager for Content Collector for SAP Applications.
    3. Verify the setup of IBM Content Collector for SAP Applications. For more information, see Completing post-deployment tasks for Content Collector for SAP Applications.