Job Management Partner 1/Base User's Guide

2.3.4 Notes on installing and uninstalling JP1/Base

Note the following points when installing and uninstalling JP1/Base:

Organization of this subsection

(1) Installation

(2) Re-installation

(3) Uninstallation

(4) Setting the OS environment

(5) Overwrite installation

(1) Installation

• If you see a message stating that installation failed while using the Hitachi Program Product Installer, check the /etc/.hitachi/.hitachi.log file. We recommend that you back up this file as required because this file is overwritten every time you start the Hitachi Program Product Installer.
  The installation log is output to the /var/opt/jp1base/log/JBS_SETUP directory. Check the installation log.
  
• If you are installing JP1/Base in a Solaris non-global zone, use a version that supports the non-global zone (09-00 or later) for all JP1/Base instances on the same device.

(2) Re-installation

• If you are reinstalling JP1/Base over the existing JP1/Base program, be sure to quit JP1/Base and all JP1 programs, and quit all programs currently accessing the JP1/Base event service.
  If you are using JP1/AJS - Manager, stop the JP1/AJS - Monitor service.
  
• When you overwrite an existing JP1/Base program with a newer version, the Hitachi Network Objectplaza Trace Library (HNTRLib2) is disabled. You cannot collect information with the integrated trace log even when you run JP1/Base. When JP1/Base is overwritten, you should use the ps command to check that the Hitachi Network Objectplaza Trace Library (HNTRLib2) is activated (it is activated if the hntr2mon process is running). If not, use the hntr2mon command to run it. For details on the hntr2mon command, see hntr2mon (UNIX only) in 13. Commands.
• 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
    Reinstall JP1/Base and then re-set up JP1/Base and JP1/IM - Manager.
    
  • JP1/AJS
    Reinstall JP1/Base and then re-set up JP1/Base and JP1/AJS.
    
  • JP1/AJS2 for Mainframe
    Uninstall both JP1/Base and JP1/AJS2 for Mainframe and then reinstall JP1/Base and JP1/AJS2 for Mainframe. Next, re-set up JP1/Base and JP1/AJS2 for Mainframe.
    
  • JP1/Power Monitor
    Reinstall JP1/Base and then re-set up JP1/Base and JP1/Power Monitor. However, you do not need to set up JP1/Power Monitor again, if you have not set up a logical host or linkage with JP1/AJS.
    
• If you are using the SNMP trap converter, execute the imevtgw_setup command after reinstalling JP1/Base.

(3) Uninstallation

After uninstalling JP1/Base, check whether the following directories still exist and delete them if so:

• /etc/opt/jp1base
• /opt/jp1base
• /var/opt/jp1base

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

/tmp/HITACHI_JP1_INST_LOG/jp1base_inst{1|2|3|4|5}.log

(4) Setting the OS environment

At JP1/Base installation, the port numbers listed in C. List of Port Numbers are set in the /etc/services file. This setting information is deleted when JP1/Base is uninstalled. However, the service name jesrd is not deleted. You must delete these settings manually when they are no longer needed.

(5) Overwrite installation

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

• Installing JP1/Base disables the Version 5 event service. To launch the Version 5 event service, execute the following command:
  

  jevmkcompat -r

  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

• To install or uninstall the JP1/IM Version 5 on a host running JP1/Base, execute the following command after installing or uninstalling JP1/IM:
  

  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 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.
  

  1. Modify the settings to enable startup of the processes added with version 07-00 or a later version.

  Modify the settings file as follows:

  When starting the authentication server on the logical host:

  cp -p /etc/opt/jp1base/conf/jp1bs_spmd.conf.session.model shared-directory/jp1base/conf/jp1bs_spmd.conf

  cp -p /etc/opt/jp1base/conf/jp1bs_service_0700.conf.model shared-directory/jp1base/conf/jp1bs_service_0700.conf

  When not starting the authentication server on the logical host:

  cp -p /etc/opt/jp1base/conf/jp1bs_spmd.conf.model shared-directory/jp1base/conf/jp1bs_spmd.conf

  cp -p /etc/opt/jp1base/conf/jp1bs_service_0700.conf.model shared-directory/jp1base/conf/jp1bs_service_0700.conf

  2. Copy the definition files added in Version 7 or later.

  Copy the definition files as follows:

  2-1 Create a directory named plugin in shared-directory/jp1base/conf/.

  2-2 Copy /etc/opt/jp1base/conf/plugin/reqforward.conf to shared-directory/jp1base/conf/plugin.

  2-3 Copy /etc/opt/jp1base/conf/user_acl/JP1_AccessLevel to shared-directory/jp1base/conf/user_acl/.

  2-4 Create a directory named jbshc in shared-directory/jp1base/conf/.

  2-5 Copy the files in /etc/opt/jp1base/conf/jbshc/ to shared-directory/jp1base/conf/jbshc/.

  2-6 Copy the files in /etc/opt/jp1base/conf/jbslcact/ to shared-directory/jp1base/conf/jbslcact/.

  2-7 Copy the files in /etc/opt/jp1base/conf/jbsdfts/ to shared-directory/jp1base/conf/jbsdfts/.

  3. Add the common definition information added with Version 7 or later.

  Modify the settings file as follows:

  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 7, copy jcocmd0710.conf.model and jbshc_com.conf.model.

  /etc/opt/jp1base/default/base_plugin.conf.model

  /etc/opt/jp1base/default/jcocmd0700.conf.model

  /etc/opt/jp1base/default/jcocmd0710.conf.model

  /etc/opt/jp1base/default/jbsspm070.conf.model

  /etc/opt/jp1base/conf/jp1bs_param_V7.conf.model

  /etc/opt/jp1base/default/jbshc_com.conf.model

  /etc/opt/jp1base/default/jbscom_default.conf.model

  /etc/opt/jp1base/default/jbslcact_default.conf.model

  /etc/opt/jp1base/default/jbssrvmgr.conf.model

  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.

  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

  This completes the upgrading of the logical host.
  
• 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 and 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 14. Definition Files.
   
2. Execute the jevdbmkrep command.
   For details on the jevdbmkrep command, see jevdbmkrep in 13. Commands.
   
3. Start the event server.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.