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
Remotely deploying the Summarization and Pruning Agent
This function allows you to remotely deploy the Summarization and Pruning Agent. You can use this function anytime the Summarization and Pruning Agent needs to be installed remotely.
For remote management of monitoring agents in general, install the appropriate OS monitoring agent. For instance, to remotely manage a Summarization and Pruning Agent on Linux systems, install the Monitoring Agent for Linux OS on the same server. To remotely manage a Summarization and Pruning Agent on Windows systems, install the Monitoring Agent for Windows on the same server.
Also, to remotely deploy the Summarization and Pruning Agent, you must populate the remote depot with the necessary bundles (the Summarization and Pruning Agent bundle and its prerequisites) for the operating systems where the Summarization and Pruning Agent needs to be deployed. This can be done using the product installer or the tacmd addBundles command.
During this process of adding bundles, IBM Tivoli Monitoring reads the descriptor file (dsc) of the specified bundle you are adding, and identifies (among all of the files in the installation media) which files need to be copied on the agent’s depot in your monitoring server. The files loaded are copied onto the path specified in the DEPOTHOME environment variable, defined in the KBBENV environment file. The tacmd viewDepot command allows you to display the types of agents in the deployment depot. The CD image contains a deploy directory where the Summarization and Pruning Agent bundle is located. When the depot is populated, you must deploy an OS agent on the remote computer, using the tacmd createNode command.
After the node has been created and OS agent is running, you can install other non-OS agents. This installation can be done using the Tivoli Enterprise Portal or using the tacmd createNode command.
Run the following command to complete enabling this function:
tacmd addSystem –t sy –n Os_node_nameProperties supported:
DBTYPE.KSY_WAREHOUSE_TYPE The database type used for TDW. Allowed values are DB2, ORACLE, MSSQL SOURCES.KSY_WAREHOUSE_JARS The comma-separated list of JDBC JAR files needed to connect to the database. SOURCES.KSY_DB2_JDBCURL The JDBC URL used to connect to DB2 database. Default is jdbc:db2://localhost:50000/WAREHOUS SOURCES.KSY_DB2_JDBCDRIVER The DB2 JDBC driver. Default is com.ibm.db2.jcc.DB2Driver SOURCES.KSY_ORACLE_JDBCURL The JDBC URL used to connect to Oracle. Default is jdbc:oracle:thin:@<server>:<port>:<database> SOURCES.KSY_ORACLE_JDBCDRIVER The Oracle JDBC driver. Default is oracle.jdbc.driver.OracleDriver SOURCES.KSY_MSSQL_JDBCURL The JDBC URL used to connect to Microsoft SQL Server. Default is jdbc:sqlserver://<server>:<port>;databasename=<database>;SelectMethod=cursor SOURCES.KSY_MSSQL_JDBCDRIVER The Microsoft SQL Server JDBC Driver. Default is com.microsoft.sqlserver.jdbc.SQLServerDriver SOURCES.KSY_WAREHOUSE_USER The user ID used to connect to the TDW database. SOURCES.KSY_WAREHOUSE_PASSWORD The password used to connect to the TDW database. SOURCES.KSY_CNP_SERVER_HOST The TEPS hostname. Default is localhost SOURCES.KSY_CNP_SERVER_PORT The TEPS port number. Default is 1920 SCHEDULING.KSY_FIXED_SCHEDULE The scheduling to be used by S&P. Y for fixed schedule or N for flexible schedule. Default is Y SCHEDULING.KSY_EVERY_N_MINS The flexible scheduling interval in minutes. Default is 15 SCHEDULING.KSY_EVERY_N_DAYS The fixed scheduling interval in days. Default is 1 SCHEDULING.KSY_HOUR_TO_RUN The fixed scheduling time to run. Default is 2 SCHEDULING.KSY_HOUR_AM_PM The fixed scheduling AM or PM of time to run. Allowed values: AM, PM Default is AM SCHEDULING.KSY_MINUTE_TO_RUN The fixed scheduling minute to run. Default is 0 SCHEDULING.KSY_BLACKOUT Comma-separated list of blackout periods in the format HH:MM-HH:MM using 24 hour format. The flexible scheduling will not start during the listed blackout periods. Note that the end time should be greater than the start time of the blackout period. WORK.KSY_START_OF_WEEK_DAY The start of the week day, used when computing weekly aggregates. Allowed values are 0 (Sunday), 1 (Monday). Default is 0 (Sunday) WORK.KSY_SHIFTS_ENABLED Controls whether shifts are used or not. Allowed values are Y or N Default is N WORK.KSY_SHIFT1_HOURS Comma-separated list of off peak shift hours. Default is 0,1,2,3,4,5,6,7,8,18,19,20,21,22,23 WORK.KSY_SHIFT2_HOURS Comma-separated list of peak shift hours. Default is 9,10,11,12,13,14,15,16,17 WORK.KSY_VACATIONS_ENABLED Controls whether vacation days are used or not. Allowed values are Y or N Default is N WORK.KSY_WEEKENDS_AS_VACATIONS Controls whether weekends are treated as vacation days. Allowed values are Y or N. Default is N WORK.KSY_VACATION_DAYS Comma separated list of vacation days in the format YYYYMMDD where YYYY is the year, MM is the month (1-12), and DD is the day (1-31). LOG.KSY_WAREHOUSELOG_PRUNE Controls the pruning of the WAREHOUSELOG table. The format is nn.uuu where nn is the number of units to retain and uuu is one of day, month, or year. Example: 5.day to retain data for 5 days. LOG.KSY_WAREHOUSEAGGREGLOG_PRUNE Controls the pruning of the WAREHOUSEAGGREGLOG table. The format is nn.uuu where nn is the number of units to retain and uuu is one of day, month, or year. Example: 5.day to retain data for 5 days. ADDITIONAL.KSY_MAX_WORKER_THREADS The number of threads that will be used for summarization and pruning. Default is 2 ADDITIONAL.KSY_MAX_ROWS_PER_TRANSACTION The number of rows per database transaction. Default is 1000 ADDITIONAL.KSY_TIMEZONE_IND Controls which time zone offset should be used. Allowed values are AGENT or WAREHOUSE Default is AGENT ADDITIONAL.KSY_HOUR_AGE_UNITS Controls the age in hours of data to be summarized. Default is 1 ADDITIONAL.KSY_DAY_AGE_UNITS Controls the age in days of data to be summarized. Default is 0 ADDITIONAL.KSY_NODE_ERROR_UNITS The number of node errors to keep for the self-monitoring workspace. Default is 10 ADDITIONAL.KSY_SUMMARIZATION_UNITS The number of summarization runs to keep for the self monitoring workspace. Default is 10 ADDITIONAL.KSY_CACHE_MINS The time in minutes that connectivity information is cached. Default is 15 ADDITIONAL.KSY_BATCH_MODE Controls whether batching of data should be used to improve performance. Allowed values are 0 (single system) or 1 (multiple systems). Default is 0 ADDITIONAL.KSY_DB_COMPRESSION Controls whether tables and indexes should be created with database compression enabled. Allowed values are N or Y. Default is N.
A Summarization and Pruning Agent should be installed and configured on the remote system once the transaction has completed successfully. The Summarization and Pruning Agent operates as usual when it is started. Connectivity of the Summarization and Pruning Agent can be checked on the Summarization and Pruning Agent Status workspace.
The configureSystem command allows CLI configuration of a remote agent. If SCHEDULING.KSY_BLACKOUT, WORK.KSY_VACATION_DAYS, LOG.KSY_WAREHOUSELOG_PRUNE or LOG.KSY_WAREHOUSEAGGREGLOG_PRUNE are not provided, their value will be set to an empty value.
It is the OS Agent that is used by remote deploy to do the work. The OS Agent log on the endpoint shows all the remote deploy activity (kdy component) processing. If you enable ERROR(UNIT:KDY ALL) on the endpoint's OS Agent tracing, you will see the remote deploy processing. To redeploy the same agent, run the tacmd updateagent command using the –v option.
Remote deploy will start the agent after installation which may cause situations to fire due to lack of default configuration. The configuration supplied during the remote deploy is applied after the install and start is done. The agent will be restarted after the configuration is complete.
Parent topic:
Tivoli Data Warehouse solutions: common procedures