2.5.4 Setting up JP1/IM - Manager (for Linux)
You need to create and set up an integrated monitoring database to change the severity of events or consolidate a large number of events into one event. You also need to create and set up an IM Configuration Management database to use IM Configuration Management to manage the system hierarchy. These databases are generically called IM databases. This subsection describes how to create and set up IM databases.
The number of arguments for a command to be executed varies depending on whether the integrated monitoring database or the IM Configuration Management database is set up first. This manual describes the command arguments when the integrated monitoring database is installed first.
- Organization of this subsection
-
-
(1) Settings of the setup information file to be created (for Linux)
-
(3) Setting up an integrated monitoring database (for Linux)
-
(4) Setting up an IM Configuration Management database (for Linux)
-
(5) Setting Up Intelligent Integrated Management Database (for Linux)
-
(6) Setting up the Intelligent Integrated Management Base (for Linux)
-
(1) Settings of the setup information file to be created (for Linux)
The following provides details about the settings specified in the the setup information file that is created in 2.5.4(2) Preparations for setting up the IM database (for Linux).
Specification details
Specification |
Description |
---|---|
#IM DATABASE SERVICE - DB Size IMDBSIZE=S |
Specifies the size of the IM database to be created as S, M, or L. At installation, S is set. |
#IM DATABASE SERVICE - Data Storage Directory IMDBDIR=/var/opt/jp1imm/database |
Specifies the absolute path of the directory in which data for the IM database is to be stored. Use a string of no more than 95 characters. At installation, /var/opt/jp1imm/database is set. To change the value of IMDBDIR, do not specify a path that contains a symbolic link (a file that is retrieved by executing find / -type l). |
#IM DATABASE SERVICE - Port Number IMDBPORT=20700 |
Specifies the port number used by the IM database. The range of permitted port numbers is from 5001 to 65535. At installation, 20700 is set. |
#IM DATABASE SERVICE - DB Install Directory IMDBENVDIR=/var/opt/jp1imm/dbms |
Specifies the absolute path of the directory in which the IM database is to be installed. Use a string of no more than 123 characters. At installation, /var/opt/jp1imm/dbms is set. To change the value of IMDBENVDIR, do not specify a path that contains a symbolic link (a file that is retrieved by executing find / -type l). |
Related topics
-
15.1.3 Estimating IM database capacity requirements in the Overview and System Design Guide
(2) Preparations for setting up the IM database (for Linux)
The following describes s preparations for setting up the IM database in Linux. You need to prepare a setup information file that specifies the size of the database area required to set up an IM database and information about the database storage directory.
Prerequisites
JP1/IM - Manager must be installed on the manager.
Procedure
-
Edit the setup information file (jimdbsetupinfo.conf).
The setup information file is created during installation. For activities described in this manual, you do not need to change the settings created during installation.
The setup information file is stored in:
/etc/opt/jp1imm/conf/imdb/setup/
Related topics
-
2.4.1 Preparations for creating IM databases (for UNIX) in the Configuration Guide
-
Setup information file (jimdbsetupinfo.conf) in 2. Definition Files in the Command, Definition File and API Reference
(3) Setting up an integrated monitoring database (for Linux)
Create an integrated monitoring database and set it up for use with the central console functions.
Prerequisites
The following conditions must be satisfied:
-
Sufficient disk space for creating an integrated monitoring database is allocated.
-
The OS user who will execute the jcodbsetup and jcoimdef commands has root permissions.
Procedure
-
Execute the following jcodbsetup command to create an integrated monitoring database.
/opt/jp1cons/bin/jcodbsetup -f setup-information-file-name -q
It might take a long time to execute this command. The IM database service is created at this time.
-
Execute the following jcoimdef command to enable the integrated monitoring database:
/opt/jp1cons/bin/jcoimdef -db ON
-
Restart the JP1/IM3-Manager service.
Related topics
-
2.4.2 Setting up the integrated monitoring database (for UNIX) in the Configuration Guide
-
jcodbsetup in 1. Commands in the Command, Definition File and API Reference
-
jcoimdef in 1. Commands in the Command, Definition File and API Reference
(4) Setting up an IM Configuration Management database (for Linux)
Create an IM Configuration Management database and set it up so that the IM Configuration Management service can be started from process management.
Prerequisites
The following conditions must be satisfied:
-
JP1/IM - View has stopped.
-
Sufficient disk space for creating an IM Configuration Management database is allocated.
-
The OS user who will execute the jcfdbsetup and jcoimdef commands has root permissions.
If the integrated monitoring database has already been set up according to the setup procedure in 2.5.4(3) Setting up an integrated monitoring database (for Linux), the following condition must also be satisfied:
-
The status of the IM database service is Running.
Procedure
-
Stop the JP1/IM3 - Manager service.
-
Execute the following jcfdbsetup command to create an IM Configuration Management database:
/opt/jp1imm/bin/imdb/jcfdbsetup -s -q
It might take a long time to execute this command.
-
Execute the following jcoimdef command to enable the IM Configuration Management service (jcfmain):
/opt/jp1cons/bin/jcoimdef -cf ON
-
Start JP1/IM - Manager.
Related topics
-
2.4.3 Setting up the IM Configuration Management database (for UNIX) in the Configuration Guide
-
jcfdbsetup in 1. Commands in the Command, Definition File and API Reference
-
jcoimdef in 1. Commands in the Command, Definition File and API Reference
(5) Setting Up Intelligent Integrated Management Database (for Linux)
Create an Intelligent Integrated Management Database and configure it to use Intelligent Integrated Management Database with Intelligent Integrated Management Base.
Prerequisites
The following conditions must be met:
-
The amount of disk space required to create an Intelligent Integrated Management Database is reserved on the drive where JP1/IM - Manager is installed.
-
OS that executes jimgndbsetup command-user has root privileges.
Operating procedure
-
Shut down JP1/IM3 - Manager servicing.
-
Run the following jimgndbsetup command to create Intelligent Integrated Management Base database.
/opt/jp1imm/bin/imgndb/jimgndbsetup -f setup-information-file-name -q
-
Restart JP1/IM3-Manager service.
Related topics
-
2.5 Construction of Intelligent Integrated Management Database (for UNIX) in the Configuration Guide
-
jimgndbsetup in 1. Commands in the Command, Definition File and API Reference
(6) Setting up the Intelligent Integrated Management Base (for Linux)
Configure the service of the Intelligent Integrated Management Base (jddmain) so that it can be started from process management.
Prerequisites
The following conditions must be satisfied:
-
Integrated Monitoring DB and Intelligent Integrated Management Database are set up.
-
The OS user who will execute the jcoimdef command has root permissions.
Procedure
-
Stop the JP1/IM3-Manager service.
-
Execute the following jcoimdef command to enable the service of the Intelligent Integrated Management Base:
/opt/jp1cons/bin/jcoimdef -dd ON -hostmap ON
-
Ensure that the integrated monitoring database is running.
-
Edit the Intelligent Integrated Management Base definition file.
Specify the value specified for "IMDBPORT" in the setup information file (jimdbsetupinfo.conf) used when setting up the integrated monitoring DB in the Intelligent Integrated Management Platform Definition File (imdd.properties).
If there is no change from the IMDBPORT default value of 20700, it is not necessary to specify it in the Intelligent Integrated Management Platform definition file.
-
Define the hierarchical structure of the system in the system node definition file (imdd_systemnode.conf).
-
Define the names of the IM management nodes in the management group that are used when collected data is displayed in the sunburst or tree chart, in the category name definition file for IM management nodes (imdd_category_name.conf).
-
Restart the JP1/IM3 - Manager service.
-
Execute the jddsetaccessuser command to configure the users who can access the monitored products when system configuration information is collected.
-
Define the linked products and the name of the hosts from which configuration information of the monitoring objects in the linked products is collected, in the target host definition file for configuration collection (imdd_target_host.conf).
-
Execute the jddcreatetree command.
-
Define the relationships between IM management nodes in the IM management node link definition file (imdd_nodeLink_def.conf).
-
Execute the jddupdatetree command.
Related topics
-
2.4.2 Setting up the integrated monitoring database (for UNIX) in the Configuration Guide
-
2.5.2 Settings of Intelligent Integrated Management Database (for UNIX) in the Configuration Guide
-
jcoimdef in 1. Commands in the Command, Definition File and API Reference
-
jddsetaccessuser in 1. Commands in the Command, Definition File and API Reference
-
jddcreatetree in 1. Commands in the Command, Definition File and API Reference
-
jddupdatetree in 1. Commands in the Command, Definition File and API Reference
-
System node definition file (imdd_systemnode.conf) in 2. Definition Files in the Command, Definition File and API Reference
-
Category name definition file for IM management nodes (imdd_category_name.conf) in 2. Definition Files in the Command, Definition File and API Reference
-
Target host definition file for configuration collection (imdd_target_host.conf) in 2. Definition Files in the Command, Definition File and API Reference
-
IM management node link definition file (imdd_nodeLink_def.conf) in 2. Definition Files in the Command, Definition File and API Reference