5.5.1 Required environment settings
The following describes the required environment settings for using JP1/Base in a cluster system. For the actual setup procedure, see 5.5.3 Setup.
- Organization of this subsection
(1) Shared directory and files
To ensure that the primary and secondary nodes access the same information at node switching, create the following directory and files on a shared disk:
Shared file type |
Directory for the shared files |
---|---|
Definition files |
shared-directory/jp1base/conf/ |
Log file |
shared-directory/jp1base/log/ |
Event server settings file |
shared-directory/event/ |
Assign a shared directory to each logical host. You must not assign the same directory to different logical hosts. In each shared directory assigned to the logical host, create the shared files and directories.
An example of creating a directory on a shared disk is shown below.
- Example: Specify /shdsk/node0 as a shared directory for logical host node0.
/shdsk/node0/jp1base/conf/ /shdsk/node0/jp1base/log/
The event service can be set independently to run in cluster mode. However, if you set up the environment according to 5.5.3 Setup, JP1/Base automatically specifies the logical host names in the event server index file (index) and creates the event server settings file (conf) in a shared directory.
(2) Communication protocol
When you set up the JP1/Base environment to support a cluster system, the socket binding method used in TCP/IP communication is automatically changed to IP addressing. This change affects settings for the logical hosts to be created and their constituent physical hosts. For details on the JP1/Base communication protocol, see 2.10 Communication protocols of JP1/Base.
(3) Common definition information
In JP1/Base and the programs that require JP1/Base (JP1/IM, JP1/AJS, or JP1/Power Monitor), information about the logical hosts is set as common definition information in the local disk. You must therefore set identical information about each logical host.
The common definition information is updated when you:
-
Change the common definition information for JP1/Base and the programs that require JP1/Base (JP1/IM, JP1/AJS, or JP1/Power Monitor).
-
Change the user mapping information by using the jbsmkumap command, the jbssetumap command, or the jbsrmumap command.
-
Change the authentication server by using the jbssetusrsrv command.
-
Delete the common definition information on the logical host by using the jbsunsetcnf command.
-
Change the jp1hosts information by using the jbshostsimport command.
-
Set the command execution environment by using the jcocmddef command.
When you change the common definition information, make the information consistent on all servers by following the procedures in 5.6 Follow-up tasks when changing settings in a cluster environment.
(4) Registering with clustering software
When starting or stopping the logical host, the clustering software controls the starting, stopping, assigning, and releasing of the services, shared disks, and logical IP addresses. The clustering software initially has functionality for controlling the shared disks and logical IP addresses. It does not, however, have functionality for controlling the services, therefore, you must register the service control functionality with the clustering software.
The following table shows the functionality you register with the clustering software and the command used for each function:
Functionality |
Description |
Command |
---|---|---|
Start |
Start JP1/Base. |
jbs_start.cluster logical-host-name |
Stop |
Stop JP1/Base. |
jbs_stop.cluster logical-host-name |
Operation monitoring |
Monitor whether JP1/Base is operating normally. Or, check whether JP1/Base is currently operating normally. Some clustering software does not support this functionality. Register this functionality only when a failover is required upon a failure in JP1/Base. |
jbs_spmd_status -h logical-host-name |
Kill |
Kill JP1/Base and release the resources it has been using. |
jbs_killall.cluster logical-host-name |
Within the jbs_start.cluster and jbs_stop.cluster commands, the following commands are executed:
- Commands executed in the jbs_start.cluster command:
-
-
jevstart logical-host-name (command for starting the event service)
-
jbs_spmd -h logical-host-name (command for starting JP1/Base processes other than the event service)
-
- Commands executed in the jbs_stop.cluster command:
-
-
jevstop logical-host-name (command for stopping the event service)
-
jbs_spmd_stop -h logical-host-name (command for stopping JP1/Base processes other than the event service)
- Note
-
-
The logical-host-name argument in the jevstart and jevstop commands corresponds to the event server name in descriptions of the event service in this manual.
-
The automatic start script for logical hosts (jbs_start.cluster) performs an unsetup of the locale settings of LC_ALL, LC_COLLATE, LC_CTYPE, LC_MONETARY, LC_NUMERIC, LC_TIME, and LC_M ESSAGES by default.
-
-