Upgrading IBM FileNet Content Manager
If you deployed IBM FileNet® Content
Manager, you must upgrade the
ecm_configuration
section in the custom resource YAML file that is used in the
previous version. If you pulled in IBM FileNet Content
Manager as a dependency for Business
Automation Workflow Authoring, you might not have the ecm_configuration
section in
your YAML file.
Before you begin
The following diagram highlights the components that are always installed when you
install a content
pattern, along with the optional components. If you are upgrading
IBM FileNet Content
Manager in your custom
resource (CR), then make sure that you update all the relevant versions for all of the capabilities
that are in your CR file.

- Business Automation Navigator: navigator_configuration
- FileNet Content Manager: ecm_configuration
- Enterprise Records: ier_configuration
- Content Collector for SAP: iccsap_configuration
- Business Automation Insights: bai_configuration
- Resource Registry: resource_registry_configuration
Plan your upgrade for a time when it is convenient to restrict all user access to content services. When a pod stops, the Content Platform Engine deployment gives the pod some time to finish the existing workloads that are already assigned to the pod. During this time, additional work requests for that pod are rejected. If the workload does not finish within the assigned time, the pod terminates. Unfinished work transitions to another pod later.
The result is the completion of more in-flight operations reducing the amount of rework and thereby, a particular pod might take longer to stop.
During the process of upgrading your container images, you must also perform the standard checks and post upgrade configuration tasks to ensure that your content services environment continues to function as it did before the upgrade.
The custom resource file includes several mandatory configuration parameters. Depending on the previous version of your custom resource YAML file, the upgradeDeployment mode of the script will modify your CR to meet the requirements of the mandatory parameters. For more information, see Upgrading your IBM Cloud Pak deployment from 23.0.2.
About this task
By default, the operator deploys each container by using the corresponding digest for the tag of the operator version that is used to deploy. If you want to override the image digest with a specific image tag, such as applying a limited availability fix, you can specify the image tag in the custom resource (CR).
The following steps assume that you have all content services containers in your environment. If you do not use all of the containers, skip over the steps for the containers that do not apply.
Procedure
What to do next
Continue to configure the other capabilities that are in your CR file, and make sure that you complete the last step Validating the YAML in your custom resource file before you apply the CR to the operator. Apply the modified custom resource file as described in Applying the upgraded custom resource for the upgrade to take place.