HP Systems Insight Manager 7.1 Installation and Configuration Guide for MS Windows

8 Configuration options
Several configurable parameters in Systems Insight Manager are not available from the GUI. These
parameters can only be configured by editing a configuration file on the CMS.
NOTE: All Systems Insight Manager parameters have been set to predefined values that are
appropriate for most situations. These parameters should only be changed if you are experiencing
issues with the default values.
There are two main default locations where configuration files are stored:
• C:\Program Files\HP\Systems Insight Manager\config\
• C:\Program Files\HP\Systems Insight Manager\hpwebadmin\lib
The Windows directory paths vary if Systems Insight Manager is not installed in the default location.
These files follow the format of a Java properties file. Therefore, the keys in these files are
case-sensitive. In addition, the backslash (\) must be represented by a double-backslash (\\). For
more information about the Java property file format, refer to http://java.sun.com/.
This chapter provides information on the following configuration options:
• “CPU utilization during data collection” (page 62)
• “GUI time-out policy” (page 62)
• “Systems Insight Manager audit log configuration” (page 63)
• “Configuring task results” (page 64)
CPU utilization during data collection
Overview
The data collection task runs many threads in parallel to overlap computing and database operations
with the wait for managed systems to respond. On slower systems, this might temporarily saturate
the CPU, depending on the processor speed of the CMS system and the number of systems being
collected. Therefore, Systems Insight Manager provides some strategies to lessen the CPU usage.
Implementation
To lessen the CPU usage during data collection on the CMS:
• Limit the number of systems that are being collected at one time. For example, create separate
data collection tasks for different groups of systems and schedule them to run at different times.
• Configure the CMS to use a remote database on a system other than the CMS. A substantial
portion of the CPU load is consumed by the database during data collection. This option is
only supported with a Windows CMS.
• Lower the DataCollectionThreadCount parameter in the globalsettings.props
file. This parameter defaults to 3. Lowering it to 2 or 1 reduces the CPU demand of data
collection tasks, but it increases the time required to complete the tasks.
GUI time-out policy
Overview
Systems Insight Manager provides two alternative time-out policies. The first time-out policy is for
environments in which Systems Insight Manager is used to monitor system status, which is called
the monitor time-out policy. The second time-out policy is more strict and will time-out inactive users.
This is called the active time-out policy and it is similar to the policy, used by Servicecontrol
Manager.
62 Configuration options