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

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.

In preparing the IBM Business Automation Studio and Application Engine environments for recovery, the sharedconfiguration. scrunasuser in the CR definition must have the same UID in common between the primary and secondary environments. This ensures that the same user account is used in both primary and secondary environments for disaster recovery.

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

It's also important that the primary and secondary environments have the same OpenShift administrator account and the same router hostname, but it's not necessary that they have identical LDAP configurations.

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/

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

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

The Cloud Pak for Business Automation standard capabilities logging is enabled to collect and forward standard output to the specified logging destination when configured. This logging is not stored in a dedicated persistent data store unless specified, and is viewable only by the OpenShift Container Platform (OCP) web console.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/bas/logging.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/bas/logging_setup.html

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/

Kafka is a distributed streaming platform that can be used to integrate events coming from BPMN workflows and from ADS (Application Data Sources). The Kafka unified data model allows for the standardized and centralized handling of data from various sources, including BPMN workflows and ADS. This setup can be used to standardize and normalize the data, which can then be used for analytics, reporting, and real-time processing.