8.2.2 Procedure for setting up the environment for a cluster system

Perform the JP1/Base tasks required on the primary node.

For details about the JP1/Base tasks, see the Job Management Partner 1/Base User's Guide.

If you activate both the physical and logical hosts concurrently, make sure that the IP address of the physical host is set as the jp1hosts or jp1hosts2 information on both hosts. Note that you might also need to set the jp1hosts or jp1hosts2 information in other cases, depending on the network configuration or the operating environment. Specify the necessary settings by referring to the notes on cluster system operation and the procedure for setting the jp1hosts or jp1hosts2 information in the Job Management Partner 1/Base User's Guide.

To use JP1/AJS3 Console, set up the physical host.

To use JP1/AJS3 Console Manager and JP1/AJS3 Console Agent, execute the following commands:

JP1/AJS3-Console-installation-folder\bin\ajscmsetup.exe

JP1/AJS3-installation-folder\bin\ajscasetup.exe

You do not have to execute the above commands if the physical host has been set up. However, make sure that the start method for the JP1/AJS3 Console service is set to Automatic.

Execute the jajs_setup_cluster command to set up the logical host, and create the shared files and folder on the shared disk.

Stop the JP1/AJS3 services on all logical hosts and physical hosts. Enable communication by using the IP address of the logical host that is being set up, and then execute the jajs_setup_cluster command.

The following shows the format of the jajs_setup_cluster command you execute:

jajs_setup_cluster 
[-h logical-host-name]
-F scheduler-service-name
-d shared-folder-name
[-n scheduler-service-ID]
[-m {cold|warm|hot}]
{-P port-number-for-the-embedded-database
-I embedded-database-setup-ID
[-M {s|m|l}] |
-S
}

For details about the jajs_setup_cluster command, see jajs_setup_cluster in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

• For the -h option, specify the logical host name set in JP1/Base.

• The -F option is required.

• The -d option must be specified during setup of the primary node environment. For this option, specify a folder on the shared disk in which the shared folder and files will be created. As the shared folder, specified-folder-name\jp1ajs2\ is created, and the definition files on the local disk (files in JP1/AJS3-installation-folder\conf\) are copied to the folder that is created. Before you execute the command, make sure that the shared disk is mounted. If the -d option is omitted, the secondary node environment is set up.

• If the -n option is omitted, the smallest available ID is assumed.

• For the -m option, specify the scheduler service start mode. The specification of this option takes effect only during setup of the primary node environment. If this option is omitted, the value for the scheduler service specified in the DEFAULTSERVICENAME environment setting parameter is inherited.

• Specify the -P and -I options only if you set up the embedded database when you set up the logical host.

  For the -P option, specify the port number for the embedded database used by the logical host.

  For the -I option, specify the setup ID of the embedded database used by the logical host.

  When the -P and -I options have been specified, the embedded database is set up with the following settings:

  - System logging: Not performed

  - System file duplication: Not performed

  - Unload log file: Not used

  - Data area directory: shared-folder\jp1ajs2\embdb\value-specified-for-the-I-option\dbarea

  - Work area directory: JP1/AJS3-installation-folder\embdb\value-specified-for-the-I-option\dbarea

  - Embedded database practical directory: JP1/AJS3-installation-folder\embdb\value-specified-for-the-I-option

  - Database area auto-increment: Enabled

  - System log auto-increment: Enabled

  For the other items, the default values are set.

• For the -M option, specify the database model. If this option is omitted, s (small scale) is assumed.

  You can use this option only when the JP1/AJS3 version is 10-00 or later.

• Specify the -S option only if advanced setup is to be performed for the embedded database.

  If the -S option is specified, setup of the embedded database is skipped during setup of the logical host. Accordingly, the embedded database must be set up separately.

Execute the following command to create the environment for executing jobs:

jpqimport -dt isam -ci execution-environment-configuration-definition-file-for-queue-and-submit-jobs [-mh logical-host-name]

For details about the jpqimport command, see jpqimport in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Perform advanced setup for the embedded database.

If you specified the -S option in step 3, perform advanced setup for the embedded database.

For details about advanced setup for the embedded database, see D. Advanced Setup for the Embedded Database (in a Cluster Configuration).

Specify the JP1/AJS3 Console Manager environment settings.

If JP1/AJS3 Console Manager is being used, the JP1/AJS3 Console Manager environment must be set up for a cluster system.

Note that you do not need to set up the JP1/AJS3 Console Agent environment for a cluster system because setup is performed during setup of the JP1/AJS3 Manager environment for cluster operation.

Execute the following command to set the DATADIRECTORY environment setting parameter to the path to the data directory on the logical host:

jajs_config -k [logical-host-name\JP1AJS2CONSOLEMANAGER] "DATADIRECTORY"="path-to-the-data-directory-on-the-logical-host"

For example, if the logical host name is node0 and the logical host shared folder is e:\shdsk\node0, the command you execute is as follows:

jajs_config -k [node0\JP1AJS2CONSOLEMANAGER] "DATADIRECTORY"="e:\shdsk\node0\jp1ajs2cm\database"

To use queueless jobs, perform the necessary setup, as described below.

Execute the following command:

ajsqlsetup -h logical-host-name -F scheduler-service-name

For details about the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Cautionary note:

Executing the ajsqlsetup command causes the files needed for queueless job execution to be created on the shared disk. Because the files are then checked, make sure that the shared disk is mounted before you attempt to execute this command.

Setting the restrictions for connection sources.

If the setting for whether the connection source restriction function is enabled or the IP addresses permitted to connect are different from those on the physical host, set restrictions for connection sources on the logical host.

Even if there is no problem if the connection source restriction setting is the same on the physical and logical hosts, the IP address of the logical host is required in the connection permission configuration files of the physical host and the logical host on which the connection source restriction function is enabled. The reason for adding the specifications is that the IP address for the logical host is newly assigned as the IP address of the local host.

For details about how to set the connection source restriction function, see 4.4 Settings for restricting connections to JP1/AJS3.

Make sure that the service settings on the logical host are specified correctly.

For example, make sure that the option appropriate for system operation is set for the STARTMODE environment setting parameter.

Stop all embedded database services.

If JP1/AJS3 Database _JFn^# services have been added, check whether the added JP1/AJS3 Database _JFn services have stopped. If these services are running, stop them.

#:

_JFn is the embedded database setup identifier used by JP1/AJS3 services on a logical host.

Change the value of the environment setting parameter EventServerName on the logical host.

If a physical host name is specified in FQDN format for the environment setting parameter EventServerName on the physical host, change the value of the logical host's parameter EventServerName to a logical host name in FQDN format.

For details about the environment setting parameter EventServerName, see 6.3.18 Setting the event server name in the system using DNS.

To use JP1/AJS3 Console, set up the physical host.

To use JP1/AJS3 Console Manager and JP1/AJS3 Console Agent, execute the following commands:

JP1/AJS3-Console-installation-folder\bin\ajscmsetup.exe
JP1/AJS3-installation-folder\bin\ajscasetup.exe

You do not have to execute the above commands if the physical host has been set up. However, make sure that the start method for the JP1/AJS3 Console service is set to Automatic.

After completing the JP1/Base, JP1/AJS3, and JP1/IM tasks on the primary node, save the common definition information to the primary node and then set up the common definition information on the secondary node.

After completing these tasks on the primary node, execute the jbsgetcnf command on the primary node to save the common definition information. Copy the backup file to the secondary node, specify the backup file as an argument of the jbssetcnf command, and then execute the command. The commands to be executed are as follows:

On the primary node:

jbsgetcnf -h logical-host-name > backup-file-name

On the secondary node:

jbssetcnf backup-file-name

Perform the JP1/Base tasks required on the secondary node.

For details about the JP1/Base tasks, see the Job Management Partner 1/Base User's Guide.

If you want to activate both the physical and logical hosts, make sure that the IP address of the physical host is set as the jp1hosts or jp1hosts2 information on the physical host.

Execute the jajs_setup_cluster command to set up the logical host.

The following shows the format of the jajs_setup_cluster command you execute:

jajs_setup_cluster
[-h logical-host-name]
-F scheduler-service-name
[-S|-C embedded-database-settings-file-name]

• For the -h option, specify the logical host name set in JP1/Base.

• For the -F option, always specify the scheduler service name that was specified on the primary node.

• Specify the -S option only if advanced setup is performed for the embedded database.

  If the -S option is specified, setup of the embedded database is skipped during setup of the logical host. Accordingly, the embedded database must be set up separately.

• Specify the -C option if you performed advanced setup during creation of an embedded database on the primary node or if you executed the jajs_setup_cluster command with the -M option specified on the primary node. Before you execute the command with this option specified, you need to copy the embedded database settings file to the secondary node from the primary node.

  Also, for an advanced setup of the embedded database on the executing host, before executing the jajs_setup_cluster command, on the standby host, create the following directories specified when the ajsembdbinstl and ajsembdbbuild commands are executed.

  - Unload log file creation directory

  - Embedded database work area directory

  - Embedded database installation directory

  Note that the unload log file creation directory must also be created on the standby host if you specify a directory on the local disk when setting up the executing host.

  When this option is specified, the embedded database on the logical host is set up with the same settings as for the primary node.

  The following indicates the output destination of the embedded database settings file.

  embedded-database-practical-directory\conf\ajsdbst\ajsembdbsetup-identifier.conf

  You cannot specify this option for an embedded database created in JP1/AJS3 whose version is 09-50 or earlier.

Perform advanced setup for the embedded database.

If you specified the -S option in step 4, perform advanced setup for the embedded database.

For details about advanced setup for the embedded database, see D. Advanced Setup for the Embedded Database (in a Cluster Configuration).

To use queueless jobs, perform the necessary setup, as described below.

Execute the following command:

ajsqlsetup -h logical-host-name -F scheduler-service-name -nc

For details about the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Stop all embedded database services.

If JP1/AJS3 Database _JFn^# services have been added, check whether the added JP1/AJS3 Database _JFn services have stopped. If these services are running, stop them.

#:

_JFn is the embedded database setup identifier used by JP1/AJS3 services on a logical host.

Perform the JP1/Base tasks required on the primary node.

For details about the JP1/Base tasks, see the Job Management Partner 1/Base User's Guide.

If you activate both the physical and logical hosts concurrently, make sure that the IP address of the physical host is set as the jp1hosts or jp1hosts2 information on both hosts. Note that you might also need to set the jp1hosts or jp1hosts2 information in other cases, depending on the network configuration or the operating environment. Specify the necessary settings by referring to the notes on cluster system operation and the procedure for setting the jp1hosts or jp1hosts2 information in the Job Management Partner 1/Base User's Guide.

Execute the jajs_setup_cluster command to set up the logical host, and create the shared files and folder on the shared disk.

The following shows the format of the jajs_setup_cluster command you execute:

jajs_setup_cluster -h logical-host-name [-d shared-folder-name]

• For the -h option, specify the logical host name set in JP1/Base.

• The -d option must be specified during setup of the primary node environment. For this option, specify a folder on the shared disk in which the shared folder and files will be created. As the shared folder, specified-folder-name\jp1ajs2\ is created, and the definition files on the local disk (files in JP1/AJS3-installation-folder\conf\) are copied to the folder that is created. Before you execute the command, make sure that the shared disk is mounted. If the -d option is omitted, the secondary node environment is set up.

To use queueless jobs, perform the necessary setup, as described below.

Execute the following command:

ajsqlsetup -h logical-host-name

For details about the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Cautionary note:

Executing the ajsqlsetup command causes the files needed for queueless job execution to be created on the shared disk. Because the files are then checked, make sure that the shared disk is mounted before you attempt to execute this command.

Specify the settings for restricting connection sources.

If the setting for whether the connection source restriction function is enabled or the IP addresses permitted to connect are different from those on the physical host, set restrictions for connection sources on the logical host.

If the setting for restricting connection sources is the same on the physical and logical host, you do not need to specify this setting on the logical host.

For details about how to set the connection source restriction function, see 4.4 Settings for restricting connections to JP1/AJS3.

Change the value of the environment setting parameter EventServerName on the logical host.

If a physical host name is specified in FQDN format for the environment setting parameter EventServerName on the physical host, change the value of the logical host's parameter EventServerName to a logical host name in FQDN format.

For details about the environment setting parameter EventServerName, see 6.3.18 Setting the event server name in the system using DNS.

After completing the JP1/Base, JP1/AJS3, and JP1/IM tasks on the primary node, save the common definition information to the primary node and then set up the common definition information on the secondary node.

After completing these tasks on the primary node, execute the jbsgetcnf command on the primary node to save the common definition information. Copy the backup file to the secondary node, specify the backup file as an argument of the jbssetcnf command, and then execute the command. The commands to be executed are as follows:

On the primary node:

jbsgetcnf -h logical-host-name > backup-file-name

On the secondary node:

jbssetcnf backup-file-name

Perform the JP1/Base tasks required on the secondary node.

For details about the JP1/Base tasks, see the Job Management Partner 1/Base User's Guide.

If you want to activate both the physical and logical hosts, make sure that the IP address of the physical host is set as the jp1hosts or jp1hosts2 information on the physical host.

Execute the jajs_setup_cluster command to set up the logical host.

The following shows the format of the jajs_setup_cluster command you execute:

jajs_setup_cluster -h logical-host-name

For the -h option, specify the logical host name set in JP1/Base.

To use queueless jobs, perform the necessary setup, as described below.

Execute the following command:

ajsqlsetup -h logical-host-name

For details about the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.