To manually scale up the Process Mining deployment in the IBM Cloud Pak for Business Automation, which parameter section needs to be updated in the custom resource YAML file?

To manually scale a Process Mining deployment, an administrator must modify the custom resource (CR) YAML file. The replicas parameter within the specification (spec) of a particular component (e.g., engine, UI) dictates the number of running pods for that service. Increasing the integer value of the replicas parameter and applying the change instructs the IBM Cloud Pak for Business Automation operator to provision additional pods, thus scaling up the service to handle a higher load.

A. install: The install section is not a standard parameter for scaling. It might be used for initial deployment settings but not for adjusting the number of running pods post-installation.
B. license: The license section in the custom resource is used exclusively for accepting the license agreement and specifying the license edition. It has no role in resource scaling.
C. namespace: The namespace parameter specifies the logical scope in Kubernetes/OpenShift where the resources are deployed. Modifying it would attempt to move the deployment, not scale it.

1. IBM. (2023). IBM Cloud Pak for Business Automation documentation: Updating the Process Mining custom resource. "To scale up or down the number of pods for a component, you change the value of the replicas parameter." Retrieved from IBM Knowledge Center. (Specific section: Administering > Post-installation tasks > Updating the Process Mining custom resource).

2. IBM. (2023). IBM Cloud Pak for Business Automation documentation: Process Mining parameters. This reference details the structure of the Process Mining custom resource, showing that the replicas parameter is located under spec..replicas and is used to define the number of pods. (Specific section: Reference > Custom resource parameters > Process Mining parameters).