On Jun 3, 2008, at 11:51 AM, Brian Semrad wrote: > From what I can tell so far I should be looking at creating a custom > module importer for our app to feed OpenNMS
I think you mean "model importer". Yes, that's a great way to go if you have an external system that serves as your source of truth about some or all of the things OpenNMS should be managing. > I don't want to have to restart OpenNMS > everytime something changes and I'd rather not implement a solution > where we rewrite the entire node list every time either. I would > prefer > to send node changes over a TCP socket if possible. The Importer figures out incremental changes in the XML file(s) that it's importing. Usually you would schedule a daily job to do the importing. If your updates are more frequent and you need them to be reflected in short order, you can send an event to OpenNMS (e.g. using send-event.pl) to tell the Importer to start an import for a given group immediately. -jeff ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
