9.4.3 Managing the system hierarchy
When you do not use IM Configuration Management, you can use the configuration definition function provided by JP1/Base to handle the system hierarchy (IM configuration) managed by JP1/IM. On the manager, define the host relationships in a configuration definition file (jbs_route.conf), and then apply the configuration definitions by executing the jbsrt_distrib command.
By defining the system hierarchy, you can perform the following operations in JP1/IM:
-
Forward JP1 events to a higher-level host
-
Execute commands from JP1/IM - View
-
Execute automated actions from JP1/IM
-
Collect and distribute definition information
If you wish to use IM Configuration Management to centrally manage the system hierarchy from JP1/IM - Manager, see Chapter 8. System Hierarchy Management Using IM Configuration Management.
- Organization of this subsection
(1) System hierarchy defined with the configuration definition functions
In a 3-tier configuration defined using the JP1/Base configuration management functions, the managers in the middle tier operate as base managers.
You can define the system hierarchy in one operation on the top-level manager, or divide it into a number of parts and define them separately on the respective managers.
Figure 9-10 to Figure 9-12 show examples of a system hierarchy defined by using the configuration management functions.
|
|
|
Define the system hierarchy in the above example in the configuration definition file (jbs_route.conf) as follows:
|
(2) Procedure for defining a system hierarchy with the configuration management functions
The following is an overview of defining a system hierarchy using the configuration management functions:
-
Define the configuration definition file on the manager.
In the configuration definition file (jbs_route.conf), define the system configuration from the manager down to the lower-level managers and agents.
To define the system hierarchy in one operation, define the entire system configuration in the definition file. To define the system hierarchy in parts, write the configuration for each of the base managers and their lower-level hosts.
-
Execute the jbsrt_distrib command on the manager.
This command distributes the definition information to the hosts defined in the configuration definition file, and applies the configuration definition.
To define the system hierarchy in parts, perform steps 1 and 2 on each manager. Then, perform the following procedure at the top-level manager to create the definition for the entire system:
-
Define the configuration definition file on the top-level manager.
Create a configuration definition file (jbs_route.conf) that includes the top-level manager host and the managers directly below it in the hierarchy.
-
Execute the jbsrt_sync command on the top-level manager.
This command collects the configuration information from all managers defined in the configuration definition file, and creates configuration information for the entire system.
To check the system configuration definitions, execute the jbsrt_get command on each host.
For details about the format of the configuration definition file, see Configuration definition file (jbs_route.conf) in the JP1/Base User's Guide.
For details about how to set configuration definition information, see 1.10 Setting the system hierarchy (when IM Configuration Management is not used) (for Windows) if you are using Windows, or 2.9 Setting the system hierarchy (when IM Configuration Management is not used) (for UNIX) if you are using UNIX, in the JP1/Integrated Management 3 - Manager Configuration Guide.