1.3.3 Notes about installing (for Windows)

(1) Relationship between products

JP1/IM - Manager requires JP1/Base. When you install the products, note the following:

• Any prerequisite products must be installed first and in the correct order.

• Install JP1/Base and then JP1/IM - Manager, in this order.

• Stop JP1/Base before you install JP1/IM - Manager. If you forgot to stop JP1/Base, make sure that you restart JP1/Base. If you do not restart JP1/Base, it will not be possible to manage system configuration information correctly.

To Page Top

(2) About Hitachi Network Objectplaza Trace Library (HNTRLib2)

• When you install JP1/IM - View, JP1/IM - Agent, or JP1/Base, Hitachi Network Objectplaza Trace Library (HNTRLib2) is installed, and the path of HNTRLib2 (system-drive:\Program Files\Common Files\Hitachi^#) is added to the Path Windows system environment variable.

• When you install JP1/IM - View or JP1/IM - Agent, the startup type of the Hitachi Network Objectplaza Trace Monitor 2 service (Hitachi Network Objectplaza Trace Library) is set to Automatic, the service can start automatically when the system starts.

  #: In Windows, this value might be different depending on the environment because the value of system-drive:\Program Files is determined by the setting of an OS environment variable at the time of installation.

To Page Top

(3) About the settings in the Windows environment

During installation, the information listed below is set in Windows.

• The bin folder path of JP1/IM and the HNTRLib2 path are as follows in the system environment variables:

  Console-path\bin

  This information is added during installation of JP1/IM - Manager.

  View-path\bin

  This information is added during installation of JP1/IM - View.

  system-drive:\Program Files\Common Files\Hitachi^#

  This information is added when either JP1/IM - View or JP1/Base is installed.

  In the services file, the port numbers indicated in Appendix C. Port Numbers in the JP1/Integrated Management 3 - Manager Overview and System Design Guide are set. The port numbers are deleted during uninstallation.

  #: In Windows, this value might be different depending on the environment because the value of system-drive:\Program Files is determined by the setting of an OS environment variable at the time of installation.

To Page Top

(4) About changing an installation path

• To change an installation path, first uninstall and then install again.

• If you are changing the installation path of JP1/Base (by uninstalling it and then reinstalling in a different folder), you must first uninstall JP1/IM - Manager and then reinstall it.

  To reinstall JP1/IM - View on the same host as for JP1/Base, uninstall JP1/IM - View first, delete the files under the conf and bin folders at the installation destination, and then reinstall JP1/IM - View.

• When you change the installation path of JP1/IM - Manager, JP1/IM - View, or JP1/Base, definitions cannot be recovered from a backup. You must re-specify individual definitions after reinstallation.

To Page Top

(5) About the files and the registry

• Do not perform the following operations, because JP1/IM - Manager and JP1/IM - View manages such information as program information, configuration information, and maintenance information in files and in the registry. If you perform the following operations, JP1/IM - Manager and JP1/IM - View may not work properly.

  • Use an application such as Explorer to delete or change files and folders for JP1/IM - Manager. Or, change the access permissions.

  • Use Registry Editor to delete or change the information on JP1/IM - Manager, or change the access permissions.

• Do not create a file or a folder named system-drive:\Program. If a file or folder has the name described above, some problems occur, such as the jcodbsetup or jcfdbsetup command outputting the following message and terminating abnormally:

  KNAN11053-E An attempt to read a file failed. (file name = instdb.log)

  In addition, if a file or folder has the name described above, various programs, including JP1/IM - Manager, might not work normally.

To Page Top

(6) About reinstallation

When JP1/IM - Manager, JP1/IM - View, and JP1/IM - Agent is uninstalled, definition files and log files that were created after installation, as well as files that might be edited by the user, are not deleted. If you reinstall the program while these files remain in the system, the program might not function correctly. Therefore, if you reinstall JP1/IM - Manager, JP1/IM - View, and JP1/IM - Agent, be sure to restart the OS and use Windows Explorer to delete the folder in which JP1/IM - Manager or JP1/IM - View had been installed, and then reinstall the program.

To Page Top

(7) About downgrade installation

JP1/IM - Manager, JP1/IM - View, and JP1/IM - Agent do not support downgrade installation. If you want to downgrade a product that has been installed, uninstall the product, and then reinstall it.

To Page Top

(8) About antivirus software

• If antivirus software scans the installation destination while you are installing JP1/IM - Manager, the installation might fail. In this case, there is a conflict between the installer and the antivirus software, which causes an application error. Make sure you terminate antivirus software before performing the installation.

• Before performing installation of JP1/IM - View, be sure to close applications that lock the JP1/IM - View files such as anti-virus software. If you do not close such applications, the installation might fail.

• Before performing a version upgrade installation of JP1/IM - View, be sure to close applications that lock the JP1/IM - View files such as anti-virus software. If you do not close such applications, the installation might fail.

• After upgrading the version of JP1/IM - View, if a message such as the following is output to the event log (application) and JP1/IM - View does not start, restart the OS and then reinstall JP1/IM - View.

  Windows Installer requires a system restart. 
  Product Name: JP1/Integrated Management - View. Product Version: <XXXX>.
  Product Language: XXXX. Manufacturer: Hitachi, Ltd.. 
  Type of System Restart: X. Reason for Restart: X.

To Page Top

(9) About silent installation

JP1/IM - Manager can be installed by using the silent installation functionality. Execute the following command:

<DVD-R-media>\_OWNEXE\HPPSINST.BAT /<full-path-of-DISK1-of-target-product> /<full-path-of-installation-destination>

JP1/IM - View can be installed by using the silent installation functionality. Execute the following command:

<DVD-R-media>\_OWNEXE\HPPSINST.BAT /<full-path-of-DISK1-of-target-product> /<full-path-of-installation-destination>

The silent installation feature provides an installation method for JP1/IM - Agent.

Command

• Case of the offering medium:

  <DVD-R-media>\_OWNEXE\HPPSINST.BAT /<DVD-R-media>\_PPDIR\PCC2A2C9GDL\DISK1 /<full-path-of-installation-destination>

• For JP1/IM - Agent packages downloaded from integrated operation viewer:

  msiexec /i JP1/IM - Agent-Package\DISK1\JP1IMAgent.msi /qn STARTFROM=NETM

• To execute the contents of DVD-R media directly from a hard drive, copy the contents of the DVD-R media to a directory on the hard drive whose path does not include any spaces. Then, compare the copied files to the original files (at the binary level, for example) to ensure that they are the same.

• Check the return value of the execution result to verify that the installation ended successfully. For details about the return values, see the JP1 website.

• If you install JP1/IM - Manager, JP1/IM - View, and JP1/IM - Agent with the silent install feature, you can not specify user information. To specify user information, install software product in the installation procedure described in the 1.3.1 Installation procedure (for Windows).

• JP1/IM - Agent must be set in setx command prior to installing with the silent install feature.

  After silent installation, execute setx command again to clear the user environment variables.

To Page Top

(10) About Windows Defender

If you install JP1/IM - Manager while Windows Defender is enabled, a Windows Defender warning event might be output to the Windows Defender history or event viewer Windows log (system log). This warning can be safely ignored.

To Page Top

(11) About restarting after performing an overwrite installation

When you perform an overwrite installation without using JP1/NETM/DM, you can operate JP1/IM - Manager and JP1/IM - View without restarting your computer, by performing the following procedure.

1. Close the following programs before performing the overwrite installation.

   • JP1/IM - Manager and JP1/IM - View

   • Applications that lock the files in the installation folder for JP1/IM - Manager and JP1/IM - View (such as applications that check for viruses)

   • All services of JP1/Base

   • All services of the products that require JP1/Base

   • Services of the integrated trace function

2. After installing the JP1/IM - Manager and JP1/IM - View, select "No" if you are asked to restart the computer.

To Page Top

(12) When using ReFS

If you install JP1/IM - Manager on Windows Server 2016, Windows Server 2019, Windows Server 2022 or Windows Server 2025 ReFS, performance might decrease compared to installations on NTFS. Therefore, if you use ReFS, conduct sufficient testing of actual operations to make sure that there is no problem with performance. If the performance requirements are not satisfied, consider using NTFS instead of ReFS.

To Page Top

(13) About JP1/IM - View

• Do not apply Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025 data deduplication on the volume on which JP1/IM - View is installed.

• If you attempt to perform an overwrite installation while JP1/IM - View is being used, a dialog box appears. In this case, click the Cancel button to abort the overwrite installation, stop all running JP1/IM - View instances, and then retry the overwrite installation of JP1/IM - View.

To Page Top

(14) Notes on upgrading JP1/IM - Agent from version 13-00 or 13-01

• The following vulnerable cipher suites are not supported for certificates required when encrypting communication between JP1/IM agent management base and JP1/IM agent control base:

  • "TLS_RSA_WITH_AES_128_CBC_SHA" up to TLS1.2

  • "TLS_RSA_WITH_AES_256_CBC_SHA" up to TLS1.2

  • "TLS_RSA_WITH_AES_128_GCM_SHA256" (TLS1.2 only)

  • "TLS_RSA_WITH_AES_256_GCM_SHA384" (TLS1.2 only)

  If you are using the cipher suites above, change the certificate to use the cipher suites that you want to support. For supported cipher suites, see Supported Cipher Suites in 3.15.7(1)(c) Encrypted communication in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

• If you are using Yet another cloudwatch exporter, make sure that the service-name specified in exportedTagsOnMetrics parameter of Yet another cloudwatch exporter configuration file (jpc_ya_cloudwatch_exporter.yml) is also specified in type of jobs parameter. If not specified, JP1/IM - Agent 13-10 or later Yet another cloudwatch exporter might fail to start theservice.

To Page Top

(15) Notes on upgrading JP1/IM - Agent from version 13-00 to 13-10

When JP1/IM - Agent is upgraded, executable row is updated and the first arguments row is added to service definition file shown in the following tables in order to apply OSS wrapper to OSS corresponding to the add-on management function. In JP1/IM - Agent installer log, verify that KAVB9447-I messaging is displayed for the respective service definition file. For details about JP1/IM - Agent installer log, see 12.2.2(8) Installer Log in the JP1/Integrated Management 3 - Manager Administration Guide.

If KAVB9448-W and KAVB9450-W messages are displayed, manually edit the appropriate service definition file to update executable line and add the first line of arguments line. For descriptions of executable line and arguments line, see Service definition file (jpc_program-name_service.xml) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

To Page Top

(16) Notes on upgrading JP1/IM - Manager from version 13-00 to 13-11 to 13-50 or later

When JP1/IM - Manager is upgraded, the recommended settings for log output of the Intelligent Integrated Management Database are not reflected.

Check the setting values of the following parameters of Intelligent Integrated Management Database configuration file (postgresql.conf). If there are no parameters or the settings are different from those listed below, set them as shown below.

For details about the parameters of Intelligent Integrated Management Database configuration file and for information about reflecting changed settings, see Intelligent Integrated Management Database configuration file (postgresql.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

To Page Top