3.4.4 Estimating the size of trace log files for JP1/AJS3 Console
This subsection explains how to estimate the size of the trace log files used with JP1/AJS3 Console.
- Organization of this subsection
(1) Estimating the size of the trace log file for JP1/AJS3 Console Manager
The settings for the JP1/AJS3 Console Manager trace log file in the initial status are as follows:
-
Storage location
- For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:
-
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2CM\log\tracelog.cm
The default %ALLUSERSPROFILE% value is system-drive\ProgramData.
A folder protected by the system is the path to a folder in any of the following:
- system-drive\Windows
- system-drive\Program Files
- system-drive\Program Files (x86) (for 64-bit Windows)
- For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:
-
JP1/AJS3-Console-installation-folder#\log\tracelog.cm
The file is installed at the following location as the default:
C:\Program Files\HITACHI\JP1AJS2CM
- In Windows Server 2003:
-
JP1/AJS3-Console-installation-folder#\log\tracelog.cm
The file is installed at the following location as the default:
C:\Program Files\HITACHI\JP1AJS2CM
- In UNIX:
-
/var/opt/jp1ajs2cm/log/tracelog.cm
-
Size
Approximately 3 megabytes (3,072 kilobytes)
The capacity required for the trace log file differs greatly depending on the details of the definitions, the nature of the operations, and whether or not errors are encountered. Estimate an appropriate capacity for the trace log file and expand the current capacity if necessary.
The formula for estimating the size of the trace log file is as follows.
Appropriate-trace-log-file-capacity (units: kilobytes) =
(5.0 + number-of-monitoring-destination-hosts-per-root-business-scope (for-each-JP1-user) x 0.5)
x number-of-logins-from-the-occurrence-of-an-error-to-collection-of-data
- Example: Saving a trace log for a 30-day period (for the physical host only)
-
-
A single JP1 user monitors applications at 30 target hosts.
-
There are 10 logins per day.
Appropriate trace log file capacity = (5.0+30 x 0.5) x (10 x 30) = 6,000 kilobytes
-
(2) Estimating the size of the trace log file for JP1/AJS3 Console Agent
The settings for the JP1/AJS3 Console Agent trace log file in the initial status are as follows:
-
Storage location
- For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:
-
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog.ca
The default %ALLUSERSPROFILE% value is system-drive\ProgramData.
A folder protected by the system is the path to a folder in any of the following:
- system-drive\Windows
- system-drive\Program Files
- system-drive\Program Files (x86) (for 64-bit Windows)
- For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:
-
JP1/AJS3-Manager-installation-folder\log\tracelog.ca
- In Windows Server 2003:
-
JP1/AJS3-Manager-installation-folder\log\tracelog.ca
- In UNIX:
-
/var/opt/jp1ajs2/log/tracelog.ca
-
Size
Approximately 3 megabytes (3,072 kilobytes)
The capacity required for the trace log file differs greatly depending on the details of the definitions, the nature of the operations, and whether or not errors are encountered. Estimate an appropriate capacity for the trace log file and expand the current capacity if necessary.
The formula for estimating the size of the trace log file is as follows.
Appropriate-trace-log-file-capacity (units: kilobytes) =
(2.0 + (0.1 + (0.04 x number-of-monitored-scheduler-services))
x (time-from-the-occurrence-of-an-error-to-collection-of-data (units: seconds) / monitoring-interval (units: seconds)))
x number-of-monitored-JP1/AJS3-Console-View-hosts
- Example: Saving a trace log for a 10-day period (for the physical host only)
-
-
Applications are monitored on the host using five JP1/AJS3 Console View hosts
-
Twenty scheduler services are monitored.
-
The monitoring interval is 300 seconds.
Appropriate trace log file capacity = (2.0 + (0.1 + (0.04 x 20)) x (864,000 / 300)) x 5 = 12,970 kilobytes
-
For details on the procedure for expanding the trace log file, see the following references:
- In Windows:
-
3.5.1 Extending trace log files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1
- In UNIX:
-
13.4.4 Extending trace log files in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1