Appendix B: TMR Clustering for Tivoli Framework 3.7b on MSCS

 < Day Day Up > 

In this appendix, we provide step-by-step instructions on how the Tivoli Management Framework 3.7b on Windows 2000 was configured in a high availability environment. We guide you through the steps needed to install and configure the TMR.

In this environment, the Windows server is configured with Windows 2000 Advanced Server Edition SP and is running the Microsoft Cluster Manager.


The setup shown in Table B-1 was used during Windows TMR installation. The cluster includes physical nodes SJC-TDB-01 and SJC-TDB-02, with a virtual node named tivoli-cluster. The shared resource that is configured to fail over is defined as drive D:.

Table B-1: Installation setup


IP address



Physical node


Physical node


Virtual node

Configure the wlocalhost

Framework 3.7b for Windows does not read the /etc/wlocalhosts file or the wlocalhosts environment variable. Instead, with Framework 3.7b, there is a wlocalhost command that is used to configure the value of the wlocalhost. The command will create the localhost registry key in the HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Platform registry path.

If you have installed Framework on another Windows machine, you can copy the $BINDIR/bin/wlocalhost binary from another machine and run it locally to set this value. The syntax we used to set the value of the wlocalhost was "wlocalhost tivoli-cluster". If you are installing Framework for the first time on the Windows platform, you can manually create this value using regedit.

Install Framework on the primary node

After the wlocalhost is set, the next step is to install Framework on the primary node. This is done by using the same procedures that are provided in the 3.7 Installation guide; the only exception is that you will want to specify the installation directory to be the shared drive (in our case, it is D:\tivoli).

Once Framework is installed, open a command prompt and run the odadmin odlist command to verify that the oserv is bound to the virtual IP and hostname defined by the wlocalhost command. Restart the primary node to register the tivoliap.dll.

Install Framework on the secondary node

Prior to installing Framework 3.7b on the secondary node, you will need to open the Cluster Manager and initiate a failover. Once the failover has occurred, you will need to delete the %DBDIR% directory and set the wlocalhost on the secondary node. If all went well during the installation on the primary node, you will be able to find the wlocalhost binary in the %BINDIR%/bin directory.

After the %DBDIR% has been removed and the wlocalhost has been set, you can install Framework on the secondary node. The Framework installation should be identical to the installation on the primary node, with the installation directory being on the shared drive (D:\tivoli). After the installation, run the odadmin odlist command to verify that the oserv is bound to the virtual IP and hostname. Restart the secondary node, if it has not already been restarted.

 < Day Day Up > 

High Availability Scenarios with IBM Tivoli Workload Scheduler and IBM Tivoli Framework
High Availability Scenarios With IBM Tivoli Workload Scheduler And IBM Tivoli Framework
ISBN: 0738498874
EAN: 2147483647
Year: 2003
Pages: 92
Authors: IBM Redbooks © 2008-2017.
If you may any questions please contact us: