Set items here for tuning the CPU, memory, and networks. This page is displayed only at the host where the managing server is installed. You should take into account the performance, network configuration, and operating environment of the PC in which the managing server operates, and then set the necessary items. For an overview of tuning, see 6.1.7(2) Adjusting the maximum number of hosts that can be connected concurrently in the Description and Planning Guide. For details about how jobs are executed on the basis of the settings of Number of subsystems that can be connected at one time and Max. number of subsystems in which jobs can execute concurrently, see 2.9.6 Flow of job execution in the Description and Planning Guide.

On this page you can also set the method for managing the results from a function that detects hosts on which JP1/Software Distribution is not installed (hosts without a JP1/Software Distribution installed). For details about the function for detecting hosts without a JP1/Software Distribution installed, see 9.7 Detecting hosts on which JP1/Software Distribution is not installed.

Figure 4-7 Server Customization page

Number of subsystems that can be connected at one time

You can limit the number of subsystems that can be connected at one time. Specifically, this value becomes the number of socket connections. Each socket connection is counted from the time it is established until the time it is released.

Use the formula below to determine the value.

If Embedded RDB is used, the minimum value is 4, the maximum value is 100, and the default value is 30.

If Microsoft SQL Server or Oracle is used, the minimum value is 4, the maximum value is 256, and the default value is 50.

Number of subsystems that can be connected at one time = number of systems that are connected directly + number of Packagers to be connected x 2

If the network traffic is heavy, resulting in many packet collisions, you can reduce the traffic by reducing this value, thereby reducing the number of subsystems that can be connected at one time.

A connection request from a subsystem that exceeds this value will be denied, but once there is room in the number of connections, execution requests are sent again.

If you are using Embedded RDB, you must perform the following operations after completion of setup in order to apply the new settings:

1. Stop the Remote Install Server service.
2. Execute the netmdb_setup.bat command that is stored in JP1/Software-Distribution-installation-directory\BIN.
   Normally, when the netmdb_setup.bat command terminates, it waits for an entry from the keyboard. To enable the command to terminate without receiving an entry from the keyboard, execute the command with the /nopause option specified.
   
3. Start the Remote Install Server service.

Max. number of subsystems in which jobs can execute concurrently

Specify the maximum number of subsystems that can process jobs concurrently. Specifically, this value becomes the number of startup messages the managing server sends at one time to subsystems (in other words, the number of clients that can execute jobs concurrently). If users execute jobs for more clients than the value specified in this field, the system splits the jobs on the basis of the specified value and executes them.

The minimum value is 0, the maximum is 100, and the default is 20. If you specify 0, the managing server no longer sends startup messages to the lower systems, disabling job execution initiated by higher systems as well as startup of target systems using the client control facility. If the size of the files to be distributed is large (10 MB or greater), the LAN load may become high even when only a few clients are connected. Therefore, specify a value that matches the network performance. The result of maximum number of subsystems in which jobs can execute concurrently x package size becomes the amount of data that flows over the network at one time.

Specify a value that does not exceed the value specified in Number of subsystems that can be connected at one time. If the subsystems are connected via a circuit-switched network, specifying a number greater than the number of agreement lines serves no purpose.

Specify when jobs will be deleted

When you delete a job definition or job execution status, the definition or execution status is not deleted immediately; rather, it is deleted at the time you specify for this item. Specify a value in the range from 00:00 to 23:59.

This setting is valid only for completed jobs, jobs that are running, and jobs in which an error occurred. Jobs that are waiting for transmission are deleted as soon as the user specifies deletion, even if a delayed execution time for jobs has been set.

The default setting is that this check box is not selected.

The managing server usually manages multiple clients. Therefore, when job definitions and execution status information are deleted, database deletion takes time, which may affect adversely other operations or place a load on the core jobs. By specifying a delayed execution time, you can avoid such problems, because the system will execute the deletions in batch processing at the specified time.

Monitor startup of subsystems

This check box determines whether or not you wish to change the job execution status to Client not started and to report the status to the managing server when a job cannot be executed because the lower system is not active. The default is for this check box to be selected. A job in Client not started status will be executed during the next polling from the client.

Break down the reason for a starting failure

This option specifies whether or not you wish to break down the cause of an error and report it to the managing server when a lower system results in a startup failure. The default is that this check box is not selected. If you select this check box, the Client not started job execution status is broken down as follows:

Job execution status	Description
Client not started (JP1/Software Distribution is not running)	Startup failure occurred because JP1/Software Distribution was not running.
Client not started (power is off)	Startup failure occurred because the PC power was off.
Client not started	Startup failure occurred for a reason other than the above.

To break down the reason for a startup failure, the Monitor startup of subsystems and Break down the reason for a starting failure check boxes must both be selected.

Monitor file transfer errors of subsystems

This check box determines whether or not you wish to change the job execution status to Communication error and to report the status to the managing server when a communication error occurs while one of the following jobs is transferring files. The default is that this check box is not selected.

• Install package job
• Send package, allow client to choose job
• Transfer package to relay system job
• Transfer registry collection definition job
• Get system information from client job
• Acquire collected files from relay system job
• Get system configuration information job
• Hold report job
• Hold-report release job
• Report message job

This facility monitors transfer only between the managing server specified in the setup and relay systems or clients connected directly under the managing server. If you want to monitor transfers for communication errors in the hierarchy from those relay systems or clients, you must configure them during setup at the relay managers or relay systems. In this manner, you can change the scope of monitoring jobs according to the quality of the communication lines.

Accept suspended/resumed file transfer jobs from sources other than the connection destination

If multiple higher systems are defined as connection destinations, this option determines whether or not you wish to accept Suspend file transfer and Resume file transfer jobs from a system other than the higher system defined as the default connection destination. The default is that this option is not selected.

If you select this option, you can restart file transfer from a different higher system than the one that instructed the suspension. Note that in such a case, at the Remote Installation Manager of the higher system that instructed the suspension, the Suspend file transfer attribute of the lower system remains as being suspended even after the file transfer is restarted.

Hold the newly detected results

The function for detecting hosts at which JP1/Software Distribution has not been installed normally detects any computer on which JP1/Software Distribution has not been installed as a host without a JP1/Software Distribution installed.

If you select this check box and execute detection of hosts without a JP1/Software Distribution installed, a computer on which JP1/Software Distribution has not been installed is detected as being on hold. The default is that this check box is not selected.

You can manually specify any of the detected computers as a host without a JP1/Software Distribution installed. In an environment where Windows computers are mixed with UNIX computers, this enables you to manage them separately, such as by treating only the Windows computers as hosts without a JP1/Software Distribution installed.