adTempus API
|
The ImportExportFacility allows you to export and import data.
__interface IImportExportFacility : IDispatch;
public interface IImportExportFacility : IDispatch;
Public Interface IImportExportFacility Inherits IDispatch
Beginning with adTempus 3.0, XML is used for export files. adTempus 3.0 and later cannot read export files produced by versions before 3.0, and vice-versa.
All import files are validated against an XML schema, and the import will fail if the file is not valid.
Use Scheduler.GetImportExportFacility to get an ImportExportFacility object to work with.
To export data, create a new ADTObjects collection, add the desired objects, and call ExportToXML. Any dependent objects are exported automatically. For example, if you export a Job object its steps, triggers, responses, etc. are all included automatically, as are any notification recipients, scripts, or other shared objects that are associated with it.
Importing data is a five-step process:
In order to export an object, the caller must have saModify permission for the object. This is because it is possible for a user to export a job to a file, make changes to the file, and import the file as a new job.
For example, Joe has permission to view and run, but not modify, a job that runs under an account with greater system authory than Joe has. If Joe were allowed to export this job, he could export it, modify the file so that the job runs a command prompt instead of the original target, then re-import the job. Now he can run the job, which opens a command prompt running under the other user's account, which gives him expanded access to the system. By requiring saModify permission for exports, he is prevented from doing anything using the export process that he couldn't already do in the Console.
adTempus API Reference version 3.0.0.0, revised 10/30/2008
|