9.7.1 Exporting management information of IM Configuration Management
By outputting (exporting) management information managed by IM Configuration Management and then inputting (importing) it, you can copy management information from one host to another. In addition, by editing the system configuration information that has been exported, you can easily modify it. This subsection explains the management information that is exported by the jcfexport command. For details about the jcfexport command, see jcfexport in Chapter 1. Commands of the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
- Organization of this subsection
(1) Host information
Information related to the host managed by IM Configuration Management is exported to the host input information file and the collected host information file.
For details about the host input information file, see Host input information file (host_input_data.csv) in Chapter 2. Definition Files of the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
For details about the collected host information file, see Collected host information file (host_collect_data.csv) in Chapter 2. Definition Files of the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
(2) System hierarchy information
The system hierarchy information is exported to a file. You can edit the exported file and import it.
The information that is output differs according to the system monitoring method:
-
Agent monitoring
-
Remote monitoring
(a) Configuration information for agent monitoring
The name of the file that is exported is system_tree_information.txt.
The following table describes the configuration information for agent monitoring that is output to the file.
Output item |
Description of output value |
---|---|
[managing-host] |
|
managed-host |
|
(b) Configuration information for remote monitoring
The configuration information for remote monitoring is exported to a file. The name of the file to be exported is system_remote_tree_information.txt.
The following table describes the configuration information for remote monitoring that is output to the file.
Output item |
Description of output value |
---|---|
[managing-host] |
|
managed-host |
A host that is managed remotely in IM Configuration Management |
(3) Profile information
The profile information that is running on the host is exported. The files that are exported differ according to the system monitoring method:
-
Agent monitoring
-
Remote monitoring
(a) Profile information for agent monitoring
The profile information of the JP1/Base that is running on the host is exported. The file is exported to the first-level directory (host-name) and the second-level directory (JP1Base) under the definition_files directory. The log file trap action definition file is exported to the third-level directory (cf_log_file_trap). The following table describes the profile information that is exported.
Profile information |
Export file name |
---|---|
Event forwarding settings file |
forward |
Log-file trap action definition file |
Any name |
Log-file trap startup definition file |
jevlog_start.conf |
Event log-trap action definition file |
ntevent.conf |
Local action execution definition file |
jbslcact.conf |
Note: There is no data to be exported for a host for which profile settings files are not collected (in such a case, the directories are not created).
(b) Profile information for remote monitoring
The profile information of JP1/IM - Manager is exported to a file, and cannot be edited.
The file is exported to the first-level directory (host-name) and the second-level directory (al) under the definition_files directory. The log file trap action-definition file is exported to the third-level directory (cf_log_file_trap), and the event log trap action definition file is exported to the third-level directory (cf_event_log_trap). The following table describes the profile information that is exported.
Profile information |
Export file name |
---|---|
Remote-monitoring log file trap action-definition file |
Any name |
Remote monitoring startup definition file |
jevlog_start.conf |
Remote-monitoring event log trap action-definition file |
ntevent.conf |
(4) Remote authentication information
When remote monitoring is used, remote authentication information is exported. The name of the file to be exported is wmi.ini or ssh.ini.
(5) Business group information
When business groups are used, information about the business groups is exported to a file named monitoring_system_data.csv. The following table describes the business group information output to monitoring_system_data.csv.
Line |
Output item |
Output value |
---|---|---|
First line (header information) |
Product name |
JP1/IM-CF |
File format version |
File format version For example, if the version of JP1/IM - Manager is 09-50, 095000 is output. |
|
Character code |
Character code This depends on the setting of the LANG environment variable on the manager. For details, see Table 2-79 Character encoding of files in Host input information file (host_input_data.csv) in Chapter 2. Definition Files of the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference. |
|
Second line (header information) |
Business group name |
Monitoring_system_name |
Assigned JP1 resource group name |
JP1_resource_group_name |
|
Comment |
Comment |
|
Host name |
Host_name_list |
|
Third and subsequent lines |
Business group name |
Name of the business group |
Assigned JP1 resource group name |
Name of the JP1 resource group assigned to the business group |
|
Comment |
Comment |
|
Host name |
Name of the host registered in the business group (If there are multiple hosts, hosts are delimited with a comma (,) and the entire string of hosts is enclosed in double quotation marks ("")) |
Note: Business group information is sorted in ascending order of business group name before being output.
The following shows an example of outputting business group information:
JP1/IM-CF;095000;UTF-8,,,
Monitoring_system_name,JP1_resource_group_name,Comment,Host_name_list
System1,,This is the empty system,
System2,Resource_A,This is System2,"host21,host22,host23,host24"
System3,Resource_A,This is System3,"host31,host32"
(6) Monitoring group information
When business groups are used, the monitoring group information of IM Configuration Management is exported to a file named monitoring_group_data.csv. The following table describes the monitoring group information that is output to monitoring_group_data.csv.
Line |
Output item |
Output value |
---|---|---|
First line (header information) |
Product name |
JP1/IM-CF |
File format version |
File format version For example, if the version of JP1/IM - Manager is 10-50, 101000 is output. |
|
Character code |
Character code This depends on the setting of the LANG environment variable of the manager. For details, see Table 2-79 Character encoding of files in Host input information file (host_input_data.csv) in Chapter 2. Definition Files of the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference. |
|
Second line (header information) |
Monitoring group path |
Monitoring_group_path |
Comment |
Comment |
|
Host name |
Host_name_list |
|
Third and subsequent lines |
Monitoring group path |
Monitoring group path |
Comment |
Comment |
|
Host name |
Name of the host registered in the monitoring group (If there are multiple hosts, hosts are delimited with a comma (,) and the entire string of hosts is enclosed in double quotation marks ("")) |
Note: Monitoring group information is sorted in ascending order of monitoring group path and before being output.
The following shows an example of outputting monitoring group information:
JP1/IM-CF;101000;UTF-8,,
Monitoring_group_path,Comment,Host_name_list
/System1/Group1,This is the empty group,
/System1/Group2,This is Group2,host2
/System2/Group1,This is Group1,"host11,host12,host13,host14"