Before NDS* runs the janitor, it queries WAN Traffic Manager to see if this is an acceptable time for this activity. The NDS_JANITOR does not have a destination address; it requires a NO_ADDRESSES policy. If WAN Traffic Manager returns DONT_SEND, janitor work will be put off and rescheduled. The following variables are supplied.
Time of the last round of janitor work since DS.NLM was started. When NDS starts, Last is initialized to zero. If NDS_JANITOR returns SEND, Last is set to the current time after NDS finishes the janitor.
The version of NDS.
The expiration interval for all connections created while running the janitor. <0, 0 Use the default expiration interval (default) >0 Expiration Interval to be assigned to this connection
This variable indicates when NDS should schedule the next round of janitor work. In the past, 0, use the default scheduling In the future, time when janitor should be scheduled
This variable tells NDS what to do if it needs to create a new connection while running the janitor. CheckEachNewOpenConnection is initialized to zero. Zero (0) indicates that NDS should not query WAN Traffic Manager, but should proceed with making the connection as in normal operations. One (1) indicates that NDS should query WAN Traffic Manager using the NDS_JANITOR_OPEN traffic type. If WAN Traffic Manager returns SEND, NDS proceeds to make the connection; otherwise it returns an error and continues with other janitor tasks. Two (2) indicates that NDS should not query WAN Traffic Manager, but should act as though the connection had failed. This variable enables policies that can run the janitor normally, decide on a connection-by-connection basis, or that only reuse existing connections. 0 Return Success without calling WAN Traffic Manager, allowing the connection to proceed normally (default) 1 Call WAN Traffic Manager and let the policies decide whether to allow the connection 2 Return ERR_CONNECTION_DENIED without calling WAN Traffic Manager, causing the connection to fail
This variable tells NDS what to do if it needs to reuse a connection it believes is already open while running the janitor. CheckEachAlreadyOpenConnection is initialized to zero. Zero (0) indicates that NDS should not query WAN Traffic Manager, but should proceed with reusing the connection as in normal operations. One (1) indicates that NDS should query WAN Traffic Manager using the NDS_JANITOR_OPEN traffic type. If WAN Traffic Manager returns SEND, NDS proceeds to reuse the connection; otherwise it returns an error and continues with other janitor tasks. Two (2) indicates that NDS should not query WAN Traffic Manager, but should act as though the connection has failed and cannot be reopened. This variable is used in environments that spoof connections to enable policies to decide if the connection is really up or if it is being spoofed. 0 Return Success without calling WAN Traffic Manager, allowing the connection to proceed normally (default) 1 Call WAN Traffic Manager and let the policies decide whether to allow the connection or not 2 Return ERR_CONNECTION_DENIED without calling WAN Traffic Manager, causing the connection to fail