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.
Before you begin
The custom resource file includes several mandatory configuration parameters. Depending on the version of your custom resource YAML file, you must add these mandatory parameters to the file, or provide specific values for parameters that previously used the default value. For more information about these parameters see Mandatory configuration parameters.
About this task
By default, the operator deploys each container by using the image digests that correspond to the image tags in the following table. If you want to override the image digest with a specific image tag (to apply an interim fix for example), you can specify the image tag in the custom resource (CR).
Configuration parameter | Value |
---|---|
cpe.image.tag | ga-558-p8cpe |
css.image.tag | ga-558-p8css |
cmis.image.tag | ga-306-cmis-la101 |
graphql.image.tag | ga-558-p8cgql |
es.image.tag | ga-3011-es |
tm.image.tag | ga-3011-tm |
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
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 result is the completion of more in-flight operations reducing the amount of rework and thereby, a particular pod might take longer to stop.
- Disable the
CBRdispatcher
as described in the topic Stopping the IBM Content Search Services index dispatcher. - If you have not already done so, make a backup of your databases and environment volumes. See Backing up the data in your FileNet® P8 domain for more information.
- Scale down your deployments before you apply the updated custom resource YAML file. Scale down
the operator first, then your other components.To scale down a specific deployment (for Content Platform Engine, Business Automation Navigator, and Content Search Services):
kubectl scale --replicas=0 deployment my_deployment_name -n my_project_name
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 updated custom resource YAML file as described in Applying the upgraded custom resource.
When the deployments are available, verify the upgrade by using the instructions in Completing and verifying the IBM FileNet Content Manager upgrade.