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

6.3.1 Types of profiles that can be managed

Using IM Configuration Management, you can manage the profiles set in JP1/Base on the hosts in the system hierarchy.

You can manage the following JP1/Base profiles:

• Valid configuration information
  The settings information that is currently valid in JP1/Base (read from a configuration file at startup of the JP1/Base service). To manage this information, JP1/Base on the target host must be version 9.
  
• Configuration file contents
  The information set in a profile configuration file in JP1/Base. This information will differ from the valid configuration information if you made any changes to the configuration file after startup of the JP1/Base service but did not apply the edited file contents.
  

Using IM Configuration Management, you can manage profiles in JP1/Base version 7 or later.

Profile management can be used for the following purposes:

• To check the status of the hosts on a routine basis or in the event of an error
• To change a profile during a system upgrade or maintenance
• To apply the contents of a profile to the JP1/Base profiles on other hosts

The table below describes the types of profiles you can manage with IM Configuration Management.

Table 6-11 Types of profiles that can be managed with IM Configuration Management

Profile type	Description
Event Forwarding	Profile about the functionality for forwarding JP1 events to a higher-level host in accordance with the system hierarchy.
Log File Trapping	Profile about the functionality for converting information output to a log file by an application program into JP1 events. Configuration files cannot have identical file names. A different file name must be assigned to the configuration file for each process, even when the files are stored in different directories.
Event Log Trapping	Profile about the functionality for converting Windows events into JP1 events.
Local Action#1	Profile about actions executed on an agent without going through a manager.
Authentication Server#1	Profile about the server for centrally managing the users of a system configured in JP1/IM or JP1/AJS.
JP1 User-Permissions Level#1, #2	Profile about the permission levels of JP1 users (users of a JP1 system such as JP1/IM or JP1/AJS).
Registered JP1 Users#1, #2	Profile about the list of JP1 users.
OS User Mapping#1, #2	Profile about the mapping between OS users who have permission to execute jobs and commands and JP1 users.

#1

Only information in JP1/Base version 9 can be managed.

#2

If the local host is used as the authentication server, information can be displayed only when the service of the authentication server is active.

If the local host is used as the authentication server, the display area appears grayed when the service of the authentication server is stopped.

The profiles in JP1/Base version 9 that can be managed by IM Configuration Management are the contents of configuration files stored in each host's conf directory. Configuration files located in other directories, such as those for log file trapping, cannot be managed by IM Configuration Management. If you want to include such files in the profile management functionality, you must move them to the conf directory.

IM Configuration Management manages JP1/Base event log traps and log file traps on a physical host basis, not on a logical host basis. To display or edit profiles about event log traps or log file traps in a logical host, you must do so on a physical host basis, identifying the physical host associated with the logical host.

All valid configuration information can be displayed, however, even for services that start with a configuration file located in a directory other than the conf directory. From the displayed information you can find out whether a service's configuration file is located in the conf directory.

The figure below shows the flow of operations required to manage profiles with IM Configuration Management.

Figure 6-20 Flow of operations for managing profiles with IM Configuration Management

Profiles on a host whose host name is defined by its IP address in the IM Configuration Management database cannot be managed using IM Configuration Management. Operations attempted on a target host defined in this way might result in the following message: Profile management failed because the host name is defined with IP address. Please define real host name. This message appears when you perform any of the following operations on a host defined by its IP address:

• Open the Display/Edit Profiles window.
• Collect profiles as a batch operation in the IM Configuration Management window.
  You cannot collect profiles from hosts defined by their IP addresses, but processing succeeds for the other hosts.
  
• Apply profiles as a batch operation in the IM Configuration Management window.
  You cannot apply profiles to hosts defined by their IP addresses, but processing succeeds for the other hosts.
  

[Contents][Back][Next]

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