Verifying the installation of the containers

You can check the status of the IBM Automation Document Processing containers after installing with the operator.

About this task

Run the following command to get the status of the containers that are installed for IBM Automation Document Processing:

oc get icp4aclusters icp4adeploy -ojsonpath-as-json='{.status.components}'

Verifying the installation of the Document Processing engine container

Check the status of the following sub-components of Document Processing engine to see whether they are deployed correctly.

Table 1. Document Processing engine containers subcomponents
Component	Possible Values	Default	Description
`caDeployment`	`NotReady` `Successful` `Failed`	`NotReady`	Tracks the overall deployment of Document Processing engine.
`caSecrets`	`NotReady` `Ready` `Failed`	`NotReady`	Checks and makes sure that the Document Processing engine prerequisite secret is created. If this subcomponent fails, the `caDeployment` status is set to `Failed` as well.
`caDatabaseVerification`	`NotReady` `Ready` `Failed`	`NotReady`	Checks whether Document Processing engine can connect to the Base database. If this subcomponent fails, the `caDeployment` status is set to `Failed` as well.
`caStorageVerification`	`NotReady` `Ready` `Failed`	`NotReady`	Checks whether the Document Processing engine persistent volume claims (PVC) was created successfully. If this subcomponent fails, the `caDeployment` status is set to `Failed` as well.
`caService`	`NotReady` `Ready` `Failed`	`NotReady`	Checks whether all Document Processing engine containers and services were successfully created, and are in `Running` status. If this subcomponent fails, the `caDeployment` status is set to `Failed` as well.
`caZenRegistration`	`NotReady` `Ready` `Failed`	`NotReady`	Checks whether Document Processing engine successfully registered with Zen. If this subcomponent fails, the `caDeployment` status is set to `Failed` as well.
`caRRRegistration`	`NotReady` `Ready` `Failed`	`NotReady`	Checks whether Document Processing engine successfully registered with Resource Registry. If this subcomponent fails, the `caDeployment` status is set to `Failed` as well.

To monitor the status of Document Processing engine, use the following command:

oc get icp4aclusters icp4a -ojsonpath-as-json='{.status.components.ca}

The following example shows the output for a successful deployment:

{
  "components": {
    "ca": {
      "caDatabaseVerification": "Ready",
      "caDeployment": "Successful",
      "caIAMRegistration": "Ready",
      "caRRRegistration": "Ready",
      "caSecrets": "Ready",
      "caService": "Ready",
      "caStorageVerification": "Ready",
      "conditions": [
        {
          "lastTransitionTime": "2021-09-02T22:04:20Z",
          "message": "Document Processing engine deploys successfully.",
          "reason": "caDeployment",
          "status": "True",
          "type": "Successful"
        }
      ]
    },
....
 "endpoints": [
  {
    "name": "Document Processing engine REST API URL",
    "scope": "External",
    "type": "UI",
    "uri": "https://cpd-<namespace>.<hostname>/adp/aca/v1/projects"
  }
],