3.4.7 Estimating the size of log files for Web Console server

This subsection explains how to estimate the size of log files that are output by JP1/AJS3 - Web Console.

This subsection covers the following JP1/AJS3 - Web Console log files:

• Storage location

  For Windows, if the installation folder is in the default folder or a folder protected by the system:

  %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\jp1ajs3web\log\appserver{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

  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 Windows in which an installation folder other than the above is used:

  JP1/AJS3-Web-Console-installation-folder\log\appserver{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

  In UNIX:

  /var/opt/jp1ajs3web/log/appserver{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16}.log

• Size

  You can specify a size from 4 to 16,384 in kilobytes (the default is 8,192 kilobytes).

  You can change size of the log file in the environment-settings file.

The required log file size depends on the trace level, operation details, and errors. The table below provides guidelines for estimating the log file size when the trace level is info (default).

Add one megabyte for estimation because re-connections might be required when JP1/AJS3 - Manager is disconnected or more operations might fail than you expect.

To estimate the log file size, add the estimation result for the Web GUI and the estimation result for the API.

Table 3‒33: Estimating the log file size for each window displayed in the Web GUI

Window	Estimated log file size required per operation (units: kilobytes)
	Initial display	Automatic update	Manual update	Execution registration	Define details	Change job status	Add	Change Plan	Change Delay Monitor	Others#1
Dashboard screen	(total-number-of-monitored-units#2 + 5) x 2.5	#3 (number-of-monitored-units + 3) x 2.5	(number-of-monitored-units#4 + 3) x 2.5	--	--	--	--	--	--	(number-of-monitored-units#4 + 4) x 2.5
List screen	10.0	5.0	5.0	12.0	--	--	--	--	--	7.5
Monitor dialog box#5	15.0	7.5	7.5	--	8.0	9.0	--	11.0	--	7.5
Monthly Schedule screen	99 + number-of-registrations-of-a-jobnet-definition-release#6 x 3	--	95 + number-of-registrations-of-a-jobnet-definition-releas#6 x 3	97 + number-of-registrations-of-a-jobnet-definition-releas#6 x 3	--	--	100 + number-of-registrations-of-a-jobnet-definition-releas#6 x 3	98 + number-of-registrations-of-a-jobnet-definition-releas#6 x 3	99 + number-of-registrations-of-a-jobnet-definition-releas#6 x 3	97 + number-of-registrations-of-a-jobnet-definition-releas#6 + 1) x 3

Legend:

--: Not applicable

#1

Refers to the following operations: canceling registration, specifying the hold setting, releasing the hold setting, interrupt operations, kill operations, re-execution, and getting detailed information.

#2

Total number of units specified as monitoring targets.

#3

Only the monitored units with automatic update enabled are summed up.

#4

Total number of units specified as monitoring targets being used.

#5

If you want to use the Monitor screen, be sure to add the size of the log file for the Monitor screen. The method for estimating the size of the log file for the Monitor screen is the same as the method for estimating the size of the log file for the Monitor dialog box.

#6

When displaying a root jobnet that does not have release information, the number of registrations of a jobnet-definition release is 1. When displaying a root jobnet that has release information, the number of registrations of a jobnet-definition release is the number of pieces of release information in the Being applied and Release wait statuses.

Example:

This example estimates the log file size required to keep a one-week log, assuming the following conditions:

• The Web GUIs run 8 hours a day, and operations are monitored in the Dashboard screen.

• In this period, 10 Web GUIs run.

• The number of monitoring targets for the Dashboard screen is set to 1.

• Automatic updating of the Dashboard screen is set to ON (the automatic update period is 10 minutes).

• The total number of monitored units for the Dashboard screen is set to 10.

The required log file size is as follows:

• Log file size required to perform initial display for an instance of Web GUI

  15 x 2.5 = 37.5 kilobytes

• Log file size required to perform automatic update for an instance of Web GUI

  13 x 2.5 = 32.5 kilobytes

• Number of automatic updates performed by Web GUI per day

  6 x 8 - 1 = 47 times

• Log file size for one day for one Web GUI

  37.5 x 1 + 32.5 x 47 = 1,565 kilobytes

• Total log file size in the period

  1,565 x 10 x 7 = 109,550 kilobytes

  When you round the above number and add 1 MB leeway, the result is 108 MB.

Table 3‒34: Estimating the log file size for each API

API	Log size per operation (units: kilobytes)
Acquisition of a unit list	12.0
Planned execution registration	12.0
Fixed execution registration	12.0
Immediate execution registration	12.0
Other APIs	7.5

Example:

This example estimates the log file size required to keep a one-week log, assuming the following conditions:

• The statuses of operations are monitored once an hour by using the API function for acquiring a list of all units.

• The number of monitored units is 5. A separate API function is issued to monitor the status of each unit.

The required log file size is as follows:

• Log file size required to monitor each unit once

  12 x 5 = 60 kilobytes

• Log file size required for one day

  60 x 24 = 1,440 kilobytes

• Total log file size required for one week

  1,440 x 7 = 10,080 kilobytes

  Round the above number and add 1 MB for safety. The final estimate is 11 MB.

To Page Top