Common Terms, Concepts, and Graphical Symbols
in alphabetical order
- Build
- The specific production sequence number of the LeasePak software. Build numbers are usually in the format
n.nn.bbbb, where n.nn corresponds to the LeasePak version number and bbbb corresponds to the build number
within that version.
- Client
- For system administration purposes, "client" refers to the client computer
that interacts with the server. Within LeasePak itself, "Client" refers to one of the many client relationships
(Lessee, Vendor, Guarantor, etc.) defined for use with leases, assets, and other components.
- Concurrent
- Simultaneous--occurring at the same time. For example, "concurrent
users" refers to users
simultaneously accessing a specific program (such as LeasePak).
- Concurrent database connections
- The approximate number of connections to the database server, whether from
LeasePak clients or from LeasePak (
lpadriver.exe
) processes on the server, that may exist at any one time.
Calculate as M * (G + 2)
, where M
is the maximum concurrent users and G
is the average number of concurrent Genform windows accessed per user.
- Concurrent LeasePak (
lpadriver.exe
) processes
- The approximate number of
LeasePak (
lpadriver.exe
) processes you anticipate will run on the server at any one time. Calculate as
M * G
, where M
is the maximum concurrent users and G
is the average number of concurrent Genform windows accessed per user.
- DBMS
- Database management system. This is the software which LeasePak uses to store, manipulate, and access its data. A DBMS usually
has both a server and client component.
- Genform windows
- A subset of the updates and reports within the LeasePak client software. Each Genform window
used starts an additional LeasePak (
lpadriver.exe
) process on the server and makes an additional
connection to the database server. Refer to the document Genform
for more information.
Instance (Oracle only)
- The set of operating system processes and shared memory segments that operate on an Oracle database. A new instance is created
each time Oracle is started, then disappears when Oracle is shut down. In most cases, the Oracle database and instance names are
the same.
- LeasePak database
- The structure of tables, indexes, views, and fields containing LeasePak data. Within Oracle, the LeasePak database is
implemented as a schema of the Oracle database; within Sybase, it is implemented as a database of the Sybase DBMS.
- Maximum concurrent users
- The highest number of LeasePak users you anticipate will access the software
at any one time.
- Release
- A specific offering of the LeasePak software to users. Typical releases include the Beta Release, the General Availability
(GA) release, and the Maintenance Release (MR).
- Server
- The server computer, usually containing most of the application software, and, in the case of LeasePak,
the database server software and LeasePak data.
- Terminal
- Either an operator's console attached directly to the server, or another computer
emulating a console and interacting directly with the server.
- Version
- The main number/letter designation of an edition of the LeasePak software. MSI usually formats version numbers one of the
following ways: , , ,
or .
The documentation never uses symbols in place of descriptive text--symbols are for visual
reinforcement only.
HP: information specific to the HP platform.
Linux: information specific to the Linux
platform.
Sun: information specific to the Sun platform.
Oracle: information specific to Oracle.
Sybase: information specific to Sybase.
Emphasizes a critically important note or warning.
Highlights a common feature or relationship found
throughout the specified software.
Directs the user or administrator to stop the current
process and complete the instructions in another section or document before resuming.
LeasePak System Administration Guide
©
by McCue Systems Incorporated. All rights reserved.
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.