A common mount point is used for the cluster filebase and the filebase directories of all node applications in this example:
The volume /vol/vol1
of an NFS4 system (e.g. NetApp Filer) that can be addressed in the network under the name MyFiler
is mounted in the local directory /myVol1
on all nodes.
This requires the following actions to be performed on all nodes:
login root mkdir /myVol1
(only required before the first mount
command)
mount -t nfs4 MyFiler:/vol/vol1 /myVol1
(for Linux)mount MyFiler:/vol/vol1 /myVol
1
(for Solaris)
mount
command must be repeated every time the computer is rebooted. It is recommended that you ask the system administrator to automate the mounting operation.Directories
In this example
two nodes are generated:
UTMHOST1
,UTMHOST2
two node applications of the UTM cluster application use the common mount point
/myVol1
the directory
/myVol1/UTMCAPPL
is used as the cluster filebasethe directories for the node applications (node filebase) are located below the cluster filebase and are designated according to the relevant host name. This directory structure improves clarity and is largely self-explanatory.
| Mount point |
| Cluster filebase |
| Filebase for UTMHOST1 |
| Filebase for UTMHOST2 |
Both node applications must have access permissions on the cluster filebase and on the node-specific directories.
KDCDEF statements
The following UTM generation statements are required to generate the UTM cluster application in this example:
|
Storing the files
Files that are global to the cluster
During the UTM generation run, the cluster configuration file (
UTM-C.CFG
) and a number of central cluster files are created in the directory/myVol1/UTMCAPPL
. The rest of the central cluster files are created when the first node application is started and also stored in the directory/myVol1/UTMCAPPL
./myVol1/
NFS4 mount point
/myVol1/UTMCAPPL/
Cluster filebase
/myVol1/UTMCAPPL/UTM-C.CFG
Cluster configuration file
/myVol1/UTMCAPPL/UTM-C.USER
Cluster user file
/myVol1/UTMCAPPL/UTM-C.CPMD
Cluster page pool control file
/myVol1/UTMCAPPL/UTM-C.CP01
Cluster page pool file
/myVol1/UTMCAPPL/UTM-C.GSSB
Cluster GSSB file
/myVol1/UTMCAPPL/UTM-C.ULS
Cluster ULS file
These files are created by KDCDEF during UTM generation.
/myVol1/UTMCAPPL/UTM-C.JRN1
/myVol1/UTMCAPPL/UTM-C.JRN2
/myVol1/UTMCAPPL/UTM-C.JKAA
Administration journal
created the first time a node application is started./myVol1/UTMCAPPL/UTM-C.LOCK
Cluster lock file
/myVol1/UTMCAPPL/UTM-C.SLCK
File for serializing the start up of individual node applications
These files are created when a node application is started for the first time.
Initial KDCFILE:
You must copy the initial KDCFILE created during this UTM generation run into all filebase directories of the node applications.Files in the filebase directory on the node
UTMHOST1
/myVol1/UTMCAPPL/UTMHOST1/KDCA
KDCFILE for UTMHOST1
Must be copied before the node is started for the first time./myVol1/UTMCAPPL/UTMHOST1/utmwork
Program for the
utmwork
process of UTMHOST1.
You must make this available before the first time the node is started....
Other files in the filebase directory on UTMHOST1
Files in the filebase directory on the node
UTMHOST2
/myVol1/UTMCAPPL/UTMHOST2/KDCA
KDCFILE for UTMHOST2
Must be copied before the node is started for the first time./myVol1/UTMCAPPL/UTMHOST2/utmwork
Program for the
utmwork
process of UTMHOST2.
You must make this available before the first time the node is started....
Other files in the filebase directory on UTMHOST2
Start parameter files
The cluster filebase must be specified in both start parameter files for the node applications:
...
.UTM START CLUSTER-FILEBASE=/myVol1/UTMCAPPL
...
Note that the statement necessary for standalone applications.UTM START FILEBASE=<filebase>
must not be contained in a start parameter file for a UTM cluster application. See also the section "Start parameters for openUTM".