Upgrading your CP4BA deployment version from 23.0.2
You can upgrade the version of the Cloud Pak for Business Automation deployment from the command line or in the OpenShift Container Platform console.
Before you begin
When you ran the cp4a-deployment.sh
script in
the upgradeOperator
mode, the script displayed the commands under Next Actions to
continue with the upgrade. You can run the commands on your cluster. The commands in the
Procedure
section are examples.
About this task
The upgradeDeployment
mode of the cp4a-deployment.sh script
takes the following actions:
- Updates the release version (appVersion) to 24.0.0.
- Creates a property file with the name "cp4ba_upgrade.property" in the <cert-kubernetes>/scripts/cp4ba-upgrade/project/<project_name> folder.
- Disables the sc_content_initialization and sc_content_verification parameters for FileNet Content Manager.
- Removes the initialize_configuration and verify_configuration parameters.
- Sets the save-points for the recovery_path under the
bai_configuration
section of the custom resource. - If the CP4BA deployment includes either Content, Workflow Authoring, or Document Processing patterns, then it stops the CSS/CPE/ICN services.
- If the CP4BA deployment includes Workflow Authoring, and the connection_point_name is not in the custom resource, it is added under workflow_authoring_configuration.case.tos_list.
- Removes all the image tags from the new version of the custom resource.
- If in the existing 23.0.2 deployment, the
shared_configuration.sc_egress_configuration.sc_restricted_internet_access
parameter is set tofalse
in the custom resource, then do not change the value totrue
before you complete the upgrade to 24.0.0. You can enable the restricted internet access post upgrade.Note: If you have already set the shared_configuration.sc_egress_configuration.sc_restricted_internet_access totrue
in the existing 23.0.2 deployment, then you do not need to change the value. You can continue with the upgrading tasks.
Procedure
What to do next
- Review the file that is generated. Note: If your deployment includes Business Automation Insights as an optional component, then the
cp4a-deployment.sh
script creates Business Automation Insights savepoints during the upgrade. Arecovery_path
parameter with the location of the savepoints is added to the generated custom resource in different sections under thebai_configuration
. After the upgrade is complete, you need to remove all the instances of therecovery_path
parameter from the custom resource.cert-kubernetes/scripts/cp4ba-upgrade/project/<project_name>/custom_resource/icp4acluster.yaml
The file is a copy of your CP4BA deployment CR that the script modified for the upgrade. It is now up to you to make further modifications that it might need before you apply the CR.
Note: A back up of the deployment CR is located in the cert-kubernetes/scripts/cp4ba-upgrade/project/<project_name>/custom_resource/backup folder. - If you use custom JDBC drivers, follow the steps in Preparing customized versions of JDBC drivers and ICCSAP libraries. These instructions tell you how to host the files for use in CP4BA and how
to update the CR. You might also want to check with your database vendor to make sure that you are
using the best driver version for your database. Note: Don't apply the CP4BA CR changes until that step in the upgrade process.
- If in the existing 23.0.2 deployment, the
shared_configuration.sc_egress_configuration.sc_restricted_internet_access
parameter is set tofalse
in the custom resource, then do not change the value totrue
before you complete the upgrade to 24.0.0. If you want to change the setting after the upgrade you can. For more information, see Configuring cluster security. - New configuration and tuning parameters are available in 24.0.0. For more information, see Tuning performance.
- Go to and complete the steps in Updating the custom resource for each capability in your deployment.