Server Directory Trees

$top Tree
env Tree
visitor env Tree
bld Tree

$top Tree

Directory Descriptions

$top: Variable that the administrator defines at the time of installation representing the location under which the various setup scripts install all the components of the particular instance (installation) of LeasePak.
bld: Top of the "build-tree" directories. See the section bld Tree for more information.
datasets: Contains user datasets only--the default datasets seed and level7 for each build are under the bld tree.
log: Contains log files, including those for individual LeasePak environments, the leasepakd and mPowerd daemons, and EOP Suite.
vertex: Contains Vertex data files (if applicable).
etc: Contains site-specific files such as relscfg.msirc and host_version_*.*, where version is in the format .
live: A symbolic link to $top/bld/bld#.##.####, where bld#.##.#### is the top directory of the specific LeasePak build.
env: Top of the "environment-tree" directories, containing all environments set up for the particular instance (installation) of LeasePak. See the section env Tree for more information.
boot: Contains files required by the setup program.

env Tree

Directory Descriptions

$top: Variable that the administrator defines at the time of installation representing the location under which the various setup scripts install all the components of the particular instance (installation) of LeasePak.
env: Top of the "environment-tree" directories, containing all environments set up for the particular instance (installation) of LeasePak.
(envs): User-defined environments. Each environment has its own "environment-tree" directory structure.
etc: Contains environment-specific configuration files, including .lplogin, .lpprofile, logdb.*, envdb.msirc, etc.
eop/com: Contains the com files for each porfolio's group of modules set to run in End of Period (for the specific environment).
eop/log: Contains the log files for all modules run for End of Period (for the specific environment).
data: Includes leasepak.lock, lpu0212.his, batch input files, and C-ISAM files.
err: Contains program exception files specific to the environment.
conv: A symbolic link to $top/live/conv/dbms, where dbms is either ora for Oracle or syb for Sybase.
exe: A symbolic link to $top/live/exe/dbms, where dbms is either ora for Oracle or syb for Sybase.; exe may be a symbolic link to a directory as shown, or it may be a directory with files and links to files.
sql: A symbolic link to $top/live/sql/dbms, where dbms is either ora for Oracle or syb for Sybase.
bin: A symbolic link to $top/live/bin.
dsets: A symbolic link to $top/live/dsets.
lib: A symbolic link to $top/live/lib.; An environment can point to a build through live, point directly to a build, or point to a build through a visitor environment.

visitor env Tree

The structure of the visitor env tree is similar to the regular env tree. The visitor shares a database with its host environment. The differences in directory contents are described below.

Directory Descriptions

(as different from the env Tree)

etc: For the logdb.* files, contains symbolic links to the files in the host_env (host environment) directory. Also, does not include the configuration files physdb.msirc and leasepak_syb_use (Sybase only)--files pertaining to the physical database.
eop: A symbolic link to the eop directory in the host_env (host environment).
data: A symbolic link to the data directory in the host_env (host environment).
err: A symbolic link to the err directory in the host_env (host environment).
conv: A symbolic link to the conv directory in the host_env (host environment).
exe: A symbolic link to an atypical exe directory.
sql: A symbolic link to the sql directory in the host_env (host environment).

bld Tree

Directory Descriptions

$top: Variable that the administrator defines at the time of installation representing the location under which the various setup scripts install all the components of the particular instance (installation) of LeasePak.
bld: Top of the "build-tree" directories, containing the installed builds for the particular instance (installation) of LeasePak.
(blds): Specific LeasePak builds, by build sequence number using the format bld#.##.####. Each build has its own "build-tree" directory structure.
exe: Depending on your license, contains subdirectories for either Oracle (ora) or Sybase (syb) or both. Within these are the DBMS-specific executables such as lpadriver.exe, lpaeopdriver.exe, and $uexe/lpautil.exe, as well as lplicense.dat.
If you are only using one DBMS, the LeasePak setup program will remove the uneeded directory during installation.
sql: Depending on your license, contains subdirectories for either Oracle (ora) or Sybase (syb) or both. Within these are the DBMS-specific files for building a LeasePak database.
If you are only using one DBMS, the LeasePak setup program will remove the uneeded directory during installation.
conv: Depending on your license, contains subdirectories for either Oracle (ora) or Sybase (syb) or both. Within these are the DBMS-specific files for converting (upgrading) LeasePak databases, including sgenlpux_conversion.
If you are only using one DBMS, the LeasePak setup program will remove the uneeded directory during installation.
html: Depending on your license, contains subdirectories for either Oracle (ora) or Sybase (syb) or both. Within these are the DBMS-specific database references. MSI also publishes these as part of the Documentation Suite.
If you are only using one DBMS, the LeasePak setup program will remove the uneeded directory during installation.
dsets: Contains the static seed and level7 datasets. db_snapshot never overwrites these and db_restore expects to find them in this directory.
bin: Contains the DBMS-neutral (not specific to Oracle or Sybase) executable files for the specific build.
lib: Contains non-executable reference files, including subroutine libraries and templates for the specific build.

The information contained in this document is the property of McCue Systems, Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. McCue Systems, Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of McCue Systems, Inc. is prohibited.