Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide

6.3.2 Collecting profile lists

Using IM Configuration Management, you can collect a list of profiles (hereafter, profile list) from each host.

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 creating a configuration file (jbslcact.conf) and applying it to a host, see 3.3.5(2) Applying edited information in configuration files to individual hosts in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.

To create or update the profile list for a host, perform either of the following:

• 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.

If the IM Configuration Management database does not contain a profile list for a particular host, performing either of the following operations will generate a profile list or update the system hierarchy:

• 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.

When a host is restarted, or when JP1/Base is restarted on a host, you must update the profile lists. In the Display/Edit Profiles window, choose Operation and Rebuild Profile Tree.

The figure below shows the flow of processing when collecting profile lists with IM Configuration Management.

Figure 6-21 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 new or edited configuration definition information in the Edit IM 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.

Table 6-12 Profile lists that can be collected by JP1/Base version

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	Event Forwarding	--
	Log File Trapping	Multiple profile configuration files can be collected.#
	Event Log Trapping	--
	Local Action	--
	Authentication Server	Limited to display of valid configuration information.
	JP1 User-Permissions Level	Limited to display of valid configuration information. Supported only for an authentication server on the local host.
	Registered JP1 Users	Limited to display of valid configuration information. Supported only for an authentication server on the local host.
	OS User Mapping	Limited to display of valid configuration information.

Legend:

--: Not applicable.

#

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 superceded 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.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.