Upgrading IBM Automation Decision Services

If you installed the previous version of Automation Decision Services, you have now the opportunity to move to the new version.

About this task

The following diagram highlights the components that are installed when you install a decisions_ads pattern, along with the optional components. If you are upgrading Automation Decision Services 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.

Note: The custom resource configuration sections for these components use the following names:

• Business Automation Navigator: navigator_configuration
• Automation Decision Services: ads_configuration
• Application Engine: application_engine_configuration
• Business Automation Insights: bai_configuration
• Resource Registry: resource_registry_configuration
• Business Automation Studio: bastudio_configuration

After making changes with the cp4a-deployment.sh -m upgradeDeployment command, check the configuration parameters.

1. If your Cloud Pak for Business Automation deployment in 24.0.0 uses an external database that is not PostgreSQL, then you need edit the custom resource file to include your external PostgreSQL database name. By default, the deployment script generates EDB Postgres configuration. You need to change it to external PostgreSQL.
   • For nonvault deployment.
     • Update the following sections in the custom resource file for Decision Designer.

       dc_ads_designer_datasource:
         dc_use_postgres: false
         dc_database_type: postgresql
         database_servername: postgres.xyz.com  # Your external PostgreSQL server
         database_name: adsdesignerdb
         database_port: "5432"
         current_schema: ads
         ssl_enabled: true
         ssl_mode: verify-ca
         database_ssl_secret_name: 'ibm-cp4ba-postgresdb-ssl-secret'
         database_instance_secret: ibm-ads-designer-database

     • Update the following sections in the custom resource file for the decision runtime.

       dc_ads_runtime_datasource:
         dc_use_postgres: false
         dc_database_type: postgresql
         database_servername: postgres.xyz.com  # Your external PostgreSQL server
         database_name: adsruntimedb
         database_port: "5432"
         current_schema: ads
         ssl_enabled: true
         ssl_mode: verify-ca
         database_ssl_secret_name: 'ibm-cp4ba-postgresdb-ssl-secret'
         database_instance_secret: ibm-ads-runtime-database

       where postgres.xyz.com is the name of your external PostgreSQL database and ibm-cp4ba-postgresdb-ssl-secret is the PostgreSQL SSL secret. For more information, see Option 3: Upgrading a CP4BA deployment that uses an external database that is not PostgreSQL.
   • For vault deployment.
     • Update the following sections in the custom resource file for Decision Designer.

       dc_ads_designer_datasource:
         dc_use_postgres: false
         dc_database_type: postgresql
         database_servername: postgres.xyz.com  # Your external PostgreSQL server
         database_name: adsdesignerdb
         database_port: "5432"
         current_schema: ads
         ssl_enabled: true
         ssl_mode: verify-ca
         database_ssl_secret_name: 'ibm-cp4ba-postgresdb-ssl-secret'

     • Update the following sections in the custom resource file for the decision runtime.

       dc_ads_runtime_datasource:
         dc_use_postgres: false
         dc_database_type: postgresql
         database_servername: postgres.xyz.com  # Your external PostgreSQL server
         database_name: adsruntimedb
         database_port: "5432"
         current_schema: ads
         ssl_enabled: true
         ssl_mode: verify-ca
         database_ssl_secret_name: 'ibm-cp4ba-postgresdb-ssl-secret'

       where postgres.xyz.com is the name of your external PostgreSQL database and ibm-cp4ba-postgresdb-ssl-secret is the PostgreSQL SSL secret. For more information, see Option 3: Upgrading a CP4BA deployment that uses an external database that is not PostgreSQL.
2. Check the following datasource_configuration parameters under the Decision Designer and decision runtime sections in the CR:
   1. Check that the dc_use_postgres parameters for Decision Designer and the decision runtime are set to false.
   2. Check the rest of the datasource_configuration parameters that are listed in Table 2 in Decision Designer parameters and Decision runtime parameters.

      Verify the values that you entered in the upgrade script correspond to the ones in your external PostgreSQL database.