7.8.1 Types of information that can be imported or exported
The following table describes the range of information managed by IM Configuration Management that can be imported or exported.
|
Information managed by IM Configuration Management |
Export |
Import |
|
|---|---|---|---|
|
Host information |
User-specified items |
Y |
Y |
|
OS information |
Y |
N |
|
|
Product information |
Y |
N |
|
|
Virtualization configuration information |
Y |
Y |
|
|
Remote communication method |
Y |
Y |
|
|
User name/password information |
Y |
Y |
|
|
System hierarchy |
Agent configuration information |
Y |
Y |
|
Remote monitoring configuration information |
Y |
Y |
|
|
Remote authentication information |
WMI authentication information |
Y |
Y |
|
SSH authentication information output |
Y |
Y |
|
|
Business group information |
Y |
Y |
|
|
Monitoring group information |
Y |
Y |
|
|
Profiles#1 |
Event forwarding setting file |
Y |
Y |
|
Action definition file for event log trapping |
Y |
Y |
|
|
Action definition file for log file trapping#2 |
Y |
Y |
|
|
Log-file trap startup definition file#2 |
Y |
Y |
|
|
Local action execution definition file |
Y |
Y |
|
|
Authentication server settings file |
N |
N |
|
|
JP1 user settings file |
N |
N |
|
|
User mapping settings file |
N |
N |
|
|
Remote-monitoring log file trap action-definition file |
Y |
Y |
|
|
Remote-monitoring log file trap startup-definition file |
Y |
Y |
|
|
Remote-monitoring event log trap action-definition file |
Y |
Y |
|
|
Service activity information |
N |
N |
|
- Legend:
-
Y: Can be imported or exported.
N: Cannot be imported or exported.
- #1
-
If the host does not collect profile settings files, there is no data to be exported (no directory is created).
- #2
-
Information is imported as follows:
When a log file trap having the same name as the log file trap corresponding to the imported profile exists and is running on the host to which the information was imported:
Information is imported when the log file trap is running, and the edited contents of the imported profile have not been applied. To apply the edited contents of the imported profile, restart the log file trap after importing the profile. For details about how to restart a log file trap to apply the profile, see 3.5.1(6)(b) Applying edited information in configuration files individually to each agent in the JP1/Integrated Management 2 - Manager Configuration Guide.
When a log file trap having the same name as the log file trap corresponding to the imported profile exists and is stopped on the host to which the information was imported:
Information is imported when the log file trap is stopped, and the edited contents of the imported profile have not been applied. To apply the edited contents of the imported profile, start the log file trap after importing the profile. For details about how to start a log file trap, see 3.5.1(7)(a) Starting log file traps in the JP1/Integrated Management 2 - Manager Configuration Guide.
When a log file trap having the same name as the log file trap corresponding to the imported profile does not exist on the host to which the information was imported:
Information is imported when the log file trap is stopped. After importing the profile, start the log file trap. For details about how to start a log file trap, see 3.5.1(7)(a) Starting log file traps in the JP1/Integrated Management 2 - Manager Configuration Guide.
For details about the IM Configuration Management information that can be exported and imported, see 9.7 Exporting and importing management information of IM Configuration Management in the JP1/Integrated Management 2 - Manager Administration Guide.