8.5.2 Collecting profile lists
In IM Configuration Management, before you collect profiles, you must obtain a list of profiles (called a profile list hereafter) that can be managed from agent hosts and remotely monitored hosts.
The collected profile list appears in the tree display area of the Display/Edit Profiles window.
If the service for which the profile is set (event log trapping service, event service, and so on) is inactive on a target host, the collected profile list is displayed as follows:
-
In the tree display area of the Display/Edit Profiles window, profiles from the host where the service is inactive appear grayed and cannot be selected in the profile list.
-
In the node display area of the Display/Edit Profiles window, the configuration file's Collection status remains unchanged.
-
When you click the Basic Information button in the node display area of the Host List page or IM Configuration page of the IM Configuration Management window, the profile collection status is shown as Collected.
The service for local actions is inactive by default because there is no configuration file (jbslcact.conf) in the host. As a result, when you collect a profile list in the Display/Edit Profiles window, the KNAN20333-I message is displayed and Collected appears as the Collection status in the node display area.
You can start the service for local actions by creating a configuration file (jbslcact.conf) and applying it to the host in question.
For details about how to create a configuration file (jbslcact.conf) and apply it to the host in question, see 3.5.1(6)(b) Applying edited information in configuration files individually to each agent in the JP1/Integrated Management 3 - Manager Configuration Guide.
Perform one of the operations listed below to delete the profile list saved on the server, and then acquire profile lists again from hosts. For agent configuration, if the profiles have not yet applied, apply the profiles to the hosts, and then rebuild the profile tree. For a remote monitoring configuration, you do not have to rebuild the profile tree.
-
In the tree display area of the Display/Edit Profiles window, click the JP1 product name (JP1/Base) and then choose Operation and Rebuild Profile Tree.
-
In the tree display area of the Display/Edit Profiles window, right-click the JP1 product name (JP1/Base) and then choose Rebuild Profile Tree.
-
On the Host List or IM Configuration page of the IM Configuration Management window, choose Operation and then Batch Collect Profiles.
If you have restarted the host or JP1/Base on the host, you must update the profile list by opening the Display/Edit Profiles window, choosing Operation, and then choosing Rebuild Profile Tree.
Note that the profile list is updated when host information is collected.
If you perform either of the following operations, and if the profile list does not exist in the IM Configuration Management database, a profile list is created, or the system is updated.
-
Open the Display/Edit Profiles window.
-
On the Host List page or IM Configuration page of the IM Configuration Management window, choose Operation and Batch Collect Profiles.
The figure below shows the flow of processing when collecting profile lists with IM Configuration Management.
|
If a host is deleted from the system hierarchy or is no longer managed by IM Configuration Management, the profile list collected from that host is deleted. Profile lists are also deleted when you perform any of the following operations:
-
Collect host information on the Host List page or IM Configuration page of the IM Configuration Management window.
-
Apply the system hierarchy created or edited in the Edit Agent Configuration window or in the Edit Remote Monitoring Configuration window.
-
Import configuration definition information on the manager running IM Configuration Management.
The following table describes the profile lists you can collect for each version of JP1/Base on the target host.
JP1/Base version |
Profile type |
Description |
---|---|---|
Versions 7 and 8 |
Event Forwarding |
-- |
Log File Trapping |
-- |
|
Event Log Trapping |
Can be collected from a Windows host only. |
|
Version 9 or later |
Event Forwarding |
-- |
Log File Trapping#1 |
Multiple profile configuration files can be collected.#2 |
|
Event Log Trapping |
-- |
|
Local Action |
-- |
|
Authentication Server |
Limited to display of valid configuration information. |
|
JP1 User-Permissions Level |
|
|
Registered JP1 Users |
|
|
OS User Mapping |
Limited to display of valid configuration information. |
- Legend:
-
--: Not applicable.
- #1
-
If the version of JP1/Base is 09-10 or later, you can collect the log-file trap action definition file and the log-file trap startup definition file.
If the version of JP1/Base is earlier than 09-10, you can collect only the log-file trap action definition file.
- #2
-
A maximum of 100 profile configuration files for log file trapping can be collected from JP1/Base on each host.
When a host is restarted, or when JP1/Base is restarted on a host, you must update the host's profile list.
You must also update the profile list in the following cases:
-
When changes are made to the index file for the event forwarding settings on a host
Unless you update the profile list, the contents of the superseded configuration file will be displayed, or an error message will appear, when you collect the host's configuration file.
-
When the service for which the profile is set (event log trapping service, event service, and so on) starts or stops on the host
Unless you update the profile list, the following problems occur:
-
An error message appears when you display valid configuration information, or when you collect or apply configuration files.
-
In the tree display area of the Display/Edit Profiles window, the profiles that you want to view appear grayed in the profile list.
-
When log file trapping starts or stops on the host, an error message appears when you display valid configuration information, or when you collect or apply configuration files.