5.11.5 Central Scope databases
The Central Scope has two databases: a monitoring objects database and a host information database.
-
Managing the monitoring objects database
The monitoring objects database is managed by JP1/IM - Manager and contains the object information displayed in JP1/IM - View.
This database is updated on request from JP1/IM - View and on receipt of a JP1 event that changes the status of a monitoring object.
Note that the following processing to update the monitoring objects database might take some time to complete:
-
Updating a server tree from the Monitoring Tree (Editing) window
-
Importing database information to the monitoring objects database by the jcsdbimport command
If the OS shuts down, or if a failover occurs in a cluster system, while this update processing is in progress, the database could become corrupted.
To prevent corruption of the database, JP1/IM provides an automatic backup and recovery function. When this function is enabled, the database is automatically backed up before either of the above types of update processing is performed, and is automatically restored to its former state if a problem occurs. If the update processing is successful, the backup data is automatically deleted.
This function is enabled for a new installation of JP1/IM, but is disabled when an upgrade installation is performed. To enhance the system's fault tolerance, we recommend that you enable the function if upgrading JP1/IM.
To enable the function, prepare an automatic backup and recovery settings file (auto_dbbackup_xxx.conf) for the monitoring objects database, and then apply the setting using the jbssetcnf command.
-
-
Managing the host information database
The host information database contains information specific to JP1/IM - Manager (Central Scope) and is managed within JP1/IM - Manager (Central Scope).
You can import and export information to the Central Scope databases using the commands shown in the table below.
|
Command name |
Purpose |
|---|---|
|
jcsdbexport command |
Acquire information from the monitoring objects database. |
|
jcsdbimport command |
Save information to the monitoring objects database. |
|
jcshostsexport command |
Acquire information from the host information database. |
|
jcshostsimport command |
Save information to the host information database. |
You can check database information using the jcsxxexport commands, and you can migrate the environment to another server using the jcsxxexport commands in conjunction with the jcsxximport commands.
The following describes how to migrate the tree configuration information and the status change conditions for monitoring objects from the local Central Scope to another server.
- Organization of this subsection
(1) Using commands (jcsdbexport and jcsdbimport) for migration
-
On the migration-source server, execute the jcsdbexport command.
The information stored in the monitoring object database is locally output as a tree configuration file.
The information output in this tree configuration file contains monitoring tree configuration information, common event monitoring conditions, and the information about Visual Monitoring window configuration.
-
Transfer the output file to the migration-destination server.
-
On the migration-destination server, execute the jcsdbimport command.
The data in the monitoring object database on the migration-source server is applied on the monitoring-destination server.
For details about the jcsdbexport command, see jcsdbexport in Chapter 1. Commands in the JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
For details about the jcsdbimport command, see jcsdbimport in Chapter 1. Commands in the JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
(2) Using the GUI for migration
-
On the migration-source server, in the Monitoring Tree (Editing) window, select File, and then choose Save Tree to save the output CSV file.
The information output to the CSV file contains the monitoring tree configuration information about the currently displayed tree and common event monitoring conditions. The information about Visual Monitoring window configuration is not output. Note that the output information also includes the changes in information for which the menu command Update Server Tree has not been executed.
-
Transfer the output CSV file to the migration-destination server.
-
On the migration-destination server, in the Monitoring Tree (Editing) window, select File, and then choose Open Tree to read the CSV file.
-
On the migration-destination server, in the Monitoring Tree (Editing) window, select File and then Update Server Tree.
The data in the monitoring object database on the migration-source server is applied on the monitoring-destination server.
(3) Notes on migrating the tree configuration information and the status change conditions for monitoring objects from the local Central Scope to another server
-
To migrate the information about Visual Monitoring window configuration, use the jcsdbexport and jcsdbimport commands, which can output and input all information with a single execution. If you use the GUI, you need to read the CSV file (output by selecting Save Visual Monitoring Data) by selecting Open Visual Monitoring Data on the migration-destination server.
-
The format of the output file differs between the migration using commands and the migration using the GUI. Therefore, the file output by using a command cannot be input by using the GUI, or the file output by using the GUI cannot be input by using a command.