C1000-150 IBM Cloud Pak for Business Automation v21.0.3 Administration Questions and Answers

ILMT (IBM License Metric Tool) report uses Processor Value Unit (PVU) to determine licensing cost. PVU is a unit of measurement used to determine the licensing requirements for certain IBM software products, including IBM Business Automation Workflow. PVU is based on the number of processor cores in a physical or virtual server, and the software vendor uses this information to determine the licensing cost.

It ' s important to note that PVU is different from other units of measurement such as API Calls or Resource Value Unit.

To enable a trace specification for Business Automation Workflow, you must create a ConfigMap. This ConfigMap will contain the trace specification that you wish to enable.

References: [1]  https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_trace_spec.html  [2]  https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/

Migrating data from a Cloud Pak for Business Automation version that does not support an upgrade requires an Administrator to uninstall the current deployment and follow the migration instructions for each component, pointing them to the existing persistent stores

When migrating data from Cloud Pak for Business Automation versions that do not support an upgrade, an Administrator must uninstall the current deployment and follow the migration instructions for each component to point to the existing persistent stores. This process involves migrating data from the existing databases and persistent volumes to the new deployment. This process may also require creating new configurations and customizing the new deployment to match the previous one.

The best approach to determine the cause of a performance issues with Operational Decision Manager Rule Execution Server is to enable an audit trace on the Decision Server Console. This will allow you to view detailed information about rule execution, including the time taken for each rule, the parameters passed to each rule, and the results returned.

References: [1]  https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_audit_trace.html  [2]  https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_ds_console_overview.html

Operator log files can be retrieved from the Ansible directory. The Ansible directory is located in the home directory at ~/.ansible/logs.

References: [1]  https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/troubleshoot/operator_logs.html  [2]  https://docs.ansible.com/ansible/latest/reference_appendices/config.html#ansible-log-dir

When backing up data within a multiple-zone cluster, it is important to make regular backups for the active zone only. This ensures that the data is up-to-date and any changes made in the other zones are not lost if something goes wrong.

To forward audit logging, the ENABLE AUDIT LOGGING FORWARDING parameter is required. This parameter is used to enable the forwarding of audit logs to an external service.

References: [1]  https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/administer/audit.html  [2]  https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/administer/overview.html

References: [1]  https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/bas/getting_started/overview.html  [2]  https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/pam/getting_started/overview.html

The parameters for accessing the images in an OpenShift Container Platform environment are set using the  oc set  command. This command allows you to set image pull secrets and other image-related parameters.

References: [1]  https://docs.openshift.com/container-platform/4.4/openshift_images/image-pull-secrets.html  [2]  https://docs.openshift.com/container-platform/4.4/cli_reference/openshift_cli/oc-set.html

In an OpenShift Container Platform environment, the parameters for accessing images are set using the " oc set " command. The " oc set " command allows an administrator to configure various aspects of a deployment, such as environment variables, resource limits, and image pull secrets. These parameters can be set for a specific deployment, service, pod, or other resource in the OpenShift cluster.

When dealing with OpenShift Container Platform (OCP) logs and log persistence, Fluentd is the component that collects all node and container logs and stores them in a dedicated project indexes. Fluentd is an open source data collector that can collect, process, and forward data from a variety of sources.

References: [1]  https://docs.openshift.com/container-platform/4.5/logging/understanding-logging.html  [2]  https://docs.fluentd.org/

Kubernetes Events are objects that provide insight about what is happening inside a cluster, such as the state of a pod, the status of a deployment, or any other type of activity. They can be used to detect and troubleshoot errors, or to track the progress of a deployment.

References: [1]  https://kubernetes.io/docs/tasks/debug-application-cluster/discover-events/  [2]  https://kubernetes.io/docs/concepts/cluster-administration/logging/

Before deploying the Cloud Pak for Business Automation operator, it is important to ensure that the necessary database and persistent volume are in place. This will allow the operator to store and persist data as needed. The other options are not prerequisites for all Cloud Pak for Business Automation capabilities.

References: [1]  https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_k8s_prereq.html  [2]  https://www.ibm.com/support/knowledgecenter/SSFTN5_9.7.1/com.ibm.wbpm.inst.doc/topics/t_k8s_install_operator.html

If a new modification to a Deployment has rendered it unstable, then the best way to regain stability is to rollback to an earlier Deployment. Rolling back to a previous Deployment will restore the system to its previous configuration, which should restore stability. The other options are not related to this process.

References: [1]  https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/  [2]  https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#rollback

A tracking event reflects an ongoing activity instance in a workflow process. It is used to capture and track the progress of the process and can be used to create an audit trail.

References: [1]  https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-monitor-and-manage-logs  [2]  http://www.bawtech.com/what-are-business-activity-workflows-baw/