[ Bottom of Page | Previous Page | Next Page | Contents ]
In addition to the steps indicated in the previous section, there are some
other tasks that you might or might not want to perform as part of the migration.
- Clean up before migration
- Effects of migration describes the effects that the migration will
have on your data. In this section are several indications of clean-up activities
that you are advised to do before starting the migration.
- Change topology
- As part of the migration, information about your existing organizations,
divisions, runtime servers and agents are all migrated to the new database. Provided
that you subsequently install the same number of new runtime servers with the same names
on the same computers, you should not need to change any of these details.
However, you may like to take this opportunity to consider changing the topology
of your Tivoli License Manager environment. If you want to reduce the workload of a runtime server by
having it share its agents with an extra server, you will need to redeploy
all of the agents that should now be registered with the new runtime server. If, however,
you want to do the opposite, and merge the agents of two runtime servers onto one, you
should redeploy the agents registered with the runtime server that is to be removed.
These activities should be performed after the migration.
- Retain users
- Decide whether you want to retain the V1.1.1 user authentication
data for use in V2.1. If you do, you need to save the file containing the
authentication data and copy it into the V2.1 directory structure, changing
the V2.1 default authentication method so that the data can be used. If you
intend to use LDAP authentication in V2.1, there is no point in doing this
step, as changing to LDAP requires you to create new accounts. The procedure
is described in detail as part of the main migration procedure.
- Print the configuration files
- Many of the configuration parameters of V1.1.1 have changed meaning or
value in V2.1. For this reason these parameters cannot be migrated. You should
consider printing the configuration files, so that where you want to restore
values that you used in V1.1.1 you can do so.
[ Top of Page | Previous Page | Next Page | Contents ]