E Using Asap; Architectural Overview - HP NonStop RDF J-series RVUs Management Manual

E Using ASAP

ASAP (Availability Statistics and Performance) allows many subsystem entities to be monitored
across a network of NonStop servers. The status and statistics for the entities are collected on a
single system, and are then monitored either through the ASAP command interface or through
the ASAP graphical user interface (GUI) PC client.
RDF/IMP and IMPX are instrumented to feed state information to ASAP, thus allowing RDF
subsystems to be monitored, in an integrated way, alongside all other subsystems supported by
ASAP. These RDF entities report state and statistical information to ASAP:
• Monitor
• Extractor
• RDFNET (optional)
• Receiver
• Purger
• Updater

Architectural Overview

RDF/IMP and IMPX are supplied with an object file called ASAPRDF which is the ASAP/RDF
Smart Gatherer Process (SGP). SGP is the interface between ASAP and the RDF environments.
For every system in which ASAP is configured to collect RDF data, the ASAP monitor starts an
RDF SGP process.
To monitor an RDF environment using ASAP, you must configure an RDF SGP on both the
primary and backup RDF systems. The SGP on the primary system reports data for the monitor
and extractor processes. The SGP on the backup system reports data for the image trails and
receiver, purger, and updater processes.
At regular intervals, the SGP process reports the status of each RDF entity residing on that system
to the ASAP collector (not shown). The ASAP collector writes the RDF status information into
the ASAP database, from which ASAP can be used to display and monitor the status of the RDF
environment. See the ASAP Server Manual and the ASAP Client Manual for details about how to
monitor ASAP entities.
Figure E-1 shows a single RDF environment replicating from \PRI to \BAK.
Architectural Overview 465