HP Systems Insight Manager 6.2 Installation and Configuration Guide for HP-UX

7 Configuration options
Several configurable parameters in Systems Insight Manager that 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. Only change these parameters if you are experiencing issues with the default values.
There are two main default locations where HP-UX configuration files are stored:
• /etc/opt/mx/config
• /opt/hpwebadmin/lib
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, see http://java.sun.com/.
This chapter provides information on the following configuration options:
• “CPU utilization during data collection”
• “GUI time-out policy”
• “HP Systems Insight Manager audit log configuration”
• “Configuring task results”
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,
HP 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.
• 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
HP Systems Insight Manager provides two alternative time-out policies. The first time-out policy is for
environments in which HP 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.
Monitor time-out policy The monitor time-out policy keeps sessions alive, provided the user has a web
browser window open displaying the HP Systems Insight Manager GUI. Closing the browser or navigating
to another web page starts the timer for the time-out period. The default time-out period is 20 minutes. Users
must use some other means to protect an unattended session from illegal use, such as password-protected
screen savers.
Active time-out policy The active time-out policy only keeps sessions alive if the user is actively using the
GUI, such as clicking on links and buttons. Display and refresh of the banner is not sufficient to keep the
session alive. The user is timed-out either by inactivity, closing the browser, or navigating to another site.
The default time-out period is 20 minutes.
CPU utilization during data collection 32