3.2.3 Notes on installing and uninstalling JP1/Base

(1) Installation

• Do not install JP1/Base in a folder in which another program product is installed.

• The highest-level folder (JP1Base), its subfolders, and files created by JP1/Base inherit the permissions the user assigns to the installation folder. We recommend that permissions are assigned to the installation folder as follows:

  • Administrators group and SYSTEM account: Full Control

  • Users account: Read & Execute

• If the JP1/Base installer displays a dialog box that asks you whether to replace the msvcrt.dll file, always choose Restart to replace the file and to restart the system after installing JP1/Base. If you choose Ignore to leave the old version of the msvcrt.dll file on the host, JP1/Base might not operate correctly (for example, the time of an event might be incorrect).

  If installation of another product causes JP1/Base to operate incorrectly, reinstall JP1/Base.

• When you install JP1/Base, the path for the bin folder of JP1/Base is automatically added to the PATH environment variable. JP1/Base cannot be installed if this would cause the length of the PATH environment variable to exceed the maximum permitted by the operating system. In this situation, remove unwanted paths from the PATH environment variable and repeat the installation process.

• If several paths are in the PATH environment variable, paths are prioritized according to the order in which they are specified. If the path to the bin folder of JP1/Base is specified later than that of the bin folder for JP1/AJS3 - View or JP1/IM - View in the PATH environment variable, products such as JP1/IM - Manager and JP1/AJS3 that have JP1/Base as a prerequisite might not operate correctly. Make sure that the path for the JP1/Base bin folder appears before the JP1/AJS3 - View and JP1/IM - View bin folder in the PATH environment variable.

To Page Top

(2) Re-installation

• If you are performing an overwrite installation of JP1/Base, be sure to shut down all services beginning with the words JP1/Base, and quit all programs currently accessing the JP1/Base event service.

• When uninstalling JP1/Base and then reinstalling it, you must first uninstall JP1/Base and all products that require it. Then, reinstall JP1/Base and then the products that require it.

  • JP1/IM - Manager

    Uninstall both JP1/Base and JP1/IM - Manager, and then reinstall JP1/Base and JP1/IM - Manager.

  • JP1/AJS

    Uninstall both JP1/Base and JP1/AJS and then reinstall JP1/Base and JP1/AJS.

  • JP1/AJS2 for Mainframe

    Stop the services for JP1/AJS2 for Mainframe and then uninstall JP1/Base. Reinstall JP1/Base and then re-set up JP1/AJS2 for Mainframe.

  • JP1/Power Monitor

    Uninstall JP1/Power Monitor before uninstalling JP1/Base. Next, reinstall JP1/Base and JP1/Power Monitor.

• At a host running JP1/Base and JP1/IM - Manager, if you uninstall JP1/Base and then reinstall it in a folder that differs from the previous installation folder, JP1/IM - Manager will not operate correctly.

  If you want to reinstall JP1/Base in a different folder, first uninstall JP1/IM - Manager, delete its installation folder, and then reinstall JP1/IM - Manager.

• If you are using the SNMP trap converter, execute the imevtgw_setup command after reinstalling JP1/Base.

To Page Top

(3) Setting the Windows environment

At JP1/Base installation, the path of the JP1/Base bin folder and the path of the Hitachi Network Objectplaza Trace Library (HNTRLib2) are set in the PATH environment variable. HNTRLib2 uses the Hitachi common folder (system-drive\Program files\Common Files\HITACHI) as its path. In addition, the port numbers listed in C. List of Port Numbers are added to the services file.

To Page Top

(4) Uninstallation

• Uninstalling JP1/Base deletes the definition files shared with other JP1 products, thereby disabling these programs.

• If you uninstall only JP1/AJS after JP1/AJS and JP1/Base are installed, the event service might not start up. In this case, you should remove the include ajs-conf parameter lines or change them to comments (add # to the beginning of the lines) in the event server settings file (conf).

• The following installer log file is created. Delete this log file after the installation ends normally.

  Windows-installation-folder\Temp\HITACHI_JP1_INST_LOG\jp1base_inst{1|2|3|4|5}.log

• When you uninstall JP1/Base, the path of the JP1/Base bin folder is removed from the PATH environment variable and the port numbers that were added to the services file are removed. The service jp1imcmda is not deleted from systems where JP1/IM - View is also installed. Manually delete any remaining settings for which you have no further need. However, take care not to delete the service jp1imcmda if JP1/IM - View is installed on the system. Take particular care not to delete the path for the Hitachi common folder, which is used by a number of products other than the Hitachi Network Objectplaza Trace Library (HNTRLib2).

To Page Top

(5) Overwrite installation

Note the following points if you are installing JP1/Base in an environment running an earlier version of a JP1 program:

• If you wish to install JP1/Base on a host that runs either JP1/IM or JP1/IM - Agent (pre-Version 6 programs), you must set the following services to manual mode before you install JP1/Base:

  • JP1/IM Agent

  • JP1/IM Control Service

  • JP1/IM Event

  • JP1/IM Rmiregistry

• Installing JP1/Base disables the event service supported by the pre-Version 6 programs JP1/IM -Agent and JP1/IM. To launch the Version 5 event service, execute the following command:

  jevmkcompat -u

  After executing the above command, execute the following command to restart the JP1/Base event service. Some programs cannot send events to the JP1/Base event service unless this command is executed:

  jevmkcompat -i

  After installing or uninstalling JP1/IM - Agent or JP1/IM Version 5 on a host running JP1/Base, you must also execute the following command:

  jevmkcompat -i

• To start the JP1/Base event service and use the pre-Version 6 JP1/SES functionality after installing JP1/Base, execute the following command:

  jevmkcompat -r

  To start the JP1/SES event service and return to the JP1/SES environment, execute the following command:

  jevmkcompat -u

• You cannot install JP1/Base Version 7 or later on a host running Version 6 of JP1/IM - Central Console or JP1/AJS.

• If you install JP1/Base Version 7 or later by overwriting an earlier version of JP1/Base, HNTRLib2 will be installed without removing HNTRLib. If HNTRLib is no longer needed, uninstall it after making sure that it is not being accessed by any programs.

• The storage format of the command execution log (ISAM) files has changed in Version 8. If you are using JP1/IM and you upgraded to JP1/Base Version 8 or later by overwriting JP1/Base 07-51 or earlier, make sure that you execute the jcocmdconv command before you recommence JP1/IM operation.

  The jcocmdconv command migrates the command execution log (ISAM) files accumulated in a previous version of JP1/Base to the file format used in Version 8 or later. If you do not execute this command, you will not be able to access the command execution logs accumulated in Version 7 or earlier. During cluster operation, while the shared disk can be accessed, execute the jcocmdconv command once only (specifying the logical host) on either the primary or secondary node.

  For details on the jcocmdconv command, see jcocmdconv in 15. Commands.

  A command execution log is created only in JP1/Base on the manager host (on which JP1/IM is also installed).

• In Version 9, the save-rep flag has been added to the options parameter in the event server settings file (conf). Setting this flag saves the duplication prevention table of the event database into the file. If this flag is not set, the duplication prevention table is saved to memory. In this case, if the event server is restarted, the table is deleted, and then re-created, causing the database to take longer to receive JP1 events forwarded from other hosts. We recommend that you set the save-rep flag for the event server that receives JP1 events forwarded from other hosts.

  If you perform an overwrite installation from JP1/Base 08-00 or earlier, this flag will not be set. In this case, you must perform the following procedure to create the duplication prevention table in the file.

  To create this table in the file:

  1. Add the save-rep flag to the options parameter in the event server settings file.

     For details on the event server settings file, see Event server settings file in 16. Definition Files.

  2. Execute the jevdbmkrep command.

     For details on the jevdbmkrep command, see jevdbmkrep in 15. Commands.

  3. Start the event server.

• The log-file trap startup definition file (jevlog_start.conf) is new in version 10-00. If you link with version 10-00 or later of JP1/IM, you can use the IM configuration management feature with this file to control the starting and stopping of log file traps.

  If you intend to use IM configuration management to control the starting and stopping of log file traps, and have defined the startup of a log file trap in the start sequence definition file (JP1SVPRM.DAT), use the following procedure to migrate the definition to the log-file trap startup definition file:

  • From the start sequence definition file, delete the startup definition for the log file trap.

  • In the log-file trap startup definition file, enter the settings for the log file trap that you want to stop and start.

  For details on the log-file trap startup definition file, see Log-file trap startup definition file in 16. Definition Files.

  Note the following when migrating these definitions:

  • You must specify the name of the log-file trap startup definition file in the -f option of the jevlogstart command.

  • Do not specify a monitoring target name or log-file trap action definition file name that is already being used by another log file trap. If the name is already in use, choose another.

To Page Top

(6) Overwrite installation for cluster use

After you perform an overwrite installation of JP1/Base version 07-51 or later on a cluster system on which JP1/Base version 07-00 or earlier was used, you must perform the following procedures (a) to (c) in order, to upgrade the environment settings for the logical host.

After you perform an overwrite installation of JP1/Base 10-50 or later on a cluster system on which JP1/Base 10-10 or earlier was used, you must perform the procedure in (d) to upgrade the environment settings for the logical host.

To Page Top