Flow of job execution

This section describes the flow of job execution.

During setup of JP1/Software Distribution Manager or JP1/Software Distribution Client (relay system), two of the items that can be specified are Number of subsystems that can be connected at one time and Max. number of subsystems in which jobs can execute concurrently.

To execute a job:

Execute the job from the Remote Installation Manager.
The managing server sends an execution request (notifying the subsystems that a job was executed) to the destinations (targets) specified during job execution.
The subsystems receive the execution request and request the job from the higher system.
The job is downloaded to the subsystems that request the job.
The execution results are sent from the subsystems to the managing server.

The following figure shows the flow of job execution.

Figure 2-47 Flow of job execution

[Figure]

The managing server monitors jobs at one-minute intervals. If there are subsystems that need to be connected, the managing server sends an execution request to them. The maximum number of subsystems to which an execution request can be sent at one time is the value specified for Max. number of subsystems in which jobs can execute concurrently. However, if the number of currently connected subsystems is fewer than the value specified for Number of subsystems that can be connected at one time, the managing server sends only as many execution requests as there are subsystems that can still be connected.

Note that the number of subsystems for the destinations specified in a job refers to only the number of subsystems directly connected to the managing server that executed the job. Therefore, if the distribution route contains relay managers/systems (relay managers or relay systems), the number of relay managers/systems that are directly connected to the managing server is included in the number of subsystems. This number does not include any systems subordinate to the directly connected relay managers/systems.

Organization of this subsection: (1) Job execution example

(1) Job execution example

This section presents an example of job execution.

Conditions: Number of destinations specified for the job: 60; Max. number of subsystems in which jobs can execute concurrently: 20; Number of subsystems that can be connected at one time: 50; Job downloading time: 200 seconds

The following figure shows the flow of job execution under these conditions.

Figure 2-48 Example of the flow of job execution

[Figure]

The execution request is sent to as many subsystems as the value specified for Max. number of subsystems in which jobs can execute concurrently, which is 20.
Number of subsystems currently connected (20) < Number of subsystems that can be connected at one time (50)
The execution request is sent to as many subsystems as the value specified for Max. number of subsystems in which jobs can execute concurrently, which is 20.
Number of subsystems currently connected (40) < Number of subsystems that can be connected at one time (50)
The execution request is sent to the remaining 10 subsystems that can still be connected concurrently.
Number of subsystems currently connected (50) = Number of subsystems that can be connected at one time (50)
No execution request is sent because the number of subsystems currently connected equals the Number of subsystems that can be connected at one time.
Execution results are sent from the subsystems that were connected in step 1.
Number of subsystems currently connected (30) < Number of subsystems that can be connected at one time (50)
Of the 60 destinations specified in the job, the execution request is sent to the remaining 10 subsystems.

All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.

2.9.6 Flow of job execution

(1) Job execution example