Service configuration for remote access

When iBase Scheduler is installed on a user’s machine solely to keep their personal database up-to-date, no configuration changes are required to the service or SQL Server databases. It is anticipated that, in this case, Scheduler can be configured by the administrator of the iBase database.

If Scheduler is installed on an application server, possibly accessing files on a file server or databases on SQL Server, the service configuration must be changed:
  • Users must have write access to the Scheduler database, Scheduler.mdb.
  • Users must log on with an iBase user name and password (they cannot use single sign-on).
The configuration of the Scheduler connections, tasks and triggers, and the iBase import or export specifications becomes more involved because of the need to use UNC paths throughout. Therefore, it is beneficial for the user who configures Scheduler to understand Windows™ security and folder sharing in an enterprise environment.
After the Scheduler service is installed on the machine that is to run the tasks, the Scheduler Configuration Utility can be installed on a remote machine for administering the Scheduler database.
Note: During the installation, the Scheduler database is installed in its default location. You can move the database if required. See Installing Scheduler on the server for details.

Configuring Scheduler

Note: To open iBase Scheduler Configuration, you require write access to the Scheduler database, Scheduler.mdb. You must log on with an iBase user name and password (not single sign-on).
This involves the following steps:
  1. Setting up database connections

    A database connection contains the information that is required by Scheduler to open the database, that is, the location of the database and its security file, and the user name and password. Notice that Scheduler does not require exclusive access to the database when scheduled tasks are run.

  2. 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 or after you import or export data.

  3. 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.