Job Management Partner 1/Software Distribution Setup Guide

[Contents][Glossary][Index][Back][Next]

4.3.2 Report To Higher System page

On this page, you set the timing of sending the result files received from lower systems to the managing server.

Figure 4-26 Report To Higher System page

[Figure]

Organization of this subsection
(1) Send the result file to the server
(2) Execute, in parallel, the receiving of jobs from and the sending of result files to the higher system
(3) Report the split package distribution execution status of the lower system to the higher system
(4) Specify whether to relay operation monitoring history to the higher system

(1) Send the result file to the server

Set the timing of sending the result files received from lower systems to the managing server. The default selection is When result is received from managed hosts.

When result is received from managed hosts
Sends the result file to the higher system whenever the file is received from a lower system. Select this option if you want to check the job execution result immediately.
Selecting this causes JP1 to issue an event when the client performs one of the following unauthorized operations.
  • Connecting to a device whose operation is suppressed
  • Starting up suppressed software
  • Execution of a print operation by a client for which printing operations are suppressed

After a specific interval
Sends the result file received from a lower system to the higher system at specific intervals. The job execution result cannot be checked until the file transmission is executed.

If When result is received from managed hosts is selected, transmission costs may increase in network environments in which the number of connections between relay systems and higher systems affects transmission costs. It can also affect how efficiently result files are transmitted.

If 200 or more clients are located under the relay system and large numbers of jobs are executed from higher system targeted at clients, or when notification files are sent frequently from lower systems, select After a specific interval so that notification files are sent to higher systems at set intervals.

If you select After a specific interval, the relay manager sends result files according to the Maximum retry count and Retry interval settings you specified for Resend the remaining installation result files on the Retry Communication page of the Detailed Information Setup dialog box. If you select After a specific interval without selecting Resend the remaining installation result files, the relay manager sends result files with Maximum retry count and Retry interval set automatically to the default values.

(2) Execute, in parallel, the receiving of jobs from and the sending of result files to the higher system

Normally, you can establish only one connection from a relay manager to the higher system. This means you can usually not send results files to the higher system while receiving jobs nor receive jobs from the higher system while sending results files.

By enabling this option, you can concurrently receive (download) jobs from the higher system (central manager or relay manager) to which the local system connects and send (upload) results files to it. The default is that this check box is not selected.

When you select this check box, the relay manager is provided with two connections to the higher system. These connections make it possible to perform downloading and uploading concurrently. However, because the number of connections to the higher system increases, the load on the network also increases. In addition, the number of client connections to the relational database also increases. Thus, you should select this option only if the network environment has sufficient capacity.

Estimating the number of subsystems that can be connected concurrently

When this option is selected, the relay manager is provided with two connections to the higher system. Therefore, during setup of the higher system (central manager), it is necessary to increase the value of Number of subsystems that can be connected at one time. Use the following formula to determine the appropriate value:

Number of subsystems that can be connected at one time
= number of relay systems to be directly connected x 2
+ number of clients to be directly connected
+ number of Remote Installation Managers to be concurrently connected
+ number of packagers to be concurrently connected x 2

If Microsoft SQL Server or Oracle is used on the higher system, you must also increase the number of clients that can connect to the relational database. The method for determining the number of clients connected to the relational database depends on the database in use (Oracle or Microsoft SQL Server).

For Oracle
For details about how to estimate the value, see 7.3.3(2) Tuning the initialization parameter file.
Determine the number of clients that can be connected using the number of concurrent client or relay system connections as the Number of subsystems that can be connected at one time.

For Microsoft SQL Server
For details about how to estimate the value, see 7.3.2(2) Tuning the database environment.
Determine the number of clients that can be connected using the number of concurrent client or relay system connections as the Number of subsystems that can be connected at one time.

(3) Report the split package distribution execution status of the lower system to the higher system

If you use split distribution of packages, select this check box to report the distribution progress at the lower systems to the higher system. The default is that this check box is not selected.

When you select this check box, you can use Remote Installation Manager's Job Status window on the higher system to check the status of split distribution that is underway at systems positioned lower than the relay manager/system.

For details about checking the status of split distribution in the Job Status window, see 8.4.3 Items displayed in the Job Status window in the manual Administrator's Guide Volume 1.

Note that when this option is enabled, the network's workload increases due to the increase in the volume of communication associated with reporting the execution status of split distribution from the lower systems to the higher system. This setting is therefore recommended only for a network environment with sufficient capacity. Do not select this check box if the higher system's version is 07-50 or earlier, or if it is UNIX, because the execution status of split distribution in the lower systems cannot be checked even when this option is selected.

(4) Specify whether to relay operation monitoring history to the higher system

The destination of operation information depends on whether the operation monitoring policy is applied via the relay manager, or by executing a job from the relay manager. This option enables you to specify whether the operation information reported from lower systems is to be managed by the relay manager, or also reported to the higher system. The default is that this check box is not selected.

(a) Operation when the check box is selected

The following describes how this operation is handled depending on whether Relay or Do not relay is selected.

Relay
Operation information that is reported periodically from the client or that is acquired by the Get software monitoring information from the client job is always reported to the higher system via the relay manager.
If the policy is applied from the higher system, the operation information is sent to the higher system that applied the policy. If the policy is applied from the relay manager, the operation information is sent to the higher system at the connection destination of the relay manager.
You can also select the information you want reported to the higher system. The following information may be selected:
  • Software operating information
  • Startup suppression information
  • Operation histories
If Relay is selected, choose at least one of the above types of information. The default is that all check boxes are selected.
Notes
To issue a JP1 event when the client performs one of the following unauthorized operations, select the Startup suppression information check box.
  • Connecting to a device whose operation is suppressed
  • Starting up suppressed software
  • Execution of a print operation by a client for which printing operations are suppressed
If the following check boxes are selected on the Event Service page of server setup for both the managing server and the relay manager, a JP1 event with the same content is reported to JP1/IM.
  • Unauthorized operation event in operation monitoring
  • Startup suppression information
To prevent this, specify one of the following settings:
  • Select Do not relay
  • Clear the Startup suppression information check box
  • Clear the Unauthorized operation event in operation monitoring check box on the Event Service page of the managing server and the relay manager.

Do not relay
Operation information reported from lower systems is not reported to any system above the relay manager that specified this setting.
For example, when a Get software monitoring information from the client job is executed from the higher system, the operation information obtained from the lower systems is sent to the relay manager, not to the higher system.
(b) Operation when the check box is not selected

Information that is reported periodically from the client or operation information that is acquired by the Get software monitoring information from the client job is sent to the system that applied the operation monitoring policy (the system that executed the Set the software monitoring policy job).

For example, if the policy is applied from the higher system, the operation information is sent to the higher system even if the Get software monitoring information from the client job is executed from the relay manager.

Note
When this check box is not selected and the Unauthorized operation event in operation monitoring check box on the Event Service page of server setup is selected in both the managing server and the relay manager, both systems may report identical JP1 events to JP1/IM. To prevent this, make sure the Unauthorized operation event in operation monitoring check box in the Event Service page of either the managing server or the relay manager is not selected.