[ Bottom of Page | Previous Page | Next Page | Contents ]
If you have the catalog manager from a prior version of Tivoli License Manager already
installed on a computer, it must be uninstalled before you attempt to install
the new catalog manager. If the catalog manager was installed on the same
computer as the administration server or database, it will have already been
uninstalled, as part of the migration procedure for these other components.
Note:
You do not need to install a new catalog manager on the same computer
as the old catalog manager. But in all cases, the old catalog manager must
be uninstalled, as it does not work with the V2.1 catalog.
The procedure is as follows:
- Close the V1.1.1 catalog manager and then run the uninstall wizard for it.
Instructions for uninstalling the catalog manager for versions 1.x of Tivoli License Manager are
given in IBM Tivoli License Manager: System Administrator's Guide, version 1.1.1.
- Delete the installation directory: If the catalog
manager was the only Tivoli License Manager component installed on the computer, delete
the installation directory in which V1.1.1 was installed.
-
Delete the registry keys: The V1.1.1 uninstaller
does not remove the V1.1.1 registry keys. If the catalog manager was the only Tivoli License Manager component
installed on the computer, 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:
- Backup the registry, using the following commands:
cp -r /etc/objrepos /etc/objrepos_backup
cp -r /usr/lib/objrepos /usr/lib/objrepos_backup
- 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.
- 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:
- Delete the registry files, which may have become corrupt, using the following
commands:
rm -rf /etc/objrepos
rm -rf /usr/lib/objrepos
- 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:
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\Catalog Manager]
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.
- Install the V2.1 catalog manager: If you want to
use the new V2.1 catalog manager from this computer, install it, as described
in IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1, on a computer with access to the V2.1 administration
server database. When requested, identify the host name of the computer where
the administration server database is installed.
[ Top of Page | Previous Page | Next Page | Contents ]