6.1.3 JP1/IM configuration in a cluster system
To run JP1/IM - Manager in a cluster system, you must execute JP1/IM - Manager and JP1/Base under the control of the cluster software and be able to handle failovers. This subsection describes the configuration of JP1/IM in a cluster system.
- Organization of this subsection
(1) Overview of a JP1/IM configuration in a cluster operation system
Product name |
JP1/IM configuration in a cluster system |
---|---|
JP1/IM - View |
|
JP1/IM - Manager |
|
(2) File organization on the shared disk
The files described below are created on the shared disk when you set up JP1/IM - Manager in a logical host environment. These files are required in order to execute JP1/IM - Manager on a logical host.
(a) In Windows
Function |
Type of shared file |
Folder name |
---|---|---|
Central Console |
Definition file |
shared-folder\jp1cons\conf\ |
Log file |
shared-folder\jp1cons\log\ |
|
Temporary file |
shared-folder\jp1cons\tmp\ |
|
History file# |
shared-folder\jp1cons\operation\ |
|
Central Scope |
Definition file |
shared-folder\jp1scope\conf\ |
Log file |
shared-folder\jp1scope\log\ |
|
Temporary file |
shared-folder\jp1scope\tmp\ |
|
Database |
shared-folder\jp1scope\database\ |
|
IM Configuration Management |
Definition file |
shared-folder\JP1IMM\conf\imcf\ |
Log file |
shared-folder\JP1IMM\log\imcf\ |
|
Temporary file |
shared-folder\JP1IMM\tmp\ |
|
IM configuration data and profile data |
shared-folder\JP1IMM\data\imcf\ |
|
IM database |
Database |
user-specified-folder-on-shared-disk\imdb |
#: Event Generation Service processing is output as the history.
(b) In UNIX
Function |
Type of shared file |
Directory name |
---|---|---|
Central Console |
Definition file |
shared-directory/jp1cons/conf/ |
Log file |
shared-directory/jp1cons/log/ |
|
Temporary file |
shared-directory/jp1cons/tmp/ |
|
History file# |
shared-directory/jp1cons/operation/ |
|
Central Scope |
Definition file |
shared-directory/jp1scope/conf/ |
Log file |
shared-directory/jp1scope/log/ |
|
Temporary file |
shared-directory/jp1scope/tmp/ |
|
Database |
shared-directory/jp1scope/database/ |
|
IM Configuration Management |
Definition file |
shared-directory/jp1imm/conf/imcf/ |
Log file |
shared-directory/jp1imm/log/imcf/ |
|
Temporary file |
shared-directory/jp1imm/tmp/ |
|
IM configuration data and profile data |
shared-directory/jp1imm/data/imcf/ |
|
IM database |
Database |
user-specified-directory-on-shared-disk/imdb |
#: Event Generation Service processing is output as the history.
(3) Services and processes of JP1/IM - Manager
JP1/IM - Manager in a cluster operation system executes the services or processes of the logical host.
(a) In Windows
If you set up JP1/IM - Manager in the logical host environment, the services listed below are registered in Windows. To use these services, you must register them in the cluster software.
Displayed name |
Service name |
---|---|
JP1/Console_logical-host-name |
JP1_Console_logical-host-name |
JP1/IM-Manager DB Cluster Service_logical-host-name#1 |
HiRDBEmbeddedEdition_JM<n>#2 |
- #1
-
Registered when IM databases are used.
- #2
-
<n> is a number from 1 to 9, and is the value of LOGICALHOSTNUMBER in the cluster setup information file. For details, 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.
The Displayed name column indicates the name that is displayed by choosing Control Panel, Administrative Tools, and then Services. To use net commands (net start and net stop) to control the services from the cluster software, specify these names in the net commands.
The names in the Service name column are used to register services into the cluster software shown below. Specify these names as service names in MSCS or WSFC.
-
In Windows Server 2003
MSCS (Microsoft(R) Cluster Service)
-
In Windows Server 2012 or Windows Server 2008
WSFC (Windows Server(R) Failover Cluster)
(b) In UNIX
When you execute JP1/IM - Manager on the logical host, the process corresponding to the logical host is run.
The process name is the argument with the logical host name attached. For details about the process names, see B. List of Processes in the Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide.
(4) Communication method
When you set up JP1/IM - Manager on the logical host, the communication method for JP1/IM - Manager is set to what is called the IP binding method. The IP binding method is applied to both logical and physical host environments.
The two types of communication methods are the IP binding method and the ANY binding method. These methods determine how the IP address used for communication is to be allocated (bound) by internal processing.
For details about the communication methods, see the descriptions of the JP1/Base communication methods in the Job Management Partner 1/Base User's Guide. JP1/IM - Manager uses the same communication methods as JP1/Base.
(5) Setting common definition information
When you set up JP1/IM - Manager on the logical host, settings for the logical host are set as common definition information.
The common definition information is managed by JP1/Base in the database that stores JP1 settings. The settings are stored in the format shown below on the local disk of each server.
|
The common definition information for the physical host (JP1_DEFAULT) is stored separately from the common definition information for the logical host. You use the jbssetcnf command to set the information for each physical and logical host, and you use the jbsgetcnf command to read the information.
The common definition information for the logical host must be the same for each server. When you perform setup or if you change the settings, copy the common definition information from the primary server where the settings are specified to the secondary server.
JP1/IM - Manager, JP1/Base, JP1/AJS, and JP1/Power Monitor (06-02 or later) use the common definition information to store the settings.