[ Bottom of Page | Previous Page | Next Page | Contents ]
The prerequisites for this migration are as follows:
- Servers and databases must be at V1.1.1: All administration
or runtime servers or databases must be upgraded to V1.1.1 before you start the migration.
Instructions for this are provided in IBM Tivoli License Manager: System Administrator's Guide, version 1.1.1.
- Agents must be at version 1.1.1: If any of your
agents are at version 1.1 you must upgrade them to V1.1.1 either before, or
as part of the migration (see the instructions for agent migration in IBM Tivoli License Manager: System Administrator's Guide, version 1.1.1) , or redeploy them after the migration as V2.1 agents
(see the instructions for agent deployment in IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1).
Note:
Agents prior to version 1.1
are not supported in any way during or after the migration.
- Agent kernels must be fixed: If you have any agents
with a version number less than 1.1.1.20, you must use the kfixer utility to resolve a problem with the agent kernel that can occur
when upgrading agents. This problem applies to almost all agent platforms.
To obtain the kfixer utility you need to first
obtain interim fix 1.1.1-TLM-0005 from the Tivoli License Manager software
support Web site (see Contacting software support) for details of
how to access the site). The utility has its own README file which describes
how and when to use it.
- You must plan for V2.1: You must read the Planning
chapter of IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1 very carefully, to determine the following:
- The new prerequisites for the components and options
- The new functionality which is available
- The changed advice about designing the product
infrastructure and topology
Our suggestion is that you plan for V2.1 as if it was a new product,
determining the infrastructure and topology that is best going to serve your
requirements. Only when this phase is complete should you start thinking how
to migrate your existing environment to the new one.
Finally, you should
keep in mind that V2.1 is a much more complex product that V1.1.1. Thus, in
your planning for V2.1, you should consider as essential the maximizing of
network speeds and computer processing capacity of the computers where components
are to be installed.
- Administration server database operating system cannot
be changed: The operating system under which the administration server database runs must not be
changed during the migration. Thus, an administration server database installed
on an operating system platform no longer supported, (AIX 4.3.3 or Windows NT), cannot be migrated. The operating systems of databases installed
on other platforms can be upgraded, but cannot be changed. For example, you
cannot change from a database on Windows 2000 to a database on HP/UX, nor Windows 2003.
[ Top of Page | Previous Page | Next Page | Contents ]