7.5.6 Editing configuration files

(1) Editing configuration file contents

In the Display/Edit Profiles window, you can edit the contents of a displayed configuration file.

The following configuration files can be edited in IM Configuration Management:

Table 7‒37: Configuration files that can be edited in IM Configuration Management

Profile type	Configuration file	Notes
Event Forwarding	Event forwarding setting file (forward)	--
Log File Trapping	Action definition file for log file trapping (any file)	If the version of JP1/Base on an agent host is 09-10 or later, the service must be restarted when an item other than MARKSTR and ACTDEF is edited. If the version of JP1/Base on an agent host is earlier than 09-10, do not edit any item other than MARKSTR and ACTDEF.
	Log-file trap startup definition file (jevlog_start.conf)	If the version of JP1/Base of an agent host is 09-10 or later, you can edit only the start options. The log-file trap startup definition file is updated based on the edited start options.
Event Log Trapping	Action definition file for event log trapping (ntevent.conf)	You cannot edit the event server name (server).
Local Action	Local action execution definition file (jbslcact.conf)	--
Remote-monitoring Log File Trapping	Remote-monitoring log file trap action-definition file (any file)	--
Remote-monitoring Event Log Trapping	Remote-monitoring event log trap action-definition file (any file)	--

You can perform the following operations on these files in the Display/Edit Profiles window.

Copy text

You can copy text from a configuration file. Exclusive editing rights are not required.

In the file contents shown in the node display area, select the text that you want to copy and then perform either of the following:

• Choose Edit and Copy.

• Right-click and choose Copy.

Cut text

You can cut text from a configuration file. To do so, you must first obtain exclusive editing rights.

In the file contents shown in the node display area, select the text that you want to cut and then perform either of the following:

• Choose Edit and Cut.

• Right-click and choose Cut.

Paste text

You can paste copied or cut text into a configuration file. To do so, you must first obtain exclusive editing rights.

In the file contents shown in the node display area, select the position where you want to paste the text and then perform either of the following:

• Choose Edit and Paste.

• Right-click and choose Paste.

The changes you make while editing a configuration file are not checked. If you quit or forcibly terminate IM Configuration Management - View during editing, the changes will not be saved.

To Page Top

(2) Saving edited file contents

The contents of edited configuration files can be saved to the manager running IM Configuration Management.

Edited file contents are saved when you perform any of the following operations:

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

• In the Display/Edit Profiles window, choose Operation, Save/Apply Profiles, and then Save on the Server.

• Import configuration files on the manager running IM Configuration Management.

The figure below shows the flow of processing when saving the contents of edited configuration files with IM Configuration Management.

Figure 7‒39: Saving edited file contents with IM Configuration Management

The following configuration files can be saved:

• Event forwarding setting file

• Action definition file for log file trapping

• Log-file trap startup definition file

• Action definition file for event log trapping

• Local action execution definition file

Note that the log-file trap startup definition file can be saved only when the version of JP1/Base on the agent is 09-10 or later.

The edited file contents saved to the manager running IM Configuration Management cannot be forwarded to hosts.

Edited file contents saved to the manager will be overwritten when profiles are collected from the hosts.

To Page Top

(3) Applying edited file contents

You can apply the contents of edited configuration files to JP1/Base on the agents. You can also enable the contents of the configuration files on remotely monitored hosts.

The operations for applying edited file contents differ depending on the items in the configuration file. For details about these operations, see 5.9.2 Configuration File page in the manual JP1/Integrated Management 2 - Manager GUI Reference.

The figure below shows the flow of processing when applying the contents of edited configuration files with IM Configuration Management.

Figure 7‒40: Applying edited file contents with IM Configuration Management

You can apply the edited file contents per host, or batch-apply the contents to all hosts.

On the Configuration File page of the Display/Edit Profiles window, you can check the status of a configuration file after the edited contents are applied. If the application is successful, the status becomes Applied. If the application fails, the status becomes Application failed. If the saved configuration file is not used on the server, the status becomes a blank (not applied). If the configuration file is saved on the server, but not used on the target host, the status becomes Saved on the server.

If the status of the configuration file is Application failed or Saved on the server, in the tree display area on the Configuration File page, an icon appears indicating that the configuration file is being edited.

If the processing fails in JP1/Base version 9 or later, the configuration files on the agent are rolled back to their previous status.

On the IM Configuration page of the IM Configuration Management window, you can check the status of the host after the contents are applied. If there are configuration files that have the Application failed or Saved on the server status, among host icons in the tree display area, an icon appears indicating an error status. To see the details, on the IM Configuration page, click the Basic Information button in the node display area.

Apply per host

The following configuration files can be applied per host in IM Configuration Management:

• Event forwarding setting file

• Action definition file for log file trapping

• Log-file trap startup definition file

• Action definition file for event log trapping

• Local action execution definition file

• Remote-monitoring log file trap action-definition file

• Remote-monitoring event log trap action-definition file

Note that the log-file trap startup definition file can be applied only when the version of JP1/Base on the agent is 09-10 or later.

For details about how to apply the edited contents per host, see 3.5.1(6)(b) Applying edited information in configuration files individually to each agent in the JP1/Integrated Management 2 - Manager Configuration Guide.

Apply to all hosts

The following configuration files can be applied in one operation with IM Configuration Management:

• Event forwarding setting file

• Log-file trap action definition file

• Log-file trap startup definition file

• Action definition file for event log trapping

• Local action execution definition file

Note that the log-file trap startup definition file can be applied only if the agent's JP1/Base version is 11-10 or later.

For details about how to batch-apply the edited contents, see 3.5.1(6)(a) Using the batch mode to apply edited information in configuration files in the JP1/Integrated Management 2 - Manager Configuration Guide.

When batch-applying the edited contents, if the configuration file does not exist on the server, the KNAN22497-I message is displayed, and the information is not applied.

To Page Top