Network Address Monitoring and Messaging API

An engine and extensible API for monitoring interface addresses and programmatically responding to their changes.

Date Posted: April 6, 2004

Overview Requirements Download FAQs Forum Reviews 1. I'm in bin/ and I typed run.sh or run.bat, and nothing happened. Good, it worked! By default, the conf/namma.properties files are set up to not run as a daemon, not "persist" any information, log only critical messages, and notify you of a new IP address detection in no way, shape, or form. Modifications to that file will change the behavior. Descriptions of the commented parts (lines preceeded by a ";") exist to explain the function. Back to top 2. How do I use or extend the API? In order to extend the API, you must have a Java compiler version above 1.4.0. You must then use the release/namma-1.00.jar file as part of your class path in order to build against the API. A description of the classes and methods to be overridden are provided in the HTML documentation residing in apidoc/. Back to top 3. What must the zone file look like in order to use FtpDnsNotify? There are only two particular requirements for the format of the zone file: The word "serial" must appear on the same line as the serial number to be used. The record to be changed must be the first IP address formatted and will be the only one changed. These requirements can easily be alleviated, but keep in mind that this is merely a sample. A zone file used for testing has been included here. The post condition for the zone file is that the serial has been incremented by 1 and the first IP address in the file will be changed to what was passed to the runNotify function. ; test.org $TTL 1200 @ IN SOA ns2.somehost.net. scuppett.us.ibm.com. ( 2004031345 ;serial 1200 ;slave refresh 120 ;slave retry 604800 ;slave expiration 1200 ) ;negative ttl NS ns2.somehost.net. NS ns1.somehost.net. A 127.74.136.71 ; ; www CNAME test.org Back to top 4. My FTP notification function isn't working. I also ran into this during testing with some FTP servers. It is caused by one of two things: Your URL string is wrong (missing log-in information, access to resource). JRE 1.4's native implementation of FTP access via the URL class is of different RFC than what is considered "standard." Please see available resources on the Web regarding this issue. External FTP APIs abound from various places including Apache's Jakarta Web site. If FTP functions are going to be very important in using this engine, I would recommend implementing the API for your own notification purposes and using an external FTP API for it as well. Back to top 5. How do I install it as a Windows/UNIX service? How do I install it as a Windows/UNIX service?The default run.sh and run.bat will work and permit testing, but they do leave something to be desired. I have provided scripts and .conf files that work with the Java Service Wrapper available from Sourceforge. Their instructions, along with the provided scripts, should be more than enough to get started. But, just in case, their files in bin/ also go in this bin/; however, their files in lib/ go into the ext/ directory on this project. Do not copy the conf/wrapper.conf file. There is a working .conf file already present and you will lose settings. Once this process has been completed, you can run Installnamma.bat to get an automatic Windows service and/or symbolically link to bin/namma on UNIX/Linux platforms. Back to top