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-ml7wt                     0/1     Completed   0          19m
bawstandalone-bawins1-baw-content-init-job-7h748                  0/1     Completed   0          19m
bawstandalone-bawins1-baw-db-init-job-pfs-42dwq                   0/1     Completed   0          19m
bawstandalone-bawins1-baw-db-init-job-r95zs                       0/1     Completed   0          19m
bawstandalone-bawins1-baw-jms-0                                   1/1     Running     0          18m
bawstandalone-bawins1-baw-ltpa-xgm5w                              0/1     Completed   0          19m
bawstandalone-bawins1-baw-oidc-registry-job-4l6m5                 0/1     Completed   0          19m
bawstandalone-bawins1-baw-server-0                                1/1     Running     0          16m
bawstandalone-bawins1-baw-workplace-job-4bhjx                     0/1     Completed   0          19m
bawstandalone-cmis-deploy-cb98744f7-rkfrq                         1/1     Running     0          18m
bawstandalone-cpe-deploy-5cc657c999-gln62                         1/1     Running     0          38m
bawstandalone-dba-rr-b857643715                                   1/1     Running     0          49m
bawstandalone-elasticsearch-statefulset-0                         2/2     Running     0          15m
bawstandalone-graphql-deploy-dfdb8b75b-dprrj                      1/1     Running     0          32m
bawstandalone-navigator-deploy-876b64567-84mj7                    1/1     Running     0          25m
bawstandalone-pfs-0                                               1/1     Running     0          13m
bawstandalone-pfs-dbareg-79f5466db9-l28zv                         1/1     Running     0          13m
bawstandalone-pfs-umsregistry-job-bzn77                           0/1     Completed   0          15m
bawstandalone-rr-backup-27807150-5p4mj                            0/1     Completed   0          4m15s
bawstandalone-rr-setup-pod                                        0/1     Completed   0          49m
bawstandalone-ums-scim-deployment-76d7674c48-b426k                1/1     Running     0          45m
bawstandalone-ums-scim-deployment-76d7674c48-jcnl5                1/1     Running     0          45m
bawstandalone-ums-sso-deployment-5d67547dcc-8gbts                 1/1     Running     0          45m
bawstandalone-ums-sso-deployment-5d67547dcc-l7f6p                 1/1     Running     0          45m
bawstandalone-ums-teams-deployment-94b866d9c-btd5c                1/1     Running     0          45m
bawstandalone-ums-teams-deployment-94b866d9c-z66dh                1/1     Running     0          45m
bawstandalone-workspace-aae-ae-db-job-jmd4l                       0/1     Completed   0          39m
bawstandalone-workspace-aae-ae-deployment-5798cd66cf-6nmmc        1/1     Running     0          39m
bawstandalone-workspace-aae-ae-oidc-job-xgdcd                     0/1     Completed   0          39m
ibm-content-operator-cdbf8bf96-dq68b                              1/1     Running     0          52m
ibm-cp4a-operator-7fb58cd7c8-wblt7                                1/1     Running     0          52m
ibm-pfs-operator-68dc6b7c94-m5lmw                                 1/1     Running     0          52m

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. 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 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 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, Case Client, and Workplace using the following steps.
  - Access Process Portal by using the URL: https://workflow_hostname/ProcessPortal where workflow_hostname corresponds to the baw_configuration.hostname property in your custom resource file.
  - Access Case Client by using the URL: https://navigator_hostname/navigator where navigator_hostname corresponds to the navigator_configuration.hostname property in your custom resource file.
  - Access Workplace by using the URL: https://navigator_hostname/navigator?desktop=workplace where navigator_hostname corresponds to the navigator_configuration.hostname property in your custom resource file.
    Note: If you upgraded from an earlier version, you might see both workplace and IBMWorkplace1. Use the new workplace desktop.
If you are using self-signed certificates, you must first go to the following URLs and accept the self-signed certificates:
- https://workflow_hostname where workflow_hostname corresponds to the baw_configuration.hostname property in your custom resource file.
- https://pfs_hostname/rest/bpm/federated/v1/systems where pfs_hostname corresponds to the pfs_configuration.hostname property in your custom resource file. Remember to log in with your LDAP user and password.
- https://ae_hostname/ where ae_hostname either corresponds to the application_engine_configuration.hostname property or the shared_configuration.sc_deployment_hostname_suffix property in your custom resource file.
If you have pfs_configuration.enable_default_security_roles set to true in the custom resource file, default security roles are enabled in the Process Federation Server configuration files. For more information, see Process Federation Server in the IBM Business Automation Workflow Runtime and Workstream Services parameters.

Check the status and endpoints for Business Automation Workflow from the OpenShift console or from the command line.

Check the status and endpoints from the OpenShift console.

In the left menu, select Operators > Installed Operators.
On the top of the right 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
                               pfs:
                                 pfsDeployment: Ready
                                 pfsService: Ready
                                 pfsZenIntegration: Ready
                               baml:
                                 bamlDeployment: Ready
                                 bamlService: Ready
                                 ...

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'
                         ...

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
```