ASAP OpenView Smart Plug-In Manual

Configuring the ASAP OpenView Adapter
HP NonStop ASAP OpenView Smart Plug-In Manual—529444-001
4-13
Deleting Services and Nodes From OpenView
4 Configuring the ASAP OpenView Adapter
against the service Chicago because no additional levels of services are present in the
tree. The message is still generated for the object Chicago\CPU\00 as before:
Deleting Services and Nodes From OpenView
The ASAP OpenView Adapter does not automatically remove any of the services or
nodes that it previously added to OpenView. Once a service or node is added to the
OpenView environment, messages can be logged against it, and that service or node
becomes part of the OpenView configuration. Even if ASAP is no longer monitoring a
given NonStop Kernel object, you can still view the history of messages logged against
that object within OpenView.
If at some point your ASAP configuration changes and you want to delete one or more
services or nodes from OpenView, you can use the OpenView Console. For example,
suppose you alter the Service Population Scheme in a way that reduces the number of
levels of service detail added (that is, you choose to now populate one level of detail,
but previously you populated two levels). Removing a given service or node from the
OpenView configuration also removes any messages associated with that object.
Messaging Options
The ASAP OpenView Adapter logs a message whenever an ASAP-monitored object
changes state. These messages appear in the OpenView Message Browser window.
The details of each message include the name of the object, the service it is part of,
the node it resides on, a severity level, and text describing the specific error or
condition that caused the message.
VST028.vsd