IBM Tivoli Software IBM Tivoli Software

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


Scenario 4.1: all new computers

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

    If both components are going to be on the same computer you can use the typical installation of the administration server components, which installs them applying default values. If the components are to be installed on separate computers, run a custom installation of each, starting with the database component. You may wish in all cases to use a custom installation as it allows you to change the installation default values.

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

  2. Test the configuration: Install a V2.1 runtime server and database and deploy a few agents. Test that the V2.1 administration server is working correctly and that you have configured it correctly, for example, for SSL. The runtime server can either be a production runtime server that you will want to use in the completed configuration, or it can be a test runtime server that you will uninstall after the testing is completed.

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

  3. Log on to V2.1 administration server computer: Log on to the computer where the V2.1 administration server is installed as Administrator (Windows) or root (AIX).
  4. Stop the V2.1 administration server Use the following command:
    AIX:
    ./srvstop
    Windows:
    srvstop
  5. Log on to V1.1.1 administration server computer: Log on to the computer where the V1.1.1 administration server is installed as Administrator (Windows) or root (AIX).
  6. Stop the V1.1.1 administration server computer: Use the following command:
    AIX:
    ./srvstop
    Windows:
    srvstop
  7. Log on to the V2.1 administration server database computer: Log on to the V2.1 administration server database computer as the DB2 administration user (Windows: default is db2admin) or the DB2 instance owner (AIX: default is db2inst1).
  8. Drop the V2.1 administration server database: Use the following command at the DB2 command line:

    db2 drop database tlma

    Do not uninstall the component.

  9. Uncatalog the V2.1 administration server database: Use the following command at the DB2 command line:

    db2 uncatalog database tlma

    There is no need to uncatalog the node.

  10. Log on to the V1.1.1 administration server database computer:
    AIX:
    The DB2 instance owner (default is db2inst1).
    Windows:
    A user with Administrator privileges.
  11. 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.
  12. Migrate the V1.1.1 administration server database: On the V1.1.1 administration server database computer, migrate the administration server database as follows:
    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:
      The 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.
  13. Copy the migrated database: Copy the migrated V1.1.1 database to the computer where the V2.1 administration server database is installed, using the DB2 backup or restore utilities or the DB2 move command. the receiving database should be empty, as you dropped it in step 8.
  14. Catalog the V2.1 administration server database: Use the following command at the DB2 command line:

    db2 catalog database tlma as tlmadb at node tlmanodea

  15. Choose how to attach the runtime servers: You have two alternatives for attaching the V1.1.1 runtime servers, as follows:
    Reconfigure runtime servers:
    Change the V1.1.1 runtime server's communications configuration files to point to the new V2.1 administration server. The procedure is as follows, and must be repeated on all runtime servers:
    1. Log on to the V1.1.1 runtime server computer as Administrator (Windows) or root (AIX).
    2. Edit the scp.properties file in the following directory:
      <INSTALL_DIR>\runtime\conf
    3. Change the server parameter, and, if necessary the port parameter, to point to the V2.1 administration server. If there is a proxy server between the V2.1 administration server and the V1.1.1 runtime server, you should also change the proxy server parameters.
    4. Stop the V1.1.1 runtime server. Use the following command:
      AIX:
      ./srvstop
      Windows:
      srvstop
    5. Restart the V1.1.1 runtime server. Use the following command:
      AIX:
      ./srvstart
      Windows:
      srvstart
    Recycle V2.1 administration server's host name
    Request your network administrator to rename the V2.1 administration server with the same host name as the V1.1.1 administration server.
  16. 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 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 recommended 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: Using the srvstart command, start the V2.1 administration server.
    2. Create the accounts: Using the V2.1 administration server GUI, create the new accounts to allow your users to access Tivoli License Manager.
  17. Import IBM Software Catalog: Using either the catalog manager or the impcat command, import the V2.1 IBM Software Catalog that you made a copy of in step 5 of 1. Getting started.
  18. Clean up database: If, in Plan to migrate to V2.1, you have identified any changes to make to the V2.1 administration server databaseafter migration, you should implement them now.
  19. Clean up the V1.1.1 administration server computers: If you intend to re-use the computer where the V1.1.1 administration server or the V1.1.1 administration server database were installed, without deleting the computer's file structures, you should perform the following clean-up activities on each computer:
    1. Uninstall the V1.1.1 administration server components: Following the instructions in IBM Tivoli License Manager: System Administrator's Guide, version 1.1.1, uninstall the administration server and the administration server database. You must also uninstall any runtime server or database components, or the catalog manager, if they are installed on the same computer, in parallel.
    2. Delete the installation directory: On each of the computers involved, 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.
    3. 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.

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