Job Management Partner 1/Integrated Management - Manager Configuration Guide

1.4 Creating an IM database

To use the IM Configuration Management database to manage a system hierarchy and to use the integrated monitoring database to manage JP1 events, you must create an IM database, which is the collective name for these two databases.

If you do not use the IM Configuration Management database during system configuration or you do not use the integrated monitoring database or the IM Configuration Management database when you start operations, there is no need to create an IM database. You can create the IM database when you need either or both of the integrated monitoring database and the IM Configuration Management database after operations have started.

This section explains how to create an IM database.

Organization of this section

(1) Preparations for creating an IM database

(2) Setting up the integrated monitoring database

(3) Setting up the IM Configuration Management database

(1) Preparations for creating an IM database

You must prepare a setup information file that specifies the size of the database area required in order to create an IM database and information about the database storage directory.

To prepare for IM database creation:
Edit the setup information file
The following shows an example of the settings:
IMDBSIZE=S  #IM DATABASE SERVICE - DB Size
IMDBDIR=Manager-path\database  #IM DATABASE SERVICE - Data Storage Directory
IMDBPORT=20700  #IM DATABASE SERVICE - Port Number
IMDBENVDIR=Manager-path\dbms  #IM DATABASE SERVICE - DB Install Directory
For details about the setup information file, see Setup information file (jimdbsetupinfo.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

(2) Setting up the integrated monitoring database

Create an integrated monitoring database and use the Central Console functions to set up the database so you can use it. If you do not use the integrated monitoring database, there is no need to perform this procedure.

To execute the jcodbsetup command that creates an integrated monitoring database, one of the following conditions must be satisfied:

Central Console Service is stopped.

The integrated monitoring database settings are disabled and the IM Configuration Management service is stopped.

To set up the integrated monitoring database:
Execute the jcodbsetup command to create an integrated monitoring database.

When an IM Configuration Management database has been set up
jcodbsetup -s [-h logical-host-name -c {online|standby}] [-q]

When no IM Configuration Management database has been set up
jcodbsetup -f setup-information-file-name [-h logical-host-name -c {online|standby}] [-q]

For details about the jcodbsetup command, see jcodbsetup in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
Execute the jcoimdef command to enable the integrated monitoring database.
jcoimdef -db ON
For details about the jcoimdef command, see jcoimdef in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
To start JP1/IM - Manager and use the integrated monitoring database, the IM database service must be running (return value: 0). Execute the jimdbstatus command to check the settings of the integrated monitoring database and the status of the IM database service.

If the operating status is that the IM database service is engaged in start or stop processing (return value: 4), is stopped (return value: 8), or is not running (return value: 16), processing is placed on wait status for the amount of time (in milliseconds) specified in the common definition.

Define the parameter as follows:
[logical-host-name\JP1CONSOLEMANAGER\IMDB]
"DB_START_RETRY_INTERVAL"=dword:hexadecimal-value
Specify a hexadecimal value in the range 3,000 to 3,600,000 (milliseconds). The default is dword:0000xbb8 (3,000 milliseconds).

The operating status of the IM database service is checked again.

Checking of the operating status of the IM database service is performed as many times as is specified in the common definition.

Define the parameter as follows:
[logical-host-name\JP1CONSOLEMANAGER\IMDB]
"DB_START_RETRY_COUNT"=dword:hexadecimal-value
Specify a hexadecimal value in the range 0 to 10,000 (times). The default is dword:0000x12c (300 times).

For details about the jimdbstatus command, see jimdbstatus in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

(3) Setting up the IM Configuration Management database

Create an IM Configuration Management database and set it up so that the IM Configuration Management service can be started from process management. If you do not use the IM Configuration Management database, there is no need to perform this procedure.

To execute the jcfdbsetup command that creates an IM Configuration Management database, one of the following conditions must be satisfied:

Central Console Service is stopped.

The integrated monitoring database settings are disabled and the IM Configuration Management service is stopped.

To set up the IM Configuration Management database:

Execute the jcfdbsetup command to create an IM Configuration Management database.

When an integrated monitoring database has been set up
jcfdbsetup -s [-h logical-host-name -c {online|standby}] [-q]

When no integrated monitoring database has been set up
jcfdbsetup -f setup-information-file-name [-h logical-host-name -c {online|standby}] [-q]

For details about the jcfdbsetup command, see jcfdbsetup in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

[Contents][Back][Next]

[Trademarks]