1.19.7 Specifying settings for upgrading (for Windows)

(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:

1. Terminate JP1/IM - Manager.

2. 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\

3. Execute the jp1csverup.bat command.

4. 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‒11: 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)

5. Start JP1/IM - Manager.

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

To Page Top

(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:

1. Terminate JP1/IM - Manager.

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

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

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

To Page Top

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

To Page Top

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

To Page Top

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

To Page Top

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

To Page Top

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

1. Terminate JP1/IM - Manager.

2. 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).

3. Add new settings.

   Add new settings corresponding to the new functions you are going to use.^#

   Note #

   When upgrading JP1/IM - Manager from 13-00 or 13-01 to 13-10 or later, add three lines ("web-enable-admin-api: true", "db-connections-max: 50", "db-writer-connection-concurrency: 1" (underlined part of "after change" below) to the end of the following file in a text editor.

   - For a physical host: Manager-pass\conf\imgndb\config.yml

   - For a logical host: shared-folder\jp1imm\conf\imgndb\config.yml

   <Example of change>

   - Before change

   db-host: localhost

   db-name: imgndb

   db-user: imuser

   db-password: rCKsdJ8vSQn2

   db-port: 20705

   web-listen-address: localhost:20706

   log-level: info

   db-ssl-mode: allow

   promql-max-points-per-ts: 30001

   - After change

   db-host: localhost

   db-name: imgndb

   db-user: imuser

   db-password: rCKsdJ8vSQn2

   db-port: 20705

   web-listen-address: localhost:20706

   log-level: info

   db-ssl-mode: allow

   promql-max-points-per-ts: 30001

   web-enable-admin-api: true

   db-connections-max: 50

   db-writer-connection-concurrency: 1

   If you do not add a "web-enable-admin-api: true" line, deleting the trend data and deleting integrated agent info will fail.

   For details on deleting trend data and integrated agent information, see 2.2.1 List of Integrated Agents window in the JP1/Integrated Management 3 - Manager GUI Reference and 5.11.4 Delete Trend Data and 5.18.2 Delete integrated agent info in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

   If you do not add the "db-connections-max: 50" and "db-writer-connection-concurrency: 1" rows, the following events may occur when collecting a large amount of performance data (when the sum of sample collected by integrated agent in the system (in the system of lower manager in a multi-stage configuration) exceeds 10,000 seconds):

   - Performance data is not saved in Intelligent Integrated Management Database and cannot be displayed and retrieved

   - Trend data management service memory usage increases

4. Start JP1/IM - Manager.

5. Execute the jddcreatetree command.

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

To Page Top

(8) Upgrading Intelligent Integrated Management Database version (for Windows)

This section describes the setting at the time of version upgrade when using Intelligent Integrated Management Database.

If you have upgraded JP1/IM - Manager from version 13-11 or earlier and you are using Intelligent Integrated Management Database, you must execute jimgndbupdate command.

If you want to see the current version of the Intelligent Integrated Management Database, you must execute jimgndbsetup command with the "-display" parameter. Also, when the Intelligent Integrated Management Database is versioned as "No Data" or "131100", jimgndbupdate command must be executed.

For details about jimgndbsetup command and jimgndbupdate command, see jimgndbsetup in Chapter 1. Commands and jimgndbupdate in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

To Page Top

(9) Updating extended startup process definition file

If you upgraded from JP1/IM - Manager version 11 or earlier, add jddmain, imbase, imbaseproxy process-definition to extended startup process definition file (jp1co_service.conf).

When upgrading from version 12, add imbase, imbaseproxy process-definition.

For details about the extended startup process definition file, see Extended startup process definition file (jp1co_service.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

To Page Top