The importer assumes that the data you send is the authoritative and
complete set of nodes you want to monitor. If nodes are missing from youf
file but are in the opennms database, they will be deleted from the opennms
database, interfaces that have been removed from nodes will be removed from
the database. Similarly, information added to the file will be added and
updated nodes will be updated. the ForeignSource:ForeignId is the key used
to match opennms nodes to nodes in your file.
Hope that helps,
Matt
On Wed, Jun 11, 2008 at 9:15 AM, Les Mikesell <[EMAIL PROTECTED]> wrote:
> Michael Smith wrote:
> > [EMAIL PROTECTED] wrote:
> >> From what I can see from this thread, it appears that this is possible
> >> via the "model import" services. I'm having trouble piecing together
> >> the detailed steps, and I think that pointers to docs and or examples
> >> would go a long way...
> >
> > Hi Doug,
> >
> > The model importer needs a URL to load the import file from. file:// and
> > http:// URLs both work.
> >
> > The model-importer.properties configuration file is documented in the
> > Wiki (http://www.opennms.org/index.php/Importer_Service), but if you
> > want to see the format expected by the importer, take a look at some of
> > the XML files here:
> >
> >
> http://opennms.svn.sourceforge.net/viewvc/opennms/opennms/trunk/opennms-import/src/test/resources/
> >
> > The XSD file for the XML syntax is here:
> >
> >
> http://opennms.svn.sourceforge.net/viewvc/opennms/opennms/trunk/opennms-config/src/main/castor/model-import.xsd?revision=7524&view=markup
> >
> > In my case I point the model importer at a CGI that rifles through my
> > provisioning database and generates the required XML dump.
> >
> > importer.importURL = http://localhost:4444/blah/export.py
> >
> > You could also push from the other side: save the XML dump to a file on
> > the OpenNMS server periodically, and trigger OpenNMS to reload the file
> > from a file:// URL following these instructions:
> >
> > http://www.opennms.org/index.php/ForceAnImport
> >
>
> Is there a way to pass information from an external database to
> indicate that an existing machine has been retired or had a name or IP
> change and that you want existing history to be preserved but polling
> stopped, renamed/numbered, or deleted, depending on the circumstances?
> I'm thinking of making a more authoritative inventory database that
> would be aware of more equipment and only have OpenNMS monitor things
> that are in production use. But I'd like a way to do
> renames/moves/deletes and some sanity checks between them.
>
> --
> Les Mikesell
> [EMAIL PROTECTED]
>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
