IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with Tivoli Monitoring components in a Microsoft Cluster Server environment > Set up the portal server in a Microsoft Cluster Server > Install and set up DB2 on a Microsoft Cluster Server
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Install DB2 on clusternode1
Procedure
- Switch the cluster to clusternode1.
- Install DB2 as you typically do on a local drive on clusternode1
- As in a default installation, create the default instance.
- Switch all DB2 services to manual so that they can be controlled by the cluster. The DB2 services are:
- DB2 - DB2-0
- DB2 Governor
- DB2 JDBC Applet Server
- DB2 License Server
- DB2 Remote Command Server
- DB2 Security Server
- DB2DAS - DB2DAS00
- DB2 Management Service
- To change the DB2 configuration so that the default drive (for creating the database to be used by Tivoli Monitoring) is the shared disk:
- Start the DB2 Administration Server by issuing the db2start command in a DB2 command line.
- Start the DB2 Control Center.
- Right-click the instance name (DB2 by default).
- Select option Confígure parameters.
The following window opens:
Figure 1. Configuring parameters in the DBM Configuration window
- Select DFTDBPATH, click the value field, and then click the “…” to change the default drive.
If you cannot save your changes, log in to your system as the db2admin user and update the default drive value as previously described.
Figure 2. Changing the default drive
Figure 3. Setting the default drive to R
- Change the drive to the shared drive for the cluster (R in the testing environment).
Figure 4. Setting the default drive to R
- Stop clusternode1 service so that the changes on DB2 take effect and the cluster switches to clusternode2.
Parent topic:
Install and set up DB2 on a Microsoft Cluster Server