Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide

6.1.2 Registering hosts

Using IM Configuration Management, you can register hosts in the network as hosts to be managed in the IM Configuration Management database.

By registering hosts, you can then perform the following operations in IM Configuration Management:

Add a host to the system hierarchy.

Check whether services on a host are active.

When IM Configuration Management starts, if there are no hosts registered in its database, information about the host (physical or logical host) running IM Configuration Management is registered automatically in the database.

Note that when the jcfimport command is executed on the manager running IM Configuration Management, the host information relating to that manager is overwritten.

To register host information, use the Register Host window.

The figure below shows the flow of processing when registering hosts in IM Configuration Management.

Figure 6-1 Registering hosts in IM Configuration Management

When you register hosts, the information entered in the Register Host window is saved to the IM Configuration Management database. At this time, the IP address set for each host is registered automatically.

The figure below shows an example of the host information registered in the database at host registration.

Figure 6-2 Example of host information registered in the IM Configuration Management database at host registration

Any unregistered hosts in the system hierarchy are automatically registered in the IM Configuration Management database when configuration definition information is collected from the hosts.

Automatically acquiring host information from the system hierarchy definitions

Host information contained in the system hierarchy definitions (configuration definition information) is automatically registered in the IM Configuration Management database when you perform any of the following operations:

Acquire the system hierarchy by using IM Configuration Management - View.
For details, see 6.2.2 Acquiring the system hierarchy.

Load the system hierarchy from a configuration definition file by using IM Configuration Management - View.
For details, see 6.2.5(6) Loading the system hierarchy.

Import the system hierarchy on the server running IM Configuration Management.
For details, see 6.5.3 Importing IM Configuration Management information.

If the number of hosts to be read from the system hierarchy exceeds the maximum number of hosts that can be registered in the IM Configuration Management database, only hosts equal to the maximum number are registered in the database.

The following checks are performed on the acquired system hierarchy when the acquisition is performed by IM Configuration Management - View is used:

Whether the local host name in the acquired system hierarchy matches the local host name registered in the IM Configuration Management database. If different, the following message is output and processing is canceled: Collection of the IM configuration failed because the local host name "host1" is different from the registered host name "host2".

Whether two or more hosts with the same host name exist in the acquired system hierarchy. If so, a message reports that the host name is duplicated and processing is canceled.

After these checks, if there is no higher-level host in the acquired system hierarchy, the configuration type of the local host changes to Integrated manager. If there is a higher-level host in the acquired system hierarchy, the configuration type of the local host changes to Relay manager.

When you import the system hierarchy on the server running IM Configuration Management, the hosts' IP addresses are not registered in the IM Configuration Management database even if set in the export file (host_input_data.csv).

[Contents][Back][Next]

[Trademarks]