Preparing for upgrade

Note

This topic is applicable only for a TrueSight Automation Console (on-premises) deployment.

BMC Helix Automation Console (SaaS) is not available for on-premises installation. For details about subscribing to this service, see BMC Helix subscriber information.

Upgrading TrueSight Automation Console requires you to complete these pre-upgrade tasks. You can download the installation files from the BMC Electronic Product Distribution (EPD) site. 

Setting up your upgrade environment

Complete the following tasks to set up your environment:

  • Back up the database.
  • Back up the installation directories of the database and the application. 
  • Back up any trusted certificates that you may be using in your environment by performing the following steps:

    1. On a host where the TrueSight Automation Console application is installed, run the following command to copy exiting certificates:

      cp <install_dir>/application/common/certs/tsvmSslCertificate.crt /opt/<backup_directory>
      cp <install_dir>/application/common/certs/tsvmSslCertificate.key /opt/<backup_directory>
    2. After successfully upgrading the application, run the following command to replace the new certificates (created during the upgrade) with the custom certificates copied earlier. 

      cp /opt/<backup_directory>/tsvmSslCertificate.crt <install_dir>/application/common/certs/
      cp /opt/<backup_directory>/tsvmSslCertificate.key <install_dir>/application/common/certs/
  • Ensure that you remove the local registry container and its mapped location on the host that contains the Docker images for the previous release. 
  • Ensure that the target computers meet the System requirements.
  • Download the installation files.

Preparing to upgrade TrueSight Automation Console

You first extract the latest images and then recreate a local registry with the latest Docker images. You can choose to delete the old registry (that contains the previous version) mapped location from the host either before you upgrade or after the upgrade is complete.  

Note

If deleting after the upgrade, ensure that you have identified the old registry mapped location.

To find out the mapped location, run the docker inspect <Registry-Container-Id> | grep "Source" command before you upgrade to the latest version.

To recreate the repository on a CentOS computer

  1. To remove the local registry, if it exists, run the following commands:

    Stop the registry container
    docker stop registry
    Remove the registry container
    docker rm registry
    Remove the registry image
    docker rmi -f registry
  2. To recreate a local Docker registry, do these:

    1. Download the TSAC<versionNo>-IMAGES-LIN64.zip file from the BMC Electronic Products Distribution (EPD).

    2. Create a directory on the Docker host and extract the TSAC<versionNo>-IMAGES-LIN64.zip into the directory.
      BMC recommends that you use version numbers while creating a directory to identify mapped locations for different versions.  
      For example, /opt/tsac_20_02/dockerrepo
    3. Run the following command to create the local Docker registry.
      In the following command, replace <Directory> with the directory and its complete path that you created in step b. If there are multiple hosts, repeat this step on all the Docker hosts.

      docker run -d \ 
        -p 5000:5000 \ 
        --restart=always \ 
        --name registry \ 
        -v <Directory>:/var/lib/registry \ 
        registry:2 

      For example,

      docker run -d \
        -p 5000:5000 \
        --restart=always \
        --name registry \
        -v /opt/tsac/dockerrepo:/var/lib/registry \
        registry:2

      This command creates a local Docker registry on port 5000.

To recreate the repository on an RHEL computer

  1. To remove the local registry, if it exists, run the following commands:

    Stop the registry container
    docker stop registry
    Remove the registry container
    docker rm registry
    Remove the registry image
    docker rmi -f registry
  2. Create a local Docker registry to manage Docker images, as follows:

    1. Download the TSAC<versionNo>-IMAGES-LIN64.zip file from the BMC Electronic Products Distribution (EPD).

    2. Create a directory on the Docker host (for example, /opt/tsac_<version>/dockerrepo) and extract the TSAC<versionNo>-IMAGES-LIN64.zip into the directory.
    3. Run the following command to create the local Docker registry. Replace <Directory> with the complete path of the directory that you created in step b. If there are multiple Docker hosts, repeat this step on all hosts.

      docker run -d \
        -p 5000:5000 \
        --restart=always \
        --name registry \
        -v <Directory>:/var/lib/registry \
        registry:2

      For example,

      docker run -d \
        -p 5000:5000 \
        --restart=always \
        --name registry \
        -v /opt/tsac/dockerrepo:/var/lib/registry \
        registry:2

      This command creates a local Docker registry on port 5000.

Where to go from here?

After completing the pre-upgrade tasks, you can now start Performing the upgrade

Was this page helpful? Yes No Submitting... Thank you

Comments