Job Management Partner 1/Base User's Guide
Note the following points when installing and uninstalling JP1/Base:
- Organization of this subsection
- (1) Installation
- (2) Re-installation
- (3) Uninstallation
- (4) Setting the Windows environment
- (5) Overwrite installation
(1) Installation
- Do not install JP1/Base in a folder in which another program product is installed.
- 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.
- After JP1/Base is installed, if you wish to install HNTRLib2 (provided by another program product) in a folder other than the default installation folder, you must first uninstall JP1/Base, delete the installation folder, and then reinstall JP1/Base.
(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 JP1/Base and then reinstall JP1/Base and JP1/IM - Manager. You do not need to uninstall 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.
(3) 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
(4) Setting the Windows environment
At JP1/Base installation, the path of the JP1/Base bin folder and the path of Hitachi Network Objectplaza Trace Library (HNTRLib2) are set as system environment variables (Path). The path of HNTRLib2 is the Hitachi common folder (system-drive\Program files\Common Files\HITACHI ). In addition, the port numbers listed in C. List of Port Numbers are set in the services file. The path of the JP1/Base bin folder set in the system environment variable (Path variable) and the port number set in the services file are deleted when you uninstall JP1/Base. The service name jp1imcmda is not deleted if JP1/IM - View is installed. Manually delete any settings that remain in the system if no longer needed. However, take care not to delete the service name jp1imcmda if JP1/IM-View is installed. Note also that the path of the Hitachi common folder is used for products other than Hitachi Network Objectplaza Trace Library (HNTRLib2).
(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:
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 -u
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
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:
To start the JP1/SES event service and return to the JP1/SES environment, execute the following command:
jevmkcompat -r
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.
- If JP1/Base version 07-00 or earlier is being used in a cluster system and you perform an overwrite installation of 07-51 or later, you must complete the following tasks to upgrade the logical host environment.
Modify the settings file as follows:
- 1. Modify the settings to enable startup of the processes added with version 07-00 or a later version.
- 1-1 Back up the following files:
- shared-folder\jp1base\conf\jp1bs_spmd.conf
- shared-folder\jp1base\conf\jp1bs_spmd.conf.session
- shared-folder\jp1base\conf\jp1bs_spmd.conf.original
- shared-folder\jp1base\conf\jp1bs_service_0700.conf
- 1-2 Modify the following files so that the processes added in Version 7 or a later version will start.
- shared-folder\jp1base\conf\jp1bs_spmd.conf
- shared-folder\jp1base\conf\jp1bs_spmd.conf.session
- shared-folder\jp1base\conf\jp1bs_spmd.conf.original
- Open these files in a text editor or other program, and add the following lines to the end of each file.
- If you are using JP1/Base version 07-00, add only jbshcd and jbshchostd.
- jbsplugin|C:\Program Files\HITACHI\JP1Base\bin\jbsplugind.exe|||60|
- jbshcd|C:\Program Files\HITACHI\JP1Base\bin\jbshcd.exe|||60|
- jbshchostd|C:\Program Files\HITACHI\JP1Base\bin\jbshchostd.exe|||60|
- The part in italics is the installation folder. The lines to be added are written in the file \conf\jp1bs_spmd.conf.original in the installation folder. Copy the required lines from this file to the files you are modifying.
- 1-3 Modify the following file so that the processes added in version 07-51 or later will start.
- If this file does not exist, it will be created automatically when the JP1/Base service starts. You do not need to create it manually.
- shared-folder\jp1base\conf\jp1bs_service_0700.conf
- Open this file in a text editor or other program, and add the following lines to the end of the file:
- jbshcd|C:\Program Files\HITACHI\JP1Base\bin\jbshcd.exe||0|3|3|21600|
- jbshchostd|C:\Program Files\HITACHI\JP1Base\bin\jbshchostd.exe||0|3|3|21600|
- The part in italics is the installation folder. The line to be added is written in the file \conf\jp1bs_service_0700.conf in the installation folder. Copy the required lines from this file to the files you are modifying.
Copy the definition files as follows:
- 2. Copy the definition files added in Version 7 or later.
- 2-1 Create a folder named plugin in shared-folder\jp1base\conf\.
- 2-2 Copy the installation-folder\conf\plugin\reqforward.conf file to shared-folder\jp1base\conf\plugin.
- 2-3 Copy the installation-folder\conf\user_acl\JP1_AccessLevel file to shared-folder\jp1base\conf\user_acl\.
- 2-4 Create a folder named jbshc in shared-folder\jp1base\conf\.
- 2-5 Copy the files in installation-folder\conf\jbshc\ to shared-folder\jp1base\conf\jbshc\.
- 2-6 Create a folder named jbslcact in shared-folder\jp1base\conf\.
- 2-7 Copy the files in installation-folder\conf\jbslcact\ to shared-folder\jp1base\conf\jbslcact\.
- 2-8 Create a folder named jbsdfts in shared-folder\jp1base\conf\.
- 2-9 Copy the files in installation-folder\conf\jbsdfts\ to shared-folder\jp1base\conf\jbsdfts\.
Modify the settings file as follows:
- 3. Add the common definition information added in Version 7 or later.
- 3-1 Back up the common definition information.
- Execute the following command:
- jbsgetcnf -h logical-host-name > backup-file-name
- 3-2 Prepare common definition information to be added to the logical host.
- Copy the following files to the temporary directory.
- If you are using JP1/Base version 07-00, copy jcocmd0710.conf and jbshc_com.conf.
- installation-folder\default\base_plugin.conf
- installation-folder\default\jcocmd0700.conf
- installation-folder\default\jcocmd0710.conf
- installation-folder\default\jbsspm070.conf
- installation-folder\conf\jp1bs_param_V7.conf
- installation-folder\default\jbshc_com.conf
- installation-folder\conf\jbscom_default.conf
- installation-folder\conf\jbslcact_default.conf
- installation-folder\conf\jbssrvmgr.conf
- 3-3 Create common definition information for the logical host by modifying the copied files using a text editor or other program.
- Replace all the occurrences of JP1_DEFAULT in the files with logical-host-name. Re-name each file as file-name.conf.
This completes the upgrading of the logical host.
- 3-4 Set up the modified files as common definition information for the logical host.
- Execute the following command for each file to add common definition information:
- jbssetcnf file-name
- 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 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. 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 13. 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:
- 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 14. Definition Files.
- Execute the jevdbmkrep command.
For details on the jevdbmkrep command, see jevdbmkrep in 13. Commands.
- Start the event server.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.