17.2.1 Environment setup items for a cluster system

(1) Creating shared files on the shared disk

To inherit information when the primary and secondary nodes are switched, create directories and files on the shared disk. The table below lists the information that is created in the shared directories on the shared disk and the names of the directories.

Table 17‒1: Information created in the shared directories and the names of the directories (JP1/AJS3 - Manager)

Information created in the shared directories	Directory name#1
Environment settings file	shared-directory-name/jp1ajs2/conf
Job execution environment file	shared-directory-name/jp1ajs2/database
Job information file	shared-directory-name/jp1ajs2/jobinf
Log file	shared-directory-name/jp1ajs2/log
System file	shared-directory-name/jp1ajs2/sys
Work file	shared-directory-name/jp1ajs2/tmp
Backup file	shared-directory-name/jp1ajs2/backup
Embedded database data area file	shared-directory-name/jp1ajs2/embdb#2

#1:

These directories are automatically generated when the jajs_setup_cluster command is executed in the shared directory specified in the -d option of the jajs_setup_cluster command.

#2:

This directory is not created when the -S option is specified for the jajs_setup_cluster command.

Table 17‒2: Information created in the shared directories and the names of the directories (JP1/AJS3 - Agent)

Information created in the shared directories	Directory name#
Environment settings file	shared-directory-name/jp1ajs2/conf
Log file	shared-directory-name/jp1ajs2/log
System file	shared-directory-name/jp1ajs2/sys
Work file	shared-directory-name/jp1ajs2/tmp

#:

These directories are automatically generated when the jajs_setup_cluster command is executed in the shared directory specified in the -d option of the jajs_setup_cluster command.

Table 17‒3: Information created in the shared directories and the names of the directories (JP1/AJS3 - Web Console)

Information created in the shared directories	Directory name#
User environment settings file	shared-directory-name/jp1ajs3web/sys/user
Environment settings file	shared-directory-name/jp1ajs3web/conf
Log file	shared-directory-name/jp1ajs3web/log
Work file	shared-directory-name/jp1ajs3web/tmp

#:

These directories are automatically generated when the ajswebsetup command is executed in the shared directory specified in the -d option of the ajswebsetup command.

As the shared directory, specify one of the directories specified during setup of the logical host environment for JP1/Base. Do not assign the same directory to more than one logical host. Create the directories and files to be shared under the directory assigned to each logical host.

Example:

The following example shows the directories created when the shared directory of logical host node0 is /shdsk/node0.

/shdsk/node0/jp1ajs2/conf
/shdsk/node0/jp1ajs2/database
/shdsk/node0/jp1ajs2/jobinf
/shdsk/node0/jp1ajs2/log
/shdsk/node0/jp1ajs2/sys
/shdsk/node0/jp1ajs2/tmp
/shdsk/node0/jp1ajs2/backup
/shdsk/node0/jp1ajs2/embdb

To Page Top

(2) Setting the communication method

Select the method to be used to bind an IP address to the TCP/IP socket that will be used for communication. To start multiple scheduler services in the cluster system, use the method that binds all hosts, including the physical hosts, to one IP address. For the operation described in 17.2.2 Procedure for setting up a cluster system environment (in UNIX version of JP1/AJS3 - Manager), the method used to bind to an IP address can be set automatically.

Set the port number when you are using the multi-startup setting of the scheduler service to add a port number for the service name of the job-status notification port.

To Page Top

(3) Setting common definition information

JP1/AJS3, JP1/Base, and JP1/IM have information specific to each logical host on the local disks of both physical hosts. Because the information is used as common definition information, it must be identical on both physical hosts.

The common definition information includes the environment settings file and job execution environment file.

To Page Top

(4) Obtaining server certificates

To use SSL communication on the logical hosts in a cluster system, obtain a server certificate for each logical host under the name of the host name of the logical host. If the host name of a physical host is used to obtain a server certificate, the server certificate cannot be used for the corresponding logical host. Note, however, that the same server certificate can be used for both a physical host and a logical host in the following cases:

• When the logical host name of the logical host is written as a subject alternative name (SAN) in the server certificate for the physical host

• When the server certificate for the physical host is a wildcard certificate and the host name written in the certificate is the same as the logical host name of the logical host

For details about how to set up SSL communication for, for example, obtaining server certificates, see 21.4 Setting up the communication using SSL.

To Page Top