Job Management Partner 1/Software Distribution Administrator's Guide Volume 1

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

6.2.4 Setup for uploading the operation monitoring result

This section explains the settings for uploading a suppression log and operation log from a client to a managing server.

Figure 6-9 Edit Software Operation Monitoring Policy dialog box (setup for uploading the operation monitoring result)

[Figure]

Notify result information
Select this check box to report the suppression log and operation log from a client to a managing server. In the system default, this check box is selected.
To report the suppression log and operation log, you can specify, or choose a regular time interval of less than 1 day. The default is time periods. You can also choose whether to immediately report a client's suppression log when an event subject to prevention has occurred at the client.
Upload based on the time zone
Select this option when you want to have the history reported during time periods with 1 day or longer in between. Because you can specify a time span during which the reporting can start, this option is useful for avoiding the possibility of many clients simultaneously reporting history, placing an excessive load on the network or computer.
  • Result notification time
    Specify the time period during which history is to be reported. The default is 12:00-13:00, and history can be reported at random timings during this period.
  • Result notification interval
    Specify a range between 1 and 60 days as the interval at which to report history.
Upload at a fixed interval
Select this option if you want to have history reported at intervals of less than 1 day.
  • Result notification interval
    Specify the interval for reporting history. The default is 1 hour 0 minutes, and history is reported every hour after an operation monitoring policy is applied.
    In a virtual environment, we recommend that you specify 2 hours regardless of the number of login users.
Notify suppression event immediately
This option is useful for preventing software from starting, devices from being used, or print operations from being performed.
Select this check box in the following cases:
  • Suppress history is to be reported whenever a software startup is suppressed.
  • A JP1 event is to be issued as an alert whenever access to a device is suppressed.
  • A JP1 event is to be issued as an alert whenever a software startup is suppressed.
  • A JP1 event is to be issued as an alert whenever a print operation is suppressed.
Organization of this subsection
(1) Operation monitoring result backup function

(1) Operation monitoring result backup function

When uploading of operation monitoring results (suppress history and operation history) from a client to the managing server does not occur due to a failure, the client's operation monitoring results are accumulated in an upload file. If the upload file exceeds two gigabytes, a backup file is created. If uploading fails again, another backup file is created.

(a) Backup files for operation monitoring results

The backup files are created in JP1/Software-Distribution-Client-installation-directory\Client\Monitor\Work\Backup. The following describes the backup files that are created.

#: YYYYMMDDhhmmss indicates the backup file's creation date and time.

You can use the dmTRUtil.exe command to output created backup files to CSV files in order to view their contents. Before you execute this command, make sure that you move the backup files from the client to the managing server.

Notes
  • The values in the columns listed below are not included in the backup files because they are added to each operation log by the central manager. For this reason, you must move the backup files to the managing server in such a manner that the computer to which each backup file belongs can be identified (for example, by assigning the host name or IP address to the corresponding folder).
    [Figure] dm_nodename
    [Figure] dm_hostname
    [Figure] dm_ipaddress
  • When the backup files exceed 6 gigabytes, the oldest file is deleted regardless of the file name. If backup files cannot be uploaded for one month or more, or if operation information for a specific period of time is missing from the managing server, it is possible that the corresponding information might be in the backup files. In such a case, check the backup files.
  • Do not rename the backup files. If a backup file is renamed, it cannot be output to a CSV file by the dmTRUtil.exe command.
(b) dmTRUtil.exe command

This subsection describes the dmTRUtil.exe command. This command is stored in JP1/Software-Distribution-Manager-installation-directory\BIN.

Function
This command outputs an operation monitoring results backup file to a CSV file.

Format
dmTRUTil.exe -f operation-monitoring-results-backup-file-name
-o output-file-name

Arguments
  • -f
    Specifies the full or relative path of the operation monitoring results backup file.
  • -o
    Specifies the full or relative path of the output CSV file.

Return codes
The following table lists and describes the return codes of the dmTRUtil.exe command.
Code Description
0 Normal termination
1 Argument error
2 Contents of the operation monitoring results backup file are invalid.
3 CSV file output error (such as an access permission error)
32 Internal error

Note
There are three operation monitoring results backup files. You must execute this command separately for each file in order to output its contents to a CSV file.

Example output in CSV file
The following shows an example of the output in a CSV file.
File Name:operation-monitoring-result-backup-file-name
DB Table Name:table-name
"column-name-1","column-name-2",...
"value-1","value-2",...

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.