3.5.1 Evaluating the system configuration

You evaluate the appropriate system configuration according to the service templates and programs that you will be using.

This subsection explains as examples of JP1/AO system configurations a basic system configuration, a cluster configuration, and a configuration linked with JP1/IM - Manager.

Organization of this subsection

(1) Basic system configuration
(2) Cluster configuration
(3) Configuration for linking with JP1/IM - Manager

(1) Basic system configuration

This basic system configuration consists of an IT operation automation server, a Web browser for logging in to JP1/AO, and target devices (connection destinations) to which JP1/AO will connect.

JP1/AO's standard package also includes Common Component that provides a collection of functions available to all Hitachi Command Suite products. Common Component is installed as a part of JP1/AO and provides functions including user management, log output, and various commands.

Figure 3‒4: Example configuration for a basic system

To Page Top

(2) Cluster configuration

JP1/AO supports operation in a cluster system. In a cluster system, if a failure occurs on the executing host that is running JP1/AO, operation can be continued by failing over to the standby host.

A host that is a unit of failover is called a logical host. A logical host name and a logical IP address are assigned to each logical host. The tasks in JP1/AO use the logical IP addresses stored on the shared disk for communications. When physical servers are swapped due to failover, information about the JP1/AO services, the shared disk, and the logical IP addresses is inherited by the standby host. For this reason, it appears to the users as if the server with the same IP address is still running.

Note that JP1/AO supports only the active-standby cluster configuration.

Figure 3‒5: Example configuration for a cluster system

A JP1/AO cluster system has the following characteristics:

The information stored on the shared disk includes JP1/AO's various definition files, log files, and the database used by Common Component.
When window operations are used, the logical host name or logical IP address is used to connect to JP1/AO.

(3) Configuration for linking with JP1/IM - Manager

You can monitor JP1 events centrally by linking your JP1/AO with JP1/IM - Manager.

To link JP1/AO with JP1/IM - Manager, on the IT operation automation server, JP1/Base must be configured to be managed by JP1/IM - Manager.

Figure 3‒6: Example configuration for linking with JP1/IM - Manager

To use single sign-on to log in to JP1/AO from the Tool Launcher window of JP1/IM - View, JP1/AO must be linked with the authentication function of JP1/Base.