ASAP 3.0 Client Manual

HP NonStop ASAP Client Manual Page 128 of 161
customize your ASAP environment, your customized settings are stored in file names
such as:
ASAP1 Custom.EDL
ASAP2 Custom.EDL
If you are communicating with the V1 ASAP server, the custom EDL file is named
ASAP1 Custom.EDL. If you are connected to an ASAP V2 server, the EDL is named
ASAP2 Custom.EDL.
You can modify (and share) ASAP Custom EDL files. In fact, custom EDL files are
automatically modified every time you change any of your property settings on the
Entity or Attribute Property sheet Tabs in the ASAP Properties window.
You can copy EDL files among different workstations. Thus the EDL file provides a
portable container for ASAP Client properties and data representing the client
environment. Once a given ASAP Client is configured as desired, users and
developers can share the EDL with other users or workstations. To share, copy or mail
the EDL file to another user or workstation, and place it in the EDL directory in the
same path as the ASAP executable.
EDL IDE Window
The EDL Interactive Development Environment (IDE) lets you interactively browse,
open, design, develop, compile, modify, and save entity definition files for your ASAP
environment.
The IDE window is your primary interface for developing entity definitions. It includes a
text area for you to work with EDL source. It also has a built-in EDL file browser that
lets you quickly open, edit, compile, and save EDL source. The top of the IDE window
includes toolbar buttons for the most common IDE functions. Pull-down menus provide
more advanced functions.
When you successfully compile an entity definition in the EDL environment, that
definition is automatically added immediately to your ASAP Client environment. If your
host session is enabled and that same entity was already defined to ASAP Server,
data for that entity also appears in your ASAP Client windows. The entity also appears
on the Entity Tab of the ASAP Property sheet. All information about the compiled entity
is also retained in the ASAP Custom.EDL file so the entity is still there next time you
run the ASAP Client.
The ASAP Client, Server, and Extension require EDL files. EDL files let ASAP
components know about properties of system and application entities as they relate to
the ASAP environment.
Entities are defined to ASAP in EDL source files so that Client, Server, and Extension
components can share entity definitions. ASAP server components and EDL files are