iPAM Developer Documentation

- Scheduling Attributes

 

Handlers and Daemons may be activated on a schedule. The schedule may be specified in through various user interfaces or in the startup file (using a text editor). At the scheduled times handlers activate their inputs to request product. Daemons have no input so they simply perform their predefined tasks at the specified times.

Scheduling is not exact. Actual activation may depend on whether internal queue slots are available for Handler/Daemon execution. Be careful not to overload your data sources with too many queries.

Below is a list of attributes as they would appear in the checkpoint or startup file.

No schedule

(schedule none)
makes the activation of the agent dependent on another agent in the data chain. The other agent may preceed or proceed this agent. There can be any number of agents in a chain.

Schedule to run once

(schedule once)
causes the agent to be activated only one time. When the agent completes its nextUpdateTime property will have the value, "already ran once". This scheduling option is especially useful in conjunction with the Daemon deleteExpiredAgents.

Periodic

(schedule periodic)(period nnnn)
nnnn specifies the reactivation period in seconds

Hourly

(schedule hourly)(minuteOfHour mm)
mm specifies the minute of the hour, from 0 - 59

Daily

(schedule daily)(hourOfDay hh)(minuteOfHour mm)
hh specifies the hour of the day from 0 - 23
mm specifies the minute of the hour, from 0 - 59

Weekly

(schedule weekly)(dayOfWeek "day")(hourOfDay hh)(minuteOfHour mm)
"day" is "Monday" "Tuesday" "Wednesday" "Thursday" "Friday" "Saturday" or "Sunday"
hh specifies the hour of the day from 0 - 23
mm specifies the minute of the hour, from 0 - 59
 

Revised: 12 November 1999