seed
and level7
for each build are under the bld
tree.relscfg.msirc
and
host_version_*.*
, where version is in the format
.$top/bld/bld#.##.####
, where
bld#.##.#### is the top directory of the specific LeasePak build.
.lplogin
,
.lpprofile
, logdb.*
, envdb.msirc
, etc.com
files for each porfolio's group of modules set to run in End of Period (for the specific
environment).leasepak.lock
, lpu0212.his
, batch input files, and C-ISAM files.$top/live/conv/dbms
, where
dbms is either ora
for Oracle or syb
for Sybase.$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.$top/live/sql/dbms
, where
dbms is either ora
for Oracle or syb
for Sybase.$top/live/bin
.$top/live/dsets
.$top/live/lib
.live
, point directly to a build,
or point to a build through a visitor environment.
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.
(as different from the env Tree)
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
directory in the
host_env (host environment).data
directory in the
host_env (host environment).err
directory in the
host_env (host environment).conv
directory in the
host_env (host environment).exe
directory.sql
directory in the
host_env (host environment).
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.
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.
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.
ora
) or Sybase (syb
) or both.
Within these are the DBMS-specific database references. NetSol 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.
Whether through a direct symbolic link or through another point such as live
, each environment will point to only
one DBMS, either exe/ora
or exe/syb
.
seed
and level7
datasets.
db_snapshot
never overwrites these and db_restore
expects to find them
in this directory.
LeasePak Documentation Suite
©
by NetSol Technologies Inc. All rights reserved.
The information contained in this document is the property of NetSol Technologies Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. NetSol Technologies 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 NetSol Technologies Inc. is prohibited.
This message should disappear within 5-15 seconds, depending on the size of the document and the speed of your connection to the Documentation Suite.
If you can still see this message after 20 seconds, try clicking the Refresh or Reload button on your Web browser.
If your document still does not load, refer to Document Load Troubleshooting for instructions on how to fix possible problems with either your Documentation Suite installation or Web browser setup.
If you do not have read access to the parent docsuite directory, you will not be able to load the Document Load Troubleshooting document. In this case, contact your network administrator for assistance.