HP (Hewlett-Packard) HP OpenView Vantagepoint – Operation Manual for UNIX User Manual
Chapter 5
225
Integrating with VantagePoint Navigator
The C++ APIs
The Registration Interface for Service Status Changes
A client sends a registration request to the interface in the service engine
which describes which events the client wishes to receive. The request is
in XML format. The registration manager parses the XML registration
structure and passes it to the core engine. The XML structure for the
registration interface is defined in the operations.dtd (which also
includes the service.dtd).
which describes which events the client wishes to receive. The request is
in XML format. The registration manager parses the XML registration
structure and passes it to the core engine. The XML structure for the
registration interface is defined in the operations.dtd (which also
includes the service.dtd).
The service name identifies the client registrations in the service engine.
The registration manager maintains the registration information for
each client during runtime but it is the client’s responsibility to react to
shutdowns of the service engine, for example, if the socket is closed on
the server side. The client has to re-register when the service engine is
restarted.
The registration manager maintains the registration information for
each client during runtime but it is the client’s responsibility to react to
shutdowns of the service engine, for example, if the socket is closed on
the server side. The client has to re-register when the service engine is
restarted.
When a client updates its registration information, the new registration
information must be passed to the interface. The handler stores it in
memory. It is the responsibility of the client to handle any additions or
removals to/from the registration information. The registration manager
initiates an update in the service engine core which propagates the
service graph data structures according all the registrations.
information must be passed to the interface. The handler stores it in
memory. It is the responsibility of the client to handle any additions or
removals to/from the registration information. The registration manager
initiates an update in the service engine core which propagates the
service graph data structures according all the registrations.
The registration information has the form of a <Registration> XML
structure. Clients pass this structure by way of an API function to the
service engine.
structure. Clients pass this structure by way of an API function to the
service engine.
The Registration Conditions
The registration conditions can register for services status changes if
certain criteria are met. The following conditions are available:
certain criteria are met. The following conditions are available:
❏ Register depending on service structure:
• Recursive: <Recursive>
• Depth of graph: <Depth>
❏ Register for all status change events:
• All events: <All>