
Base System Configuration
# P0602477 Ver: 3.1.11 Page 87
The MPSHOME Directory
The MPS system installation process creates a home directory and several
subdirectories beneath it. On Solaris systems, this is represented as $MPSHOME
(/opt/vps by default). On Windows systems, this is indicated as %MPSHOME%.
See the Avaya Packages Install Guides and the Avaya Media Processing Server Series
System Operator’s Guide for more information about the home and subdirectories.
The relevant subdirectories (from a configuration standpoint) are identified in the
following table, and described in greater detail later in this chapter.
On Solaris systems, if the defaults are not used, only the symbolic links to the Avaya
packages exist in /opt/vps.
On Windows systems, if the defaults are not used, the specified target directory
contains a Avaya subdirectory with the common and mpsN component directories,
the distribution directory, and the bin executables directory.
MPSHOME
Directory Description
common
Contains files common to all MPS components associated with
a particular node. (See The MPSHOME/common Directory on page
88 for more information.)
packages
Contains the actual released software and sample configuration
files. This directory is referenced by means of symbolic links in
/opt/vps in the format PERIxxx (where xxx represents a
package acronym). (See The $MPSHOME/packages Directory
on page 125 for more information.)
PERIxxx
Individual packages of actual released software and
configuration files. These packages are located directly under
%MPSHOME%. Use the Table of Contents to locate each package
by name.
tmscommN
Contains files used for bridging between and within MPS
components. (See The MPSHOME/tmscommN Directory on page
138 for more information.)
mpsN
Contains files unique to each MPS, where N denotes the
particular MPS number. One mpsN directory exists for each
defined on the node with which it is associated. (See The
MPSHOME/mpsN Directory on page 139 for more information.)
Comentarios a estos manuales