High Availability Scenarios With IBM Tivoli Workload Scheduler And IBM Tivoli Framework

Installing the Tivoli TMR (or Tivoli server) must be done on all nodes in the cluster; if there are two nodes in the cluster, then two IBM Tivoli Workload Scheduling installations must occur. This is best done after the HACMP software is up and running, so you can install the TMR over the same intended HACMP TCP/IP Service address.

Patching the Tivoli TMR software

In contrast to the frequent patching of many TMR production environments, it is recommended that you patch your TMR to the latest code during the initial installation and then leave the TMR alone from there. Since IBM Tivoli Workload Scheduling uses the TMR solely for authentication, patching of the TMR rarely provides added benefits to the IBM Tivoli Workload Scheduling/Standalone TMR configuration.

TMR versus Managed Node installation

Tivoli recommends that the TMR used to facilitate the connection of the JSC to the IBM Tivoli Workload Scheduling engine be configured as a standalone TMR, for the following reasons:

• As mentioned, the TMR associated with IBM Tivoli Workload Scheduling rarely needs maintenance applied to it. Generally speaking, this has not proven to be the case for Framework infrastructures that are supporting other applications such as monitoring and software distribution.

  Having the TMR associated with IBM Tivoli Workload Scheduling separate allows for the mission-critical IBM Tivoli Workload Scheduling application to be isolated from the risks and downtime associated with patching which may be necessary for other Framework applications, but is not necessary for IBM Tivoli Workload Scheduling.

• The Framework is a critical component to the JSC GUI. Unlike monitoring, software distribution, or other applications, IBM Tivoli Workload Scheduling operations can typically tolerate very little downtime. By isolating the IBM Tivoli Workload Scheduling TMR from other Managed Nodes in the environment, different service level agreements can be established and adhered to for the environment.

In some cases, customers may decide to not follow Tivoli's recommended practice of using a dedicated TMR. In such cases, they will need to install a Tivoli Managed Node instead. Regardless of the customers' decision, they must still install the Managed Node into the HACMP Cluster similarly to installing a TMR.

If customers require a Tivoli Endpoint on the IBM Tivoli Workload Scheduling Master, that is an optional installation procedure that they will need to perform in the HACMP Cluster. In order to save time, this installation step should be coordinated with the TMR installation.