Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference
When status acquisition is performed with JP1/AJS3 - Web Operation Assistant, the acquisition performance depends on the following processing:
- Processing time for JP1/AJS3 - Manager or JP1/AJS2 - Manager
- Processing time for JP1/AJS3 - Web Operation Assistant
- Data transmission time between JP1/AJS3 - Manager or JP1/AJS2 - Manager, JP1/AJS3 - Web Operation Assistant, and the Web browser from which statuses are monitored
- The Web browser's drawing time for status monitoring
The above processing times depend in particular on the number of units for which statuses are acquired, as well as the number of units for which statuses are displayed.
- Organization of this subsection
- (1) Estimating status acquisition time
- (2) Recommended configuration
- (3) Recommended status acquisition method
- (4) Recommended number of Web browsers connected concurrently
(1) Estimating status acquisition time
You can use the following formula to calculate the approximate time required for status acquisition (the time from which status acquisition starts until all collected information is displayed) for JP1/AJS3 - Web Operation Assistant:
time-for-status-acquisition (in seconds) = a + b
- a:
- Sum of the following times:
- Processing time for JP1/AJS3 - Manager or JP1/AJS2 - Manager
- Processing time for JP1/AJS3 - Web Operation Assistant
- The data transfer time between JP1/AJS3 - Manager or JP1/AJS2 - Manager, JP1/AJS3 - Web Operation Assistant, and the Web browser used for status monitoring
- b:
- Drawing time for the Web browser for status monitoring
You can use the following formula to calculate the approximate processing time a (in seconds):
- When the database type for the scheduler service to be monitored is ISAM:
(8 x number-of-units-whose-statuses-are-acquired) / 1000 + 3#
- When the database type for the scheduler service to be monitored is embedded database or HiRDB:
2 + (3 x number-of-job-groups-included-in-the-unit-to-be-monitored + 60 x number-of-root-jobnets-included-in-the-unit-to-be-monitored + 0.8 x number-of-units-whose-statuses-are-acquired) / 1000
The processing time b (in seconds) depends on the performance of the Web browser, and varies depending on the number of units displayed. You can use the following formula or table to calculate the approximate processing time:
- When JP1/AJS3 - Web Operation Assistant displays the statuses of 0 to 1,000 units:
(13 x number-of-units-whose-status-is-displayed) / 1000#
- The following table lists the approximate processing times when JP1/AJS3 - Web Operation Assistant displays the statuses of more than 1,000 units:
Table E-1 Estimates of the Web browser drawing time when more than 1,000 units are displayed#
Number of units whose statuses are displayed Web browser drawing time b (in seconds) 3000 100 5000 250 8000 500 10000 850
- #
- The processing time depends on the performance of the machine on which JP1/AJS3 - Manager or JP1/AJS2 - Manager is installed, the machine on which JP1/AJS3 - Web Operation Assistant is installed, and the machine that uses the Web browser for status monitoring. The processing time also depends on the data transfer rate between these machines.
(2) Recommended configuration
When you use the machine on which JP1/AJS2 - Manager and JP1/AJS3 - Web Operation Assistant are installed to perform status acquisition from the Web browser, the processing time for JP1/AJS3 - Manager or JP1/AJS2 - Manager will increase. At this time, the processing time for JP1/AJS3 - Web Operation Assistant, the data transmission time, and rendering time will also increase, causing an increase in the response time from JP1/AJS3 - Manager or JP1/AJS2 - Manager. To prevent this, we recommend that you install JP1/AJS3 - Manager or JP1/AJS2 - Manager and JP1/AJS3 - Web Operation Assistant on separate machines, and use separate machines for performing status acquisition from the Web browser.
(3) Recommended status acquisition method
When you select Display x records per page in the frame for setting status acquisition conditions, if the number of records to be displayed is smaller than the number of units for which statuses are to be acquired, the time required for status acquisition is shorter than the time when Display all is selected. We recommend that you select Display x records per page when performing status acquisition for a large number of units. The following shows the optimal status acquisition method for each display method.
(a) Display all
For optimal status acquisition when selecting Display all in the frame for setting status acquisition conditions, keep the number of units for which statuses are acquired within 1000. This will keep the acquisition time to within 41 seconds.#
- #
- The status acquisition time is the value calculated in (1) Estimating status acquisition time.
(b) Display x records per page
When you select Display x records per page in the frame for setting status acquisition conditions, the fewer the number of records per page, the shorter the status acquisition time. We recommend that you keep this number low when performing status acquisition for a large number of units.
(4) Recommended number of Web browsers connected concurrently
Connecting many Web browsers to a single JP1/AJS3 - Web Operation Assistant may increase the processing time on JP1/AJS3 - Web Operation Assistant, thus causing Web browser response time to increase. We recommend that you restrict the maximum number of Web browsers that can connect to a single JP1/AJS3 - Web Operation Assistant to about 32.
When multiple Web browsers monitor the same JP1/AJS3 - Manager or JP1/AJS2 - Manager concurrently, the load on the monitored JP1/AJS3 - Manager or JP1/AJS2 - Manager and the network greatly increases. As much as possible, avoid concentrating monitoring on the same JP1/AJS3 - Manager or JP1/AJS2 - Manager. If you want to use multiple Web browsers to monitor the same JP1/AJS3 - Manager or JP1/AJS2 - Manager, disable auto refresh for each JP1/AJS3 - Web Operation Assistant window, or set a minimum auto refresh interval of 600 seconds.
Copyright (C) 2010, Hitachi, Ltd.
Copyright (C) 2010, Hitachi Software Engineering Co., Ltd.