ASAP 1.1 Hybrid Manual

HP NonStop ASAP Hybrid Manual – 529729-004
Page 3-20
Cleaning Up Domains Interactively
In general, applications that utilize the ASAP Hybrid API operate as follows:
 Register one or more domains
 Update domain data items, operational state, and so on
 Remove domains at shutdown or if the domains no longer need to be
monitored
When the application finally removes a domain, the ASAP Hybrid for Linux server
notifies NonStop ASAP. NonStop ASAP then cleans up domain information and
sends an acknowledgement back to the ASAP Hybrid for Linux server, which in
turn cleans up its information on the domain. This approach ensures that the
Linux side stays in sync with the rest of ASAP.
In order for this removal and acknowledgement scheme to function as intended,
several conditions must be met:
 The application must remove the domain before exiting. If an application
does not remove a domain prior to exiting (or failing), the ASAP Hybrid for
Linux server detects that the application has stopped and marks the domain
as down. ASAP on the host is notified of this and reports the down domain
via its standard reporting and alerting mechanisms. Thus operators are
immediately notified if a Linux client application fails. The domain continues
to be marked as down until the client application restarts and reregisters the
domain.
 A communication link must exist between the Linux machine and the
NonStop host. If the link does not exist, the ASAP Hybrid for Linux server
cannot notify NonStop ASAP that a domain has been removed. In this case,
the server keeps the removal pending until it successfully notifies NonStop
ASAP that the domain has been removed.
 ASAP must be running on the NonStop host. If it is not running, the ASAP
Hybrid for Linux server cannot notify NonStop ASAP that a domain has been
removed, and it keeps the removal pending until such notification can take
place.