Scheduling imports and exports

Before you use iBase Scheduler to schedule the import or export of data, you need to configure it in the iBase Scheduler Configuration dialog.

This involves the following steps:

Set up a connection to the required iBase database.
A database connection contains the information required by iBase Scheduler to open the database, that is the location of the database and its security file, and the user name and password. Notice that iBase Scheduler does not require exclusive access to the database when running scheduled tasks.
Add one or more tasks to specify the data to import or export.
A task specifies the batch specification that defines the import or export specifications to run. (Specifications and batch specifications are created in iBase itself.) You can also set up programs or custom plug-ins to perform specific actions (task actions) either before and/or after importing or exporting data.
Set up one or more triggers for each task to determine the scheduling frequency.
A trigger is the event that causes the task to run, for example either when a specified date and time is reached or when the modification date on a file changes. A trigger can recur or be a once-only event.

Scheduler and iBase security features

The user account for running iBase Scheduler does not need any security restrictions applied. However, iBase Scheduler does support these iBase security features:

Database Management groups. These determine whether users will be denied access to the database when they try to test a connection or create a new task. The minimum user permissions are described in Minimum user permissions below.
Data Access Control groups. These restrict access to specific entity and link type records or to specific fields, and will prevent iBase Scheduler from running tasks that access those records and fields. In these circumstances, the completion status of the task will indicate that the task failed.
Folder Object Control— specifically this restricts access to the folder containing the batch import or export specifications.

The following iBase security features are not supported by iBase Scheduler, and any restrictions imposed by these features will be ignored in iBase Scheduler:

System Command Access Control
Reason for Action
Auditing— nothing is recorded in the audit log

Minimum user permissions

Scheduling can only be run by authorized users with the following minimum user permissions in iBase:

Add Entity/Link Records
Update Entity/Link Records
Update/Delete Entity/Link Records created by other users

These are the same as those required to run import specifications in iBase itself.

Note: If you need to change the permissions granted to a user account which is used to run iBase Scheduler then make sure you re-test the connection to the database. If you are using Data Access Control groups then you need to run a trial import/export to verify that these are set correctly.