1.3.6 Flow of job execution
This section describes the flow of job execution.
You can specify Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently and Number of JP1/IT Desktop Management 2 - Agent instances that can execute jobs concurrently during JP1/IT Desktop Management 2 - Manager setup and in the agent configurations.
-
The job is executed from Remote Install Manager.
The managing server sends execution requests to the destinations specified during job execution. This notifies the lower systems that a job has been executed.
-
The lower systems receive the execution requests, and request the job from the higher system.
-
The job is downloaded to the lower systems that requested it.
-
The lower systems report the execution results to the managing server.
The following figure shows the flow of job execution:
|
The managing server monitors jobs at one-minute intervals. If there are lower systems that require a connection, the managing server sends an execution request to those lower systems. The maximum number of lower systems to which the managing server can send an execution request at one time is the value of Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently. If the number of connected lower systems is less than the value specified for this parameter, the managing server sends only as many execution requests as there are lower systems that can establish new connections.
Note that the number of lower systems corresponding to the destinations specified in a job refers to only the number of lower systems directly connected to the managing server that executed the job. Therefore, if the distribution route contains relay systems and management relay servers, the number of lower systems includes only the number of relay systems and management relay servers that are directly connected to the managing server. It does not include lower systems connected to these relay systems and management relay servers.
- Organization of this subsection
(1) Example of job execution
An example of job execution is described below.
- Conditions
-
Number of destination specified for job: 60
Value of Number of JP1/IT Desktop Management 2 - Agent instances that can execute jobs concurrently: 20
Value of Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently: 50
Job download time: 200 seconds
The following figure shows the flow of job execution with these conditions:
|
-
Execution requests are sent to 20 destinations, the number specified for Number of JP1/IT Desktop Management 2 - Agent instances that can execute jobs concurrently.
Number of connected subsystems (20) < Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently (50)
-
Execution requests are sent to another 20 destinations, the number specified for Number of JP1/IT Desktop Management 2 - Agent instances that can execute jobs concurrently.
Number of connected subsystems (40) < Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently (50)
-
Execution requests are sent to the remaining 10 destinations permitted by the number specified for Number of JP1/IT Desktop Management 2 - Agent instances that can execute jobs concurrently.
Number of connected subsystems (50) = Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently (50)
-
No further execution requests are sent because the number of connected subsystems is equivalent to the value of Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently.
-
The subsystems that were connected in step 1 report their execution results to the managing server.
Number of connected subsystems (30) < Number of JP1/IT Desktop Management 2 - Agent instances that can connect to the management server concurrently (50)
-
Of the 60 destinations specified in the job, the execution request is sent to the remaining 10 subsystems.