1.19.7 Specifying settings for upgrading (for Windows)
This subsection describes the setup items to be specified during upgrade installation of JP1/IM - Manager.
If you are using IM database, you must update IM database by referring to 1.4.5 Updating IM databases (for Windows).
- Organization of this subsection
(1) Executing the Central Scope upgrade command
If you have upgraded JP1/IM - Central Scope from version 8 or earlier, apply the procedure below to execute the upgrade command. Until you execute the upgrade command, JP1/IM - Central Scope will run in the mode that is compatible with the old version of JP1/IM - Central Scope (no new functions can be used).
To execute the Central Scope upgrade command:
-
Terminate JP1/IM - Manager.
-
Check the available disk capacity.
To execute the jp1csverup.bat command in the next step, you will need sufficient free space for the monitoring object database. The monitoring object database includes all the data in the following folder:
Scope-path\database\jcsdb\
-
Execute the jp1csverup.bat command.
-
Execute the jbssetcnf command.
Whether the following functions are enabled or disabled depends on the settings of the old version of JP1/IM - Central Scope:
-
Completed-action linkage function
-
Monitoring of the maximum number of status change events
To enable these functions, execute the jbssetcnf command using the files shown in the table below as arguments.
Table 1‒9: Setting files for enabling functions File name
Description
action_complete_on.conf
File for enabling the completed-action linkage function
evhist_warn_event_on.conf
File for enabling the JP1 event issuance function when the number of status change events for the monitored object exceeds the maximum value (100)
-
-
Start JP1/IM - Manager.
-
Use JP1/IM - View to connect to JP1/IM - Manager (JP1/IM - Central Scope) to check for any problems.
-
About the jp1csverup.bat command
See jp1csverup.bat (Windows only) in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
(2) Updating the automated action definition file
If you have upgraded JP1/IM - Manager from version 11-10 or earlier, apply the procedure below to update the automated action definition file.
If you want to continue using the automated action definition file for version 11-10 or earlier as is, there is no need to perform this procedure.
To update the automated action definition file:
-
Terminate JP1/IM - Manager.
-
Execute the following jcadefconv command to update the automated action definition file:
jcadefconv -i action-definition-file-name-before-conversion -o action-definition-file-name-after-conversion
-
Rename the file specified for the -o option of the jcadefconv command to actdef.conf, and then move the file to the correct location.
The path name (including the file name) of the correct location is shown below. Note that you do not need to perform this step if the file name that was specified for the -o option in step 2 is the path name including the file name shown below.
For a physical host: Console-path\conf\action\actdef.conf
For a logical host: shared-folder\jp1cons\conf\action\actdef.conf
-
Start JP1/IM - Manager.
-
About the automated action function
See Chapter 6. Command Execution by Automated Action (JP1/Base linkage) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
-
About the jcadefconv command
See jcadefconv in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
(3) Specifying the event report output format
If you have upgraded from JP1/IM - Manager version 10-50 or earlier, the function for assigning one column to each program-specific extended attribute when event reports are output in CSV format is disabled. To specify whether this function is to be enabled, use the PROGRAM_SPECIFIC_EX_ATTR_COLUMN parameter in the environment definition file for event report output (evtreport.conf). This function is enabled when you perform a new installation. If necessary, configure the environment definition file for event report output.
For details about the environment definition file for event report output, see Environment definition file for event report output (evtreport.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
(4) Displaying the Start the process automatically when the log file trap service starts check box
If you have upgraded JP1/IM - Manager from version 11-01 or earlier, the Start the process automatically when the log file trap service starts check box is disabled (hidden).
You can use the LOGFILETRAP_AUTO_START_CONTROL parameter in the profile management environment definition file (jp1cf_profile_manager.conf) to specify the enable/disable setting for the Start the process automatically when the log file trap service starts check box. For details, see Profile management environment definition file (jp1cf_profile_manager.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
(5) Updated agent profile notification function
If you have upgraded JP1/IM - Manager from version 11-01 or earlier, the updated agent profile notification function is disabled.
You can use the AGENT_PROFILE_UPDATE_NOTICE parameter in the profile management environment definition file (jp1cf_profile_manager.conf) to specify the enable/disable setting for the updated agent profile notification function. For details, see Profile management environment definition file (jp1cf_profile_manager.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
(6) Setting for monitoring logs while remote monitoring is stopped
If you have upgraded JP1/IM - Manager from version 11-01 or earlier, the log data that is output while remote monitoring is stopped is set to be not collected.
You can use the START_OPTION parameter in the remote log trap environment definition file (jp1cf_remote_logtrap.conf) to specify the setting for whether log data that is output while remote monitoring is stopped is to be collected. For details, see Remote log trap environment definition file (jp1cf_remote_logtrap.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
(7) Upgrading the Intelligent Integrated Management Base (for Windows)
If you are using the Intelligent Integrated Management Base, you can upgrade it as follows:
When upgrading a linked product at the same time, upgrade the linked product prior to do step 5.
-
Terminate JP1/IM - Manager.
-
When upgrading JP1/IM - Manager from version 12-50 or earlier, construct the Intelligent Integrated Management Database.
For details, see 1.5 Construction of Intelligent Integrated Management Database (for Windows).
-
Add new settings.
Add new settings corresponding to the new functions you are going to use.
-
Start JP1/IM - Manager.
-
Execute the jddcreatetree command.
-
Execute the jddupdatetree command in new and rebuilding mode.
-
jddcreatetree command
For details, see jddcreatetree in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
jddupdatetree command
For details, see jddupdatetree in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
Unless you upgrade the Intelligent Integrated Management Base, you cannot use the functionality provided by Intelligent Integrated Management Base 13-00.