Verifying Business Automation Workflow Runtime
Verify your installation and then log in to the web application to get started.
Procedure
-
Wait for about 45 minutes, depending on your computer's performance. Then, check the status of
the pods. Get the names of the pods that were deployed by running the following command:
oc get pod -n my_project
The following example shows a successful pod status. The pods are all running or completed, depending on their type.NAME READY STATUS RESTARTS AGE common-service-db-1 1/1 Running 0 32h common-web-ui-5c66c4b558-6xk7w 1/1 Running 0 31h icp4adeploy-insights-engine-flink-86c754b47d-ggzvg 2/2 Running 0 31h icp4adeploy-insights-engine-flink-taskmanager-5c98544brrj 1/1 Running 0 31h icp4adeploy-insights-engine-flink-taskmanager-5c9854xdgkj 1/1 Running 0 31h icp4adeploy-bai-bpmn-f8d7t 0/1 Completed 0 31h icp4adeploy-bai-icm-8p5xn 0/1 Completed 0 31h icp4adeploy-bai-setup-wsztk 0/1 Completed 0 31h icp4adeploy-bawins1-baw-case-init-job-nmbj8 0/1 Completed 1 30h icp4adeploy-bawins1-baw-content-init-job-q7dgg 0/1 Completed 1 30h icp4adeploy-bawins1-baw-db-init-job-xd5bq 0/1 Completed 0 30h icp4adeploy-bawins1-baw-ltpa-h8bdh 0/1 Completed 0 30h icp4adeploy-bawins1-baw-server-0 1/1 Running 0 30h icp4adeploy-cmis-deploy-99fcfdd9d-kjp7n 1/1 Running 0 31h icp4adeploy-cpe-deploy-794b54475d-f44kj 1/1 Running 0 31h icp4adeploy-cpe-watcher-5d9f8c474c-dkdkn 1/1 Running 0 14m icp4adeploy-dba-rr-9dba5fa2a8 1/1 Running 0 31h icp4adeploy-graphql-deploy-7ffd957d96-52frc 1/1 Running 0 30h icp4adeploy-insights-engine-application-setup-ltzpt 0/1 Completed 0 31h icp4adeploy-insights-engine-cockpit-7ff57c8cb6-7zjzg 1/1 Running 0 31h icp4adeploy-insights-engine-management-c87f7d75c-ljvkm 2/2 Running 0 31h icp4adeploy-mls-itp-d875bcccb-c9msd 1/1 Running 0 7h54m icp4adeploy-mls-wfi-855d948bdd-66g2l 1/1 Running 0 7h54m icp4adeploy-navigator-deploy-658c7f89d7-z25jw 1/1 Running 0 30h icp4adeploy-navigator-watcher-64bc9c5794-5gp9d 1/1 Running 0 10m icp4adeploy-rr-backup-28616625-4ncgr 0/1 Completed 0 100s icp4adeploy-rr-setup-pod 0/1 Completed 0 31h create-postgres-license-config-mrwgp 0/1 Completed 0 32h create-secrets-job-ckzvl 0/1 Completed 0 31h flink-kubernetes-operator-84fd68467b-c8rjf 2/2 Running 4 (98m ago) 31h iaf-system-entity-operator-68bdc695bc-v9xwl 2/2 Running 0 32h iaf-system-kafka-0 1/1 Running 0 32h iaf-system-zookeeper-0 1/1 Running 0 32h iam-config-job-6hwmv 0/1 Completed 0 31h ibm-ads-operator-9456bddd4-nv8jt 1/1 Running 0 32h ibm-bts-cnpg-auto-6vlw1-cp4ba-bts-1 1/1 Running 0 31h ibm-bts-cnpg-auto-6vlw1-cp4ba-bts-2 1/1 Running 0 31h ibm-bts-cp4ba-bts-316-deployment-588c67bcdf-78rjl 1/1 Running 0 31h ibm-bts-cp4ba-bts-316-deployment-588c67bcdf-ff7zw 1/1 Running 0 31h ibm-bts-operator-controller-manager-7d5f4d455c-jwj47 1/1 Running 0 31h ibm-common-service-operator-5cfc86f56d-4vs6k 1/1 Running 0 32h ibm-commonui-operator-d9758bb85-nkjp6 1/1 Running 0 32h ibm-content-operator-6f44bf9cb4-grgzh 1/1 Running 0 32h ibm-cp4a-operator-68d4b644dc-zss8l 1/1 Running 0 32h ibm-cp4a-wfps-operator-6fbfc6849b-wcjkp 1/1 Running 0 32h ibm-dpe-operator-66868fdc76-qgkgn 1/1 Running 0 32h ibm-elasticsearch-operator-ibm-es-controller-manager-7f5bbbhj4d 1/1 Running 0 32h ibm-events-operator-v5.0.1-85cdbc98b5-599c8 1/1 Running 0 32h ibm-iam-operator-69d7944487-gwkld 1/1 Running 0 32h ibm-insights-engine-operator-86886f9855-rqdqd 1/1 Running 0 32h ibm-nginx-847b7fbd76-wzr8v 2/2 Running 0 31h ibm-nginx-tester-569f5b6868-xgsvl 2/2 Running 0 31h ibm-odm-operator-7467b6f65b-v5dx2 1/1 Running 0 32h ibm-pfs-operator-765684597d-8nflf 1/1 Running 0 32h ibm-workflow-operator-5c8cbfb45-bcprw 1/1 Running 1 (7h54m ago) 32h ibm-zen-operator-65b89f4dc4-h69zp 1/1 Running 0 32h icp4a-foundation-operator-c9cd4df6c-7gvd8 1/1 Running 0 32h meta-api-deploy-759dddd687-9f9xp 1/1 Running 0 32h oidc-client-registration-nrv7v 0/1 Completed 0 32h opensearch-ib-6fb9-es-server-all-0 2/2 Running 0 32h opensearch-ib-6fb9-es-server-all-1 2/2 Running 0 32h opensearch-ib-6fb9-es-server-all-2 2/2 Running 0 32h operand-deployment-lifecycle-manager-6c66b5cd46-hq8wf 1/1 Running 0 32h platform-auth-service-87f7b9dc6-cghr2 1/1 Running 0 32h platform-identity-management-b445bdc6b-82nv8 1/1 Running 0 31h platform-identity-provider-795c4f5989-prjjb 1/1 Running 0 31h postgresql-operator-controller-manager-1-18-12-7778fc64f-8rhhk 1/1 Running 0 31h setup-job-bfzls 0/1 Completed 0 32h usermgmt-5887785dd5-2vgct 1/1 Running 0 31h usermgmt-ensure-tables-job-shkvb 0/1 Completed 0 31h zen-audit-775bbd67b-bkhv7 1/1 Running 0 31h zen-core-7df8d8f59d-8c8fn 2/2 Running 1 (31h ago) 31h zen-core-api-cbd74d974-8rmnw 2/2 Running 0 31h zen-core-create-tables-job-qv89s 0/1 Completed 0 31h zen-core-pre-requisite-job-pmcvf 0/1 Completed 0 31h zen-metastore-backup-cron-job-28615200-g5v66 0/1 Completed 0 23h zen-metastore-backup-cron-job-28615680-vx9mm 0/1 Completed 0 15h zen-metastore-backup-cron-job-28616160-wxmsq 0/1 Completed 0 7h46m zen-metastore-edb-1 1/1 Running 0 31h zen-minio-0 1/1 Running 0 31h zen-minio-1 1/1 Running 0 31h zen-minio-2 1/1 Running 0 31h zen-minio-create-buckets-job-485q2 0/1 Completed 0 31h zen-pre-requisite-job-f2l4j 0/1 Completed 0 31h zen-watcher-55dfc8cdf7-2h2p2 2/2 Running 0 31h
- For each pod, check under Events to see that the images were successfully pulled and the
containers were created and started, by running the following command with the specific pod
name:
oc describe pod pod_name -n my_project
-
Get the URLs and log in to Process Portal, Case Client, and Workplace.
To get the URL of the web applications and the user credentials to log in, access the Config Maps from the OpenShift® web console.
- Log in to your cluster web console.
- Select your namespace.
- In the left panel, select Workloads > Config Maps.
- Find cp4ba-access-info. You can get IBM Cloud Pak® dashboard information from workflow-server-access-info.
- Access Process Portal, Case Client, and Workplace by using the URLs in workflow-server-access-info.
If you are using self-signed certificates, you must first go to the following URL and accept the self-signed certificate:https://workflow_hostname
whereworkflow_hostname
corresponds to thebaw_configuration.hostname
property in your custom resource file.
- Check the status and endpoints for IBM Business Automation Workflow from the OpenShift console or from the
command line.
- Check the status and endpoints from the OpenShift console.
- In the left panel select Operators > Installed Operators.
- On the upper-right of the window, select your project (namespace).
- Click the installed operator for IBM Cloud Pak for Business Automation.
- Go to the CP4BA deployment tab page.
- Click your deployment (for example, icp4adeploy).
- Go to the YAML tab page.
- Find the top level
status:
element, then check every component's status. For example:status: components: ... baw: - bawDeployment: Ready bawService: Ready bawZenIntegration: Ready name: bawins1 baml: bamlDeployFailedMsg: deploying is under good status bamlDeployStatus: Ready bamlServiceStatus: Ready
- Under
status:
search forendpoints
, then check the endpoints. For example:endpoints: ... - name: BAW Login URL scope: External type: UI uri: 'https://baw-bawins1-tensor.apps.bawdev-large-x100.cp.fyre.ibm.com/ProcessPortal' ...
- You can also check the endpoints in the Details page.
- Check the status and endpoints from the command line.
- To get your deployment name, run the following
command:
oc get ICP4ACluster -n <your_project>
- To get the deployment YAML and check the status and endpoints, run the following
command:
oc get ICP4ACluster icp4adeploy -o yaml
- To get your deployment name, run the following
command:
- Check the status and endpoints from the OpenShift console.