Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 Administration Guide


1.17.1 Operating the management server in a large-scale environment

In asset management using JP1/IT Desktop Management 2, device information is collected from agent devices and agentless devices into the management server. The asset management functionality, such as security judgment and report calculation, is then performed based on the collected device information.

The amount of data in the device information collected into the management server has to be decreased, so that the server can operate stably with its limited resources. Operations such as security judgment can make the management server busy. Performing such operations periodically, instead of doing them when triggered by collection of device information, can reduce the load on the server.

Configuring the collection of device information from a managed device

The default values for the following settings are the recommended values for when managing 300,000 devices. The same applies to agent configuration for agent devices connected to the management relay server.

Reducing these setting values causes the amount of data for device information collected by the management server to increase, which may place a burden on the management server.

Agent configuration
  • Timing of communication with the higher system under Basic settings

    • Monitoring Interval (Security)

    • Monitoring Interval (Others)

    • Polling interval

Tuning the security judgment function

The security judgment function puts a high load on the server. As a result, it may take several hours for the function to finish as the number of managed devices increases. The parameters for security judgment can be tuned based on the specifications of the management server.

Tuning the start time of security judgment

Security judgment on a managed device starts at 18:00 by default. The result of the security judgment is used as input for report calculation that starts by default at 23:00. Adjust the start time of security judgment so that it can be completed by 1:00 (25:00), because security report calculation starts at 1:00 (25:00), which is two hours after the start of report calculation.

The start and end times of the judgment are logged in the publishing log file. You can specify the start time of security judgment by opening the Settings module from the management window and then selecting Security Schedule.

Tuning the number of processes handling security judgment

Increasing the value of the following property in the configuration file helps improve the performance when security judgment is performed. Do so if the CPU load is low.

Number of processes for handling security judgment (Mgrsrv_jdnmssecurityctrl_L)

While it does vary depending on the environment, it takes approximately one hour to perform security judgments for 50,000 devices with ten processes for handling security judgment.

Changing the timing for compilation of software license information

Software license information is normally compiled each time device information is updated.

The more managed devices there are, the slower installed software information is reflected for devices. Furthermore, as the number of software licenses in use is compiled after the device installed software information is updated, the number will be inaccurate for a time.

By setting the following property in the configuration file, you can change the timing for compilation of software license information to every three minutes.

Software_Licenses_Totalization_Method=SCH

Note

If you set this property, it may take up to three minutes after the device installed software is reflected on the window until the compilation result is reflected.

Backing up the database

The management server must be stopped to back up the database. Therefore, consider the conditions, such as the days of week and times when the management server is not used, before the backup.

Related Topics: