ASAP 2.8 Client Manual

Introduction to ASAP
HP NonStop ASAP Client Manual—425263-004
1-7
OEM Architectural Overview
you click a cell that intersects the Disk row, the Down column automatically locates all
Down Disk state changes that have occurred. For more information, see OSC Window
on page 4-23.
Notifications - Overview
You can use the Notify control panel to configure automatic alerts and report
notifications. ASAP alerts and report notifications can be sent via phone, pager, e-mail,
or Internet browser. Notifications can be sent when objects change state, or can be
scheduled to occur at various times of the day, or they can occur at the end of each
analysis sample for inclusion in web site content. Notification reports can include high-
level object state summaries, object state change alerts, or lists of critical sorted object
state information. Reports can be formatted either in color-coded HTML format or in
short text format for use with short text message devices such as wireless phones or
pagers. For more information, see Notify Control Panel on page 5-24.
Icon Server
You can customize icons and colors that appear in your ASAP environment and in the
OEM and OIL views to allow for internationalization. Use the Icons button on the
General tab of the ASAP Properties window. For more information on the Icon Server,
see Icon Server Control Panel on page 5-14.
EDL ADE
The ASAP Client includes an Entity Definition Language application development
environment (EDL ADE). The EDL lets you define system entities, customer
application domains, and third-party entities, and dynamically add them to the ASAP
client environment. For more information, see Section 6, Entity Definition Language
(EDL).
OEM Architectural Overview
The Open Enterprise Management (OEM) Gateway provides customer applications
with an optional encapsulated interface layer to enterprise management frameworks.
The ASAP subsystem communicates node, entity, and object information to the OEM
Gateway. It reports object state information, so objects and their operational states are
displayed in Enterprise Management Frameworks supported by OEM Gateway
adapters.
The OEM consists of a Server component and one or more Adapter components.
Statistics agents such as the ASAP Client communicate with the OEM Server
component. The Server communicates with an OEM Adapter or Adapters on behalf of
the client’s agents, while the Adapters handle communication to and from enterprise
management frameworks.
The OEM layer handles all details of the interface to enterprise management
frameworks. As a result, ASAP can communicate statistics information in a uniform