12.2.2 Upgrading from version 8 JP1/IM - Manager products

Note the following points if you are upgrading to JP1/IM - Manager version 10 from a version 8 JP1/IM - Manager product.

Organization of this subsection

(1) Upgrading from the Central Console version 8
(2) Upgrading from the Central Scope version 8
(3) Using IM Configuration Management with version 10 products

(1) Upgrading from the Central Console version 8

Back up the settings information before you upgrade JP1/IM - Manager. For the procedure, see the manual for the previous version.

When you upgrade, the definition information for the Central Console is migrated from JP1/IM - Manager version 8. However, note the following points:

In a logical host (cluster) environment, you must execute the jp1cohaverup command to apply the definition information added in the current version.

See jp1cohaverup in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

If you were using the event acquisition filter (for compatibility) with the previous versions of JP1/IM - Manager and JP1/IM - Central Console, the event acquisition filter will continue to work in compatibility mode after the upgrade. The event acquisition filter (for compatibility) resides within the event console service and affects JP1 event monitoring only.

Figure 12‒2: Position of the event acquisition filter (for compatibility)

With the event acquisition filter (for compatibility), the following functions apply to all JP1 events acquired by JP1/IM - Manager:

Automated actions (automatic action service)
Central Scope (central scope service)
Issue of correlation events (event generation service)

As a result, certain anomalies may occur, depending on the filter settings. For example, an automated action may be executed, but the JP1 event that triggered it may not appear in the Event Console window.

Also, the only contents you can define in an event acquisition filter (for compatibility) are whether to acquire JP1/SES events, and whether to acquire JP1 events that have a particular event level or a particular event ID (you cannot set detailed conditions as with other filters).

To ensure consistency among the types of JP1 events acquired across the system, or to define detailed filter conditions as with other filters, execute the jcochafmod command to migrate the event acquisition filter from the event console service to the event base service. For details about migrating the settings in the event acquisition filter (for compatibility), see the table below. Change the settings and condition group names as required.

Table 12‒3: Migration of event acquisition filter settings
Settings before jcochafmode command execution	After jcochafmode command execution
No settings	Moved to Existing conditions group without any settings.
Event ID only	Moved to Existing conditions group.
Event level only	Moved to Existing conditions group.
JP1/SES events only	Moved to Existing conditions group_SES
JP1/SES events and event ID	The JP1/SES event setting and event ID^# setting are moved to Existing conditions group_SES. The event ID^# setting is moved to Existing conditions group.
Event level and event ID	Moved to Existing conditions group.
JP1/SES events and event level	The JP1/SES event setting is moved to Existing conditions group_SES. The event level setting is moved to Existing conditions group.
JP1/SES events, event level, and event ID	The JP1/SES event setting and event ID^# setting are moved to Existing conditions group_SES. The event level setting and event ID^# setting are moved to Existing conditions group.

#: The event ID setting is inherited by both condition groups.

There is no need to execute the jcochafmode command if you want to continue using the event acquisition filter from the previous version.

See jcochafmode in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

Note:: When you execute the jcochafmode command to migrate the event acquisition filter from the event console service to the event base service, you cannot move it back again. Before you execute the jcochafmode command, carefully consider the effects of repositioning the filter.

After you upgrade, the automatic action definition file (for compatibility) of the automated action function takes effect. To use version 10 action definitions, convert them to the automated action definition file for version 10 by executing the jcadefconv command.
After enabling action definitions for version 10, you can:
- Specify Match, Does not match, First characters, Is contained, Is not contained, and Regular expression as event conditions in an action definition.
- Display the Action Parameter Definitions window in JP1/IM - View version 10. If you are using the automatic action definition file (for compatibility), the Action Parameter Definitions (for compatibility) window is displayed instead.
The regular expression settings of the automated action function are migrated from the previous version. The Windows version of JP1/IM version 10 uses extended regular expressions instead of JP1-specific regular expressions. Review your use of regular expressions as required.
The same start option as the previous version is used for the event generation service. However, the default changes from cold to warm. Review the settings as required.
In UNIX, if you use the jco_start command to start JP1/IM - Manager, copy the following file to the command directory after upgrading:

Copy from: /etc/opt/jp1cons/jco_start.model

Copy to: /etc/opt/jp1cons/jco_start
The JP1/IM - Manager will have a different name and adopt a different configuration after the upgrade. In JP1/IM - Manager, if process monitoring is performed linking with JP1/Cm2/SSO with a version earlier than 8, check and, if necessary, revise the settings according to the process configuration of version 10 products.

To Page Top

(2) Upgrading from the Central Scope version 8

Back up the settings information and the databases before you upgrade JP1/IM - Manager. For the procedure, see the manual for the previous version.

When you upgrade, the definition information for the Central Scope is migrated from JP1/IM - Manager version 8, regardless of whether the Central Scope is enabled or disabled. However, note the following points:

Immediately after an upgrade, the functionality of the Central Scope is limited to that of the previous version. If you took CSV snapshots of the monitoring tree information and visual monitoring information in the previous version of JP1/IM - View, and you wish to use this information in the new version of JP1/IM - Manager (Central Scope), edit and apply the data now.

When you have applied the data or determined that none of the previous information is needed, execute the jp1csverup.bat command (in Windows) or the jp1csverup command (in UNIX) to migrate to the version 10 environment of JP1/IM - Manager (JP1/IM - Central Scope).

In a logical host (cluster) environment, you must execute the jp1cshaverup.bat command to apply the definition information added in the current version and upgrade the monitoring objects database.

For Windows systems, see jp1csverup.bat (Windows only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

For UNIX systems, see jp1csverup (UNIX only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

Reference note

In version 8 of JP1/IM - View, you can view and edit CSV files created using previous versions. The version of the CSV file appears in the title bar. You can also apply the contents of such files to the same version of JP1/IM - Manager and the Central Scope.

The Central Scope operates in the environment of the previous version until you execute the command. This allows you to apply the contents of CSV files created using previous versions of JP1/IM - View.
Consider enabling automatic backup and recovery of the monitoring objects database if this feature was not enabled in the previous version.

If the OS shuts down or if a failover occurs in a cluster system while the monitoring tree is being updated, the write operation to the monitoring objects database is interrupted and the database may be corrupted. To prevent corruption of the database, we recommend that you enable the automatic backup and recovery function for the monitoring objects database. It is particularly important to enable this function in a cluster system.

To set up the automatic backup and recovery function, execute the jbssetcnf command specifying the automatic backup and recovery settings file for the monitoring objects database (auto_dbbackup_xxx.conf) as an argument. This applies the contents of the definition file to the JP1 common definition information.

See Automatic backup and recovery settings file for the monitoring object database (auto_dbbackup_xxx.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
If the following functions were disabled in the previous version, consider enabling them:
- Completed-action linkage function
- Monitoring the maximum number of status change events
To enable these functions, edit the relevant definition files and then execute the jbssetcnf command.

See Settings file for the maximum number of status change events (evhist_warn_event_xxx.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

Also see Settings file for the completed-action linkage function (action_complete_xxx.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

To Page Top

(3) Using IM Configuration Management with version 10 products

In version 8 products, JP1/IM - Manager managed the system hierarchy (IM configuration) using the configuration management functionality provided by JP1/Base. However, in version 10 products, the system hierarchy can also be managed from IM Configuration Management.

If you intend to use IM Configuration Management to manage the system hierarchy in version 10, when you migrate the system you can convert the configuration definition information defined in JP1/Base, using the IM Configuration Management functionality. The following shows the flow of the operations done using the IM configuration management viewer:

Acquire the system hierarchy.
Collect host information.
Check and, if necessary, revise the lower-level host information, basic information, product information, and service information.

For details, see 1.9.1(2) Editing an existing system hierarchy (for Windows) or 2.8.1(2) Editing an existing system hierarchy (for UNIX) in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.

When using IM Configuration Management to manage the system hierarchy after migrating the system, do not edit the configuration definition files used by the JP1/Base configuration management functionality or execute the associated commands.

To Page Top