Okay
guys (and gals)-
Here
is an expert-level question for all you WUG users who need a
challenge.
Situation:
We
have new devices come up on a daily basis on our monitored network. As
a corporate service, we offer the WEB view of these devices some of our
employees.
The
problem is, someone has to go into WUG and "create" the new workstation (no,
it cannot be discovered), then re-save the WUG map so the HTML view reflects
the new devices added. (the "device" is a set-top box network located
throughout the U.S.) As new set-top boxes come on line, and bad ones are
taken off-line, we need the web view to represent and monitor these
devices. Then the web view will allow customers to view and monitor
these devices.
I
wrote a PERL script to dynamically create an INI file based on a query to our
Oracle server. The output from Oracle is a CSV file which is them ran
against the PERL script to dynamically create the INI.
Follow me so far? Good.
The
problem is, we have some 40-60 (and growing) separate maps to IMPORT via WUG
every day. Yes, that means opening WUG, selecting File | Import | INI
and this has to be done every day for every map. This is "becoming" *a
pain.* Actually, it sucked from day 1 but the benefits of offering this
to customers outweight the pain-in-the-ass factor. Until now. We
are growing quickly and this approach is not scalable. What happens when
we get 200-500 maps?
The
Question:
I
need your assistance in automating the File | Import process to automatically
create the WUG map files. This might be in the form of an API?
Maybe a commandline switch for WUG: "C:\Program Files\WhatsUp"
/mapimport:myfile.ini (??) Maybe dump the INI conversion and go
with something else? The solution must be able to be automated. We
query an Oracle database for the available devices.
Thanks for reading and any approach will be
considered.
Garry Egan
Product Engineering
HCorp, INC