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

2017-07-07 02:10:07

< Day Day Up >

Follow these steps, in the order specified, to configure the TMR.

Set the root administrators login

When installing Framework, a default high level administrator is created that is named Root_SJC-TDB-02. This administrator is, by default, bound to a login at the hostname where the TMR was installed. In order to log in to the Tivoli Desktop, you need to modify the login so the user will be able to log in at the virtual host.

First, open a command prompt and run the following command to set up an alias to allow the root user to log in:

odadmin odlist add_hostname_alias 1 10.254.47.190 SJC-TDB-02

Once the alias has been set, log in to the desktop and set the login with the appropriate hostname. Then use the following command to remove the alias:

odadmin odlist del_hostname_alias 1 10.254.47.190 SJC-TDB-02

Force the oserv to bind to the virtual IP

In order for the oserv to work properly, you need to bind it to the virtual IP address. This can be done with the following command:

odadmin set_force_bind TRUE 1

Change the name of the DBDIR

When Framework is installed, it will still point to SJC-TDB-02.db for the DBDIR, regardless of whether or not the wlocalhost is set. To resolve this, manually rename the DBDIR from the SJC-TDB-02.db to the tivoli-cluster.db directory.

Modify the setup_env.cmd and setup_env.sh

Next, modify the c:\winnt\system32\drivers\etc\tivoli\setup_env.* files that are used to set up the environment variables. Since Framework on Windows installs the DBDIR using the <hostname>.db directory instead of in the <virtual hostname>.db directory, you need to open a text editor and modify the directory where the environment variables point by changing all references of SJC-TDB-02.db to tivoli-cluster.db.

Once this is done, copy the modified setup_env.cmd and setup_env.sh to the c:\winnt\system32\drivers\etc\tivoli on both nodes.

Configure the registry

There are two places to modify in the Windows registry when Tivoli is installed. You can modify these locations by using the regedit command.

The first place to modify is under the HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Platform\oserv94 path. You will need to modify the Service directory key and the Database directory key to point to the new D:\tivol\db\tivoli-cluster.db directory, instead of to the SJC-TDB-02.db directory.

The second place to modify is where the oserv service looks for the oserv.exe executable; the location in the registry is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\oserv. You will only need to modify the path to the oserv.exe to "d:\tivoli\db\tivoli-cluster.db".

The modifications will have to be made on both primary and secondary nodes.

Rename the Managed Node

The TMR's Managed Node, which was created during the installation of Tivoli, was named by the hostname instead of the virtual hostname. This is not necessarily a problem since the oserv is bound to the virtual hostname and IP. To maintain consistency, however, in our case we opted to rename the ManagedNode to the name of the virtual hostname.

This was done with the following command from the Windows bash shell:

MN='wlookup -r ManagedNode SJC-TDB-02' idlcall $MN _set_label '" tivoli-cluster"'

If you perform this task, run the wlookup -ar tivoli-cluster command afterward to verify that the rename was successful.

Rename the TMR

The default name of the TMR when it was installed on Windows was still SJC-TDB-01-region instead of tivoli-cluster-region. This is not a problem, but to maintain consistency we renamed the TMR using the following command:

wtmrname <virtual hostname>-region

If you perform this task, verify the result of the command by running the wtmrname command and check that the output shows tivoli-cluster-region.

Rename the top-level policy region

When the Framework was installed, it created a top-level policy region call SJC-TDB-02-region. This is not a problem, but to maintain consistency we chose to rename the region.

This can be done from the Tivoli Desktop by right-clicking the SJC-TDB-02-region icon on the root administrator's desktop and selection properties. Once the Properties dialog is open, you can change the name to "tivoli-cluster-region" then click Set & Close to activate the changes.

We chose to change the name of the top-level policy region from the command line by using the following command:

PR='wlookup –r PolicyRegion SJC-TDB-02-region' idlcall $PR _set_label '" tivoli-cluster-region"

If you perform this task, run the following command to verify the change:

wlookup –r PolicyRegion tivoli-cluster-region'

Rename the root administrator

The default Tivoli administrator that was created was named Root_SJC-TDB-02-region. This is not a problem, but for consistency we choose to change the name to Root_tivoli-cluster-region.

This was done from the Tivoli Desktop by opening the administrator's window and right-clicking Root_SJC-TDB-02-region administrator and selecting Properties. Once the properties window was open, we modified the name to Root_tivoli-cluster-region. If you perform this task, then click Save & Close and the configuration is complete.

Configure the ALIDB

When Tivoli was installed, the ALIDB was set to SJC-TDB-02.db; this is an internal value that is hardcoded into the Tivoli object database. In order to change this value, we had to output the sequence list to a file, then modify the file, and re-import the sequence list. In order to get the sequence list, we ran the following command from a bash shell:

MN='wlookup –r ManagedNode tivoli-cluster' idlcall $MN _get_locations > c:/locations.txt

We opened the c:\locations.txt file with a text editor and changed all occurrences of SJC_TDB-02 to tivoli-cluster. When the editing was complete, we re-imported the sequence-list using the following command.

idlcall $MN _set_locations < c:/locations.txt

If you perform this task, once the value is set you should be able to install software successfully.