Hitachi

JP1 Version 13 JP1/Integrated Management 3 - Manager Overview and System Design Guide


11.3.2 Prerequisite programs

The following table lists the prerequisite programs for JP1/IM and JP1/Base.

Table 11‒5: Prerequisite programs for JP1/IM and JP1/Base

Product

Prerequisite programs

JP1/IM - View

To display the windows of a linked program in JP1/IM - View, either of the following is required (depending on the type of linked product):

  • A JP1 program or other application program to be launched from JP1/IM - View

  • Web browser

JP1/IM - Manager

Within the same machine

  • - JP1/Base

JP1/IM - Agent

Within the same machine

■For Windows

  • .NET Framework 4.6.2 or higher

■For Linux

  • tar

  • gzip

In the system
  • JP1/IM - Manager 13-00 or later#

#

Intelligent Integrated Management Base setting must be enabled for JP1/IM - Manager that co-exist with JP1/IM - Agent's product plugin.

JP1/Base

--

Legend:

--: Not required.

Important
  • In order for JP1/IM - Manager to run normally, the corresponding DLL and OS-standard DLLs are required.

    If another product injects a DLL into a JP1/IM - Manager process, it will affect the behavior of JP1/IM - Manager. This might lead to unstable operation or prevent JP1/IM - Manager from starting.

    If this problem occurs, to identify the cause, you can ask the customer to confirm whether the same problem occurs when no other products are installed.

    If the customer cannot verify that a DLL being injected by another product is not the cause of the problem, Hitachi might not be able to provide normal support service.

  • Before using JP1/IM - View via a remote desktop connection, perform the appropriate tests to verify normal operation. Regarding inquiries about the standard ways of using JP1/IM - View and failures in JP1/IM - View, issues that occur in the standard environment and those that occur in the remote desktop environment are handled in the same way. However, you might be asked to reproduce an issue in the standard environment to verify that the issue is not due to a problem with your remote desktop environment.