7.1.2 Prerequisites for cluster operation (for Windows)
JP1/IM - Manager runs in a logical host environment in a cluster system and supports failover. The prerequisites for running JP1/IM - Manager in a logical host environment are the allocation and release of the shared disk and logical IP addresses, and normal control of operation monitoring by the cluster software.
- Important
-
Depending on the system configuration and environment configuration, the cluster software supported by JP1/IM - Manager might not always meet the prerequisites described here. Evaluate the system configuration and environment configuration so that the prerequisites are satisfied.
- Organization of this subsection
(1) Prerequisites for the logical host environment
When JP1/IM - Manager is to be run in a logical host environment, the prerequisites with respect to logical IP addresses and the shared disk that are described in the table below must be satisfied.
Logical host component |
Prerequisites |
---|---|
|
|
|
If any the above conditions are not satisfied, problems such as the following might occur during JP1 operation:
-
Data written by the primary node becomes corrupted during failover
Normal operation cannot be achieved due to problems with JP1, such as errors, data loss, or startup failure.
-
Recovery processing is disabled due to a LAN board failure
JP1 cannot operate normally due to communication errors until the LAN boards are swapped or a failover to another server is achieved by a means such as the cluster software.
(2) Prerequisites for the physical host environment
In a cluster system where JP1/IM - Manager is run on a logical host, the physical host environment for each server must meet the prerequisites described below.
Physical host component |
Prerequisites |
---|---|
Server core |
|
Disk |
|
Network |
|
OS, cluster software |
|
Service |
|
(3) JP1's support range
When JP1 is run on a logical host in a cluster system, the range controlled by JP1 is JP1 itself. Control of the logical host environment (shared disk and logical IP addresses) and the JP1 startup and termination timing depend on the control by the cluster software.
If the prerequisites for the logical host environment and physical host environment discussed above are not satisfied, or there are problems in the control of the logical host environment, there will be problems with the JP1 operations as well. In such a case, the problems must be dealt with by the OS and cluster software that controls the logical host environment.
(4) Physical host names
When IM databases are used, a physical host name must be a character string of not more than 32 characters consisting of only one-byte alphanumeric characters, -, and . (period).
(5) Logical host names
Note the following when you specify a logical host name in JP1/IM - Manager:
-
The logical host name must be specified in the hosts file or on the name server to enable TCP/IP communication.
-
JP1/Base, the prerequisite product, must be able to handle the logical host name. For details, see the JP1/Base User's Guide.
-
When IM databases are used, a logical host name must be a character string of not more than 32 characters consisting of only one-byte alphanumeric characters and one-byte hyphens (-).
When specifying logical host in JP1/IM - Agent, check the following points.
-
The logical host name must be specified in the hosts file or on the name server to enable TCP/IP communication.
-
Logical host name must be 63 characters or less and consist of single-byte alphanumeric characters and hyphens (-).
(6) Other Conditions
When using JP1/IM - Agent, note the following:
-
When installing JP1/IM - Agent on primary server and secondary server in Windows, the installation destination must be the same folder.
-
When installing JP1/IM - Agent on primary server and secondary server, make version the same.
-
When installing the SAP system log extract command, perform the same setup on the running server and the standby server. The I/O file # of the SAP system log extract command, must be placed on the shared disk.
- #
-
The command input and output files are as follows.
-
Environment parameters file
-
Log file of SAP system log extract command
-
Trace file of SAP system log extract command
-
Trace file output by RFC library
-