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

6.3.3 Collecting profiles

Using IM Configuration Management, you can collect valid configuration information and configuration files from the hosts.

Collect this information in the Display/Edit Profiles window.

Organization of this subsection

(1) Collecting valid configuration information

(2) Collecting configuration files per host

(3) Batch-collecting configuration files

(4) Saving configuration files

(1) Collecting valid configuration information

Valid configuration information can be collected from hosts running JP1/Base version 9.

To collect valid configuration information:

Open the Display/Edit Profiles window.

In the tree display area, select a profile.

Click the Valid Configuration Information button.

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

Figure 6-22 Collecting valid configuration information with IM Configuration Management

If collection fails, the possible causes are as follows:

Table 6-13 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.

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.

(2) Collecting configuration files per host

Profile configuration files can be collected from hosts running JP1/Base version 9.

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 6-23 Collecting configuration files with IM Configuration Management (per host)

The table below describes the configuration files you can collect per host.

Table 6-14 Configuration files that can be collected per host

Profile type Configuration file Notes

Event Forwarding Event forwarding setting file (forward) 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, #2} You must restart the service if you edited parameters other than MARKSTRS and ACTDEFS, or if the start command has been changed. If the number of files collected during batch collection exceeds the maximum number of log file traps that can be managed, a message appears and batch collection is canceled.

Event Log Trapping Action definition file for event log trapping (ntevent.conf)^#2 Collected only from a Windows host. The event server name (server) cannot be edited.

Local Action Local action execution definition file (jbslcact.conf) --

Legend:

--: Not applicable.

#1

Of the currently valid log file trapping profiles on the host, IM Configuration Management collects only the configuration files in the conf directory.

#2

JP1/Base event log traps and log file traps cannot be activated on a logical host basis. To manage trap information in a Display/Edit Profiles window connected to the logical host, the physical host corresponding to the logical host must be placed in the same system hierarchy as the logical host.

Profile type	Configuration file	Notes
Event Forwarding	Event forwarding setting file (forward)	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, #2}	You must restart the service if you edited parameters other than MARKSTRS and ACTDEFS, or if the start command has been changed. If the number of files collected during batch collection exceeds the maximum number of log file traps that can be managed, a message appears and batch collection is canceled.
Event Log Trapping	Action definition file for event log trapping (ntevent.conf)^#2	Collected only from a Windows host. The event server name (server) cannot be edited.
Local Action	Local action execution definition file (jbslcact.conf)	--

(3) Batch-collecting configuration files

You can collect profile configuration files from all the hosts in one operation. On the Host List page or IM Configuration page of the IM Configuration Management window, choose Operation and then Batch Collect Profiles.

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 6.3.6 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 6-24 Collecting configuration files with IM Configuration Management (all hosts)

The following table describes the configuration files you can collect in a batch for each version of JP1/Base on the target hosts.

Table 6-15 Configuration files that can be batch-collected by JP1/Base version

JP1/Base version Profile type

Earlier than version 9 Event Forwarding

Log File Trapping

Event Log Trapping

Version 9 Event Forwarding

Log File Trapping

Event Log Trapping

Local Action

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.

The following limitations apply to collection of configuration files for log file trapping from a host running JP1/Base version 7 or 8:

Only one configuration file is collected.

The action definition file that has the default file name (jevlog.conf) and is located in the default location (conf directory) is regarded as the valid action definition file for log file trapping.

JP1/Base version	Profile type
Earlier than version 9	Event Forwarding
Log File Trapping
Event Log Trapping
Version 9	Event Forwarding
Log File Trapping
Event Log Trapping
Local Action

(4) Saving configuration files

Configuration files collected from the hosts, or edited in IM Configuration Management - View, can be saved to the manager running IM Configuration Management.

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.

Valid configuration information cannot be saved in IM Configuration Management. Also, 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.

[Contents][Back][Next]

[Trademarks]