IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with monitoring components in a System Automation for Multiplatforms environment > Set up a cluster for Tivoli Monitoring > Predefined Tivoli System Automation for Multiplatforms Cluster for Tivoli Monitoring > Building a Tivoli System Automation for Multiplatforms Cluster for the portal server and Tivoli Data Warehouse components
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Cataloging the Portal server/Tivoli Data Warehouse Database on node 2
Procedure
- Switch the RG_NAME resource group to the other node:
rgreq –o move RG_NAME
The terminal session might end after the move completes.
- Wait until the resource group is online on node2, using:
lssam -top
- Grant full database access to the database user on node2.
- On the active node, switch to the user ID of the instance owner.
- Catalog the database in this instance using the command:
db2 catalog database <DBName> on /shareddisk/DBdirectory
- Test the connection to the database using the command:
db2 connect to <DBName>
- After successful connection, reset the connection using the command:
db2 connect reset
- Change back to the root user.
- To install a portal server in the cluster, and the Tivoli Data Warehouse is on another computer, also catalog the Tivoli Data Warehouse database and database server for the local DB2 as a remote database server on both nodes, so that the portal server can access this database later. For further information, refer to the IBM Tivoli Monitoring: Installation and Setup Guide.
Results
You are now ready to install the portal server or Tivoli Data Warehouse components in this cluster.
Parent topic:
Building a Tivoli System Automation for Multiplatforms Cluster for the portal server and Tivoli Data Warehouse components