Known issues and limitations for content services containers

The following information describes known issues and limitations when you deploy content services containers. These limitations cover the deployment process as well as using the content services components in a container environment.

Support details for content services components in container environments

For details about support in container environments, see the Software Product Compatibility report for the following products:
  • FileNet® Content Manager
  • IBM® Content Foundation
  • IBM Content Navigator

Limitations for Content Platform Engine

For detailed list of limitations, see technote What are the current limitations for containerized deployments of FileNet Content Manager and IBM Content Foundation.

(V5.5.5) Known Issue: A smaller number of indexing batches than configured leads to a noticeable degradation in the overall indexing throughput rate.

Because obsolete Virtual Servers in the Global Configuration Database (GCD) are not automatically cleaned up, that Virtual Server count can be higher than the actual number of CE instances with dispatching enabled. That inflated number will then result in a smaller number of concurrent batches per CSS server, negatively affecting indexing performance.

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

(V5.5.4) Known Issue: zero-byte file causes error message

When you deploy the external share container with the operator, but do not use the external LDAP settings, a zero-byte file called ibm_ext_ldap_AD.xml is created inside the container. This file triggers an invalid file error message. To solve the issue, you must manually delete the file from the disk.

(V5.5.4) Limitation of Google ID in Edit Service on an External Share desktop

In external share deployments that use Google ID for the identity provider authentication, issues can occur when using the Edit Service to edit or add Microsoft documents. The issue causes login to be unsuccessful.

(V5.5.3 and earlier) IBM Content Navigator Task Manager

The IBM Content Navigator Task Manager feature and any functions associated with the feature are not supported when IBM Content Navigator is deployed in a container environment. (Task Manager is available in V5.5.4 and later.) This limitation includes the following functions:
  • Teamspace deletion
  • IBM Content Navigator Box Share
  • IBM Case Manager Box Integration
  • IBM Enterprise Records sweep
  • IBM Content Collector for SAP

(V5.5.3 and earlier) Known Issue: When using IE or Edge browser to access the IBM Business Automation Configuration Container tool, the log output might not display as expected

On the deployment result page, the job container displays the log output in real time. When using an Internet Explorer or Edge browser, sometimes no log output displays and the deployment progress continues to show as not started.

The EventSource API that is used to fetch the server log information is not supported by Internet Explorer and Edge browsers, as explained in the following information: https://developer.mozilla.org/en-US/docs/Web/API/EventSource#Browser_compatibility

Workaround:

Use other browsers like Chrome, Safari, and Firefox.

Known Issue: In some cases the rerun function displays the log of the previous event before starting with the new event information

When a job fails, after you troubleshoot and fix the issues, you can rerun the failed job by clicking Rerun in the user interface.

When you click Rerun, it can take some time for the backend job container to restart and clean the log of the previous run. It can happen that the log is requested before the previous log is cleaned, and in this situation it prints the older log.

Resolution:

To get a clean view, after the new log starts to display messages, refresh the page. The old log is removed from the display.

(V5.5.1) Known Issue: Initializing IBM Content Navigator

When you choose the Include initialization step while deploying IBM Content Navigator, the application initializes a repository and a new default desktop.

Known Issue: When you try to edit the repository, the Save button is disabled.

Reason: The repository cannot be saved because the default repository ID includes an underscore (“_”).

Impact: You cannot modify the repository settings. However, there is no impact to the functionality connecting to the object store in FileNetP8. Users still can browse, create documents, and add documents to the repository.

Resolution: Update the following fields in the jobs.yml file to values that do not include an underscore:
  • ADD_REPO_ID
  • ADD_DESKTOP_REPO_ID

(V5.5.1) Known Issue: The Initialization and Verification options in the configuration tool are not working properly for environments that are using Oracle databases

If you are using Oracle database configured through the IBM Business Automation Configuration Container, do not select the optional steps Initialize and Verification in the configuration tool. If a user uses Initialize and Verify with an Oracle database the object stores are not created correctly.

By default the IBM Business Automation Configuration Container Initialize option configures shared database connections for the object store. However, this process works only with certain prerequisites in place. The recommended approach is to not use the Initialize and Verify options in the configuration tool so that you don't encounter issues due to the shared database connections without the proper prerequisites.

Workaround:

If you are deploying with an Oracle database, make sure that the following options in the configuration tool are not selected:
  • Include initialization step
  • Include verification step

When your deployment completes, you must initialize your Content Platform Engine and other components manually. See the following topic for details: Initializing and verifying your content services environment

If you selected the options during configuration, you can fix the environment by deleting the created object store, cleaning the associated tablespace, and recreating the object stores manually through the Administration Console for Content Platform Engine.