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

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

Appendix D.2 Setting up an embedded database (on the primary node)

This section describes the procedures for installing an embedded database, setting up the environment for operating the embedded database, and setting up the embedded database on the primary node in a cluster configuration.

Organization of this subsection
(1) Tasks required before installing the embedded database
(2) Installing an embedded database
(3) Setting up the embedded database environment
(4) Environment setting parameter settings
(5) Setting up the scheduler database in an embedded database environment
(6) Setting up multiple scheduler databases in one or more embedded database environments
(7) Setting up an embedded database again
(8) Uninstalling an embedded database

(1) Tasks required before installing the embedded database

Review the tasks required before installing the embedded database. For details about these tasks, see C.2(1) Tasks required before installing the embedded database.

(2) Installing an embedded database

To install an embedded database, you must perform the procedure described in C.2(2) Installing an embedded database. If you plan to install the embedded database on the primary node in a cluster configuration, read the following notes before starting the installation.

Cautionary notes:
  • When you install the embedded database, install it on the local disk of the primary node. Specify the same drive name and the same folder name for both the primary and secondary nodes.
  • If you create a physical host and multiple logical hosts on the same machine and use different embedded databases, specify unique setup identifiers to avoid duplication conflicts.

Also check the detailed information about installation. For details about installation, see C.2(2) Installing an embedded database.

(3) Setting up the embedded database environment

To set up the embedded database environment:

  1. Stop services.
    Stop all services that access the scheduler database. Such services include the JP1/AJS3, and JP1/AJS3 Console Agent services on the physical host and all logical hosts.

  2. In UNIX, delete the environment setting information from the shared memory.
    Use the ajsshmdel command to delete the environment setting information in the shared memory.
     
ajsshmdel >/dev/null 2>&1

  3. Execute a command to set up the embedded database environment.
    Use the ajsembdbbuild command to set up the embedded database environment.
    When executed, the ajsembdbbuild command performs the following operations:
    • Creates the definition information of the embedded database.
    • Creates the embedded database work area.
    • Starts the embedded database system.
    Specify an area on a shared disk for the data area and system file area specified in the -d option of the ajsembdbbuild command. Specify an area on the local disk for the embedded database work area specified in the -ld option.

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

The following shows examples of specifying the ajsembdbbuild command when a large-scale embedded database environment is set up. The examples also provide the combination of item numbers shown in Table C-2 and Table C-3.

Supplementary note:
You cannot set up an environment that duplexes the system file, but does not use the system log (the combination of items in Table C-2 and Table C-3 is 14-A, 16-A, 18-A, 20-A, 22-A, or 24-A).

Cautionary notes:
  • In the hosts file or in the DNS, you must register the names of both the primary node physical and logical hosts on which an embedded database environment is set up.
  • A host name registered in the jp1hosts definition file cannot be used as the name of a host on which an embedded database environment will be set up.
  • Do not use an alias for the name of a host on which an embedded database environment will be set up.
  • The maximum length of the name of a host on which an embedded database can operate is 32 bytes. Therefore, make sure that the name of a primary node physical or logical host on which an embedded database is set up is 1 to 32 bytes.

(a) For Windows

The specification examples in this subsection assume that the following values are set. Create the following directories before executing the ajsembdbbuild command:

(b) For UNIX

The specification examples in this subsection assume that the following values are set. Create the following directories before executing the ajsembdbbuild command:

The following table shows the data area creation directory and system file area creation directory that are used in the specification example.

Type of area Type of file
Normal file RAW file
Data area creation directory /share1/RDArea_JFA /dev/vgshare1/rdb_JFA
System file area creation directory 1 /share2/SYSArea_JFA /dev/vgshare2/rsys_JFA
System file area creation directory 2 /share3/SYSArea_JFA /dev/vgshare3/rsys_JFA

(4) Environment setting parameter settings

Set the environment setting parameters for the scheduler service, as considered in C.1(2)(c) environment setting parameter.

Also, create the directories you specified in the environment setting parameters.

If you create an environment by specifying the -S option in the jajs_setup_cluster command, you do not need to specify the settings in this subsection.

For details on setting the environment setting parameters, see 4.2 Environment setting parameter settings (for Windows) or 13.2 Environment setting parameter settings (for UNIX).

(5) Setting up the scheduler database in an embedded database environment

The ajsembdbsetup command can be used to set up the contents of a scheduler database in an embedded database environment. Before you start setup by executing the ajsembdbsetup command, make sure that the scheduler service is set up in the logical host environment.

When executed, the ajsembdbsetup command performs the following operations:

An example of executing the ajsembdbsetup command in a large-scale embedded database environment is shown below. This example assumes that the following values are set:

 
ajsembdbsetup -F AJSROOT4 -ru -l -id _JFA 
-mh logical_host -p 22230

Supplementary note:
When the ajsembdbsetup command is executed, the environment setting parameters listed in the following table are set. Do not change the values set for these environment setting parameters. For details about the parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

Table D-1 Environment setting parameters specified when the ajsembdbsetup command is executed

Environment setting parameter Definition Setting specified by the ajsembdbsetup command#
AJSDBTYPE Type of database EmbedDB
TABLENAMEPREFIX Table name prefix Either of the following:
  • -tp option specification value
  • AJS1
TABLENAMEPOSTFIX Table ID --
RDBAUTHID RDB permission identifier root
RDBUSER RDB access user name ajs2
RDBPASSWORD RDB user password --
RDBHOST Name of the host at the RDB connection destination Either of the following:
  • -mh option specification value
  • Setting of the JP1_HOSTNAME environment variable.
RDBPORT RDB connection port number Either of the following:
  • -p option specification value
  • 22220
RDBIPC Method for communication with RDB server MEMORY
RDBSENDMEMSIZE Send-data memory size for RDB interprocess memory communication Either of the following:
  • -s option specification value
  • 100
RDBRECVMEMSIZE Receive-data memory size for RDB interprocess memory communication Either of the following:
  • -r option specification value
  • 1600

#:
Settings that are numeric values use decimal numbers.

(6) Setting up multiple scheduler databases in one or more embedded database environments

The following describes how to set up multiple scheduler databases in one or more embedded databases.

(a) Setting up a different embedded database environment for each scheduler service

To set up a different embedded database environment for each scheduler service when multiple scheduler services are defined, prepare the following areas separately.

Prepare the system file area and unload log file creation directory if these are necessary. For the data area and system file area, specify areas on a shared disk.

When you set up the embedded database environment, specify a port number and a setup identifier for the embedded database so that there are no duplication conflicts with other databases. That is, when executing the ajsembdbbuild or ajsembdbsetup command, you must specify a unique port number for each embedded database in the -p option. Similarly, when executing the ajsembdbinstl, ajsembdbbuild, or ajsembdbsetup command, you must specify a unique embedded database setup identifier for each embedded database in the -id option.

A setup example is shown below.

This example assumes that the environment described in D.2(3) Setting up the embedded database environment and D.2(4) Environment setting parameter settings is already set up.

n For Windows

Environment for the embedded database:
The following are the details of the environment for the embedded database to be added:
  • Data area creation directory: q:\EmbDB\RDArea
  • System file area creation directory 1: r:\EmbDB\SYSArea1
  • System file area creation directory 2: s:\EmbDB\SYSArea2
  • Unload log file creation directory: t:\EmbDB\Unload_Log
  • Embedded database work area directory: u:\EmbDB\WorkArea
  • Embedded database installation directory: c:\Program Files\Hitachi\JP1AJS2\embdb\_JFB
  • Scheduler service name: AJSROOT5
  • Port number of the embedded database: 22231
  • Embedded database setup identifier: _JFB
  • Name of the primary node physical host: physical_host
  • Logical host name: logical_host

Specification of the ajsembdbinstl command:
 
ajsembdbinstl -mh logical_host 
-s "c:\Program Files\Hitachi\JP1AJS2\tools\AJS3DB" 
-i "c:\Program Files\Hitachi\JP1AJS2\embdb\_JFB" -id _JFB

Specification of the ajsembdbbuild command:
 
ajsembdbbuild -l 
-d "q:\EmbDB\RDArea,r:\EmbDB\SYSArea1,s:\EmbDB\SYSArea2" 
-ld u:\EmbDB\WorkArea -br -bl t:\EmbDB\Unload_Log 
-i "c:\Program Files\Hitachi\JP1AJS2\embdb\_JFB" 
-p 22231 -id _JFB -r -mh logical_host -eh physical_host

Specification of the ajsembdbsetup command:
 
ajsembdbsetup -F AJSROOT5 -ru l -id _JFB -p 22231 
-mh logical_host

n For UNIX

Environment for the embedded database:
The following are the details of the environment for the embedded database to be added:
  • Data area creation directory: /share4/RDArea_JFB
  • System file area creation directory 1:/share5/SYSArea_JFB
  • System file area creation directory 2:/share6/SYSArea_JFB
  • Unload log file creation directory: /Unload_Log_JFB
  • Embedded database work area directory: /WorkArea_JFB
  • Embedded database practical directory: /opt/jp1ajs2/embdb/_JFB
  • Scheduler service name: AJSROOT5
  • Port number of the embedded database: 22231
  • Embedded database setup identifier: _JFB
  • Name of the primary node physical host: physical_host
  • Logical host name: logical_host

Specification of the ajsembdbinstl command:
 
ajsembdbinstl -mh logical_host -s /opt/jp1ajs2/tools/AJS3DB 
-i /opt/jp1ajs2/embdb/_JFB -id _JFB

Specification of the ajsembdbbuild command:
 
ajsembdbbuild -l 
-d "/share4/RDArea_JFB,/share5/SYSArea_JFB,
/share6/SYSArea_JFB" -ld /WorkArea_JFB -br 
-bl /Unload_Log_JFB -i /opt/jp1ajs2/embdb/_JFB 
-p 22231 -id _JFB -r -mh logical_host -eh physical_host

Specification of the ajsembdbsetup command:
 
ajsembdbsetup -F AJSROOT5 -ru l -id _JFB 
-p 22231 -mh logical_host

For details about the ajsembdbinstl, ajsembdbbuild, and ajsembdbsetup commands, see 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

(b) Setting up multiple scheduler databases in one embedded database environment

If you want to set up multiple scheduler databases in one embedded database environment, you must create and manage a different table for each scheduler service in the embedded database. To do this, you must change the table name prefix specified when you execute the ajsembdbsetup command.

The following shows an example of specifying the ajsembdbsetup command when setting up the second scheduler database in an embedded database environment. Note that the example assumes that the following settings are specified:

 
ajsembdbsetup -F AJSROOT6 -tp AJS2 -ru l 
-id _JFA -mh logical_host -p 22230

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

Cautionary notes:
  • In an embedded database environment in which multiple scheduler databases are set up, you cannot reorganize just one scheduler database. In this environment, you need to reorganize all the scheduler databases that have been set up. If you want to reorganize only one scheduler database, you must prepare an embedded database environment for each scheduler service. For details, see (a) Setting up a different embedded database environment for each scheduler service.
  • In an embedded database environment in which multiple scheduler databases are set up, you cannot use the ajsembdbbackup command to back up only one scheduler database. The ajsembdbbackup command can only back up all the scheduler databases set up in an embedded database environment. If a backup created by using the ajsembdbbackup command is used for restoration, all the scheduler databases are restored. Therefore, when you use the ajsembdbbackup and ajsembdbrstr commands to perform backup and restore operations, you must stop all the scheduler services that access the relevant embedded database beforehand.
    If you use the ajsprint command to back up only the unit definition, you can create a backup for each scheduler database without stopping scheduler services.
    If you want to use the ajsembdbbackup command to back up only one scheduler database, you must prepare an embedded database for each scheduler service. For details, see (a) Setting up a different embedded database environment for each scheduler service.
  • You cannot set up both the scheduler database for the logical host and the scheduler database for the physical host in one environment database environment.

(7) Setting up an embedded database again

For details about setting up the embedded database again, see C.2(7) Setting up an embedded database again.

(8) Uninstalling an embedded database

For details about uninstalling an embedded database, 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.