[ Bottom of Page | Previous Page | Next Page | Contents ]
The migration requires you to install a V2.1 runtime server and database,
to replace the old versions.
- Choice: do you want to use new computers or reinstall the components
on the same computers?
- The advantages and disadvantages of using or not using new computers
are the same as for the administration server computers.
The differences in the procedures are illustrated in the following scenarios:
- Step 7 Scenario 1: all new computers
- In this scenario you install the V2.1 components on new computers.

You take the following
steps:
- Install new runtime components: Install new runtime servers
and databases on the new computers you have chosen for this purpose. 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 computers where
the runtime servers are going to be.
- Test the configuration: Configure the runtime server
or servers to plug in to the V2.1 administration server, and deploy a couple
of test agents. Test that the configuration is working correctly.
- Redeploy agents: Using all the facilities of V2.1,
redeploy your agents as V2.1 agents, pointing to the new runtime servers.
Use the facilities in the administration server GUI to measure the progress
of the redeployment.
- Optionally maintain V1.1.1 runtime servers for unsupported
platforms: Agents that are on now unsupported platforms, as in the Windows 9x agent in this scenario, can remain attached to their V1.1.1 runtime
servers for as long as you wish. However, if you have no agents on supported
platforms, the runtime servers and its database can be switched off and uninstalled.
See Scenario 6.1: new computers for full details of this procedure.
- Step 7 Scenario 2: same computers
- The second scenario assumes that you have the administration server
and its database on separate computers, and you want to maintain them on those
computers.
Take the following steps:
- Stop the V1.1.1 runtime server:
- Uninstall V1.1.1 runtime server components: Uninstall the runtime server and
its database, dropping the database when requested.
- Upgrade the hardware and operating system: You will
almost certainly want to upgrade the memory of the administration server database's
computer, and maybe the operating system as well.
- Upgrade WebSphere Application Server: None of the versions of WebSphere Application Server that
were supported by V1.1.1 are supported by V2.1. You will need to upgrade WebSphere Application Server on
the runtime server computer. You can use either the bundled prerequisite version
or your own version (see the discussion in the Planning chapter of the IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1). The migration procedure described below
explains when to do this upgrade, but for detailed instructions on how to
upgrade, you must refer to the original documentation for WebSphere Application Server.
- Upgrade DB2: The version of DB2 that was supported
by V1.1.1 (version 7.2.0 with fix pack 7) is not supported by V2.1. You will
need to upgrade DB2 on the runtime server computer. You have two choices:
apply a fix pack to bring DB2 up to the V2.1 supported level (fix pack 10a) or upgrade
to version 8.1.4. If you choose the former, you need only apply the fix pack
to the existing version of DB2; if you decide to upgrade you will need to export the Tivoli License Manager database
or databases involved, and uninstall the old version before installing version
8.1.4 If you decide to migrate to version 8.1.4, you can use either the bundled
prerequisite version or your own version (see the discussion in the Planning
chapter of the IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1). The migration procedure described below explains
when to do this upgrade, but for detailed instructions you must refer to the
original documentation for DB2.
- Install V2.1 runtime server components: Install the V2.1 runtime server and
its database. You must give the V2.1 runtime server the same names as it had in V1.1.1.
- Start V2.1 runtime server: Start the runtime server. It will plug in
to the administration server and download its new catalog and other data. The next time that
an agent connects to the runtime server, the mismatch between its catalog
and the runtime server's catalog causes the new catalog to be downloaded to the agent.
Note:
If both runtime server and database are on the same computer you
follow the same basic procedure, but you can uninstall the old and install
the new components together.
See Scenario 6.2: same computers for full details of this procedure.
Combined scenario: You can also choose to combine
these scenarios, to get the advantages of both. For example, in Step 7, Scenario
1, a new runtime server was created and the agents were redeployed to it,
leaving the old V1.1.1 runtime server supporting only those agents that cannot
be deployed on V2.1 runtime servers. You can now migrate these runtime servers,
without changing the computers on which they run, exactly as described in
Scenario 2:
This option enables you to continue supporting older agents in a way that
when those platforms have all been replaced you can take the runtime server
out of service without disturbing the rest of the environment.
Whichever choice you make, you will end up with new V2.1 runtime servers
and databases, using the required prerequisite software.
When the migration of the server is completed, your V1.1.1 agents will return
to full V1.1.1 functionality using the new server. You can keep this configuration
with no agents migrated for an indefinite period, but during that period you
will not be able to take advantage of the new facilities in the V2.1 runtime server.
Note:
If you have any agents at versions prior to 1.1.1, they will become
inactive.
If you are using the alternative server option at division level, before
migrating the agents belonging to a server, all runtime servers in the same division
must be migrated. If you are using the alternative server option at organization
level, before migrating the agents belonging to a server, all runtime servers in the
same organization must be migrated.
[ Top of Page | Previous Page | Next Page | Contents ]