![[Contents]](FIGURE/CONTENT.GIF)
Job Management Partner 1/Software Distribution Description and Planning Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Relay systems can be used to reduce the workload on the managing server and the network in a JP1/Software Distribution system. Using relay systems enables you to manage a large number of clients in a hierarchical configuration. Relay systems can also reduce the number of clients that are connected directly to the managing server and the volume of data to be handled by the network.
For clients in a virtual environment, the number of operation logs collected increases in proportion to the number of login users. Therefore, we recommend that you use an operation mode in which clients are directly connected to the managing server.
We recommend that, in general, a maximum of 200 clients be connected directly to a managing server, although the number depends on the hardware environment. If more than 200 clients are to be managed, we recommend installing relay manager/systems between the managing server and the clients
If you are using the managing server functions on a relay system, we recommend that you connect no more than 1,000 machines directly to that relay system.
If you are not using the managing server functions on a relay system, we recommend that you connect no more than 200 clients directly to that relay system. Once the number of managed clients exceeds 200, you should consider installing another relay manager.
For example, in a configuration in which JP1/Software Distribution is installed in a medium-sized network of 500 clients and managing server functions are used to manage the clients, the following figure depicts a system configuration that could be considered.
Figure 5-5 Guidelines for installing relay managers/systems
![[Figure]](FIGURE/KAN0050.GIF)
You can manage a larger number of clients by increasing the number of relay system hierarchies. However, if there are too many hierarchies, processes such as software distribution may slow down. You should determine an appropriate number of hierarchies by considering hardware acquisition costs as well as network performance.
During setup of a managing server, you can set Number of subsystems that can be connected at one time to limit the number of subsystems that can be connected simultaneously. Similarly, during setup of a relay system, you can set Number of clients that can be connected at one time to limit the number of clients that can be connected simultaneously. You should tune these settings based on data such as the network's workload and server CPU usage factors.
An extremely large number of clients can be managed by setting up an appropriate number of relay system hierarchies. However, hardware costs increase as the number of relay systems increases, because relay systems require better hardware performance than clients. Moreover, if a software package must pass through many relay systems before reaching clients, it may take too long to distribute software. Therefore, you must determine an appropriate number of relay system hierarchies by taking into consideration hardware implementation costs and network performance.
The number of relay systems must be within the following limits:
The following explains the limit on the number of hierarchies based on the host name length.
To execute a job from a managing server, you specify processing-target clients. The route from the managing server to the clients is managed by an address that consists of the host names of all the relay systems and clients involved in the processing. The address format is as follows.
Host names are delimited by an exclamation point (!). If DNS is used, specify a host in the format host-name.domain-name. The maximum address length is 255 bytes, including the delimiters (! and .). You can specify up to 64 bytes for a single host name.
Relay systems must observe these limits. Therefore, very long host names or long DNS domain names will limit the number of relay system hierarchies.
The following figure shows an example of a relay manager/system hierarchy.
Figure 5-6 Example of relay manager/system hierarchy
![[Figure]](FIGURE/KAN0070.GIF)
In this example, the managing server manages the following addresses:
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.