2.2.3 Installing a JP1/AJS3 series program

This subsection describes how to install a JP1/AJS3 series program on a Windows host.

Organization of this subsection

(1) New installation
(2) Upgrade installation
(3) Upgrade installation in a cluster configuration
(4) Upgrade installation of embedded database

(1) New installation

To install a JP1/AJS3 series program as a new installation on a Windows host:

Cautionary notes:

If you are using Windows Firewall, a pop-up message might appear during setup. In this case, you will need to add the affected program to the firewall exclusion list. Refer to the cautionary notes that accompany the ajsembdbinstl command and take the appropriate action.
Even if a new installation of JP1/AJS3 - Manager or JP1/AJS3 - Agent whose version is 09-50 or later is successful, JP1/AJS3-related menu items will not display when you choose the Windows Start menu.
The language environment of JP1/AJS3 is automatically set according to the locale set in the OS. When the locale set in the OS is a Japanese, English, or Chinese locale, the language environment of JP1/AJS3 is set to be the same as that of the OS. When the locale set in the OS is other than Japanese, English, or Chinese locales, the language environment of JP1/AJS3 is set to English.

Log in as a user with administrator privileges to the host on which you want to install the JP1/AJS3 series program.
Stop all programs linked with JP1/AJS3.

If a program linked with JP1/AJS3 is running on the host on which you want to install JP1/AJS3, stop the program. If the Windows Event Viewer window is open, close it.
Insert the media that contains the JP1/AJS3 series program you want to install.

The Hitachi Integrated Installer window opens.
Enter the information requested by the Hitachi Integrated Installer.

You will need to enter the following information during installation:
- User information
  
  Enter the user name and other necessary information.
- Installation folder
  
  Specify the folder where the JP1/AJS3 series programs are to be installed.
- Setup
  
  Specify this item only when installing JP1/AJS3 - Manager. Specify whether to set up a scheduler service and an embedded database during installation. When you set up the scheduler service and embedded database, you also need to select the database model of the embedded database.
In the following cases, you need to perform installation without setting up a scheduler service or an embedded database. When installation has finished, perform the individual setup procedure.

When performing advanced setup of the embedded database

When installation has finished, add a scheduler service. For details about the procedure for adding a scheduler service, in Windows, see 6.1.1(1) Adding a scheduler service. In UNIX, see 15.1.1(1) Adding a scheduler service.

When adding the scheduler service, execute the jajs_setup command with the -S option specified to perform advanced setup of the embedded database. For details about advanced setup of an embedded database, see 23.4 Advanced setup of an embedded database.

When using an external database as the JP1/AJS3 database

When installation has finished, perform the setup necessary to use an external database. For details about how to do this, see 24. Performing setup for using an external database in a cloud environment.

Note that when JP1/AJS3 - View is installed, the integrated trace log function (HNTRLib2) is also installed in the system-drive\Program Files (x86)^#\HITACHI\HNTRLib2\ folder. However, the Hitachi Network Objectplaza Trace Monitor 2 service does not start automatically if only JP1/AJS3 - View has been installed on a host. If the service does not start automatically, start it by selecting Hitachi Network Objectplaza Trace Monitor 2 in the list box of the Windows Services administrative tool.

When JP1/AJS3 - Web Console is installed, the integrated trace log function (HNTRLib2 (x64)) is also installed in the system-drive\Program Files\HITACHI\HNTRLib2\ folder. In preparation for possible problems, open the Services administrative tool of Windows, and check whether the Hitachi Network Objectplaza Trace Monitor 2 (x64) service is started. If the service is not started, start it.

If a dialog box displaying An attempt to build a Scheduler service failed. After installation, please re-build the Scheduler service. appears during installation of JP1/AJS3 - Manager, take appropriate action after checking the KAVS2128-E message that has been output to the Windows event log.

#

For 32-bit versions of Windows, replace Program Files (x86) with Program Files.
When installation has finished, restart the host when a restart is requested.

For details about setting up JP1/AJS3 series programs, see 3. Setup.

To Page Top

(2) Upgrade installation

To install a JP1/AJS3 series program as an upgrade installation on a Windows host:

Log in as a user with administrator privileges to the host on which you want to install a JP1/AJS3 series program.
Stop all programs linked with JP1/AJS3.

If JP1/AJS3 series programs or programs linked with JP1/AJS3 are running on the host on which you want to install JP1/AJS3, make sure that you stop those programs. If the Windows Event Viewer window is open, close it.
Set the JP1/AJS3 series program installation media, and start installation.

The overwrite or upgrade installation start window appears.
Perform installation.

Perform the necessary installation operations as directed in the installer window.

Note that when JP1/AJS3 - View is installed, the integrated trace log function (HNTRLib2) is also installed in the system-drive\Program Files (x86)^#\Hitachi\HNTRLib2\ folder. If you are installing only JP1/AJS3 - View on a host, select and activate the Hitachi Network Objectplaza Trace Monitor 2 service from the list box of the Windows Services administrative tool.

#

For 32-bit versions of Windows, replace Program Files (x86) with Program Files.
Important
An upgrade installation updates the following files. If necessary, back them up before performing the installation.
- Files with the .model extension in the JP1/AJS3-installation-folder\conf folder
- Files with the .bat extension in the JP1/AJS3-installation-folder\tools folder^#
#: If the version of JP1/AJS3 is 10-50 or later, the data collection tool jajs_log.bat is added to the tools folder in JP1/AJS3-installation-folder. Note that, if you upgrade JP1/AJS3 from a version earlier than 10-50 to version 10-50 or later, and if the file jajs_log.bat already exists, it is overwritten by the data collection tool. For this reason, if the file jajs_log.bat created in a JP1/AJS3 version earlier than 10-50 is necessary, move the file to another folder before performing installation.
When installation has finished, restart the host when a restart is requested.
Important
- Operation of JP1/AJS3 - Manager following an upgrade from JP1/AJS2 - Manager cannot start until setup has been completed after the upgrade installation. For details about the setup procedure required after an upgrade installation from JP1/AJS2 - Manager to JP1/AJS3 - Manager, see 8.5 Upgrading JP1/AJS2 - Manager to JP1/AJS3 - Manager in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- If JP1/AJS3 - Manager in a standard configuration is installed as an upgrade installation, you might also need to install the embedded database as an upgrade installation. If an upgrade installation of the embedded database is necessary, perform the installation after reading Installation Procedures and System Generation Precautions in the Release Notes.
- If the embedded database is already in use when you perform an upgrade installation, the file Pdcltm32.dll might not be present in the folder JP1/AJS3-installation-folder\bin. In this case, create the file by copying and renaming the Pdcltm32.dll.model file.

For details about setting up JP1/AJS3 series programs, see 3. Setup.

To Page Top

(3) Upgrade installation in a cluster configuration

The following describes the procedure for installing a JP1/AJS3 series program as an upgrade installation on a Windows host in a cluster configuration.

The installation procedure differs according to whether JP1/AJS3 - Manager is updated from JP1/AJS2 - Manager or from JP1/AJS3 - Manager.

Note that, in the procedures that follow, the node that normally operates is called the primary node, and the node that normally does not operate but remains on standby is called the secondary node.

(a) Upgrade procedure for a program other than JP1/AJS2 - Manager

To perform an upgrade installation from JP1/AJS3 - Manager, JP1/AJS3 - Agent, or JP1/AJS2 - Agent:

Make sure that the logical host is not operating on the secondary node.

Make sure that JP1/AJS3 or JP1/AJS2 of the logical host is not operating on the secondary node.

No problems are caused if JP1/AJS3 or JP1/AJS2 of the logical host is operating on the primary node.
Perform an upgrade installation on the secondary node.

For details about installing a JP1/AJS3 series program as an upgrade installation, see (2) Upgrade installation.
Make sure that the logical host is not operating on the primary node.

Either fail over the logical host from the primary node to the secondary node or stop the logical host to ensure that JP1/AJS3 or JP1/AJS2 of the logical host is not operating on the primary node.

No problems are caused by failing over the logical host to the secondary node on which an upgrade installation has finished.
Perform an upgrade installation on the primary node.

For details about installing a JP1/AJS3 series program as an upgrade installation, see (2) Upgrade installation.

Important

When the logical host has been failed over to the secondary node on which an upgrade installation has finished, do not fail back the logical host to the primary node until the upgrade installation on the primary node has finished.

(b) Upgrade procedure (from JP1/AJS2 - Manager to JP1/AJS3 - Manager in a standard configuration)

Important: An upgrade installation of JP1/AJS2 - Manager in a cluster configuration requires some setup, such as the migration of data on the shared disk, after completion of the upgrade installation. This setup requires that cluster operation be temporarily stopped. You will not be able to start JP1/AJS3 - Manager operation until this setup is complete. Because the time required for the setup to finish depends on the amount of data and other factors, the upgrade installation and setup must be performed according to a suitable plan.

To perform an upgrade installation from JP1/AJS2 - Manager:

Note: If your system consists of multiple logical hosts, perform steps 6 to 16 and 20 to 23 for each logical host. When using a logical host in a non-cluster environment, perform only the steps that relate to the primary node. You cannot begin using JP1/AJS3 until setup is completed on all physical and logical hosts.

Note: The following procedure assumes that one scheduler service is stored in one embedded database. If multiple scheduler services have been set up, perform steps 8, 11, and 12 for all of the scheduler services. To add an embedded database, perform steps 9, 10, 20, and 21.

Terminate JP1 on both the primary and secondary nodes.

Use the cluster software to stop all JP1 programs and services running on the primary and secondary nodes. For details about how to do so, see the documentation for your cluster software.
Install JP1/Base as an upgrade installation on the primary node.

For details about installing JP1/Base, see the JP1/Base User's Guide.
Install JP1/AJS3 - Manager as an upgrade installation on the primary node.

On the primary node, upgrade JP1/AJS2 - Manager to JP1/AJS3 - Manager.

For details about an upgrade installation of a JP1/AJS3 series program, see (2) Upgrade installation.
Start the embedded database or instance of HiRDB you were using before the upgrade on the physical primary node host.

To provide access to the database from before the upgrade, start the embedded database or instance of HiRDB that was used as the database of the scheduler service on the physical host of the primary node.

For details about how to start the embedded database or HiRDB, see the manual for the JP1/AJS2 product or HiRDB you are using.
Perform setup on the physical host of the primary node.

On the physical host of the primary node, execute the jajs_migrate command.

For example, execute the command as follows:
```
jajs_migrate -convert
```
For details about the jajs_migrate command, see jajs_migrate in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Confirm that the shared disk and logical IP address are available to the primary node.

Make sure that the shared disk is mounted and the logical IP address is valid so that the data on the shared disk can be migrated. If the shared disk is not mounted or the logical IP address is invalid, use the cluster software or volume manager software to mount the shared disk and enable the logical IP address. For details about how to do so, see the documentation for your cluster software.
Start the embedded database or instance of HiRDB you were using before the upgrade on the logical host of the primary node.

To provide access to the database from before the upgrade, start the embedded database or instance of HiRDB that was used as the database of the scheduler service on the logical host of the primary node.

For details about how to start the embedded database or HiRDB, see the manual for the JP1/AJS2 product or HiRDB you are using.
Execute the ajscnvdbexport command on the primary node to back up the contents of the database.

For example, execute the command as follows:
```
ajscnvdbexport -mh LHOST -F AJSROOT2 -b D:\workdir
```
For details about the ajscnvdbexport command, see ajscnvdbexport in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the ajsembdbinstl command on the primary node to install the JP1/AJS3 database.

For example, execute the command as follows:
```
ajsembdbinstl -s "C:\Program Files (x86)\HITACHI\JP1AJS2\tools\AJS3DB" 
-id _JF1 -mh LHOST
```
For details about the ajsembdbinstl command, see ajsembdbinstl in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the ajsembdbbuild command on the primary node to build the environment for the database.

For example, execute the command as follows:
```
ajsembdbbuild -s -r -d "D:\products\jp1ajs2\embdb\_JF1" 
-ld "C:\Program Files (x86)\HITACHI\JP1AJS2\embdb\_JF1\dbarea" -mh LHOST 
-eh hostA -p 22221 -i "C:\Program Files (x86)\HITACHI\JP1AJS2\embdb\_JF1" 
-id _JF1
```
For details about the ajsembdbbuild command, see ajsembdbbuild in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the ajsembdbsetup command on the primary node to set up the environment for the database.

For example, execute the command as follows:
```
ajsembdbsetup -mh LHOST -F AJSROOT2 -p 22221 -id _JF1 -ru s -convert
```
For details about the ajsembdbsetup command, see ajsembdbsetup in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the ajscnvdbimport command on the primary node to import the contents of the database.

For example, execute the command as follows:
```
ajscnvdbimport -mh LHOST -F AJSROOT2 -b D:\workdir
```
For details about the ajscnvdbimport command, see ajscnvdbimport in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Perform setup on the primary node.

Execute the jajs_migrate command on the primary node to set up the environment for running JP1/AJS3.

For example, execute the command as follows:
```
jajs_migrate -convert -h LHOST -r -S
```
For details about the jajs_migrate command, see jajs_migrate in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Stop the embedded database, which was started automatically during the setup process.

For example, execute the command as follows:
```
ajsembdbstop -id _JF1
```
For details about the ajsembdbstop command, see ajsembdbstop in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the jbsgetcnf command on the primary node to back up the common definition information to a file.

Execute the command as follows:
```
jbsgetcnf -h logical-host-name > backup-file-name
```
Copy the file you created in step 15 to the secondary node.
Install JP1/Base as an upgrade installation on the secondary node.

For details about installing JP1/Base, see the JP1/Base User's Guide.
Install JP1/AJS3 - Manager as an upgrade installation on the secondary node.

On the secondary node, upgrade JP1/AJS2 - Manager to JP1/AJS3 - Manager.

For details about an upgrade installation of a JP1/AJS3 series program, see (2) Upgrade installation.
Perform setup on the physical host of the secondary node.

Execute the jajs_migrate command on the physical host of the secondary node.

For example, execute the command as follows:
```
jajs_migrate -convert
```
For details about the jajs_migrate command, see jajs_migrate in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the ajsembdbinstl command on the secondary node to install the JP1/AJS3 database.

For example, execute the command as follows:
```
ajsembdbinstl -s "C:\Program Files (x86)\HITACHI\JP1AJS2\tools\AJS3DB" 
-id _JF1 -mh LHOST
```
For the -id option, specify the same value that you used when installing the database on the primary node.

For details about the ajsembdbinstl command, see ajsembdbinstl in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the ajsembdbbuild command on the secondary node to build the environment for the database.

For example, execute the command as follows:
```
ajsembdbbuild -s -f -d "D:\products\jp1ajs2\embdb\_JF1" 
-ld "C:\Program Files (x86)\HITACHI\JP1AJS2\embdb\_JF1\dbarea" 
-mh LHOST -eh hostA -p 22221 
-i "C:\Program Files (x86)\HITACHI\JP1AJS2\embdb\_JF1" -id _JF1
```
For the -id, -d, and -p options, specify the same value that you used when building the environment on the primary node.

For details about the ajsembdbbuild command, see ajsembdbbuild in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Execute the jbssetcnf command on the secondary node to apply the common definition information.

Execute the command as follows:
```
jbssetcnf name-of-file-copied-in-step-16
```
Perform setup on the secondary node.

Execute the jajs_migrate command on the secondary node to set up the environment for running JP1/AJS3.

For example, execute the command as follows:
```
jajs_migrate -convert -h LHOST -f -S
```
For details about the jajs_migrate command, see jajs_migrate in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
Unregister the embedded database or instance of HiRDB you were using with JP1/AJS2 before the upgrade from the cluster software.

For details about how to do so, see the documentation for your cluster software.
Start JP1 on the primary node.

Use the cluster software to start the JP1 programs and services on the primary node. This starts JP1/AJS3 operation in a cluster environment.

(c) Upgrade procedure (from JP1/AJS2 - Manager to JP1/AJS3 - Manager in a compatible ISAM configuration)

Because JP1/AJS3 - Manager version 11-10 or later does not support a compatible ISAM configuration, JP1/AJS2 - Manager cannot be upgraded to JP1/AJS3 - Manager version 11-10 or later in a compatible ISAM configuration. Therefore, to upgrade JP1/AJS2 - Manager to JP1/AJS3 - Manager in such a case, perform the procedure described in (b) Upgrade procedure (from JP1/AJS2 - Manager to JP1/AJS3 - Manager in a standard configuration) to upgrade to JP1/AJS3 - Manager in a standard configuration.

(d) Upgrade procedure for JP1/AJS3 - Web Console

To perform an upgrade installation from JP1/AJS3 - Web Console:

Make sure that JP1/AJS3 - Web Console is not operating on the secondary node.

Make sure that services of JP1/AJS3 - Web Console is not operating on the secondary node.

No problems are caused if services of JP1/AJS3 - Web Console is operating on the primary node.
Install JP1/AJS3 - Web Console as an upgrade installation on the secondary node.

For details about installing a JP1/AJS3 - Web Console as an upgrade installation, see (2) Upgrade installation.
Make sure that JP1/AJS3 - Web Console is not operating on the primary node.

Fail over from the primary host to the secondary host, or stop JP1/AJS3 - Web Console on the primary host, and then make sure that the JP1/AJS3 - Web Console service is not running on the primary host.

Note that, you can fail over to the secondary host (for which an upgrade installation was completed in step 2) without any problems.
Install JP1/AJS3 - Web Console as an upgrade installation on the primary node.

For details about installing a JP1/AJS3 - Web Console as an upgrade installation, see (2) Upgrade installation.

Important

If, after performing an upgrade installation for the secondary host, you run JP1/AJS3 - Web Console on the secondary host, do not fail back to the primary host until upgrade installation is complete for the primary host.

To Page Top

(4) Upgrade installation of embedded database

After the upgrade installation of JP1/AJS3 - Manager, check whether the version of the embedded database is the same as the version indicated in the Release Notes. If the versions are different, perform an upgrade installation of the embedded database. If multiple embedded databases are used, upgrade every embedded database by performing an upgrade installation.

The following describes the procedure for the upgrade installation of the embedded database:

For details about the commands shown in the procedure described below, see the JP1/Automatic Job Management System 3 Command Reference.

(a) Upgrade installation of an embedded database

The following describes the procedure for the upgrade installation of an embedded database:

Stop all JP1/AJS3 services.
Start the JP1/AJS3 Database _JFn service (n is 0 to 9 or A to Z).
Start the embedded database.

Execute the ajsembdbstart command with the -id _JFn option specified.

If JP1/AJS3 has been upgraded from an earlier version by upgrade installation and pd_mode_conf has been set to AUTO, the ajsembdbstart command might result in an error because the embedded database starts when the JP1/AJS3 Database _JFn service starts. In such a case, even if the error occurs, you do not need to deal with the error. Go to the next procedural step.
Check that the embedded database is operating.

Execute the ajsembdbstatus command with the -s ust and -id _JFn options specified to check that the embedded database is operating (UNIT-STAT is ONLINE).
Stop the embedded database normally.

Execute the ajsembdbstop command with the -id _JFn option specified. Do not specify the -f option in the command.
Check that the embedded database is stopped.

Execute the ajsembdbstatus command with the -s ust and -id _JFn options specified to check that the embedded database is stopped (UNIT-STAT is STOP).
Execute the ajsembdbinstl command to perform the upgrade installation of the embedded database.
Check that the embedded database is stopped.

Execute the ajsembdbstatus command with the -s ust and -id _JFn options specified to check that the embedded database is stopped (UNIT-STAT is STOP). If the embedded database is operating, execute the ajsembdbstop command to normally stop the embedded database.
Start the services that were stopped in step 1.

(b) Upgrade installation of embedded databases in a cluster configuration

For the upgrade installation of embedded databases in a cluster configuration, follow the procedure below.

On the primary node

On the primary node, perform the upgrade installation of the embedded database while the shared disk and logical IP address are available to the primary node. For details about the procedure, see (a) Upgrade installation of an embedded database.
On the secondary node

After the upgrade installation of the embedded database on the primary node, execute the ajsembdbinstl command on the secondary node to perform the upgrade installation of the embedded database.

Note that, for the upgrade installation of the embedded database on the secondary node, you do not need to enable the IP address and shared disk allocated to the logical host.

To Page Top