IBM Tivoli Monitoring for Virtual Environments, Version 7.2 Fix Pack 2

Configuring homogeneous federation for the Capacity Planner for VMware

To configure the homogeneous federation, you must create federation between the IBM® Tivoli® Data Warehouse database and the Capacity Planner database.

Note: The federation server configuration for Tivoli Data Warehouse is supported on the DB2®, MSSQL Server, and Oracle databases.

Before you begin

The Java™ Runtime Environment (JRE) version 1.6.0 or later must be available on the database server where you want to complete the federation steps.
The federation steps must be completed by using a user account that has instance owner authority and/or permission on the database instance for which the Capacity Planner database was created.
Note: Typically, the instance owner is "db2inst1" on the UNIX systems and "db2admin" on the Windows systems. You might observe failures if you are completing the federation steps by using a user account with non-compliant authorization levels.
You must enable the federation.
Complete the following steps to enable the federation:
1. Keep the federated mode as On for the database manager configuration.
2. Check the parameter by connecting to the database, running the following command at the command line:
  # db2 get dbm cfg | grep -i federated
  Note: Use this command on the Linux systems.
  
  If the parameter is set to no, set the parameter to yes by using the following command:
  
  # db2 update dbm cfg using federated yes
3. Restart the database manager by using the following command:
  # db2stop
  
  # db2start
For federation of Tivoli Data Warehouse on Oracle or MSSQL server, you must install and configure IBM InfoSphere® Federation Server.

About this task

This task provides information about creating federation between the IBM Tivoli Data Warehouse database and Capacity Planner database.

Procedure

Log on to the computer where the database is installed.
Open a command line.
Copy the federation directory from dash_home\installedDashboards\com.ibm.tivoli.cpdash\AnalyticsDatabaseInstaller to a temporary directory. The federation scripts are available in the federation directory.
After installation, the scripts are placed in the following directory for the Capacity Planner for VMware: dash_home\installedDashboards\com.ibm.tivoli.cpdash\AnalyticsDatabaseInstaller where dash_home has the following path on the Windows systems: \Program Files\IBM\JazzSM or this path: /opt/IBM/JazzSM on the UNIX systems.
Note: The directory where you copy these scripts must have write permissions for the database instance owner. For the Windows systems, the target directory should not have any spaces in the path, otherwise the federation scripts fail.
Edit the fed_config.cfg file in the temporary directory, and set the following properties with appropriate values:
TDW_REMOTE_HOST_NAME

The IP address or complete host name of the database server where the Tivoli Data Warehouse is installed.

TDW_REMOTE_PORT

The port number of the DB2 database server where the Tivoli Data Warehouse is installed.

TDW_REMOTE_DB_NAME

The name of the remote Tivoli Data Warehouse database.

TDW_REMOTE_DB_SCHEMA_NAME

The schema name in the Tivoli Data Warehouse database.

TDW_REMOTE_DB_INSTANCE_OWNER

The instance owner of the remote Tivoli Data Warehouse database. The default owner is ITMUSER, who created the Tivoli Data Warehouse database on the remote Tivoli Data Warehouse database server.

TDW_REMOTE_DB_INSTANCE_OWNER_PASSWORD

The password of the remote Tivoli Data Warehouse database instance owner. This password is required when you register the federation server definition.

NODE_ID

The node name that is used to create the DB2 node on the database server. This NODE_ID must not be more than 8 characters in length, and must not contain special characters.

TDW_LOCAL_ALIAS

The alias name that is used to catalog the remote Tivoli Data Warehouse database on the local DB2 database server.

FED_DB_SERVER_TYPE

The DB2 server data source, for example, DB2/CS.

FED_DB_VERSION

The version of the DB2 Server, for example 10.1 or 9.7.

USE_EXISTING_CATALOGED_TDW

This property must be set to Yes if you manually created an alias for the remote Tivoli Data Warehouse database and want to use the alias for federation. If the catalog is not created, the federation script attempts to create an alias for the remote Tivoli Data Warehouse by using the value that is provided for the TDW_LOCAL_ALIAS property. Set this property to NO if you do not want to use existing alias to be used in federation.
Note: Set USE_EXISTING_CATALOGED_TDW to NO only if you are sure that no alias is available on the capacity planner database with the name provided for the TDW_LOCAL_ALIAS property. Otherwise, the scripts might remove this alias after it fails to register the federation server.

CP_DB_NAME

The name of the capacity planner database, for example, TADFDCDB.

CP_DB_INSTANCE_OWNER

The instance owner of the capacity planner database. This owner is the same user that was used to create the capacity planner database.

CP_DB_INSTANCE_OWNER_PASSWORD

The password of the capacity planner database instance owner. This password is required to connect to the capacity planner database.

CP_DB_SCHEMA_NAME

The schema name in the Capacity planner database. For PowerVM®, the schema name is TADFDCP. For VMware, the schema name is TADFDC.

FED_SERVER_NAME

The name of the federation server that is configured. This name might be any unique name without special characters and space characters in it. You use this federation server when you federate the Tivoli Data Warehouse tables or views.
Navigate to the temporary directory, and run any of the following commands that matches your operating system:
- fed_admin.bat: Use this script on the Windows systems.
- fed_admin.sh: Use this script on the UNIX and AIX® systems.
You can run the fed_admin.sh or fed_admin.bat script in any one of the following two modes:
- Non-interactive mode
  In this mode, use one of the following scripts:
  - fed_admin.sh
  - fed_admin.bat
  - fed_admin.sh JAVA_HOME -f custom_config_file
  - fed_admin.bat JAVA_HOME -f custom_config_file
  where custom_config_file_name is the file with non-default configuration parameters.
  For example, the following script configures the federation server and creates all views for the physical server and the virtual machine and prints the summary of views created in the console:
```
fed_admin.sh JAVA_HOME -f fed_config.cfg
```
- Interactive mode
  In this mode, use the one of the following scripts, which have the -i argument to select the task that you want to complete:
  - fed_admin.sh JAVA_HOME -i -f custom_config_file
  - fed_admin.bat JAVA_HOME -i -f custom_config_file
  Where:
  -i
  
  Runs the script in interactive mode. For example, you can configure a new server; update user mapping; add views; and delete views. If you choose to add all views, a summary of the views that were created is displayed.
  
  -f custom_config_file_name
  
  custom_config_file_name is the file with non-default configuration parameters.
  Note: When this file is not used, the script uses the default fed_config.cfg file. To get the correct result from the scripts in any mode, you must specify correct input parameters in the fed_config.cfg file.
- DBA verification mode
  In this mode, use the fed_admin.sh or fed_admin.bat script with the -v argument to print the federation commands for the task in a file instead of running the commands against the database.
  - Change the directory to the directory that contains the federation.
  - At the command line, run the fed_admin script in interactive mode and DBA verification mode:
    ./fed_admin.sh JAVA_HOME -i -v -f custom_config_file
    
    When you are prompted for input, select one of the following options:
    Configure new server
    
    Update user mapping
    
    Add views
    
    Delete views
    
    If you select Add views or Delete views, type the view names to be added or deleted separated by a space, for example, VM_CPU_D VM_CPU_M. For all views, type the argument all.
    Note: View names must be typed in uppercase.
  - At the command line, run the fed_admin script only in DBA verification mode to print the queries that are to be run against the database for the following options:
    Configure federation server
    
    Add all views for physical server and virtual machine: ./fed_admin.sh JAVA_HOME -v -f custom_config_file
  The federation commands are printed in the federationqueries.ddl file.
Configure new federation server by running the fed_admin.sh OR fed_admin.bat script.
Note: Ensure that you have set all the input parameters in the fed_config.cfg file.
- If you run the fed_admin.sh or fed_admin.bat, or the fed_admin.sh -f or fed_admin.bat -f custom_config_file script, the script configures the federation server and creates all views for the physical server and virtual machines.
- If you run the fed_admin.sh -i -f or fed_admin.bat -i -f custom_config_file script, type 1.
  This script configures a federation server that is based on the configuration parameters that are specified in the fed_config.cfg file.
If the credentials of Tivoli Data Warehouse instance owner are changed on the remote database server after the federation server is configured, you must update the existing federation server details.
1. Set TDW_REMOTE_DB_INSTANCE_OWNER_PASSWORD property in configuration file to new password. The default configuration file is fed_config.cfg.
2. Run the fed_admin.sh/bat script.
  - If you run the fed_admin.sh or fed_admin.bat, or the fed_admin.sh -f or fed_admin.bat -f custom_config_file script, the script updates the federation server details.
  - If you run the fed_admin.sh -i or fed_admin.bat -i script, type 2.
    This script uses the configuration parameters that are specified in the fed_config.cfg file to update the federation server details.
Add the selected views.
1. Run the fed_admin.sh -i or fed_admin.bat -i script.
2. Type 3.
3. Type space separated view names that you want to add. For example, VM_CPU_H VM_NET_M.
  Note: You must type the view names in uppercase. If you want to add all the views, type the argument all.
Delete the selected views.
1. Run the fed_admin.sh -i or fed_admin.bat -i script.
2. Type 4.
3. Type space separated view names that you want to delete. For example, VM_CPU_H VM_NET_M.
  Note: You must type the view names in uppercase. If you want to delete all the views, type the argument all.

Feedback