Reinitializing a CP4BA deployment with Business Automation Workflow

Edit online

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

About this task

Reinitialize a CP4BA deployment with Business Automation Workflow by using the following extra steps.

  1. Reinitialize CPE. For more information, see Reinitializing FileNet Content Manager.
  2. Reinitialize Navigator. For more information, see Reinitializing FileNet Content Manager.
  3. If installed, reinitialize Business Automation Insights. For more information, see Reinitializing a CP4BA deployment with Business Automation Insights.
  4. If federation is enabled, reinitialize Process Federation Server. For more information, see Redeploying a Process Federation Server (PFS) deployment.
  5. If the Common Web UI is enabled and you installed data persistence for Application Engine, see Reinitializing FileNet Content Manager.
  6. If Workflow Kafka services is enabled, remove all the topics associated with Kafka services if the topic data is not used. You can get the topics from the Workflow AsyncAPI. For more information, see Creating a Kafka service.
  7. If Workflow full-text search is enabled, remove the SavedSearchIndex from the Federated Data Repository. The default SavedSearchIndex name has ibmbawqueries as a suffix.
  8. Reinitialize Business Automation Workflow Runtime and Automation Workstream Services.

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.