Scheduling the GCF processors

After the settings in the configuration files have been configured, the GCF processors can be scheduled to run on a periodic basis using Windows Task Scheduler.

There should be the following scheduled tasks for each collaborating site:

• Scheduled export
• Immediate export
• Scheduled import

To schedule the processors:

• For each collaborating site, create a task in Windows Task Scheduler for each of the preceding tasks. For instructions on created tasks with Windows Task Scheduler, see the Windows Help. For information on the task frequency and the command lines to specify, see the following topics.

  Note    Installing the processors as described in Installing the GCF processors installs sample .cmd files for export and import with the correct configuration file names and share names that you can use to compose the command line.

If the export and import processors for two collaborating sites A and B reside on the same computer, the export and import tasks may be combined into a single scheduled task. The task should execute two actions, one for each share in turn, first the export processor for share A and then the import processor for share B. A second task should also execute two actions but in the opposite direction, first the export processor for share B and then the import processor for share A. This configuration is described in more detail in the following topics.

An example of this configuration is when vaults on two Meridian Enterprise servers are collaborating and the servers reside at the same physical location and share a GCF computer. In that case, briefcases are immediately available to the import processor so it can run immediately after the export processor. This method results in a total of two scheduled tasks (one for each direction between both sites) instead of four (two for each direction between both sites).

When you are finished scheduling the processors, Global Collaboration Framework installation and configuration is complete. For advanced configuration and integration with existing configurations and customization, see Configuring with VBScript.