All interaction between a client application and the Scheduler service takes place in the context of a session, represented by the ADSSession object.
To gain access to the Scheduler on a given computer, the client must create an ADSSession object on that computer. Once the object is created, the Connect method must be called to authenticate the client. Alternatively you may create the ADSSession object on the local computer and use the ConnectRemote method to connect to the remote computer.
Until one of the Connect methods is called, the client cannot gain access to any jobs on the target computer.
The Arcana Scheduler service must be installed and running on the target computer in order to administer the Scheduler. The service does not need to be running in order to create the ADSSession object. Therefore after creating the session the client program can use the StartService method to start the service if necessary.
Depending on the security configuration for the Scheduler, a given client may not have access to all scheduled jobs. In this case, the number of jobs available through the session will be smaller than the total number of jobs. Use the Attributes property to determine whether the session's view is restricted.
When a session first connects to the Scheduler, it receives a copy of the configuration data from the Scheduler. This information is not automatically updated to reflect changes in job status or configuration changes made by other clients. To retrieve the latest configuration information, use the Refresh method.
Likewise, changes made to jobs through a session are buffered until the session's Save method is called. Until Save is called, changes will not be visible to other clients or to the Scheduler service.
Program ID |
ADScheduler.ADSSession |
Interface |
IADSSession2 |