IBM Tivoli Software IBM Tivoli Software

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


Migrate the agents by self-update

If you so choose, your agents need not be reregistered and will be upgraded automatically. During the period while those agents are without their runtime server they will fail to obtain a license (if they need one) or pass license-related information when they try to contact the uninstalled runtime server. A license for the application to run would then be granted or not depending on the setting of the Run offline parameter in the application's license entitlement details. If Run offline is enabled, a license will be granted. In addition, an error will be logged in the agent's trace file, if the trace is enabled.

To enable the automatic upgrade of the agent you must do the following:

  1. Ensure that the new runtime servers you create have exactly the same organization, name, URL and access port as the old runtime servers.
  2. Prepare a schedule for upgrading the agents. The agent upgrade occurs when the agents first contact an upgraded runtime server where the updateAgentEnabled option in the agent configuration file is enabled (see the appendix on the agent in IBM Tivoli License Manager: Planning, Installation, and Configuration, version 2.1). The updateAgentEnabled option is disabled by default, so you should enable it for each runtime server in turn. After you have ascertained that all agents have upgraded, you can disable this option. Use the Agents option in the Manage Components section of the administration server Web user interface to ascertain if the agent has been upgraded. Upgraded agents have a version number of 2.1.0.0.
  3. If you deployed agents in Tivoli License Manager version 1.1 using non-ASCII characters in the agent name, you must redeploy these agents after upgrading their runtime server, otherwise they will not be recognized by it. This is because those non-ASCII characters were in the ISO code set that was supported in version 1.1, while the UTF-8 code set that is supported from V1.1.1 onwards, does not recognize these characters.

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