HP Instant Support Enterprise Edition Client Installation and Upgrade Guide

Installing ISEE on OpenVMS Clients
Understanding the OpenVMS Installation Options
Appendix D
89
Understanding ISEE in Clustered Environments
If you have chosen the Shared or Multi Server models for your clustered environment
the details in this section will help you better understand the file structures and
processes used by ISEE.
When selecting the shared disk for your cluster, consider the disk’s availability and use
in your environment. This disk will be key to the ISEE support of your OpenVMS cluster.
The ISEE$SERVER account is added to all nodes running the ISEE processes. However,
if you use an account management utility, this account must be configured to remain
valid for ISEE to function properly. The ISEE installation adds the logical
ISEE$HPSERVICES to the LNM$SYSCLUSTER table. This logical is used by the
utilities to identify the location of the ISEE package in the cluster. Do not change or
deassign this logical. If you want to remove ISEE after it is installed reference
“Removing HP ISEE Software” on page 111.
The Shared Server Model only requires one ISEE active client process to run in your
cluster. The Multi-server Model requires the ISEE client processes run on each
monitored OpenVMS client. For more information about each of these models, please
read the following sections. Choose the model that works best for your business needs.
A weekly cleanup process removes closed incidents and temporary files from the ISEE
directory structure.
The ISEE Client Installation creates a common directory structure for files shared
between nodes (see Example E-1) on a single hard disk. After the installation completes,
the configuration utility creates a directory based on the selected installation model,
either Shared Server or Multi-server (see Example E-2 and Example E-3).
Example D-1 Example of the OpenVMS Common Installation Directory Structure
DISK$USER1:[HPSERVICES]
[._COMMON_]
Example D-2 Example of the Shared Server Configuration Directory Structure
DISK$USER1:[HPSERVICES]
[._COMMON_]
[._SHARED_]
Example D-3 Example of the Multi-server Configuration Directory Structure
DISK$USER1:[HPSERVICES]
[._COMMON_]
[.NODENAME1]
[.NODENAME2]
[.NODENAME3]
As demonstrated by preceding examples, the Shared Server model requires less disk
space on the shared disk for configuration data. The disk space requirements for the
Multi-server model will require iterative increases of disk space based on the number of
supported nodes. For more information about the system requirements for each
supported model, see “Meeting ISEE Support Prerequisites for OpenVMS” on page 90.