Known limitations and issues

If you want to delete and recreate a Document Processing project to start over, you might encounter errors after recreating the project. This occurs because the recreated project is out of sync with the Git repository.

For more information, see Saving an ADP Project fails with status code 500 service error.

You reach the Verify client user interface in different ways, depending on your application. For example, for the single document application, you tab into the content list on the start page, select a document from the list by pressing the Tab or Arrow keys, and then you tab to the context icon (the 3 ...), select the icon by pressing the space bar or the Enter key, and finally press the Arrow keys to select Review document.

In a single or batch document processing application, the Fit to height option does not fit to height properly.

Due to a limitation when editing the document to fix classification issues in batch document processing applications, the current icp4adeploy-viewone-svc service session affinity is configured as ClientIP and the session has to be sticky.

Workaround

To display the key value pair (KVP) fields correctly in the Data extraction issues page, update the settings for your Batch Document Processing Template or Document Processing Template application in Application Designer.

1. Log in to Business Automation Studio, and from the menu, click Design > Business applications.
2. Create a version for your application:
   1. Find your application and click Open to open your application.
   2. Click the Versions icon at the top and select Create a version.
   3. Go back to Business Automation Studio. In Applications, double-click the tile for your application and select a version to export:
      • If you want to export the most recent version, click the three dot menu at the top and click Export.
      • If you want to export a specific version, click the three dot menu in the row for the version, and click Export.
   4. Click Export this version to be shared or backed up (.twx) and save the file to your machine. If you have more than one application to export, repeat the steps for each application in your authoring environment.
3. Log in to the destination Business Automation Studio and from the menu, click Design > Business applications. Click Import and import your .twx application file. After importing, find the tile for your application and click the icon to accept any available updates.
4. Open your application and go to VerifyPage for a document processing application, or the Verify data page for a batch document processing application.
   1. Click Properties . Click Switch to advanced properties and open Configuration > General.
   2. Update the environment variable settings by using the Select... button, as follows:
      • Content project ID: DbaProjectId
      • Content Analyzer project ID: ACAProjectId
   3. Click Done, then Finish editing.
5. For a batch document application, go to the Classify page and repeat steps 4.a, 4.b and 4.c.
6. Go to Application project settings > Environment Variables.
   1. Update evDbaProjectId to the current project ID.
   2. Update evObjectStoreName to the current object store name.
   3. Create the variable idTokenSupport and give it a value of GRAPHQL_APP_RESOURCE,VIEW_APP_RESOURCE,CA_APPRESOURCE.
7. Click Finish editing, go back to the application page, and click Preview. Ignore any alert about folder access for a document processing application, as the following steps correct the problem.
8. Close the preview and exit your application.
9. Create a version for your application and export it: repeat steps 2.a to 2.c of this procedure and when you select a version to export, click the three dot menu next to the most recent version, select Export this version to be published (.zip), and click Export. Save the file to your machine.

   If you have more than one application to export, repeat the steps for each application in your authoring environment.

10. Import the file to your application service connections in IBM Business Automation Navigator. For more information, see Moving your application to runtime.

When you create an application in Business Automation Studio, an application configurator displays where you enter configuration parameters for the application.

However, after the application is created you cannot access the same configurator. As a result, you cannot change the configuration settings the same way.

Workaround

In the Batch Document Processing template, use the view configurator for the Verify Data page.

In the Document Processing template, use the view configurator for the VerifyPage.

If you deployed Business Automation Studio with the Business Automation Workflow server in the same custom resource YAML file, and you do not see process applications from Business Automation Workflow server in Business Automation Studio, restart the Business Automation Workflow server pod.

If you use the kubectl get pods command to check the pods when a pod is in the CrashLoopBackOff state, you get the following error message:

Warning Failed 3m kubelet, <IP_ADDRESS>
Error: failed to start container: 
Error response from daemon: 
OCI runtime create failed: container_linux.go:348: 
starting container process caused "process_linux.go:402: container init caused \"
rootfs_linux.go:58: 
   mounting \\\"/var/lib/kubelet/pods/XXXXX/volume-subpaths/key-trust-store/ibm-dba-ums/2\\\" 
   to rootfs \\\"/var/lib/docker/overlay2/XXXXXXX/merged\\\" 
   at \\\"/var/lib/docker/overlay2/XXXXXXX/merged/opt/ibm/wlp/usr/shared/resources/security/keystore/jks/server.jks\\\" 
   caused \\\"no such file or directory\\\"\"": unknown

To recover a pod, delete it in the OpenShift console and create a new pod.

To use IBM Business Automation Application Engine (Application Engine) with Db2® for High Availability and Disaster Recovery (HADR), you must have an alternative server available when Application Engine starts.

IBM Resource Registry can get out of sync.

After you create the Resource Registry, you must keep the replica size.

• If you update the Resource Registry admin secret to change the username or password, first delete the instance_name-dba-rr-random_value pods to cause Resource Registry to enable the updates. Alternatively, you can enable the update manually with etcd commands.
• If you update the Resource Registry configurations in the icp4acluster custom resource instance, the update might not affect the Resource Registry pod directly. It affects the newly created pods when you increase the number of replicas.

After you deploy Business Automation Studio or Application Engine, you cannot change the Business Automation Studio or Application Engine admin user.

Because of a Node.js server limitation, Application Engine trusts only root CA.

• The certificate can be self-signed, or signed by a well-known root CA.
• If you are using a depth zero self-signed certificate, it must be listed as a trusted certificate.
• If you are using a certificate that is signed by a self-signed root CA, the self-signed CA must be in the trusted list. Using a leaf certificate in the trusted list is not supported.
• If you are adding the root CA of two or more external services to the Application Engine trust list, you can't use the same common name for those root CAs.

The Java™ Message Service (JMS) statefulset doesn't support scale.

For more information and to resolve the issue, see Content Platform Engine uneven CBR indexing workload and indexing degradation.

This problem can arise if the IAM LDAP to SCIM mapping contains a value for the SCIM userName attribute that is an email address but there is no value mapped to the SCIM email attribute. For example, using a MSAD LDAP server, the UserPrincipalName can be populated with the user's email address, but no value is populated for the mail attribute. With IAM's default LDAP to SCIM map, the LDAP UserPrincipalName value is mapped to the SCIM userName field and the LDAP mail value is mapped to the SCIM email field.

If the user logs in with a userName that looks like an email address, the CPE server will attempt to retrieve the users information from IAM via a SCIM request. Since the userName looks like an email, the SCIM query that is performed uses the SCIM email field. Since the SCIM email field is mapped from the underlying LDAP mail field, if there is no value in this mail field, then the SCIM query will fail and the user will get an authentication failure.

The workaround for this scenario is to configure IAM's SCIM attribute mapping to also map the LDAP UserPrincipalName attribute to the SCIM email attribute. Thus CPE SCIM queries will succeed when a value is present for a SCIM email and the user will be able to login. You can configure the IAM SCIM attribute map as described in Updating SCIM LDAP attributes mapping.

• Ensure that cpe is deployed in a highly available setup, with at least two replicas.
• Monitor the cpe pod and restart if issues occur.
• On the cpe pod, consider setting the disable_fips production parameter to "true" for any environments where FIPS is not required.

Business Performance Center

You cannot create an alert for a period KPI if it contains a group. If you want to create an alert for a period KPI, go to the Monitoring tab and remove the Group by keyword. Then, go to the Thresholds tab to create one or more alerts.

Kibana

In the Kibana graphical user interface, the Alerting menu item for monitoring your data and automatically sending alert notifications is present but the underlying feature is not enabled.

Because Business Performance Center uses Elasticsearch as its database, approximation problems can be found with aggregations of numbers greater than 2^53 (that is, about 9 * 10^15). See the Limits for long values section of the Aggregations page of the Elasticsearch documentation.

When you create a metric, aggregations (minimum, maximum) are not supported on data of type double. Use a float instead.

Defining a high number of fields in an Elasticsearch index might lead to a so-called mappings explosion which might cause out-of-memory errors and difficult situations to recover from. The maximum number of fields in Elasticsearch indices created by IBM Business Automation Insights is set to 1000. Field and object mappings, and field aliases, count towards this limit. Ensure that the various documents that are stored in Elasticsearch indices do not lead to reaching this limit.

Event formats are documented in Reference for event emission.

For Operational Decision Manager, you can configure event processing to avoid the risk of mappings explosion. See Operational Decision Manager event processing walkthrough.

To avoid this issue, edit the filter in the User tasks currently waiting to be processed search. Set the state filter to accept one of the following values: TASK_CREATED, TASK_STARTED, TASK_CLAIM_CANCELLED, TASK_CLAIMED.

When upgrading the Business Automation Insights, the event forwarder job fails.

Restart the event forwarder job using the following command:

oc get job iaf-insights-engine-event-forwarder -o json | jq 'del(.spec.selector)' | jq 'del(.spec.template.metadata.labels)' | oc replace --force -f - }}

For further instructions, see Troubleshooting Apache Flink jobs

The same applies to Business Performance Center.

Fixed date time range

If, in a fixed date time range, you modify only the date or time, your changes are not saved.

Data tables

When any chart is displayed as a data table, only the first 1000 rows are shown.

Data permissions

You can set up data permissions by monitoring source or by team. If you encounter an error when you set a permission by source, try setting the same permission by team.

{\"error_description\":\"OpenID Connect client returned with status: SEND_401\",\"error\":401}

The log indicates that the IAM certificate cannot be found in the truststore.jks file.

The IAM certificate has probably been renewed but the ODM pods have not been refreshed with the new certificate.

Restart the ODM pods manually to apply the new certificate.