Job Management Partner 1/Software Distribution Setup Guide

[Contents][Glossary][Index][Back][Next]

4.2.14 Operation Monitoring page

This page is used to set how to store operation history that is reported to the managing server when software operation status is monitored. Specify these settings taking into account the number of clients to be monitored and the disk capacity available to the managing server.

See 2.6.5 Examples of managing operation information in the manual Description and Planning Guide for examples of using operation histories.

Figure 4-17 Operation Monitoring page

[Figure]

Save the operation monitoring history
Specifies whether to retain operation histories, suppression histories and operating times reported from lower systems. The default is that this check box is selected.
Operation histories are retained in the directory specified for storing operation histories when the product was installed.
Suppression histories and operating times are retained in the JP1/Software Distribution relational database.
Up to 10,000 suppression histories can be stored. If that number is exceeded, the oldest items are deleted.
Up to 220 days of operating time information are retained for each client. If that number of days is exceeded, the oldest operating times are deleted.
If you clear this check box, log information reported from subsystems is not stored. Note that when log information is reported, the following information is updated on the Attributes page in Remote Installation Manager's System Configuration, Destination, or Directory Information window:
  • Final update date/time of software operation information
  • Applied software operation monitoring policy
  • Applied software operation monitoring policy version
Log information that has already been stored is retained even if this check box is not selected.
If you use Embedded RDB and have changed the settings, you must perform the following procedure after the setup is completed in order to apply the new settings:
  1. Stop the Remote Install Server service.
  2. Execute the netmdb_setup.bat command that is stored in JP1/Software-Distribution-installation-directory\BIN.
    When the netmdb_setup.bat command terminates, the system is placed in key entry wait status. If you wish to have the command terminate without setting a wait for a key entry, specify the /nopause option before executing the command.
  3. Start the Remote Install Server service.
Organization of this subsection
(1) Saving operation histories
(2) Store the operation monitoring history in the JP1/SD database
(3) Enable automatic storage

(1) Saving operation histories

Automatically delete the operation history from the storage directory
Select to delete operating information from the operation history storage directory if the threshold is exceeded. The default is to automatically delete.
See Table 4-2 for the thresholds and deletion sizes.

Compress and move the operation history to the storage directory
Select to compress operating information in the operation history storage directory and back it up to another directory when the threshold is exceeded.
See Table 4-2 for the thresholds.
Storage directory
Specifies the target backup directory when the Compress and move the operation history to the storage directory radio button is selected. Specify an existing directory as the backup directory.
You can specify up to 127 single-byte characters (63 double-byte characters) for a local disk directory or a shared directory. Specify shared directories using the UNC path.
You can specify the following single-byte characters: - _ \ . : ( ). However, you cannot specify to back up operation history directly under a drive (for example, D:\) or use network drives whose drive characters are already assigned (for example, G:\NETM\MONITORING). Moreover, you cannot specify the directory used as the operation history storage directory.
Do not manually create files or directories under the operation history backup directory.
For each client, the archived operation history is saved in the OPERATION directory that is created under the operation history backup directory specified here.
Archived operation histories are not automatically deleted. Check the size of the operation history backup directory periodically and delete operation histories.
Output a message to Event Viewer when the threshold value is reached
Select this box to output a message to the Event Viewer when the size of the operating information in the operation history backup directory exceeds the threshold. The default is OFF.
Threshold value
Specifies the threshold (1 to 1,000 GB) for the size of operating information in the operation history backup directory when the Output a message to the Event Viewer when the threshold value is reached check box is selected. The default is 30 GB.

When the Enable automatic storage check box is selected, operating information in the operation history storage directory is backed up to the operation history backup directory.

The threshold value and deletion size when operating information is automatically backed up to the operation history backup directory vary depending on the new installation values and the setting for timing of storage to the database. The following table shows the threshold values and deletion sizes when operation history is being automatically backed up to the operation history backup directory.

Table 4-2 Threshold values and deletion sizes for saving to the operation history backup directory

Timing Item Value
At a new installation (default) Threshold 3 MB
Deletion size 1 MB
When upgrading the version Threshold Inherits the setting from the previous version
Deletion size Inherits the setting from the previous version
When Storage interval is changed in setup Threshold 2 MB x {storage-interval (days) + storage-interval (days) [Figure] 2}#
Deletion size 2 MB x {storage-interval (days) [Figure] 2}#

#
Storage intervals of 1 to 24 hours are counted as one day.

If the Enable automatic storage check box is not selected, operating information is backed up to the operation history backup directory only when the dcmmonrst command is executed.

Since an event log is output when the operation history storage directory size exceeds 20 MB, you can treat this event log as a reminder for you to execute the dcmmonrst command to back up the currently stored operating information to the operation history backup directory.

(2) Store the operation monitoring history in the JP1/SD database

Select this check box to automatically store operating information in the JP1/Software Distribution relational database or when you manually execute a dcmmonrst command to store operating information.

For details about the dcmmonrst command, see 4.13 dcmmonrst.exe (storing operating information in a database) in the manual Administrator's Guide Volume 2.

(3) Enable automatic storage

Select this check box to automatically store operating information in the JP1/Software Distribution relational database when managing operating information (suppression history and operation history) in the Operation Log List window. The default is not selected.

To manage operating information using the Operation Log List window, operating information must be stored in the JP1/Software Distribution relational database.

Note
When operating information is acquired from clients in a virtualized environment, the amount of operating information increases proportionally to the number of users logged on. Therefore, we recommend that you deselect the Enable automatic storage check box and manually execute the dcmmonrst command as needed to back up operating information to the operation history backup directory.

Data retention length
For each client, specifies the number of days to hold the stored operating information.
Operating information that has aged the specified number of days is deleted, using the latest operating information for each client as the reference point.
Specify 1 to 31 days. The default is 7 days.

Log the storage status
Select this check box to log when operating information is stored in the database to MONRST.LOG. The default is that this check box is selected.
For details about MONRST.LOG, see 6.3.1 Checking log files in the manual Administrator's Guide Volume 2.

Store data at a specified time
Operating information is stored at the time specified in Database storage time after the number of days specified in Storage interval have elapsed since information was last stored. The default is to select this item.
The initial operating information is stored at the time specified in the Database storage time after Remote Install Server service has started.
Specify Database storage time between 0:00 and 23:59. The default is 0:00.
Specify Storage interval between 1 and 30 days. The default is 1 day.

Store data at a fixed interval
Stores new operating information after the time specified in Storage interval has elapsed since the previous storage operation was completed.
The initial operating information is stored when the time specified in Storage interval has elapsed since the Remote Install Server service has started.
Specify Storage interval between 1 and 24 hours. The default is 1 hour.
(a) Notes