To set a managing server for specification of host names, you must first define the managing server in the TCP/IP definition database. A relay system must have definitions of the lower hosts in the TCP/IP definition database.

You specify the settings explained below during setup. When you complete the setup, the system configuration information for relay systems and clients is reported automatically to the higher system.

Managing server

On the System Configuration page, select the Apply the system configuration information automatically check box.

Relay system

On the System Configuration page, select Apply the system configuration information automatically. To change ID group information on the basis of changes in the system configuration, select the Link with system configuration modifications check box under Linkage when system configuration is changed.

Client

On the Connection Destination page, select the Automatically register this computer in the system configuration check box.

The facility for automatic registration of the system configuration enables you to change clients' connection destination from the managing server and apply the change to the system configuration information automatically.

To do this:

1. Specify the following settings during setup:
   

   Managing server

   On the System Configuration page, select the following check boxes:

   - Apply the system configuration information automatically

   - Link with system configuration modifications

   Relay system

   On the System Configuration page, select the following check boxes:

   - Apply the system configuration information automatically

   - Link with system configuration modifications

   Client

   On the Connection Destination page, select the following check boxes:

   - Automatically specify the higher system that requested a job execution as the connection destination

   - Automatically register this computer in the system configuration

2. Change the connection destination of the desired client to the new relay system, and then execute the job.
   Do not move the client in the System Configuration window prior to job execution. The client's connection destination is changed when the job executes; however, information about this client remains in the relay system that had been set before the change as the connection destination.
   

You should note the following points abut registering the system configuration information automatically.

(a) If host IDs are used

If you are newly using host IDs as the ID key for operations, you must execute system version upgrades from the higher system.

If you mistakenly delete system configuration information on the higher system, or if the database is damaged, recover the information from a backup or have the lower systems report their system configuration information files again.

(b) Handling host ID management file errors

If an error occurs in the host ID management file of a client, recover the file by executing the following procedure from the higher system:

1. In the System Configuration or Destination window of the Remote Installation Manager, choose File and then Save to File to output the system configuration information file.
2. Using the host name or IP address of the client in which the error occurred as a key, search the host group file and identify the client in which the error occurred.
   If you use host names as the node identification key, use a host name as the key for searching; if you use IP addresses as the node identification key, use an IP address as the key for searching.
   
3. Save the information about the client in which the error occurred as a host ID management file.
   Set the file name of the host ID management file in netmdmp.hid. The file format of the host ID management file is the same as the file format when you create the system configuration information from a file or create a host group from a file. For details about the file format of the system configuration information file, see 8.1.4 Creating the system configuration information from a file. For details about the file format of the host group file, see 8.2.3 Creating a host group from a file.
   
4. Transfer the created host ID management file to the client in which the error occurred, and restore the file.
   Create the host ID management file in the operating system installation directory.
   
5. Restart the client.

When you create the host ID management file from the host group file, do not mistakenly create the destination of another client as the host ID management file, or change the destination information that was copied from the host group file using a cut-and-paste operation. If you do, the consistency of the host IDs in the system will be lost, and system operation cannot be guaranteed.

(c) If a host name is duplicated when host IDs are not used

If you use host names instead of host IDs as the node identification key, you must assign unique host names to the hosts that use JP1/Software Distribution. If the system configuration information is reported automatically and a host name is duplicated, the system displays log information. Check the log information, and set up the TCP/IP environment again in the client that has the duplicate host name.

• Log information storage location
  The log information is stored in the following directories:
  

  For a managing server

  installation-directory-of-JP1/Software-Distribution-Manager\LOG\NODE.LOG

  For a relay system

  JP1/Software-Distribution-Client-(relay-system)-installation-directory\LOG\NODE.LOG

• Log information contents
  

  WARNING: The host name (host-name) already exists. Processing will continue.

  This message indicates that the client reported information about a host that has the same host name and IP address as another node that is registered in the system configuration information of the managing server (or relay system).

  WARNING: A host with the host name (host-name) already exists, but the existing host has a different IP Address. Processing will continue.

  This message indicates that the client reported information about a host that has the same host name but a different IP address as another node that is registered in the system configuration information of the managing server (or relay system).

• Corrective action
  Check the TCP/IP environment settings of the host that was reported in the log information. If the host name is duplicated, change the host name. After changing the host name, execute client setup again.
  

(d) Notes on building the system

• If the system configuration information of a relay system has not been registered, the configuration information of a lower system may be deleted when the lower system reports system configuration information. Therefore, when upgrading to a higher version of JP1/Software Distribution, upgrade the system components in the following sequence: managing servers, relay systems, and then clients.
• When the facility for automatically registering the system configuration is used, do not modify the system configuration information at the managing server. If the system configuration information has been created by using automatic registration of the system configuration, terminate the setup of JP1/Software Distribution Manager (relay manager) and JP1/Software Distribution Client (relay system) and then apply their system configuration information to the system configuration information of JP1/Software Distribution Manager.
  You must set up JP1/Software Distribution Client (client) when the system configuration information of JP1/Software Distribution Manager (relay manager) and JP1/Software Distribution Client (relay system) has already been applied to JP1/Software Distribution Manager. If the system configuration information has not been applied correctly, use JP1/Software Distribution Manager (central manager) to execute a Get system configuration information job.
  

(e) Notes on editing system configuration information

When system configuration information is registered automatically, do not edit it in the managing server. If editing is necessary, at the Remote Installation Manager, save the system configuration information to a file, back up the file, and then edit the information.

In particular, if you delete a relay system in the system configuration information, the information for the clients that are connected to that relay system will also be deleted. Even if a client whose system configuration information was deleted reports the information again, it will not be recorded in the managing server.

For details about how to output system configuration information to a file and how to create it from a file, see 8.1.4 Creating the system configuration information from a file.

(f) Deleting a destination that was added incorrectly in a relay system

In an environment where the system configuration information is registered automatically, if you add a destination at a relay system by mistake, use the following procedure to delete the destination.

To delete a destination:

1. Choose Start, and then Client Manager. In the displayed Software Distribution - Client Manager dialog box, click the Stop button.
2. At relay system setup, on the System Configuration page, clear the Apply the system configuration information automatically check box.
3. Exit relay system setup.
4. In the Software Distribution - Client Manager dialog box, click the Start button.
5. Start the Remote Installation Manager, and delete the destination that you added incorrectly.
6. Stop the Remote Installation Manager, and in the Software Distribution - Client Manager dialog box, click the Stop button.
7. At relay system setup, on the System Configuration page, select the Apply the system configuration information automatically check box.
8. Exit relay system setup.
9. In the Software Distribution - Client Manager dialog box, click the Start button.