3.5.1 Setting the profiles on hosts in an agent configuration

The following profiles for information can be set in the configuration file:

Profiles (Information in the configuration file)

This is the configuration file stored at the agent. The JP1/Base services do not use the settings in a configuration file. If you edit a configuration file but do not apply the modified information to the services, the valid configuration information will differ from the settings in the configuration file.

The following table describes the types of profiles you can manipulate, the types of operations you can perform on profiles, and the configuration files that correspond to the profiles.

Table 3‒3: Types of profiles and configuration files that correspond to the profiles
Operation	Type of profile you can manipulate	Corresponding configuration file
Add, delete	Log file trap information	Log file trap action-definition file Log-file trap startup definition file
Edit, save, temporarily apply, apply by reloading configuration files, apply by restarting log file traps	Event transfer information Log file trap information Event log trap information Local action information	Log file trap action-definition file Log-file trap startup definition file

Note that you can start and stop only log file traps.

For details about the prerequisites for setting the profiles on hosts in an agent configuration, see 3.5.1(8) Prerequisites for managing profiles on agents.

Organization of this subsection

(1) Collecting profile lists
(2) Collecting profiles
(3) Displaying profiles
(4) Adding or deleting profiles
(5) Editing configuration files
(6) Applying edited information in configuration files
(7) Starting or stopping log file traps
(8) Prerequisites for managing profiles on agents

(1) Collecting profile lists

Lists of profiles that are to be managed by IM Configuration Management can be collected from the agents. The collected information is displayed in the tree area of the Display/Edit Profiles window.

The profile lists are placed in unregistered status at the time of any of the following operations:

Initial startup of IM Configuration Management
Collection of host information
Reflection of system hierarchy
Execution of the jcfimport command

To collect profile lists:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent from which you want to obtain a list of profiles.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area, select a JP1 product name (JP1/Base), and then use either of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- Right-click to display a pop-up menu and choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
From the tree area, choose a JP1 product name (JP1/Base), and then use one of the following methods to update a profile list:
- From the menu bar, choose Operation, and then Rebuild Profile Tree.
- From the pop-up menu that is displayed by right-clicking, choose Rebuild Profile Tree.
The profile tree is rebuilt and the profile list is updated. If you have restarted the agent or the agent's JP1/Base, rebuild the profile tree before you edit or apply the profile.

Notes

If profile tree rebuild processing fails, an error message is displayed, together with the profile tree that existed before the rebuild processing was executed. Although you can perform operations on the profiles that existed before the rebuild processing was performed and on profiles whose information is still the same as at the agents, such operations might have adverse effects on future operations. Therefore, eliminate the cause of the error, and then perform the profile tree rebuild processing again.
Collection of profile lists fails if multiple log file traps are started using the same operation definition file or using operation definition files with the same name in different directories. Note that when the OS of the JP1/IM - Manager host is Windows, the names of configuration files used on agents are not case sensitive.
When you rebuild a profile tree, all the profiles stored on the manager are deleted and profile lists are collected from the agents again. If the profiles have not been applied to agents, apply them first and then rebuild the profile tree.

To Page Top

(2) Collecting profiles

There are two ways to collect the JP1/Base profiles from the agents, depending on the collection range. This subsection describes the two methods.

(a) Collecting profiles in batch mode

The following describes how to batch-collect JP1/Base profiles from all the agents defined in a system hierarchy (IM configuration).

Note that profile collection cannot be performed in batch mode in the following cases:

Another user has exclusive editing rights for one of the configuration files.
Another user is performing batch collection of profiles.
Another user is performing batch reflection of edited information in the configuration files.

To collect profiles in batch mode:

In the IM Configuration Management window, click the Host List or IM Configuration tab.

The Host List page or the IM Configuration page is displayed.
From the menu bar, choose Operation, then Batch Collect Profiles.

When a confirmation message asking whether you wish to collect profiles in batch mode is displayed, choose Yes. Profiles are collected in batch mode and stored on the manager running IM Configuration Management. The execution result is displayed in the Execution Results window.

After executing the batch collection, you can check profile status in the Display/Edit Profiles window. If there is a profile whose collection has failed, its Configuration file contents in the node information display area is grayed out, and the profile status is displayed in Status.

After executing batch collection of profiles, you can check agent status on the IM Configuration page in the Configuration Management window. If there is a profile whose collection has failed, a host icon indicating the error status is displayed in the tree area on the IM Configuration page. To view the detailed information, click the Basic Information button in the node information display area on the IM Configuration page.

(b) Collecting profiles individually from each agent

The following describes how to collect profiles individually from each agent.

Note that profiles cannot be collected while another user has exclusive editing rights for the configuration files.

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent from which you want to collect profiles.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area, choose a JP1 product name (JP1/Base), and then use one of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- From the pop-up menu that is displayed by right-clicking, choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
Click the Configuration File button.

The Configuration File page is displayed.

If you have never collected configuration files, clicking the Configuration File button automatically starts configuration file collection.
On the Configuration File page, in the tree area, select a profile you want to obtain. Then use either of the following methods to collect it:
- From the menu bar, choose Operation, and then Collect Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Collect Profiles.
When a confirmation message asking whether you wish to collect the target profile from the agent is displayed, choose Yes. Profiles are collected and stored in the manager where IM Configuration Management is running.

To Page Top

(3) Displaying profiles

You can display the profiles stored on the manager running IM Configuration Management by using either of two methods according to the information to be displayed. This subsection describes both methods.

(a) Displaying the valid configuration information

To display the valid configuration information for each agent:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent whose valid configuration information you want to display.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area of the Display/Edit Profiles window, choose an item for which valid configuration information is to be displayed.
Click the Valid Configuration Information button.

The valid configuration information that is displayed depends on the item selected in the tree area of the Display/Edit Profiles window. For details about the relationship between the selected item and the displayed information, see 5.9.1 Valid Configuration Information page in the manual JP1/Integrated Management 2 - Manager GUI Reference.

(b) Displaying configuration files

The following describes how to display the configuration files of each agent. These files are displayed in the Display/Edit Profiles window.

To display configuration files:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent whose configuration files you want to display.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area of the Display/Edit Profiles window, choose an item for which the configuration file is to be displayed.
Click the Configuration File button.

The contents of the configuration file that is displayed depends on the item selected in the tree area of the Display/Edit Profiles window. For details, see 5.9.2 Configuration File page in the manual JP1/Integrated Management 2 - Manager GUI Reference.

Whether the information displayed in a configuration file can be edited depends on the item. For details about how to edit the configuration files, see 3.5.1(5) Editing configuration files.

To Page Top

(4) Adding or deleting profiles

You can use IM Configuration Management to add profiles to the existing profiles stored on the manager running IM Configuration Management or delete profiles from the manager.

(a) Adding profiles

To add a profile:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent whose profile you want to add to the manager.
Use either of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose View, and then Display Profiles.
- Right-click to display a pop-up menu, and choose Display Profiles.
In the tree area, select a JP1 product name (JP1/Base), and then use either of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- Right-click to display a pop-up menu, and choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
Click the Configuration File button.

The Configuration File page is displayed.
On the Configuration File page, in the tree area, select Log File Trapping.
Use either of the following methods to display the Add Profile window:
- From the menu bar, choose Edit, and then Add Profile.
- Right-click to display a pop-up menu, and choose Add Profile.
Enter values in the following boxes.
- Log file trap name
  
  You cannot specify an existing log file trap name or a name that is the same as the log file trap action-definition file. For details, see 5.10 Add Profile window in the manual JP1/Integrated Management 2 - Manager GUI Reference.
  
  When you configure a log file trap for a cluster system, specify the same log file trap name in the Add Profile window on the physical host running as the active server and in the Add Profile window on the physical host running as the standby server. This item is mandatory.
- Cluster ID
  
  When you configure a log file trap for a cluster system, on the physical host running as the active server, select the Enable check box and enter a cluster ID in the ID box.
  
  On the physical host running as the standby server, in the Add Profile window, enter the same cluster ID you entered on the active server. This item is optional.
Click the OK button.

The name of the added log file trap name of the log file trap appears in the tree area.

For details about how to edit the configuration file for log file traps, see 3.5.1(5) Editing configuration files.

When you add the profile of a log file trap, the log file trap name is displayed in gray in the tree area because the log file trap is not running yet. For details about how to start log file traps, see 3.5.1(7)(a) Starting log file traps.

(b) Deleting profiles

The following describes how to delete profiles.

You cannot delete profiles in the following case:

The log file trap corresponding to the selected profile is running.

If the log file trap is running, stop it. For details about how to stop log file traps, see 3.5.1(7)(b) Stopping log file traps.

To delete a profile:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent whose profile you want to delete from the manager.
Use either of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose View, and then Display Profiles.
- Right-click to display a pop-up menu, and choose Display Profiles.
In the tree area, select a JP1 product name (JP1/Base), and then use either of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- Right-click to display a pop-up menu, and choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
Click the Configuration File button.

The Configuration File page is displayed.
On the Configuration File page, in the tree area, select the applicable log file trap name.

In the tree area, under Log File Trapping, a list of the log file trap names appears. Select the log file trap name you want to delete.
Use either of the following methods to delete the log file trap name:
- From the menu bar, choose Edit, and then Delete Profile.
- Right-click to display a pop-up menu, and choose Delete Profile.
When a message appears asking whether you want to delete the log file trap name, click the Yes button.

The log file trap name is deleted.

To Page Top

(5) Editing configuration files

The following describes how to edit and save the configuration files collected as described in 3.5.1(2) Collecting profiles. You can use the Display/Edit Profiles window to edit and save a configuration file.

To edit and save a configuration file:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent whose configuration file you want to edit.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area, choose a JP1 product name (JP1/Base) and then use one of the following methods to obtain exclusive editing rights:

When you cut or paste the character strings in a configuration file, make sure that you obtain exclusive editing rights first.
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- From the pop-up menu that is displayed by right-clicking, choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained or you are copying only the character strings in a configuration file.
From the tree area in the Display/Edit Profiles window, choose the configuration file that is to be edited.
In the node information display area in the Display/Edit Profiles window, click the Configuration File button.

The contents of the configuration file are displayed for the profile that is stored at the manager where IM Configuration Management is running and that is to be edited and saved. For details about the items that can be edited, see 5.9.2 Configuration File page in the manual JP1/Integrated Management 2 - Manager GUI Reference.
When you have finished editing, from the menu bar, choose Operation, Save/Apply Profiles, and then Save on the Server.

The edited configuration file is saved in the manager where IM Configuration Management is running.

Note that the contents of the configuration file that was stored in the manager where IM Configuration Management is running are not forwarded to the agent. When you perform reflection processing on the configuration file, its contents are saved automatically. For details about how to forward and apply the contents of configuration files, see 3.5.1(6) Applying edited information in configuration files.

If you save the contents of a configuration file in the manager where IM Configuration Management is running and then collect the profile from the agent, the configuration file will be overwritten by the collected information. If you want to apply a configuration file to the agent, make sure that you do so before you collect profiles.

To Page Top

(6) Applying edited information in configuration files

After you edit a configuration file on the manager, you can apply the new information to all the agents in batch mode or to each agent individually.

After applying a configuration file, you can check whether the operation was successful on the Configuration File page in the Display/Edit Profiles window. If it was successful, Application status is Applied. If the configuration file could not be applied, Application status is Application failed. If the configuration files stored on the manager are not used, Application status is blank (not applied). If configuration files are stored on the manager but not used on the target agent, Application status is Saved on the server.

When Application status is Application failed or Saved on the server, the icon displayed in the tree area on the Configuration File page indicates that the configuration file is being edited.

In the case of JP1/Base version 9, if configuration file reflection processing fails, the agent's configuration file is rolled back to the original configuration file.

After applying a configuration file, you can check the status of the agent on the IM Configuration page in the IM Configuration Management window. If Application status of any of the configuration files is Application failed or Saved on the server on the Configuration File page, the agent icon in the tree area of the IM Configuration page indicates an error. To view the details, click the Basic Information button in the node information display area on the IM Configuration page.

(a) Using the batch mode to apply edited information in configuration files

The following describes how to batch-apply the modified information in configuration files to all the agents registered in a system hierarchy (IM configuration) at one time.

The batch mode cannot be used to apply edited information in configuration files in the following cases:

Another user has exclusive editing rights for one of the configuration files.
Another user is performing batch collection of profiles.
Another user is performing batch reflection of edited information in configuration files.

To use the batch mode to apply edited information in configuration files:

In the IM Configuration Management window, click the Host List or IM Configuration tab.

The Host List page or the IM Configuration page is displayed.
From the menu bar, choose Operation, and then Batch Reflect Profiles.

Batch reflection of profiles is executed. The execution result is displayed in the Execution Results window.

When a confirmation message asking whether you wish to perform batch reflection of configuration files is displayed, choose Yes. The contents of the configuration files stored at the manager where IM Configuration Management is running are applied to all hosts. If no configuration files are found on the manager, the KNAN22497-I message appears and no configuration file is applied.

(b) Applying edited information in configuration files individually to each agent

Three methods are available for applying the modified information in configuration files to each agent.

■ By reloading

You can reload configuration files onto an agent to apply the modified information in the configuration files.

You cannot use reloading to apply the modified information in configuration files in the following case:

The selected log file trap is not running when you attempt to apply the log file trap profile.

To apply the modified information in a configuration file by reloading the configuration file:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent to which you want to apply the modified information in a configuration file by reloading the file.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area, choose a JP1 product name (JP1/Base) and then use one of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- From the pop-up menu that is displayed by right-clicking, choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
In the tree area, select the profile you want to apply, and then click the Configuration File button.

The Configuration File page is displayed.

This step is unnecessary if you are currently editing the profile (configuration file) you want to apply.
On the Configuration File page, in the node information display area, in the Saving/application section, click the two options below. Then click the Execute button.
- Apply
- Reload
The profile is applied.

When a message appears asking whether you want to apply the information in the configuration file, click the Yes button.

■ By restarting a log file trap

The following describes how to apply the modified information in configuration files by restarting a log file trap.

You cannot apply the modified information in configuration files by restarting a log file trap in the following cases:

The selected log file trap is not running.
The selected log file trap is not specified in the log-file trap startup definition file.
A cluster ID is specified.

To apply the modified information in a configuration file by restarting a log file trap:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent to which you want to apply the modified information in a configuration file by restarting a log file trap.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area, choose a JP1 product name (JP1/Base) and then use one of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- From the pop-up menu that is displayed by right-clicking, choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
In the tree area, select the log file trap name you want to apply, and click the Configuration File button.

The Configuration File page is displayed.

This step is unnecessary if you are currently editing the profile (configuration file) you want to apply.
On the Configuration File page, in the node information display area, in the Saving/application section, click the following two options.
- Apply
- Restart
When a message appears asking whether you want to apply the information in the configuration file, click the Yes button. The profile is applied.

■ By sending configuration files to agents

The following describes how to apply the modified information in configuration files by sending the configuration files from the manager to agents.

The following are the methods of applying modified information through file transmission:

Applying the modified information by sending the configuration files collected from agents
Applying the modified information by sending the configuration files added from IM Configuration Management

IM Configuration Management can collect configuration files from the agents' folders shown in the following. When the collected configuration files are sent, the configuration files are applied to the same folders as those from which they were collected.

Table 3‒4: Send destinations for configuration files (when sending the configuration files collected from agents)
Configuration file	Type of OS on agent	Send destination
Log file trap action-definition file	Windows	`Base-path\conf`
		`Base-path\conf\any-folder`
		`Base-path\conf\cf_log_file_trap`
	UNIX	`/etc/opt/jp1base/conf`
		`/etc/opt/jp1base/conf/any-directory`
		`/etc/opt/jp1base/conf/cf_log_file_trap`
Log-file trap startup definition file	Windows	`Base-path\conf\event\`
Log-file trap startup definition file	UNIX	`/etc/opt/jp1base/conf/event/`

When the configuration files added from IM Configuration Management are used to apply information, the configuration files are sent to the following folders.

Table 3‒5: Send destinations for configuration files (when sending the configuration files added from IM Configuration Management)
Configuration file	Type of OS on agent	Send destination
Log file trap action-definition file	Windows	`Base-path\conf\cf_log_file_trap\`
Log file trap action-definition file	UNIX	`/etc/opt/jp1base/conf/cf_log_file_trap/`
Log-file trap startup definition file	Windows	`Base-path\conf\event\`
Log-file trap startup definition file	UNIX	`/etc/opt/jp1base/conf/event/`

You cannot apply the modified information in configuration files to agents by sending them in the following cases:

The version of JP1/Base on agents is earlier than 09-10.
The selected log file trap is running on agents.
The agent's JP1/Base version is earlier than 11-10 and a cluster ID is not specified.

To apply the modified information in a configuration file by sending a file:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent to which you want to apply the modified information in a configuration file.
Use one of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose Display, and then Display Profiles.
- From the pop-up menu that is displayed by right-clicking, choose Display Profiles.
From the tree area, choose a JP1 product name (JP1/Base) and then use one of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- From the pop-up menu that is displayed by right-clicking, choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
In the tree area, select the applicable log file trap name and click the Configuration File button.

The Configuration File page is displayed.

This step is unnecessary if you are currently editing the profile (configuration file) you want to apply.
On the Configuration File page, in the node information display area, in the Saving/application section, click the two options below. Then click the Execute button.
- Apply
- Send a file
The profile is applied.

When a message appears asking whether you want to apply the information in the configuration file, click the Yes button. The configuration file is sent to a preset folder.

To Page Top

(7) Starting or stopping log file traps

You can start or stop log file traps on agents.

(a) Starting log file traps

The following describes how to start log file traps.

You cannot start a log file trap in the following cases:

The selected log file trap is already running.
The version of JP1/Base is earlier than 09-10.
A cluster ID is specified.

To start a log file trap:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent on which you want to start a log file trap.
Use either of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose View, and then Display Profiles.
- Right-click to display a pop-up menu, and choose Display Profiles.
In the tree area, select a JP1 product name (JP1/Base), and then use either of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- Right-click to display a pop-up menu, and choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
In the tree area, select the applicable log file trap name.
Use either of the following methods to start the log file trap:
- From the menu bar, choose Operation, and then Start Process.
- Right-click to display a pop-up menu, and choose Start Process.
When a message appears asking whether you want to start the log file trap, click the Yes button. The log file trap starts.

(b) Stopping log file traps

The following describes how to stop log file traps.

You cannot stop log file traps in the following cases:

The version of JP1/Base on agents is earlier than 09-10.
The selected log file trap is not running.
A cluster ID is specified.

To stop a log file trap:

In the IM Configuration Management window, click the IM Configuration tab.

The IM Configuration page is displayed.
On the IM Configuration page, in the tree area, select the agent on which you want to stop a log file trap.
Use either of the following methods to display the Display/Edit Profiles window:
- From the menu bar, choose View, and then Display Profiles.
- Right-click to display a pop-up menu, and choose Display Profiles.
In the tree area, select a JP1 product name (JP1/Base), and then use either of the following methods to obtain exclusive editing rights:
- From the menu bar, choose Edit, and then Exclusive Editing Settings.
- Right-click to display a pop-up menu, and choose Exclusive Editing Settings.
This step is unnecessary if exclusive editing rights have already been obtained.
In the tree area, select the applicable log file trap name.
Use either of the following methods to stop the log file trap:
- From the menu bar, choose Operation, and then Stop Process.
- Right-click to display a pop-up menu, and choose Stop Process.
When a message appears asking whether you want to stop the log file trap, click the Yes button. The log file trap stops.

(c) Starting or stopping log file traps for cluster systems

If you want to start or stop a log file trap for cluster systems, register the following commands in the cluster software:

jevlogstart command (only for cluster systems)
jevlogstop command (only for cluster systems)

For details, see the description of these commands in the JP1/Base User's Guide.

To Page Top

(8) Prerequisites for managing profiles on agents

When using both profile management by IM Configuration Management and profile management by JP1/Base

The version of JP1/Base on agents must be 11-10 or later.
When manipulating log file traps

If you want to perform the following operations, the version of JP1/Base on agents must be 09-10 or later:
- 3.5.1(4) Adding or deleting profiles
- 3.5.1(6)(b) Applying edited information in configuration files individually to each agent
  
  - By restarting a log file trap
  
  - By sending configuration files to agents
- 3.5.1(7) Starting or stopping log file traps
If the version of JP1/Base on agents is a version before 09-10, perform an overwrite installation of JP1/Base to version 09-10 or later. For details about overwrite installations, see the chapter on installation and setup in the JP1/Base User's Guide. To perform an overwrite installation to upgrade JP1/Base version earlier than 09-10 to 09-10 or later, perform the following operations:
- When log file traps are configured to start by using the start sequence definition file or the jbs_start command, move the definition of log file traps to the log-file trap startup definition file.
  
  For details, see the cautionary notes on installation and uninstallation in the JP1/Base User's Guide.
- Use IM Configuration Management to collect information from agents.
  
  For details, see 3.1.3 Collecting information from hosts.
When manipulating profile lists and profiles

If you want to perform the following operations, the version of JP1/Base on agents must be 9 or later.
- Collecting profile lists
- Collecting profiles
- Displaying profiles
If the version of JP1/Base is 9 and an attempt to apply the edited information in the configuration files to agents fails, the modified configuration files are rolled backed to the previous configuration files.
When log file traps are defined

If you upgrade JP1/Base on agents from a version earlier than 09-10 to 09-10 or later and log file traps are configured to start by using the start sequence definition file or the jbs_start command, you need to move the definition of log file traps to the log-file trap startup definition file. For details about how to move definitions, see the cautionary notes on installation and uninstallation in the JP1/Base User's Guide.
When starting or stopping log file traps for cluster systems
- The information in the configuration files stored on the standby server must match the information in the configuration files stored on the active server.
- If you change the configuration files on the active server or the standby server, you need to send the modified configuration files to JP1/Base on agents to apply the changes. For details about how to apply changes by sending configuration files, see By sending configuration files to agents in 3.5.1(6)(b) Applying edited information in configuration files individually to each agent.
- To start or stop log file traps, execute cluster software commands. For details, see 3.5.1(7)(c) Starting or stopping log file traps for cluster systems.

To Page Top