ASAP 2.8 Client Manual

Entity Definition Language (EDL)
HP NonStop ASAP Client Manual—425263-004
6-4
Factory EDL Files
ASAP environment using the FILE… IMPORT function. The IMPORT function lets
ASAP integrate disjoint, and disparate entity information.
Factory EDL Files
The ASAP Client installs factory EDL files when the client is installed. Factory EDL file
names have the form:
ASAPn Factory.EDL
This special EDL file contains the default startup settings for your ASAP environment.
The ASAP Client compiles the EDL in this file when you first start the client. You should
not modify factory EDL files. To customize your environment, store your custom
settings in a custom EDL file. For more information, see Custom EDL Files.
The factory EDL file name includes the ASAP version number. This version number is
the ASAP release major version that the EDL represents. For example, in release 2.0
of ASAP, two factory EDL files are included in the installation:
•
ASAP1 Factory.EDL
•
ASAP2 Factory.EDL
When the ASAP Client connects to the ASAP server, the client determines the version
of the server. If the server is ASAP V1, the ASAP1 Factory.EDL file is compiled. If the
server is V2.0, V2.1, V2.2 ... the ASAP2 Factory.EDL file is compiled.
Custom EDL Files
The ASAP Client saves your customized entity-attribute settings in EDL files named:
ASAPn Custom.EDL
This special EDL file contains custom entity attribute definition settings for your ASAP
environment. The ASAP Client compiles the EDL statements in a custom EDL file
when you first start the client.
The custom EDL file name includes the ASAP version number. This version number is
the ASAP release major version that the EDL represents. For example, when you
customize your ASAP environment, your customized settings are stored in file names
such as:
EDL Term Description
Entity Defines a class of objects such as a CPU, Disk, Expand, or Application
domain. ENTITY statements are used to define entities to the ASAP
environment.
Attribute Defines a user-defined property of an entity. Use an ATTRIBUTE statement
to define an entity attribute in EDL. Attributes include properties such as
NodeName, CPU Number, CPU Busy, CPU Queue, and Transactions.
Data
statement
Optionally defines a simple table of data to associate with an entity.