NvdmAPI is a Java-based object-oriented application programming interface (API)
to HP OpenView Radia Configuration Servers (RCS, formerly known
as Novadigm Radia Configuration Server). The interface provides
full read / write access to the RCS database with easy-to-use
object abstractions. In this respect it is a faster running and
more intuitive to use replacement for HP's (Novadigm's) proprietary
Tcl-based API. The NvdmAPI requires a Java VM 1.2 or above, and
runs cross-plattform on Windows, Unix, Linux, MacOS, and so on.
As there have been quite some discussions between Novadigm and myself
about potential infringements of copyrights or nondisclosure
agreements, I want to clearly state the following:
This API has been implemented without any insight knowledge
of the implementation of the Radia products, their internal
protocol, or any other information not publicly available. When I
developed the API, I did not work for Novadigm, nor did I have
access to any internal Novadigm or HP material that would have
facilitated my attempts. The sole input to this effort has
been the TCP traffic logging of the RCS, which is a standard
product feature and can be configured easily by everybody
with simply setting a (well documented!) switch in the RCS
configuration file. This logging allows to monitor the TCP
traffic between the Radia System Explorer and the RCS on
byte level.
NvdmAPI represents just my conclusions I've
drawn from observing communications with the RCS. And while
the API seems to work correctly in all the tests I
conducted, I can not be sure that it will behave as desired
or expected in all cases! I did not have access to HP's (Novadigm's)
internal specification of the protocol, and the implementation
of NvdmAPI is just based on pure speculation. So if you should be
looking for a way to re-engineer Radia's protocol by
re-engineering my Java code, you are on the wrong track! :-)
|
|
|
By the way: if you really want to look at the definitive protocol
implementation, you probably know that there are much simpler
ways than re-engineering my Java code or trying to draw
conclusions from the TCP logging... I don't want to discuss this
here in detail, but it is easy to look at HP's (Novadigm's)
own Tcl source code -- no tricks, no hacks involved. But once again:
that's not what I did! (I don't like Tcl ;-)
Comments, suggestions, feature requests and so on are as always welcome!
|