Job Management Partner 1/Integrated Management - Manager Configuration Guide

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


6.3.2 Installing and setting up the logical host

This subsection describes the installation and setup of the logical host for JP1/IM - Manager. It also describes the setup of JP1/Base because JP1/Base must be set up on the same logical host.

Before you start the procedure, check the following information about the cluster system.

Table 6-10 Items to be checked before you install and set up the logical host (UNIX)

Item to be checked Description
Logical host name Name of the logical host that executes JP1
Logical IP address IP address that corresponds to the logical host name
Shared folder Folder on the shared disk that stores a set of files for the JP1 execution environment on the logical host

Additionally, make sure that these items satisfy the prerequisites described in 6.1.2 Prerequisites for cluster operation.

Once you have finished checking the above items, you are ready to start the installation and setup.

Organization of this subsection
(1) Installing
(2) Setup during upgrading
(3) Setting up the physical host environment
(4) Setting up the logical host environment (primary node)
(5) Copying the common definition information
(6) Setting up the logical host (secondary node)

(1) Installing

Install JP1/IM - Manager and JP1/Base on the local disk of both the primary server and the secondary server. If you are upgrading, back up the settings and database before you start the installation (for the backup method, see the manual for the old version).

To install:

  1. Install JP1/Base.
  2. Install JP1/IM - Manager.

Do not install these programs on the shared disk.

(2) Setup during upgrading

If you are upgrading the logical host environment, follow the setup procedure described below. If you are setting up a new environment, see 6.3.2(3) Setting up the physical host environment through 6.3.2(6) Setting up the logical host (secondary node).

(a) Setting up the primary node

If you use the functions of Central Scope, steps 6 through 8 are required. If you do not use the functions of Central Scope, skip steps 6 through 8.

To set up the primary node:

  1. Terminate JP1/IM - Manager.
    Terminate the JP1/IM - Managers in both the physical and the logical host environments.
  2. Set up a logical host environment for JP1/Base.
    If you have upgraded JP1/Base, see the notes about installation and uninstallation in the Job Management Partner 1/Base User's Guide and then perform the setup. If you have not upgraded JP1/Base, there is no need to perform this setup.
  3. Make sure that the shared disk is available.
  4. Execute the jp1cohaverup command.
    /opt/jp1cons/bin/jp1cohaverup -h logical-host-name
  5. If you want to change the location of the event acquisition filter to Event Base Service, execute the jcochafmode command.
    /opt/jp1cons/bin/jcochafmode -h logical-host-name
  6. Check the available disk capacity.
    To upgrade JP1/IM - Manager, you need as much free space on the hard disk as the disk capacity under /var/opt/jp1scope/database/.
  7. Execute the jp1cshaverup command.
    /opt/jp1scope/bin/jp1cshaverup -h logical-host-name -w work-directory
  8. Execute the jbssetcnf command.
    Whether the following functions are enabled or disabled depends on the settings in the old version of JP1/IM - Manager or Central Scope:
    • Completed-action linkage function
    • Monitoring of the maximum number of status change events

If these functions are currently disabled but you want to enable them, execute the jbssetcnf command using the files shown in the table below as arguments.

Table 6-11 Settings files for enabling the functions

File name Description
action_complete_on.conf File for enabling the completed-action linkage function
evhist_warn_event_on.conf File for enabling the function for issuing JP1 events when the number of status change events for the monitoring object exceeds the maximum value (100).

  1. Back up the common definition file.
    /opt/jp1base/bin/jbsgetcnf -h logical-host-name > common-definition-information-backup-file-name

(b) Setting up the secondary node

To set up the secondary node:

  1. Terminate JP1/IM - Manager.
    Terminate the JP1/IM - Managers in both the physical and the logical host environments.
  2. Copy the common definition information backup file that was backed up at the primary node to the secondary node.
    Use a method such as FTP.
  3. Set the common definition information.
    /opt/jp1base/bin/jbssetcnf common-definition-information-backup-file-name

(3) Setting up the physical host environment

At each server, set up the physical host environment for JP1/Base and JP1/IM - Manager.

To set up the physical host environment:

  1. Set up the physical host environment for JP1/Base.
  2. Set up the physical host environment for JP1/IM - Manager.

For details about how to set up JP1/Base, see theJob Management Partner 1/Base User's Guide.

The setup procedure for JP1/IM - Manager is the same as for non-cluster operation. See 2. Installation and Setup (for UNIX). If you will not be using JP1/IM - Manager at the physical host, there is no need to perform this setup.

(4) Setting up the logical host environment (primary node)

(a) Preparations for setup

To prepare for setup:

  1. Make sure that JP1 is stopped.
    Make sure that the processes of JP1/IM and JP1/Base are stopped on the physical host and all logical hosts.
  2. Make sure that the shared disk is available.
    Execute the mount command to make sure that the shared disk is mounted.

(b) Setting up JP1/Base

To set up JP1/Base:

  1. Set up the logical host for JP1/Base (primary node).
    For details about the procedure, see the Job Management Partner 1/Base User's Guide.
  2. Set up a command execution environment for JP1/Base.
    For details, see 2.15 Setting up a command execution environment.

(c) Setting up JP1/IM - Manager

n Setting JP1/IM - Manager (Central Console)

To set JP1/IM - Manager (Central Console):

  1. Execute the setup command for the logical host of JP1/IM - Manager (Central Console).
    /opt/jp1cons/bin/jp1cc_setup_cluster -h logical-host-name -d shared-directory-name
    Specify the logical host name and shared directory name using arguments.
    • logical-host-name (-h option)
      Specify the logical host name that was set in JP1/Base.
    • shared-directory-name (-d option)
      Specify a directory on the shared disk.
      The specified-directory-name/jp1cons/ directory is created and a set of JP1/IM - Manager (Central Console) files for the logical host is created.
    For details about the command, see jp1cc_setup_cluster (UNIX only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
    To achieve correct failover operation, customize the environment settings for JP1/IM - Manager for the logical host.
  2. Setting re-execution of automated actions.
    Execute the following command to set re-execution of automated actions in the event of failover:
    /opt/jp1cons/bin/jcoimdef -r { EXE | OUTPUT | OFF } -h logical-host-name
    Specifying EXE re-executes the actions whose status is Wait, Send, Queue, and Running in the event of failover; specifying OUTPUT outputs those actions to the actions list; specifying OFF executes no processing. Specify this setting according to your evaluation during the system design. This setting is optional.
    For details about the jcoimdef command, see jcoimdef in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

n Setting JP1/IM - Manager (Central Scope)

  1. Execute the setup command for the logical host of JP1/IM - Manager (Central Scope).
    /opt/jp1scope/bin/jp1cs_setup_cluster -h logical-host-name -d shared-directory-name
    Specify the logical host name and shared directory name using arguments.
    • logical-host-name (-h option)
      Specify the logical host name that was set in JP1/Base.
    • shared-directory-name (-d option)
      Specify a directory on the shared disk.
      The specified-directory-name/jp1scope/ directory is created and a set of JP1/IM - Manager (Central Scope) files for the logical host is created.
    For details about the command, see jp1cs_setup_cluster (UNIX only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

n Setting JP1/IM - Manager (IM Configuration Management)

To specify settings for using JP1/IM - Manager (IM Configuration Management):

  1. Execute the setup command for the logical host of JP1/IM - Manager (IM Configuration Management).
    /opt/jp1imm/bin/imcf/jp1cf_setup_cluster -h logical-host-name -d shared-directory-name
    Specify the logical host name and shared directory name using arguments.
    • logical-host-name (-h option)
      Specify the logical host name that was set in JP1/Base.
    • shared-directory-name (-d option)
      Specify a directory on the shared disk.
    When you execute jp1cf_setup_cluster, the following directories are created:
    • shared-directory/jp1imm/conf/imcf
    • shared-directory/jp1imm/tmp
    • shared-directory/jp1imm/log/imcf
    • shared-directory/jp1imm/data/imcf
    For details about the command, see jp1cf_setup_cluster (UNIX only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

n Setting JP1/IM - Manager (IM database)

This subsection describes the setting procedure for using JP1/IM - Manager (IM databases). You must create the IM databases in order to use the integrated monitoring database to manage JP1 events and the IM Configuration Management database to manage the system hierarchy.

To set JP1/IM - Manager (IM database):

  1. Edit the cluster setup information file.
    Prepare a cluster setup information file that contains information about the size of the database area required for creating the IM databases and the database storage directory.
    For details about the settings in the cluster setup information file, see Cluster setup information file (jimdbclustersetupinfo.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  2. Execute the jcodbsetup command to create an integrated monitoring database.
    jcodbsetup -f cluster-setup-information-file-name -h logical-host-name -c online [-q]
    Use arguments to specify the cluster setup information file name, logical host name, setup type, and whether a message asking whether processing is to be continued is to be displayed.
    • cluster-setup-information-file-name (-f option)
      Specify the name of the cluster setup information file that was created in step 1.
    • logical-host-name (-h option)
      Specify the logical host name that was set up at the primary server.
    • Setup type (-c option)
      Specify the setup type (online) of the active host.
    • Whether a message asking whether processing is to be continued is to be displayed (-q option)
      If a message asking about execution of processing is not to be displayed after command execution, specify -q; if the message is to be displayed, do not specify -q.
    For details about the jcodbsetup command, see jcodbsetup in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  3. Execute the jcoimdef command to enable the integrated monitoring database.
    jcoimdef -db ON -h logical-host-name
    For details about the jcoimdef command, see jcoimdef in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  4. Execute the jcfdbsetup command to create an IM Configuration Management database.
    jcfdbsetup -f cluster-setup-information-file-name -h logical-host-name -c online [-q]
    Use arguments to specify the cluster setup information file name, logical host name, setup type, and whether a message asking whether processing is to be continued is to be displayed.
    • cluster-setup-information-file-name (-f option)
      Specify the name of the cluster setup information file that was created in step 1.
    • logical-host-name (-h option)
      Specify the logical host name that was set up at the primary server.
    • Setup type (-c option)
      Specify the setup type (online) of the active host.
    • Whether a message asking whether processing is to be continued is to be displayed (-q option)
      If a message asking about execution of processing is not to be displayed after command execution, specify -q; if the message is to be displayed, do not specify -q.
    For details about the jcfdbsetup command, see jcfdbsetup in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  5. Execute the jcoimdef command to enable the IM Configuration Management database.
    jcoimdef -cf ON -h logical-host-name
    For details about the jcoimdef command, see jcoimdef in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

Setup of the logical host at the primary server is now complete.

Make sure that the JP1/IM - Manager files for the logical host have been created on the shared disk and, if necessary, unmount the shared disk.

(5) Copying the common definition information

Copy the common definition information from the primary server to the secondary server.

The common definition information contains the settings needed to execute JP1/IM - Manager and JP1/Base on the logical host.

To copy the common definition information:

  1. Back up the common definition information at the primary server.
    At the primary node, execute the jbsgetcnf command to back up the common definition information.
    /opt/jp1base/bin/jbsgetcnf -h logical-host-name > common-definition-information-backup-file-name
  2. Copy the backup file from the primary server to the secondary server.
    Use a method such as FTP.
  3. Set the common definition information at the secondary server.
    Use the backup file copied from the primary server to set the common definition information at the secondary server.
    /opt/jp1base/bin/jbssetcnf common-definition-information-backup-file-name

Additionally, if you use the IM databases, the contents of the cluster setup information files at the primary and secondary servers must be identical. Copy the cluster setup information file that was used at the primary server to the secondary server. Store the copy in /etc/opt/jp1imm/conf/imdb/setup/.

(6) Setting up the logical host (secondary node)

(a) Preparations for setup

To prepare for setup:

  1. Make sure that JP1 is stopped.
    Make sure that all processes of JP1/IM and JP1/Base are stopped on the physical host and all logical hosts.

Note that there is no need for the shared disk to be available for use at the secondary server.

(b) Setting up JP1/Base

To set up JP1/Base:

  1. Set up the logical host (secondary node) for JP1/Base.
    For details about the procedure, see the Job Management Partner 1/Base User's Guide.
  2. Set up a command execution environment for JP1/Base.
    For details, see 2.15 Setting up a command execution environment.

(c) Setting up JP1/IM - Manager

n Setting JP1/IM - Manager (Central Console)

To set JP1/IM - Manager (Central Console):

  1. Execute the setup command for the logical host of JP1/IM - Manager (Central Console).
    /opt/jp1cons/bin/jp1cc_setup_cluster -h logical-host-name
    Specify the logical host name by using an argument.
    • logical-host-name (-h option)
      Specify the logical host name that was set up at the primary server.
    For details about the command, see jp1cc_setup_cluster (UNIX only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

n Setting JP1/IM - Manager (Central Scope)

To set JP1/IM - Manager (Central Scope):

  1. Execute the setup command for the logical host of JP1/IM - Manager (Central Scope).
    /opt/jp1scope/bin/jp1cs_setup_cluster -h logical-host-name
    Specify the logical host name by using an argument.
    • logical-host-name (-h option)
      Specify the logical host name that was set up at the primary server.
    For details about the command, see jp1cs_setup_cluster (UNIX only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

Setup of the secondary node is now complete.

n Setting JP1/IM - Manager (IM Configuration Management)

To specify settings for using JP1/IM - Manager (IM Configuration Management):

  1. Execute the setup command for the logical host of JP1/IM - Manager (IM Configuration Management).
    /opt/jp1imm/bin/imcf/jp1cf_setup_cluster -h logical-host-name
    Specify the logical host name by using an argument.
    • logical-host-name (-h option)
      Specify the logical host name that was set in JP1/Base.
    When you execute jp1cf_setup_cluster, the following directories are created:
    • shared-directory/jp1imm/conf/imcf
    • shared-directory/jp1imm/tmp
    • shared-directory/jp1imm/log/imcf
    • shared-directory/jp1imm/data/imcf
    For details about the command, see jp1cf_setup_cluster (UNIX only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

n Setting JP1/IM - Manager (IM database)

This subsection describes the setting procedure for using JP1/IM - Manager (IM database). You must create the IM databases in order to use the integrated monitoring database to manage JP1 events and the IM Configuration Management database to manage the system hierarchy.

To set JP1/IM - Manager (IM database):

  1. Edit the cluster setup information file.
    Prepare a cluster setup information file that contains information about the size of the database area required for creating the IM databases and the database storage directory. Check the contents of the cluster setup information file that was copied from the active host in 6.3.2(5) Copying the common definition information. The settings in the cluster setup information file must be the same as those specified at the primary node.
    For details about the settings in the cluster setup information file, see Cluster setup information file (jimdbclustersetupinfo.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  2. Execute the jcodbsetup command to create an integrated monitoring database.
    jcodbsetup -f cluster-setup-information-file-name -h logical-host-name -c standby [-q]
    Use arguments to specify the cluster setup information file name, logical host name, setup type, and whether a message asking whether processing is to be continued is to be displayed.
    • cluster-setup-information-file-name (-f option)
      Specify the name of the cluster setup information file that was created in step 1.
    • logical-host-name (-h option)
      Specify the logical host name that was set up at the primary server.
    • Setup type (-c option)
      Specify the setup type (standby) of the standby host.
    • Whether a message asking whether processing is to be continued is to be displayed (-q option)
      If a message asking about execution of processing is not to be displayed after command execution, specify -q; if the message is to be displayed, do not specify -q.
    For details about the jcodbsetup command, see jcodbsetup in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  3. Execute the jcoimdef command to enable the integrated monitoring database.
    jcoimdef -db ON -h logical-host-name
    For details about the jcoimdef command, see jcoimdef 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  4. Execute the jcfdbsetup command to create an IM Configuration Management database.
    jcfdbsetup -f cluster-setup-information-file-name -h logical-host-name -c standby [-q]
    Use arguments to specify the cluster setup information file name, logical host name, setup type, and whether a message asking whether processing is to be continued is to be displayed.
    • cluster-setup-information-file-name (-f option)
      Specify the name of the cluster setup information file that was created in step 1.
    • logical-host-name (-h option)
      Specify the logical host name that was set up at the primary server.
    • Setup type (-c option)
      Specify the setup type (standby) of the standby host.
    • Whether a message asking whether processing is to be continued is to be displayed (-q option)
      If a message asking about execution of processing is not to be displayed after command execution, specify -q; if the message is to be displayed, do not specify -q.
    For details about the jcfdbsetup command, see jcfdbsetup in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
  5. Execute the jcoimdef command to enable the IM Configuration Management database.
    jcoimdef -cf ON -h logical-host-name
    For details about the jcoimdef command, see jcoimdef in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

[Contents][Back][Next]


[Trademarks]

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