3.9.2 Notes on operating PFM - RM for Platform

• Before you start PFM - Remote Monitor for Platform, confirm that a connection to the monitoring target host can be established by using WMI or SSH.

• When you perform a new installation of this product, the first icon displayed might be replaced immediately by another icon. This problem concerns only what icon is displayed. Product operation is not affected.

• For notes on executing the jpctool service list command for the Remote Monitor Collector service or Remote Monitor Store service, see the chapter that describes commands in the manual JP1/Performance Management Reference.

• For notes on executing the jpcspm start command or the jpcspm stop command for PFM - RM for Platform, see the chapter that describes commands in the manual JP1/Performance Management Reference.

• If a disk device name points to a different disk device as a result of changes to the system configuration, the continuity of the performance information will be lost despite the disk device name remaining the same.

• When the user specified in the RMHost_User parameter of the instance settings logs off, a situation might occur in which the Microsoft-Windows-UserProfilesService1530 event is registered in the application event log and performance information cannot be collected. In this case, take the following actions:

  1. From the Windows Start menu, choose Run.

  2. Enter gpedit.msc and then click OK.

     The Group Policy window appears.

  3. Expand the tree by clicking Computer Configuration, Administrator Templates, System, and then User Profile.

  4. Right-click [Do not forcibly unload the user registry at user logoff], and then choose Properties.

     The properties window for the [Do not forcibly unload the user registry at user logoff] policy appears.

  5. Display the Settings page and select Enabled.

  6. Click OK.

     The properties window for the [Do not forcefully unload the user registry at user logoff] policy closes.

  7. Restart the OS.

• Due to the effects of a virus detection program, file access permission for the files and folders used by Performance Management might be locked by the exclusion control function. As a result, the following symptoms might occur:

  • Performance Management cannot be started.

  • Performance information cannot be collected, or collection is delayed.

  • A Performance Management command terminates abnormally.

  • Logs cannot be output, or a problem cannot be investigated.

  If you want to check viruses while Performance Management is running, deselect the files (including the files in the new storage location if you changed the storage location of the Store database) under the installation folder of Performance Management.

  If you want to check viruses when Performance Management stops and then to restart Performance Management, confirm that the virus check for the files under the installation folder of Performance Management (including the files in the new storage location if you changed the storage location of the Store database) is complete.

• For notes about operations in a Docker environment, see the document JP1/Performance Management Points to Remember for Docker Environments on the JP1 website.

To Page Top