6.7.1 Workload on JP1/AJS3 - Manager
Depending on the number of units that the API operates on and the system configuration, the workload on JP1/AJS3 - Manager might be increased. The following describes what kind of operations might increase the workload on JP1/AJS3 - Manager, and the actions to be taken to solve the problems.
-
When many users execute processing at the same time
When multiple users issue API requests to the scheduler service of the same JP1/AJS3 - Manager program, multiple processing tasks are executed on JP1/AJS3 - Manager. If too many APIs are requested for processing, the processing takes time or an excessive workload is placed on JP1/AJS3 - Manager. In such a case, limit the number of users who can perform operations (limit the maximum number of simultaneous sessions). For details about the maximum number of simultaneous sessions, see 20.4.2(21) CDMAXSESSION in the JP1/Automatic Job Management System 3 Configuration Guide.
-
When API requests are frequently issued
If API requests are issued frequently, processing must be executed frequently on APIs, so workload is continuously placed on JP1/AJS3 - Manager. Therefore, if user applications repeatedly issue API requests in your system, re-design the system so that API requests are not frequently issued.
-
When there are many units and generations
If there are many units under the unit for which API requests are to be issued, or if the units have many generations, a heavy load might be placed on JP1/AJS3 - Manager for API processing. The APIs that might place a load on JP1/AJS3 - Manager and the operation conditions are described below. For each API, consider the load on JP1/AJS3 - Manager, and determine the number of units to be processed and the number of generations.
-
Fixed execution registration API
If there are many units under the root jobnet, or if many generations are subject to execution registration, a heavy load might result.
-
Registration cancellation API
If execution registration has been performed for many generations, or if there are many units in the target jobnet, a heavy load might result.
-
Unit list acquisition API
If many units are subject to acquisition, a heavy load might result.
-
- Supplementary note
-
You can set a connection timeout for when it takes time to establish a connection between the Web Console server and JP1/AJS3 - Manager or to receive a response. The timeout time can be set in the network-settings file in the Web Console server, or by using the CDSESSIONTIMEOUT environment setting parameter of JP1/AJS3 - Manager. The following values are set by default:
- Network-settings file in the Web Console server
-
Connection timeout time: None
Receive timeout time: 180 seconds
- CDSESSIONTIMEOUT environment setting parameter of JP1/AJS3 - Manager
-
Connection timeout time: 180 seconds
For details about the network-settings file, see 3.4.4 Details on the settings in the network-settings file (ajscd_ajs3web.properties) in the JP1/Automatic Job Management System 3 Configuration Guide.
For details about the CDSESSIONTIMEOUT environment setting parameter, see 20.4.2(104) CDSESSIONTIMEOUT in the JP1/Automatic Job Management System 3 Configuration Guide.