Before trying to use my script with NetXMS I was making use the scheduler services of the underlying operating system. It works but has major disadvantage of keeping things in sync. You end up with different program having different schedules to test the results of the program that run before them. Because there is no formal relation between the different programs there is no central place to see which program depends on which. Over time when one changes the schedule of one program it can easily break the whole chain. My idea was to use a single program to set the schedule and test the result, however it's now clear that NetXMS expects results to be readily available for its DCIs.
A scheduler within NetXMS for long running tasks can be a solution. At the moment I thing I'll revert to using the Windows scheduler and (search to see how I can) modify the script to push an event to NetXMS informing it of success or failure of the script.
Regards,
Dan
A scheduler within NetXMS for long running tasks can be a solution. At the moment I thing I'll revert to using the Windows scheduler and (search to see how I can) modify the script to push an event to NetXMS informing it of success or failure of the script.
Regards,
Dan