Verifying the installation of IBM Business Automation Workflow on containers

Containers:
Verify your installation and then log in to the web applications 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
bawstandalone-bawins1-baw-case-init-job-xtldp        0/1     Completed   0          5h59m
bawstandalone-bawins1-baw-content-init-job-wd7hx     0/1     Completed   0          6h6m
bawstandalone-bawins1-baw-db-init-job-xhp8j          0/1     Completed   0          6h17m
bawstandalone-bawins1-baw-ltpa-rc42g                 0/1     Completed   0          6h17m
bawstandalone-bawins1-baw-oidc-registry-job-cld8r    0/1     Completed   0          6h17m
bawstandalone-bawins1-baw-server-0                   1/1     Running     0          6h13m
bawstandalone-cmis-deploy-6569485866-wwtw2           1/1     Running     0          5h54m
bawstandalone-cpe-deploy-6c594474c8-fpd82            1/1     Running     0          5h59m
bawstandalone-dba-rr-551ee8cd5f                      1/1     Running     0          31m
bawstandalone-graphql-deploy-59bfdb7747-4ldq9        1/1     Running     0          6h12m
bawstandalone-navigator-deploy-5784778bd-lwvmj       1/1     Running     0          6h4m
bawstandalone-rr-backup-28347365-7vjfz               0/1     Completed   0          36s
bawstandalone-rr-setup-pod                           0/1     Completed   0          31m
bawstandalone-ums-scim-deployment-676979f54d-4l6px   1/1     Running     0          6h23m
bawstandalone-ums-scim-deployment-676979f54d-nl8vg   1/1     Running     0          6h23m
bawstandalone-ums-sso-deployment-6b68f785f-lxvpc     1/1     Running     0          6h23m
bawstandalone-ums-sso-deployment-6b68f785f-nv6hr     1/1     Running     0          6h23m
bawstandalone-ums-teams-deployment-db97f7fd8-6spnd   1/1     Running     0          6h23m
bawstandalone-ums-teams-deployment-db97f7fd8-9w47z   1/1     Running     0          6h23m
ibm-content-operator-76dc466465-dr2ks                1/1     Running     0          6h29m
ibm-cp4a-operator-7dcc884f7b-z76sh                   1/1     Running     0          6h31m
ibm-pfs-operator-5c4cb6589c-x4d4p                    1/1     Running     0          6h29m

To check the deployment status and see the containers that were created and started, run the following command with the specific namespace:
```
cert-kubernetes/scripts/baw-std-healthcheck.sh -n <namespace>
```
For each pod, check under Events to see that the images were successfully pulled. Check whether 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. Use either of the following methods to get the URL of the web applications and the user credentials to log in.
- Access the Config Maps from the Red Hat® OpenShift® web console.
  - Log in to your cluster web console.
  - Select your namespace.
  - In the left window, select Workloads > Config Maps.
  - Find cp4ba-access-info. You can get dashboard information from workflow-server-access-info.
  - Access Process Portal, Case Client, and Workplace by using the URLs in workflow-server-access-info.
- Access Process Portal, Workplace, and Case Client.
  - Process Portal URL: https://workflow_hostname/ProcessPortal where workflow_hostname corresponds to the baw_configuration.hostname property in your custom resource file.
  - Workplace URL: https://workflow_hostname/Workplace where workflow_hostname corresponds to the baw_configuration.hostname property in your custom resource file.
  - Case Client URL: https://navigator_hostname/navigator where navigator_hostname corresponds to the navigator_configuration.hostname property in your custom resource file.
If you are using self-signed certificates, you must first go to the following URL and accept the self-signed certificate:
- https://workflow_hostname where workflow_hostname corresponds to the baw_configuration.hostname property in your custom resource file.
Check the status and endpoints for Business Automation Workflow from the Red Hat OpenShift console or from the command line.
- Check the status and endpoints from the Red Hat OpenShift console.
  1. In the left menu, select Operators > Installed Operators.
  2. In the beginning of the right window, select your project (namespace).
  3. Click the installed operator for IBM Cloud Pak for Business Automation.
  4. Go to the CP4BA deployment tab page.
  5. Click your deployment (for example, icp4adeploy).
  6. Go to the YAML tab page.
  7. Find the top level status: element. Then check every component status. For example:
```
  status:
                         components:
                                ...
                               baw:
                                 bawDeployment: Ready
                                 bawService: Ready
                                 bawZenIntegration: Ready
                               baml:
                                 bamlDeployment: Ready
                                 bamlService: Ready
                                 ...
```
  8. Under status: search for endpoints, 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'
                         ...
```
  9. You can also check the endpoints in the Details page.
- Check the status and endpoints from the command line.
  1. To get your deployment name, run the following command:
```
oc get ICP4ACluster -n <your_project>
```
  2. To get the deployment YAML and check the status and endpoints, run the following command:
```
  oc get ICP4ACluster icp4adeploy -o yaml
```