eDirectory object timestamp tool



By: ab

September 8, 2010 11:51 am

Reads: 381

License:
GPL v3

Download obitTimestamp.sh__1

So how do we setup something to use the web interface in a scripted fashion? There are actually a lot of ways. Something like SecureLogin could be used to “click” in predicable places over and over with a web browser. Other ways include using utilities that, at the command line, can get data from a webpage, parse it, and then act on it. This is the route Peter Lambrechsten took in his post here: http://forums.novell.com/showthread.php?t=393511

Taking the hard work he did and making a script out of it was fairly easy. The addition basically asks for parameters (machine to hit via port 8030 (iMonitor’s HTTPS port), username in eDirectory DN format, and a password) and then lets the user choose which report to parse. The report in iMonitor must already exist and links to current documentation are included. Once a report is selected the script hits iMonitor once per object telling the system to timestamp the object. The EIDs that are being timestamped are returned as the script runs so progress can be monitored.

This was tested against eDirectory 8.8.5 FTF 1 x86_32 on SLES 10 SP2 x86_32. The result is a way, with no more work than iMonitor would require anyway, to timestamp all objects that show up in the iMonitor obituary report. It could even be set to be automated after an automated report was created in iMonitor to run once in a while and watch for old obituaries for you.

To use this script copy it to your system with ‘bash’ and ‘wget’ (both default on most *nix systems), make it executable (`chmod +x ./obitTimestamp.sh`) and then run it:

./obitTimestamp.sh machine.goes.here admin.context.goes.here passwordHere

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: , , , , , ,
Categories: Cool Tools, eDirectory

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Comment