Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1

[Contents][Glossary][Index][Back][Next]


8.2.7 Setting startup of multiple scheduler services on a logical host

To set the startup of multiple scheduler services, first set information such as the names of the scheduler services to be added and then create databases for those scheduler services.

The following describes the procedure for setting the startup of multiple scheduler services on a logical host and the procedure for deleting scheduler services that have been added.

Organization of this subsection
(1) Starting multiple scheduler services on a logical host
(2) Deleting an added scheduler service
(3) Uninstalling a database environment that is no longer necessary

(1) Starting multiple scheduler services on a logical host

The following describes the procedure for enabling startup of multiple scheduler services on a logical host.

(a) Tasks required on the primary node

To specify the necessary settings on the primary node:

  1. In Windows Control Panel, open the Services administrative tool, and stop the following service:
    • The JP1/AJS3 service on the logical host to which you want to add a scheduler service
      Note
      Do not stop the JP1/AJS3 Database services. Make sure that all JP1/AJS3 Database_JF? (?: 1 to 9 or A to Z) services are running. If there are JP1/AJS3 Database_JF? services that are not running, start them.
      Note that you can display all the setup identifiers of the embedded databases for which Database_JF? services must be started by using the ajsembdbidlist command.
      For each setup identifier, execute the ajsembdbstatus command with -s ust -id _JFn (n: 1 to 9 or A to Z) specified to confirm that the embedded database is operating (UNIT-STAT is ONLINE). If the database is not operating, use the ajsembdbstart command with -id _JFn specified to activate it.
  2. Use Explorer or another means to create the following folders on the shared disk:
    • Database folder
    • Folder for temporary files
    • Job information folder
    • Backup information folder
    Make sure that the above folders, other than the backup information folder, are neither folders used by other scheduler services set on the local hosts (the physical host and all logical hosts) nor subfolders of those folders.
  3. Execute the jajs_setup command to add the scheduler service that is to be started.
     
    jajs_setup -a -h logical-host
     -F scheduler-service
     -p service-for-the-port-reporting-the-job-status
     -d database-folder
     -t folder-for-temporary-files
     -j job-information-folder
     -b backup-information-folder
     -n scheduler-service-ID-number
     -D logical-host-shared-folder
     -I setup-identifier
     -P embedded-database-port-number
     
    Example of adding a scheduler service named AJSROOT3 to the logical host LHOST whose shared folder is x:\products:
    jajs_setup -a -h LHOST
     -F AJSROOT3
     -p jp1ajs2report3
     -d "x:\products\jp1ajs2\database\schedule\AJSROOT3"
     -t "x:\products\jp1ajs2\tmp\schedule3"
     -j "x:\products\jp1ajs2\jobinf\schedule3"
     -b "x:\products\jp1ajs2\backup\schedule3"
     -n 3
     -D "x:\products"
     -I _JF2
     -P 22225
     
    For details about the jajs_setup command, see jajs_setup in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
  4. Open the following file with a text editor such as Notepad:
    system-folder\system32\drivers\etc\Services
  5. For the service name of the port that reports the job status specified in step 3, set the port number.
    Example of setting 20248 as the port number:
       jp1ajs2report3 20248/tcp 

    Cautionary note:
    Make sure that the port number you specify does not duplicate any existing port number.
  6. If you want to use queueless jobs, you must perform the setup required for using queueless jobs.
    Execute the following command:
     
    ajsqlsetup -F scheduler-service -h logical-host
     
    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.
  7. Restart the JP1/AJS3 service on the logical host to which you have added the scheduler service.
    The scheduler service is added and started with the specified settings. After the JP1/AJS3 service has been restarted, use JP1/AJS3 - View to confirm that the root job group is displayed with the name of the added scheduler service attached.

(b) Tasks required on the secondary node

To specify the necessary settings on the secondary node:

  1. Set up the embedded database on the secondary node.
    Note: This step is required only if the setup identifier specified during setup on the primary node is an identifier that is not output by the ajsembdbidlist command.
    Execute the following commands:
     
    ajsembdbinstl
     -s directory-containing-the-embedded-database-installation-media
     -id setup-identifier
     -mh logical-host-name
     
    ajsembdbbuild
     -d logical-host-shared-directory\JP1AJS2\embdb\setup-identifier
     -s
     -f
     -mh logical-host
     -eh physical-host-of-the-primary-node
     -ld work-area-directory
     -p embedded-database-port-number
     -i embedded-database-installation-directory
     -id setup-identifier
     -ext_db
     -ext_log
     
    For setup-identifier, logical-host-shared-directory, and embedded-database-port-number, specify the values that are specified on the primary node.
    For details about the commands executed in this step, see 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

    Example of the commands to be executed when you set up an embedded database on logical host LHOST whose logical host shared directory is x:\products, setup identifier is _JF3, and embedded database port number is 22222:
     
    ajsembdbinstl
     -s "c:\Program Files\HITACHI\jp1ajs2\tools\AJS3DB"
     -id _JF3
     -mh LHOST
     
    ajsembdbbuild
     -d "x:products\jp1ajs2\embdb\_JF3"
     -s
     -f
     -mh LHOST
     -eh HOST1
     -ld "c:\Program Files\HITACHI\jp1ajs2\embdb\_JF3\dbarea"
     -p 22222
     -i "c:\Program Files\HITACHI\jp1ajs2\_JF3"
     -id _JF3
     -ext_db
     -ext_log
  2. Set the common definition information of the primary node on the secondary node.
    When you have completed the tasks for the primary node, execute the jbsgetcnf command on the primary node to save the common definition information. Copy the saved file to the secondary node, specify the name of the saved file as an argument, and execute the jbssetcnf command.
    Execute the commands as follows:

    On the primary node:
    jbsgetcnf -h logical-host > backup-file

    On the secondary node:
    jbssetcnf backup-file
  3. Open the following file with a text editor such as Notepad:
    system-folder\system32\drivers\etc\Services
  4. On the secondary host, set the port number that you set in step 5 in (a) above.
    Example of setting 20248 as the port number:
       jp1ajs2report3 20248/tcp 

    Cautionary note:
    Set the same port number as that used on the primary node.

Supplementary note on commands executed to enable startup of multiple scheduler services:
If multiple scheduler services are running and you execute the command without specifying the -F scheduler-service option, the system assumes the command is being executed for the default scheduler service.
You can omit the -F option if you specify a scheduler service name in the AJSCONF environment variable.

(2) Deleting an added scheduler service

When you delete a scheduler service that has been added, you must delete it from both the primary node and the secondary node.

To delete an added scheduler service:

  1. Stop the JP1/AJS3 services.
    Stop all the JP1/AJS3 services on the physical and logical hosts.
    Note
    Do not stop the JP1/AJS3 Database services. Make sure that all JP1/AJS3 Database_JF? (?: 1 to 9 or A to Z) services are running. If there are JP1/AJS3 Database_JF? services that are not running, start them.
    Note that you can display all the setup identifiers of the embedded databases for which Database_JF? services must be started by using the ajsembdbidlist command.
    For each setup identifier, execute the ajsembdbstatus command with -s ust -id _JFn (n: 1 to 9 or A to Z) specified to confirm that the embedded database is operating (UNIT-STAT is ONLINE). If the database is not operating, use the ajsembdbstart command with -id _JFn specified to activate it.
  2. Execute the jajs_setup command to delete the scheduler service.
     
    jajs_setup -e -F scheduler-service
     
    Example of the command executed when the scheduler service to be deleted is AJSROOT3:
    jajs_setup -e -F AJSROOT3
     
    For details about the jajs_setup command, see jajs_setup in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

    On the secondary node, use the jbsunsetcnf command instead of the jajs_setup command.
     
    jbsunsetcnf  -i -h logical-host-name -c JP1AJSMANAGER -n scheduler-service-name
     

    Example of the command for deleting the scheduler service AJSROOT3:
    jbsunsetcnf  -i -h LHOST -c JP1AJSMANAGER -n AJSROOT3
     
  3. Delete the folders that you created when you added the scheduler service.
    Delete the following folders that were created when you executed the jajs_setup command:
    • Database folder specified in the -d option
    • Folder for temporary files specified in the -t option
    • Job information folder specified in the -j option
    • Backup information folder specified in the -b option
      Note
      Do not delete the logical host shared folder specified in the -D option.
  4. Start the JP1/AJS3 services.
    Restart the JP1/AJS3 services that you stopped in step 1, and confirm that the scheduler service has been deleted.

(3) Uninstalling a database environment that is no longer necessary

For details about how to uninstall a database environment that is no longer necessary, see 6.1.1(3) Uninstalling an unnecessary database environment.

[Contents][Back][Next]


[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.