IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


Scenario 6.1: new computers

To migrate a runtime server and its database, follow this procedure:

  1. Install new V2.1 runtime components: Install the new V2.1 runtime server and database on the new computers you have chosen for this purpose. This will be the permanent home for your runtime server components. Either before or during this process you install the prerequisite version of DB2 on all computers, and the prerequisite version of WebSphere Application Server on the computer where the runtime server is going to be.

    You should use a custom installation of each, starting with the database component, as the custom installation allows you to change the installation default values. You must give each runtime server the same name as the runtime server it is to replace.

    See the instructions in IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1.

  2. Test the configuration: Configure the V2.1 runtime server to connect to the V2.1 administration server and deploy a few agents. Test that the V2.1 runtime server is working correctly and that you have configured it correctly, for example, for SSL.

    See the instructions in IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1.

  3. Redeploy agents: Using any of the V2.1 agent deployment methods, deploy the V2.1 agent on all computers where you have a V1.1.1 agent that has a platform supported in V2.1. Ensure that their deployment parameters include the new host name of the V2.1 runtime server and any other parameters that have changed.
  4. Optionally maintain the V1.1.1 runtime components: While the runtime server is still supporting agents that you cannot redeploy onto V2.1, you can retain it as a V1.1.1 runtime server. However, you may wish to migrate it to V2.1 using the procedures described in Scenario 6.2: same computers.
  5. Eventually uninstall the V1.1.1 runtime server components: When the V1.1.1 runtime server has no more agents registered with it, you can uninstall the V1.1.1 runtime server components from the computers where they are installed, dropping the V1.1.1 runtime server database.
    Attention: Each time you run the uninstall wizard on the computers where the Tivoli License Manager components are installed, it will ask you if you want to save the configuration files. As none of these are migrated, you may always answer "No".
  6. Clean up the V1.1.1 runtime server computer: If you intend to re-use the computers where the V1.1.1 runtime server and runtime server database was installed, without deleting the file structures, you should perform the following clean-up activities:
    1. Delete the installation directory: On each of the computers involved, delete the installation directory in which V1.1.1 was installed.
    2. Delete the registry keys: The V1.1.1 uninstaller does not remove the V1.1.1 registry keys. It is necessary to remove the keys in order to successfully install V2.1. The process requires you to modify the computer's registry. This is a process that must be undertaken with care, as it is possible to render the computer unusable if the files become corrupt. The process differs, depending on the platform:
      AIX
      The process requires the following steps:
      1. Backup the registry, using the following commands:
         cp -r /etc/objrepos  /etc/objrepos_backup
         cp -r /usr/lib/objrepos /usr/lib/objrepos_backup
        
      2. Check that the registry keys exist, by issuing the following commands:
        export ODMDIR=/usr/lib/objrepos 
        
        odmget -q "name='Tivoli License Manager'" lpp 
        odmget -q "lpp_name='Tivoli License Manager'" product 
        
        If the registry keys exist the STDOUT will list details relating to them. If they do not exist nothing will be written to STDOUT.
      3. If the registry keys exist, delete them, using the following commands:
        export ODMDIR=/usr/lib/objrepos 
        
        odmdelete -o lpp -q "name='Tivoli License Manager'"
        odmdelete -o product -q "lpp_name='Tivoli License Manager'"

        If you have any concern that something has gone wrong with the ODM commands, you should take the following steps:

        1. Delete the registry files, which may have become corrupt, using the following commands:
          rm -rf /etc/objrepos
          rm -rf /usr/lib/objrepos
          
        2. Restore the backed up files, using the following commands:
          mv /etc/objrepos_backup /etc/objrepos
          mv /usr/lib/objrepos_backup /usr/lib/objrepos
          
      Windows

      Delete the following keys using the registry editor on your computer:

      Runtime server

      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM]
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM]
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM\1.1.1]
      "Install Location"="$P(SLMRoot.installLocation)"
      "RegCompany"="IBM"
      "DisplayVersion"="1.1.1"
      "DisplayName"="IBM Tivoli License Manager"
      "VersionMajor"="1"
      "VersionMinor"="1"
      "VersionMaintenance"="1"
      
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM\1.1.1\Features]
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM\1.1.1\Features\Runtime Server]
      "Customer Name"="$W(runtimeConfig.customerName)"
      "Runtime Server Name"="$W(runtimeConfig.runtimeName)"
      "Administrator Server Name"="$W(runtimeToAdmin.adminHost)"
      "Administrator Server Port"="$W(runtimeToAdmin.port)"

      Runtime server database

      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM]
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM]
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM\1.1.1]
      "Install Location"="$P(SLMRoot.installLocation)"
      "RegCompany"="IBM"
      "DisplayVersion"="1.1.1"
      "DisplayName"="IBM Tivoli License Manager"
      "VersionMajor"="1"
      "VersionMinor"="1"
      "VersionMaintenance"="1"
      
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM\1.1.1\Features]
      [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\TLM\1.1.1\Features\Runtime Database]
      Note:
      The fact that the V1.1.1 keys are different from the V2.1 keys means that if you attempt to install V1.1.1 on top of an existing V2.1 installation, the installation will not give an error, but you will overwrite some V2.1 files, and V2.1 will become corrupted and unusable. Thus, you are recommended at this point to place all V1.1.1 installation CDs in secure storage and delete any CD images that you may have, to avoid any risk that they are used in error.

[ Top of Page | Previous Page | Next Page | Contents ]