About scheduling a job
If a design generates a large document, schedule a job to run the design. Attempting to generate a very large document by running a design unscheduled tends to cause time‑out errors. iHub waits a fixed amount of time for the generated document, 30 minutes by default. If document generation takes longer than the wait period, iHub stops waiting for the document and displays a time‑out message.
Scheduled jobs run in the background. You do not have to wait for the processing to complete before you perform other tasks, such as submitting another run request. iHub saves the output in the Encyclopedia volume, so you can view the output at a later time.
You can schedule a job to generate a weekly document that contains the summary sales figures for a store, for example. iHub generates the document once each week and saves the document in the Encyclopedia volume. Alternatively, you can schedule an event-based job. For example, you can schedule a job that presents sales data for an area after iHub finishes running jobs that present the sales data for individual stores in that area. Conditions that trigger event-based jobs include the following:
The existence of a specific file in the Encyclopedia volume
The completion of another job
The output of a web service event
Finally, you can schedule iHub to run a job that is based both on time and on an event.
When you schedule a job to run, you can also perform the following tasks:
Schedule printing after iHub generates the document.
Set priorities for running designs.
Retry running scheduled designs that fail to run.
Manage version control.
Limit user access to the generated document.
Distribute the document.
Send notification of the availability of the document.