IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse solutions: common procedures
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Install the Warehouse Proxy Agent and Summarization and Pruning Agent in silent mode, using the silent response file
A silent installation runs on its own and does not require you to provide input to dialog boxes or monitor the installation. This configuration option allows for an unattended and automatic installation and configuration of the Warehouse Proxy Agent and Summarization and Pruning Agent as well as the remote configuration of these two agents. Configuration of the Warehouse Proxy Agent and Summarization and Pruning Agent takes place during the setup of the IBM Tivoli Monitoring infrastructure, or manually later.
The database administrator must create the following before the silent install is run:
- An empty database that will serve as the Data Warehouse database. The default DB2 database is WAREHOUS.
- The username and password that will be used with the database default ITMUser.
- The ODBC connection that will be used to connect the database to the Warehouse Proxy and Summarization and Pruning Agents default ITM Warehouse. The ODBC datasource connection must be created in 32-bit and 64-bit mode if the 64-bit Warehouse Proxy Agent is used to connect to the Data Warehouse database.
After these items are created, the database administrator must provide the database name, username and password, and ODBC connection information to the IBM Tivoli Monitoring administrator. The IBM Tivoli Monitoring administrator takes the information provided by the database administrator and updates all the configuration information in the silent response file that drives the installation and configuration process.
You must complete the following steps for this configuration option:
- Fill in the silent response file (silent_server.txt), providing the configuration information for the Warehouse Proxy Agent and the Summarization and Pruning Agent.
You can also have response files created automatically on Windows. From the Manage Tivoli Enterprise Monitoring Services screen, right-click the agent whose configuration information you want saved, and select the Advanced → Utilities → Generate Response Files option from the pop-up menu.
- Start the installation in silent mode, providing the silent response file as a parameter.
- Start a DOS Command Shell.
- From the shell, cd to the directory containing this installation (where setup.exe and setup.isn reside).
- Invoke setup as follows:
start /wait setup /z"/sfC:\temp\SILENT_SERVER.txt" /s /f2"C:\temp\silent_setup.log"You must specify the parameters in the same order listed above.
Where:
- /z"/sf
- Specifies the name of the installation driver you have customized for your site. This is a required parameter. This file must exist.
- /s
- Specifies that this is a silent install. This causes no responses to be displayed during installation on the installed target workstation.
- /f2
- Specifies the name of the InstallShield log file. If you do not specify this parameter, the default is to create Setup.log in the same location as setup.iss. This log is the InstallShield log not the install log. The install log can be found in the install target directory, default c:\IBM\ITM sub-directory InstallITM, or on the Windows Boot drive root directory if the install aborts before the install location has been identified. In either case, the Setup program must be able to create and write to this file.
What to do next
You can confirm a successful configuration when the Warehouse Proxy Agent, Summarization and Pruning Agent, and Performance Analyzer Warehouse Agent show a connection to the Data Warehouse database. To verify this, login to the Tivoli Enterprise Portal Desktop and check the state of the Data Warehouse database connectivity for all three agents. The Summarization and Pruning Agent should also show connectivity to the Tivoli Enterprise Portal. The connections should be displayed as green.
Parent topic:
Tivoli Data Warehouse solutions: common procedures