7.5.3 Collecting profiles

(1) Collecting valid configuration information

You can collect valid configuration information from the agent hosts on which JP1/Base version 9 or later is running and from the remotely monitored hosts.

To collect valid configuration information:

1. Open the Display/Edit Profiles window.

2. In the tree display area, select a profile.

3. Click the Valid Configuration Information button.

The figure below shows the flow of processing when collecting valid configuration information with IM Configuration Management.

Figure 7‒32: Collecting valid configuration information with IM Configuration Management

If collection fails, the possible causes are as follows:

Table 7‒32: Causes of failures to obtain valid configuration information

Status	Cause	Action
No valid configuration information could be obtained in the event forwarding, from the forwarding filter entry onward.	The possible cause is that a higher-level host is set in the forwarding setting file (forward) as the destination host for forwarded events, but no higher-level host exists for the source host in the system hierarchy.	Check whether the system hierarchy is correct.
No valid configuration information could be obtained in the log file trapping.	The process ID might have changed when log file trapping was restarted on the host, resulting in a mismatch with the process ID managed by IM Configuration Management. The process ID changes each time log file trapping starts.	Update the profile list: 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.
No valid configuration information could be obtained in the JP1 user-permissions level or Registered JP1 Users.	The local host might not be acting as the authentication server.	Check whether the authentication service is active on the local host.
Other status	The target service might be inactive on the host.	Execute the jbs_spmd_status command to check whether the service started successfully. Alternatively, in a Windows system, check the service status from the Computer Management window.

To Page Top

(2) Collecting configuration files per Agent

You can collect the profile configuration file for each host from the agent hosts on which JP1/Base version 9 or later is running.

To collect configuration files from a host, perform either of the following:

• In the Display/Edit Profiles window, make sure the Exclusive Editing Settings command is checked in the Edit menu, or look at the icons in the tree display area to make sure you have exclusive editing rights to the profiles on the target host. Then choose Operation and Collect Profiles.

• In the IM Configuration Management window, choose Operation and Batch Collect Profiles.

The figure below shows the flow of processing when collecting configuration files from a host with IM Configuration Management.

Figure 7‒33: Collecting configuration files with IM Configuration Management (per host)

For details about the configuration files that can be collected, see 7.5.3(4) Configuration files that can be collected for each version of JP1/Base.

To Page Top

(3) Batch collection of configuration files on agent hosts

On the Host List page or IM Configuration page of the IM Configuration Management window, if you select Batch Collect Profiles from the Operation menu, configuration files on agent hosts are collected in a batch.

You cannot collect profiles in a batch if another user has exclusive editing rights to any of the configuration files. To obtain these rights, see 7.5.7 Obtaining and releasing exclusive editing rights for a configuration file.

The figure below shows the flow of processing when collecting configuration files from all hosts as a batch operation with IM Configuration Management.

Figure 7‒34: Collecting configuration files with IM Configuration Management (all hosts)

For details about the configuration files that can be collected, see 7.5.3(4) Configuration files that can be collected for each version of JP1/Base.

In the Display/Edit Profiles window, you can check whether all the configuration files were successfully collected. If any file could not be collected, Configuration file contents is unavailable and the file status appears in Status in the node display area.

On the IM Configuration page of the IM Configuration Management window, you can check whether the configuration files were successfully collected from all the hosts. If files could not be collected from any host, an error-status icon is displayed for the affected host in the tree display area. To view further details, click the Basic Information button in the node display area.

If batch collection fails for any host, processing continues and the profiles on the other hosts are collected. Also, if the maximum number of profile configuration files for log file trapping is exceeded on a host, a message appears and collection processing is canceled for that host.

At batch collection, the profile list on each host is updated automatically. For this reason, configuration files are not collected for services and processes that were inactive at the time the profile list was updated.

When batch collection is completed, a message to that effect appears.

To Page Top

(4) Configuration files that can be collected for each version of JP1/Base

The following table describes the configuration files that can be collected for each version of JP1/Base.

Table 7‒33: Configuration files that can be collected

Profile type	Configuration file	JP1/Base version			Notes
		Earlier than version 9	Version 09-00 to 09-01	Version 09-10 or later
Event Forwarding	Event forwarding setting file (forward)	Y	Y	Y	Files such as the event server index file (index) and event server settings file (conf) are not collected.
Log File Trapping	Action definition file for log file trapping (any file)#1	Y	Y	Y	The following restrictions are applied if the version of JP1/Base is earlier than 09-00: Only batch-collection is available. Only the setting file for a log file trap is collected. Only the action definition file saved with the default file name (jevlog.conf) in the default location (the conf directory) is regarded as a valid definition file.
	Log-file trap startup definition file (jevlog_start.conf)#2	N	N	Y	Displayed as the start option, not as a profile. When a host that is a UNIX or Linux environment collects log files without the startup LANG specified, IM Configuration Management collects them by assuming that the startup LANG is C. The startup LANG should be specified to prevent a wrong LANG from being used for collection.
Event Log Trapping	Action definition file for event log trapping (ntevent.conf)	Y	Y	Y	Collected when the host environment is Windows.
Local Action	Local action execution definition file (jbslcact.conf)	N	N	N	--

To Page Top

(5) Saving configuration files

The configuration files collected from agents or the configuration files for agents or remotely monitored hosts edited on the IM configuration management viewer can be saved on a manager host on which IM Configuration Management is running. For the configuration files for remotely monitored hosts, only action definition files can be saved.

Configuration files are saved when you perform any of the following operations:

• In the Display/Edit Profiles window, choose Operation and Collect Profiles (provided no one has obtained exclusive editing rights to the configuration files).

• On the Host List page or IM Configuration page of the IM Configuration Management window, choose Operation and Batch Collect Profiles.

• In the node display area (settings information) of the Display/Edit Profiles window, select the Save check box and then click the Execute button.

• In the node display area (settings information) of the Display/Edit Profiles window, select the Apply check box and then click the Execute button.

• Import configuration definition information on the manager running IM Configuration Management.

IM Configuration Management stores only one configuration file per profile. The saved profile information will be overwritten if the same configuration file is collected by another user before the saved information is applied to the host.

Configuration files that could not be collected during batch collection of profiles from all hosts cannot be saved.

The file names and location of files saved by IM Configuration Management cannot be specified by the user.

When you delete a host, the host's configuration files are also deleted from the manager running IM Configuration Management. When you delete host information on the Host List page of the IM Configuration Management window, the host's configuration files are also deleted.

To Page Top