Disabling Unified Automation Builder for watsonx Orchestrate

This page provides instructions for disabling the Unified Automation Builder (UAB) component in watsonx Orchestrate.

Warning: The UAB disabling process is irreversible. After you disable UAB and run the cleanup script, you cannot re-enable UAB without reinstalling the watsonx Orchestrate instance. Ensure that you have a valid business reason and obtain the necessary approvals before proceeding.

Overview

UAB provides automation capabilities that include:
  • Automation Decision Services
  • Workflow Services
  • Document Processing
When you disable UAB, it removes these capabilities from your watsonx Orchestrate instance.

Prerequisites

  • You must have access to the Red Hat® OpenShift® cluster with appropriate permissions.
  • Ensure that the oc CLI tool is installed and configured.
  • You must have admin access to the watsonx Orchestrate namespace.
  • Backup your watsonx Orchestrate configuration (recommended).

Disabling UAB

Update the CR and run the UAB cleanup script
Export your watsonx Orchestrate namespace.
export PROJECT_CPD_INST_OPERANDS=<cpd_operand_namespace> 
Run the following script to update the CR for disabling UAB and remove the UAB components:
#!/bin/bash

# Patch the WO CR to disable UAB
oc patch wo wo -n $PROJECT_CPD_INST_OPERANDS \
  --type=merge \
  -p '{"spec":{"uab":{"enabled":false}}}'

echo "Cleaning up UAB components.!!!"

# Delete UAB Automation Decision Services
oc delete uabautomationdecisionservices wo -n $PROJECT_CPD_INST_OPERANDS

# Delete UAB Workflow Services
oc delete uabwfservices wo -n $PROJECT_CPD_INST_OPERANDS

# Delete Document Processing
oc delete documentprocessings wo-docproc -n $PROJECT_CPD_INST_OPERANDS

echo "Cleanup completed.!!!"
echo "Monitor the WO CR status by running:"
echo "  oc get wo -n ${PROJECT_CPD_INST_OPERANDS} -o yaml"
echo "Ensure the WO CR status is 'Completed'"
echo "------------------------------------------------------------------"
Script execution steps
  1. Save the script to a file (for example, disable_uab.sh):
    vi disable_uab.sh
  2. Make the script executable:
    chmod +x disable_uab.sh
  3. Update the PROJECT_CPD_INST_OPERANDS variable in the script to match your namespace.
  4. Run the script:
    ./disable_uab.sh
Verify the cleanup
  1. To monitor the watsonx Orchestrate CR status and verify that the changes are successfully applied:
    oc get wo -n $PROJECT_CPD_INST_OPERANDS -o yaml
    Wait until the status shows Completed.
  2. To verify that the UAB components are removed:
    # Check for UAB Automation Decision Services
    oc get uabautomationdecisionservices -n $PROJECT_CPD_INST_OPERANDS
    
    # Check for UAB Workflow Services
    oc get uabwfservices -n $PROJECT_CPD_INST_OPERANDS
    
    # Check for Document Processing
    oc get documentprocessings -n $PROJECT_CPD_INST_OPERANDS
    All commands must return "No resources found" or similar messages.
  3. To check whether the UAB configuration is disabled in the watsonx Orchestrate CR:
    oc get wo wo -n $PROJECT_CPD_INST_OPERANDS -o jsonpath='{.spec.uab.enabled}'
    The command must return false.