F.5 Notes on migration (version 11-00 or later)

• When you perform an upgrade installation of PFM - Web Console 11-00 or later, Performance Management might behave differently after the version upgrade than described below. To make it behave in the same way as before the version upgrade, after installation, modify the settings for the properties in the initialization file (config.xml).

  • If a value other than ja, en, or en_US is specified for the browser's language setting and no value is specified for selectFormat in the initialization file (config.xml), the date format of the files that are output by the browser or an export operation changes from pattern-yyyyMMdd (year-month-day) to pattern-ddMMyyyy (day-month-year).

  • If no value is specified for characterCode in the initialization file (config.xml), the character code that is output by the browser or an export operation changes from Shift_JIS to UTF-8.

• When you upgrade PFM - Manager, PFM - Base, or PFM - Web Console from a version earlier than 11-00 to version 11-00 or later, the new environment requires twice as much memory as before the upgrade. Therefore, before performing an upgrade installation, carefully estimate the memory requirement. For specific memory requirements, see the Release Notes.

• If you install the version 11-00 or later of PFM - Manager or PFM - Base on the same host as the version 11-00 or earlier of PFM - RM for VM, the migration command (jpcaovm2rmvm) cannot be used.

• When the conditions listed below are satisfied, first execute the migration command (jpcaovm2rmvm command) to migrate to PFM - RM for VM, and then upgrade PFM - Manager or PFM - Base to version 11-00 or later.

  • PFM - Agent for VM is installed on the same host as PFM - Manager or PFM - Base.

  • You plan to execute the migration command (jpcaovm2rmvm command) to migrate from PFM - Agent for VM to PFM - RM for VM version 10-00.

  • You plan to upgrade only PFM - Manager or PFM - Base to version 11-00 or later.

  When you execute the migration command after migrating PFM - Manager or PFM - Base to version 11-00 or later, the command terminates abnormally. In this case, you must upgrade PFM - RM for VM to version 11-00. For details, see the Release Notes for PFM - RM for VM.

• If you want to perform an overwrite installation of PFM - Manager or PFM - Base from a version earlier than 11-00 that was linked with NNM to version 11-00 or later, you must first perform unsetup of the NNM linkage. For details about how to perform unsetup, see F.9 Performing an unsetup of NNM linkage.

• When you perform an overwrite installation of PFM - Manager or PFM - Base from a version earlier than 11-00 to version 11-00 or later, the OpenView service (NNM Object Manager service) remains included in the following locations:

  • Template that is output by the jpcconf port define command

  • jpcconf port list command

  • Settings of the OS's services file

  Even though the service remains included, this does not affect system operation itself. To exclude the OpenView service, delete the applicable line from the services file and from the NNMEx folder (including its subordinate folders and files) that is immediately below the installation folder, and then restart Performance Management.

• In PFM - Manager and PFM - Base of version 11-00 or later, the default values of several functions are different from earlier versions. If you upgrade the version, the settings are inherited from the earlier environment. However, in the cases listed below, the settings in the environment of 11-00 or later differ from those in the earlier environment. Therefore, review the settings as needed in these cases:

  • an agent of 11-00 or later is installed on a host on which an earlier version of the agent is installed.

  • Instead of an upgrade being performed, PFM - Manager of 11-00 or later is installed on a new host, and data is imported from an earlier environment.

  The following table shows the changes.

  Table F‒1: Changes in the default values of version 11-00

  No.	Function	Changes and related notes	Setting location
  1	Synchronous execution controller for actions	Disabled → Enabled	jpccomm.ini file [Action Handler Section] Action Execution Count Limitation
  2	Function to place execution of the alarm command in a standby state when commands that cannot be concurrently executed by PFM - Manager are executing	Disabled → Enabled	jpccomm.ini file [Common Section] Alarm Command Wait Mode
  3	Function for measurement value output at alarm recovery	Disabled → Enabled (If alarms are bound whose alarm definition is set to Evaluate all data, the number of alarm events during normal recovery might increase.)	jpccomm.ini file [Common Section] Alarm Message Mode
  4	Monitoring suspension function	Disabled → Enabled	jpccomm.ini file [Common Section] Monitoring Suspend Mode
  5	Functionality for binding multiple alarm tables	Disabled → Enabled	jpccomm.ini file [Common Section] Multiple Alarm Table Bind
  6	JP1 event type when an alarm event occurs	JP1 user event → JP1 system event	Master Manager in the Services tree window, health check agent, or Action Handler property JP1 Event Configurations - Alarm - JP1 Event Mode

To Page Top