Reinitializing a CP4BA deployment with Automation Decision Services

Edit online

After you deleted the CP4BA CR YAML file of your ICP4ACluster instance, you have extra steps to do when your deployment includes Automation Decision Services.

About this task

Reinitialize a CP4BA deployment with Automation Decision Services by using the following extra steps.

  1. If a remote MongoDB database is used (spec.ads_configuration.mongo.embedded: false or unset), then ADS designer projects are kept during the uninstallation and recovered after reinstallation.

    Save the designer and runtime admin secrets and the encryption keys that are provided in Configuring Decision Designer and Configuring the decision runtime to connect to the MongoDB from the new instance.

  2. If runtime uses dynamic provisioning, the related PVC is deleted when the ICP4ACluster CR is removed. Depending on your storage class retain policy, the related PV is deleted or kept. If you want to keep the decision archives, a backup must be done before you remove the CR. If s3 persistence is used, then decision archives are kept and recovered after the CR is reapplied.

What to do next

Return to the Redeploying Cloud Pak for Business Automation deployments task, reinitialize the storage and databases for any other capability in your deployment, and then complete the redeployment by applying the CR again.