3.3.4 Notes on installing and uninstalling JP1/Base

Organization of this subsection

(1) Installation
(2) Re-installation
(3) Setting the OS environment
(4) Uninstallation
(5) Overwrite installation
(6) Overwrite installation for cluster use

(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.
When you install JP1/Base, the path for the bin directory 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 appears 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 for which JP1/Base is 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 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 15. 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.

To Page Top

(3) Setting the OS environment

At JP1/Base installation, the port numbers listed in C. List of Port Numbers are added to the /etc/services file. This information is removed when JP1/Base is uninstalled.

To Page Top

(4) 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 
```
The port numbers for the jesrd service are not removed from the services file. Delete them if they are no longer needed.

To Page Top

(5) Overwrite installation

Note the following if you are performing an overwrite installation of 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.
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 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 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 in conjunction 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 jbs_start, use the following procedure to migrate the definition to the log-file trap startup definition file.
- Delete the startup definition for the log file trap from jbs_start.
- 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-50 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.

(a) Enabling the processes added in version 07-00 or later to start

Execute the following commands to modify the configuration files:

When the authentication server is started 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 the authentication server is not started 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

(b) Copying the definition files added in version 07-00 or later

To copy the definition files added in version 07-00 or later:

Create the plugin directory in shared-directory/jp1base/conf/.
Copy /etc/opt/jp1base/conf/plugin/reqforward.conf to shared-directory/jp1base/conf/plugin/.
Copy /etc/opt/jp1base/conf/user_acl/JP1_AccessLevel to shared-directory/jp1base/conf/user_acl/.
Create the jbshc directory in shared-directory/jp1base/conf/.
Copy the files in /etc/opt/jp1base/conf/jbshc/ to shared-directory/jp1base/conf/jbshc/.
Copy the files in /etc/opt/jp1base/conf/lcact/ to shared-directory/jp1base/conf/lcact/.
Copy the files in /etc/opt/jp1base/conf/jbsdfts/ to shared-directory/jp1base/conf/jbsdfts/.

(c) Adding common definition information added in version 07-00 or later

To modify the configuration files to add common definition information added in version 07-00 or later:

Back up the common definition information.

Execute the following command:
```
jbsgetcnf -h logical-host-name > backup-file-name
```
Note that the logical host name must be correctly specified with lower or upper case as specified when the logical host was set up.

Prepare the common definition information to be added to the logical host.

Copy the files below to a temporary directory.

For JP1/Base version 07-00, copy jcocmd0710.conf.model and jbshc_com.conf.model only.

/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

Use an editor to modify the files copied in step 2, and create the common definition information for the logical host.

Change every JP1_DEFAULT in the files to logical-host-name. The file names must have the extension .conf.
Set the files modified in step 3 as the common definition information for the logical host.

Execute the following command for each file to add the common definition information:
```
jbssetcnf file-name
```

(d) Copying the definition files added in version 10-50 or later

To copy the definition files:

Create the suppress directory in shared-directory/event/.
Copy /etc/opt/jp1base/conf/event/servers/default/suppress/forward_suppress to shared-directory/event/suppress/.

To Page Top