IBM Tivoli Software IBM Tivoli Software

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


Scenario 4.2: same computers

The following scenario assumes that the administration server and the administration server database are installed on the same computer. In the scenario this computer will be called the "administration" computer. At the end of the scenario you will find an explanation of the difference in the procedures if they are installed on separate computers (Scenario 4.2: same computers; where the server and database are on separate computers).

  1. Log on to V1.1.1 administration computer: Log on to the computer where the V1.1.1 administration server and database are installed, as Administrator (Windows) or root (AIX).
  2. Stop the V1.1.1 administration server Use the following command:
    AIX:
    ./srvstop
    Windows:
    srvstop
  3. Uninstall the V1.1.1 administration server and the administration server database: You must also uninstall any V1.1.1 runtime server or database components, or the V1.1.1 catalog manager, if they are installed on the same computer, in parallel.
    Attention: Do not drop the databases. The instructions in IBM Tivoli License Manager: System Administrator's Guide, version 1.1.1, for uninstalling the V1.1.1 administration server database, include how to drop the database. These instructions must be ignored.
    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".
  4. Delete the installation directory: As you have uninstalled all Tivoli License Manager components, you can now delete the installation directory in which V1.1.1 was installed, making sure that any files that you copied following earlier steps in this procedure are outside the installation directory structure. This step will ensure that V2.1 has a clean environment in which it will be installed. Do not delete the DB2 install directory.
  5. 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:

    Administration 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\Administrator Server]

    Administration 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\Administrator 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.
  6. On AIX, change user on the V1.1.1 administration computer: If the V1.1.1 administration server and database are on AIX, change user to the DB2 instance owner (default is db2inst1).
  7. Backup the V1.1.1 administration server database: Backup the V1.1.1 administration server database and place the backup in a directory outside the DB2 installation tree (on AIX, outside the home directory of the DB2 instance owner. It can be recovered from here, if necessary.
  8. Migrate the V1.1.1 administration server database: On the V1.1.1 administration server database computer, migrate the administration server database as follows:
    Note:
    This step can be left until after DB2 has been upgraded, if you prefer.
    1. Open a DB2 command line window.
    2. From within the window, change directory to the directory where you copied the files in step 2 of 3. Prepare the components:
      AIX:
      The home directory of the DB2 instance owner (for example, /home/db2inst1).
      Windows:
      A temporary directory.
    3. Run the migration tool as follows:
      AIX:
      . ./migration_111_21.sh
      Windows
      migration_111_21.bat
      Messages indicating success or failure will be written to a log file called migration_111_21.log, saved in the directory from which you are running the tool.
      Note:
      The migration tool commences with a backup that allows it to restore the database should there be any problems. If that backup fails on AIX, one possible reason might be that the database is large, and the environment is not enabled to permit the creation of large files. The following are steps that may be necessary to allow such files to be written:
      1. Issue the command smitty fs to check the fileset. Set the fileset attribute Large Files Enabled to true.
      2. Issue the command ulimit -a to check if there are any limits on file sizes for the DB2 instance owner. To set the file size limit to Unlimited, issue the command chuser fsize=-1 <DB2_Instance_Owner>
      3. Rerun the migration.
  9. Backup the migrated administration server database: This is the backup that you will restore to become the new database.
  10. Drop the migrated administration server database: Use the following command at the DB2 command line:

    db2 drop database tlma

  11. Uncatalog the migrated administration server database: Use the following command at the DB2 command line:

    db2 uncatalog database tlma

    There is no need to uncatalog the node.
  12. Upgrade DB2 and WebSphere Application Server, and optionally upgrade operating systems: If you have been using V1.1.1 on the administration computer with the supported prerequisite versions of DB2 and WebSphere Application Server, you will now need to upgrade them, as the V1.1.1 prerequisites are not supported in V2.1.

    While you are doing this, you may want to take the opportunity of upgrading the computer's operating system.

    V2.1 comes bundled with version 8.1.4 of DB2 and version 5.1 of WebSphere Application Server (see IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1, for full details). These bundled versions only perform fresh installs, so you must first uninstall the old version before using the bundled prerequisites.

    Perform the following steps:

    1. Uninstall WebSphere Application Server. You do not need to install a fresh version of WebSphere Application Server, as it will be installed automatically when you install the V2.1 administration server
      • If you plan to upgrade DB2 from 7.0.2 to 8.1.4, or upgrade the operating system, or both, perform the following steps:
        1. Uninstall DB2
        2. Optionally upgrade the operating system. If the upgrade requires that the disk is reformatted, copy the backup of the database to a remote location before starting.
        3. You do not need to install a fresh version of DB2 or , as it will be installed automatically when you install the V2.1 administration server.
      • If, on the other hand, you plan to stay with version 7.0, on the same computer, with the same operating system, you should just install fix pack 10a

    If you do not wish to use the bundled prerequisites you should uninstall DB2 and WebSphere Application Server and then make fresh installs using your own versions of them.

  13. Install the V2.1 administration server and database: On the administration computer install the V2.1 administration server and administration server database components, as described in IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1. You can optionally also install one or other of the prerequisite software items.

    You can use the typical installation of the administration server components, which installs them applying default values. Alternatively, you may prefer to use a custom installation as it allows you to change the installation default values.

  14. Drop the V2.1 administration server database that you have just installed: Use the following command at the DB2 command line:

    db2 drop database tlma

  15. Uncatalog the V2.1 administration server database that you have just installed: Use the following command at the DB2 command line:

    db2 uncatalog database tlma

    There is no need to uncatalog the node.
  16. Restore the migrated database: Restore the migrated database from the backup you took in step 9.
  17. Catalog the restored migrated administration server database: Use the following command at the DB2 command line:

    db2 catalog database tlma as tlmadb at node tlmanodea

    There is no need to catalog the node as you did not uncatalog it.
  18. Create user access:
    Optionally import the authentication file from V1.1.1:
    If you want to use the V1.1.1 authentication information in V2.1, and you saved the password file (see step 5, follow these steps:
    1. Change default authentication method: Change the authentication method from the default value of "DB" to "XML" (see IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1 for a full description of how to do this.
    2. Restore the authentication file: Locate the file psw.xml in the following directory on the V2.1 administration server computer:
      <INSTALL_DIR>\admin\SLM_Admin_Application.ear\slm_admin.war\WEB-INF\conf\users
      Replace it with the file backed up in step 5.

      This enables you to use the user account information.

    3. Optionally set a more secure authentication method: You are advised to change the authentication method from "XML" to "DB", as this option is more secure. If you do make this change, you will have to create new passwords for your users in the V2.1 administration server GUI, after the migration is complete.
    4. Start the V2.1 administration server: Use the following command:
      AIX:
      ./srvstart
      Windows:
      srvstart
    5. Optionally reset user passwords: If you have changed the authentication method to "DB", you must log on as "tlmroot" with password "system" to the V2.1 administration server and reset all of the user passwords, including "tlmroot".
    Create new accounts:
    If you do not want to use the V1.1.1 authentication information in V2.1, or you want to implement LDAP authentication in V2.1, you will need to do the following:
    1. Start the V2.1 administration server: Use the following command:
      AIX:
      ./srvstart
      Windows:
      srvstart
    2. Create the accounts: Using the GUI, create the new accounts to allow your users to access Tivoli License Manager.
  19. Import IBM Software Catalog: Using either the V2.1 catalog manager or the V2.1 impcat command, import the V2.1 IBM Software Catalog that you made a copy of in step 5.
  20. Clean up database: If you have identified any changes to make to the V2.1 administration server database in Plan to migrate to V2.1, after migration, you should implement them now.
Scenario 4.2: same computers; where the server and database are on separate computers

If the V1.1.1 administration server and V1.1.1 administration server database are installed on different computers, follow the scenario 4.2 procedure, with these differences:


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