Using the upgrade configuration utility


Use the upgrade configuration utility to simplify the process of updating the infra.configdeployment.config, and secrets.txt files while upgrading from the previous versions (23.1.02 or 23.2.02) of BMC Helix IT Operations Management (BMC Helix ITOM) to the current version. The utility performs the following tasks:

  • It picks the values from the latest successful deployment of BMC Helix ITOMto configure the infra.config, deployment.config, and secrets.txt files. 
    You need not manually configure any parameter that you had configured previously.
  • It lists the infra.config file parameters whose names have been modified in the current release and updates their values automatically.
  • It lists the infra.config file parameters that were added in the current release. You must manually enter the values for the new configuration parameters in the infra.config file.


To run the upgrade configuration utility

  1. Download the upgrade configuration utility from Electronic Product Distribution (EPD).
    The upgrade configuration utility is a part of the deployment manager. For more information, see Downloading-the-deployment-manager.

  2. Go to helix-on-prem-deployment-manager/utilities/upgrade.
  3. If upgrade-configuration.sh does not have execute permission, run the following command to provide execution permission:

    $chmod a+x ../helix-on-prem-deployment-manager/utilities/upgrade/upgrade-configuration.sh

  4. Run the upgrade configuration utility:

    ./upgrade-configuration.sh <namespace>

    <namespace> is the namespace that you used to deploy BMC Helix ITOM.

    You will get a confirmation message after the utility has completed updating the 
    infra.config, deployment.config, and secrets.txt files.

    The utility 
    lists the infra.config file parameters that were added in the current release. You must manually enter the values for the new configuration parameters in the infra.config file.
    For more information about the 
    infra.config, and deployment.config files, see Configuration-file-settings. For more information about secrets.txt file, see Preparing-for-password-encryption.

    Important

    The utility only picks the values from the latest successful deployment of BMC Helix ITOM. We recommend that you to review the infra.config, deployment.config, and secrets.txt files before starting the upgrade. 

    If you set the value of the parameters CUSTOM_CA_SIGNED_CERT_IN_USE to false and MONITOR to yes, you must name the public CA certificate file (full chain) as public_cacert.pem and copy it to the commons/certs directory; that is, commons/certs/public_cacert.pem.

Where to go from here

Back to process

Complete the other prerequisites tasks listed on the Preparing-for-upgrade page.

Next task



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*