Upgrading components of License Metric Tool (disconnected scenario)

You can upgrade to License Metric Tool 9.2.37 from all 9.x versions. Upgrade of License Metric Tool consists of upgrading the server, VM Manager Tool, and the disconnected scanner. Upgrading the License Metric Tool server directly to the latest version is possible for 8 versions back. For older versions, additional steps are required. You cannot upgrade between different operating systems.

Before you begin

  • Ensure that no files or directories in the License Metric Tool installation directory are open in an external program. For example, that no log files are open in a text editor.
  • Ensure that no PDF reports are being generated during the server upgrade. Otherwise, the upgrade might fail with error code 41.
  • The following programs were confirmed to interrupt the upgrade of the server. If you use any of these programs, disable it for the period of the upgrade.
    • Arcserve Backup
    • Dynatrace OneAgent
  • Ensure that you provide enough space for the upgrade. For more information, see the following links.

About this task

If you are upgrading from application update earlier than 9.2.29, additional steps are required. For more information, see: Upgrading to the latest version.

9.2.26 Starting from application update 9.2.26, if the local VM Manager Tool does not exist, it is installed during the upgrade of the server. You can continue using the VM Manager Tool that you had previously, or switch to using the local one. For more information, see: VM Manager Tool deployment types and flow of data.

Procedure

  1. Verify whether your version of the database is supported by the new version of the License Metric Tool server. If it is no longer supported, upgrade the database. Ensure that the version of the database to which you are upgrading is supported by your current version of License Metric Tool and the one to which you are upgrading.
  2. Create a back up of the License Metric Tool database, installation registry, and the server files to be able to restore the server if the upgrade fails. For more information, see: Backing up the server.
  3. Download the latest License Metric Tool installer from Passport Advantage. For more information, see: Downloading IBM License Metric Tool 9.2.
  4. Upgrade the License Metric Tool server in interactive or silent mode. During the upgrade of the server, new software catalog and PVU table are uploaded to License Metric Tool.
    • To upgrade the server in interactive mode, perform the following steps.
      1. Extract the installer.
      2. Run one of the following installation files.
        • Linux setup-server-linux-x86_64.sh
        • Windows setup-server-windows-x86_64.bat
      3. Follow the steps in the installation wizard.
      4. When the upgrade is complete, click Done.

        If the upgrade fails, check the logs. For more information, see: Server installation and upgrade logs. You can resume a failed upgrade after you solve the problem. For more information, see: Resuming a stopped or failed upgrade.

    • To upgrade the server in silent mode, perform the following steps.
      1. Extract the installer.
      2. Go to the licenses subfolder and read the license agreements in the following files: LA_<language>, LI_<language>, non_ibm_license, notices.
      3. Edit the upgrade_response.txt file. Set the RSP_LICENSE_ACCEPTED parameter to true.
      4. To start the upgrade, run one of the following commands.
        • Linux ./setup-server-linux-x86_64.sh -i silent -f /response_file_path/upgrade_response.txt
        • Windows setup-server-windows-x86_64.bat -i silent -f response_file_path\upgrade_response.txt
        For response_file_path, enter the absolute path to the response file. For example:
        setup-server-windows-x86_64.bat -i silent -f C:\images\LMT\upgrade_response.txt

        If the upgrade fails, check the logs. For more information, see: Server installation and upgrade logs. You can resume a failed upgrade after you solve the problem. For more information, see: Resuming a stopped or failed upgrade.

  5. If the new version of the VM Manager Tool contains security fixes, fixes of problems that appear in your environment, or new features that you want to use, upgrade the VM Manager Tool to the latest version.
    • 9.2.23 If you use the local VM Manager Tool, it is upgraded automatically during the upgrade of the License Metric Tool server.
    • If you use the disconnected VM Manager Tool, see: Upgrading the disconnected VM Manager Tool.
    To check which type of the VM Manager Tool you have, log in to License Metric Tool, hover over Management, and click VM managers. Then, check the value in the Deployment Type column. Disconnected VM Manager Tool is listed as Distributed.
  6. If the new version of the disconnected scanner contains security fixes, fixes of problems that appear in your environment, or new features that you want to use, upgrade the scanner to the latest version.
  7. To ensure that all changes are processed, run an import. In License Metric Tool, click Management > Data Imports, and click Import Now.
    Important: The first import after the upgrade might last longer because it includes the new software catalog.
  8. If you use Ansible to manage disconnected scanners, update the License Metric Tool playbooks.
    1. Keep your current version of the inventory file.
    2. Download the new License Metric Tool playbooks from the GitHub repository and copy them to the directory in which you store the old playbooks.
    3. Review the inventory file and decide whether you want to use any of the parameters that were added in the new version of the playbooks.
  9. Optional: If you use Ansible to manage disconnected scanners, upgrade Ansible to the latest stable version. For more information, see the Ansible documentation.

Results

To verify that the upgrade was successful, perform the following steps.
  • Log in to License Metric Tool, hover over the Help icon, and click About. If the upgrade is successful, a new version is displayed on the panel.
  • Run an import. If the upgrade is successful, the import finishes without errors.