Scheduling

Typically, you create publication settings for recurring tasks. With FrameMaker Publishing Server, you can create multiple publication tasks and schedule them to run at specified intervals. In a typical technical publications department, many teams create automated builds that are then run at the required intervals. You can specify the intervals as once, daily, weekly, or monthly. A publication task requires a defined schedule to run or a user can run them manually. For more information on running tasks manually, see Create a schedule for run.

After you schedule a task to run, FrameMaker Publishing Server adds these as scheduled tasks to the Windows Task Scheduler. You can view and edit these tasks from Windows Task Scheduler independent of FrameMaker Publishing Server. The scheduled tasks appear with the name of the task and the user name associated with the task.

Keep in mind the following when you determine the build schedules:

• Each source document requires a separate publication task. If you have a large documentation set that heavily uses single-sourcing approach, you will need to create as many publication tasks as the number of book files.

• Builds are queued—if you want to run an immediate publication task when a large number of builds are in the queue, you will have to wait for the builds in the queue to be completed before you can run your publication task.

• If you require daily builds, consult with other teams so that your build schedule doesn’t clash with theirs. If you schedule a large build in the day time, chances are that a once-only build task you want to run urgently will have to wait until the build queue is completed. A good way to ensure that daily build schedules do not affect other build tasks is to plan your daily builds to run in after-office hours.