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

[Contents][Glossary][Index][Back][Next]


6.2.1 Hierarchical configurations managed by IM Configuration Management

Using IM Configuration Management, you can define the host relationships and manage the JP1/IM system configuration as a hierarchy.

Defining the system hierarchy in IM Configuration Management allows you to perform the following operations in JP1/IM:

In addition, by using IM Configuration Management, you can manage the JP1/Base profiles on the hosts added to the system hierarchy.

The figure below shows an example of defining a system hierarchy using IM Configuration Management.

Figure 6-10 System hierarchy example (physical configuration)

[Figure]

Two types of 3-tier system configurations can be defined in IM Configuration Management:

Organization of this subsection
(1) Centralized management by an integrated manager
(2) Agent management in separate domains

(1) Centralized management by an integrated manager

In a configuration where the agents in the JP1/IM system are centrally managed by an integrated manager, agent information is collected by relay managers placed in the middle tier.

The relay managers do not provide the IM Configuration Management functionality.

Figure 6-11 System hierarchy example (centralized management by an integrated manager)

[Figure]

The table below describes the operations that can be performed from the integrated manager on the hosts in the above configuration example.

Table 6-5 Operations that can be performed from the integrated manager (with relay managers in the middle tier)

Target host Operation
View the system configuration Change the system configuration View host information View and change profile information
Integrated manager (jp1-sv1) Y Y Y Y
Relay manager (jp1-sv2 and jp1-sv3) Y Y Y Y
Agent Under the integrated manager (jp1-bs1 and jp1-bs2) Y Y Y Y
Under a relay manager (jp1-bs3, jp1-bs4, and jp1-bs5) Y Y Y Y

Legend:
Y: Can be performed.

(2) Agent management in separate domains

In a configuration where the agents are managed by base managers in separate domains, base managers are placed in the middle tier.

The base managers provide the IM Configuration Management functionality.

Figure 6-12 System hierarchy example (agent management in separate domains)

[Figure]

The table below describes the operations that can be performed from the integrated manager on the hosts in the above configuration example.

Table 6-6 Operations that can be performed from the integrated manager (with base managers in the middle tier)

Target host Operation
View the system configuration Change the system configuration View host information View and change profile information
Integrated manager (jp1-sv1) Y Y Y Y
Base manager (jp1-sv2 and jp1-sv3) Y Y Y Y
Agent Under the integrated manager (jp1-bs1 and jp1-bs2) Y Y Y Y
Under a base manager (jp1-bs3, jp1-bs4, and jp1-bs5) Y N N N

Legend:
Y: Can be performed.
N: Cannot be performed.

The table below describes the operations that can be performed from a base manager on the hosts in the configuration example shown in Figure 6-12 System hierarchy example (agent management in separate domains).

Table 6-7 Operations that can be performed from a base manager (base managers in the middle tier)

Target host Operation
View the system configuration Change the system configuration View host information View and change profile information
Integrated manager (JP1-sv1) Y# N N N
Base manager (local host) Y Y Y Y
Base manager (remote host) N N N N
Agent Under the integrated manager (jp1-bs1 and jp1-bs2) N N N N
Under a base manager (local host) Y Y Y Y
Under a base manager (remote host) N N N N

Legend:
Y: Can be performed.
N: Cannot be performed.

#
Viewable only when the integrated manager is a level above the base managers.

[Contents][Back][Next]


[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.