Configuring content download jobs
Microsoft Forefront Threat Management Gateway content download jobs proactively update the cache to anticipate client requests, improving performance and saving bandwidth. Use the following procedure to configure a content download job.
To configure a content download job
In the Forefront TMG Management console tree, click Firewall Policy.
On the details pane, click the Web Access Policy tab.
On the Tasks tab, click Configure Web Caching.
On the Content Download tab, click New.
On the Welcome page of the Content Download Job Wizard, specify a name for the job. Then complete the wizard as outlined in the following table.
Page Field or Property Setting or Action
Run the job
The job should run only once, either immediately after the wizard or at a specified time. Alternatively, a recurring download job can be automated. The job can only run if the Microsoft Forefront TMG Job Scheduler service is running. For a scheduled run-once job or for a daily or weekly job, specify a date and time for the job to run.
Run the job one time only
If you selected a download frequency of One time only, scheduled, the job will run in accordance with settings on this page.
Job start date and Job stop date
If you selected a download frequency of Daily, the job will run in accordance with settings on this page.
Select the days the job will run
If you selected a download frequency of Weekly, the job will run in accordance with settings on this page.
Download content from this URL
Download content from specified URL.
Do not follow link outside the specified URL domain name
Limit the content download to a single domain
Maximum depth of links per page
Limit how embedded links are followed
Limit number of objects retrieved to a maximum of
Maximum number of objects stored for the download
Maximum number of concurrent TCP connections to create for this job
Maximum number of TCP connections created for the job.
Cache all content
Cache all content, including redirection responses (301, 302, and 307)
If source and request headers indicate to cache, or if content is dynamic, then the content will be cached
Cache if headers indicate. In addition, cache if content is dynamic, even if not indicated by headers.
If source and request headers indicate to cache, then the content will be cached
Cache only if headers indicate.
Expire content according to the cache rule
Content remains valid in accordance with cache rule settings and response headings.
Set TTL if not defined in response
TTL of object is overridden if the object does not have a response header that sets the TTL. If the object has a TTL, it is handled in accordance with cache rule settings
Override object's TTL
Mark downloaded content with a new TTL to indicate how long it remains in the cache. Indicate the TTL value.