Scheduled updates and Automation Services rules You can modify the following settings for scheduled updates and Automation Services rules. Child Topics:Preventing users from opening scheduled update files outside of their schedule window Large analysis files are often managed by scheduled updates so that end users can view these files without waiting for them to download. If an end user tries to open one of these scheduled update files outside of its schedule window, however, the file can take a long time to open and may significantly tie up system resources. You can configure the server to block end-user access to these files when the files are not scheduled. Changing whether scheduled updates are sent to exhausted service instances By default, if all the Web Player instances in an implementation or a site are listed as "exhausted", scheduled update requests for analyses that are not cached will not be sent to a Web Player instance until one becomes available (no longer exhausted). In the same situation, a scheduled update request for an analysis that is already cached will be sent to exhausted instances. You can change these defaults by editing the Spotfire Server configuration file. Changing whether recovered rules are automatically enabled When an analysis file is deleted from the library, any scheduled update or routing rule for that file fails. If the analysis file is then imported back to its previous location, the rule is recovered but it does not run because the rule is, by default, in the "disabled" state. You can switch the default for these recovered rules to "enabled". Setting the maximum execution time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can run before the server cancels the job. The default setting for this property is 259,200 seconds (72 hours). Setting the maximum inactivity time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can remain inactive before the server cancels the job. The default setting for this property is 600 seconds (10 minutes). Preventing users from opening scheduled update files outside of their schedule window Large analysis files are often managed by scheduled updates so that end users can view these files without waiting for them to download. If an end user tries to open one of these scheduled update files outside of its schedule window, however, the file can take a long time to open and may significantly tie up system resources. You can configure the server to block end-user access to these files when the files are not scheduled. Changing whether scheduled updates are sent to exhausted service instances By default, if all the Web Player instances in an implementation or a site are listed as "exhausted", scheduled update requests for analyses that are not cached will not be sent to a Web Player instance until one becomes available (no longer exhausted). In the same situation, a scheduled update request for an analysis that is already cached will be sent to exhausted instances. You can change these defaults by editing the Spotfire Server configuration file. Changing whether recovered rules are automatically enabled When an analysis file is deleted from the library, any scheduled update or routing rule for that file fails. If the analysis file is then imported back to its previous location, the rule is recovered but it does not run because the rule is, by default, in the "disabled" state. You can switch the default for these recovered rules to "enabled". Setting the maximum execution time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can run before the server cancels the job. The default setting for this property is 259,200 seconds (72 hours). Setting the maximum inactivity time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can remain inactive before the server cancels the job. The default setting for this property is 600 seconds (10 minutes). Parent topic: Advanced proceduresHomeAdvanced proceduresScheduled updates and Automation Services rules
Scheduled updates and Automation Services rules You can modify the following settings for scheduled updates and Automation Services rules. Child Topics:Preventing users from opening scheduled update files outside of their schedule window Large analysis files are often managed by scheduled updates so that end users can view these files without waiting for them to download. If an end user tries to open one of these scheduled update files outside of its schedule window, however, the file can take a long time to open and may significantly tie up system resources. You can configure the server to block end-user access to these files when the files are not scheduled. Changing whether scheduled updates are sent to exhausted service instances By default, if all the Web Player instances in an implementation or a site are listed as "exhausted", scheduled update requests for analyses that are not cached will not be sent to a Web Player instance until one becomes available (no longer exhausted). In the same situation, a scheduled update request for an analysis that is already cached will be sent to exhausted instances. You can change these defaults by editing the Spotfire Server configuration file. Changing whether recovered rules are automatically enabled When an analysis file is deleted from the library, any scheduled update or routing rule for that file fails. If the analysis file is then imported back to its previous location, the rule is recovered but it does not run because the rule is, by default, in the "disabled" state. You can switch the default for these recovered rules to "enabled". Setting the maximum execution time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can run before the server cancels the job. The default setting for this property is 259,200 seconds (72 hours). Setting the maximum inactivity time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can remain inactive before the server cancels the job. The default setting for this property is 600 seconds (10 minutes). Preventing users from opening scheduled update files outside of their schedule window Large analysis files are often managed by scheduled updates so that end users can view these files without waiting for them to download. If an end user tries to open one of these scheduled update files outside of its schedule window, however, the file can take a long time to open and may significantly tie up system resources. You can configure the server to block end-user access to these files when the files are not scheduled. Changing whether scheduled updates are sent to exhausted service instances By default, if all the Web Player instances in an implementation or a site are listed as "exhausted", scheduled update requests for analyses that are not cached will not be sent to a Web Player instance until one becomes available (no longer exhausted). In the same situation, a scheduled update request for an analysis that is already cached will be sent to exhausted instances. You can change these defaults by editing the Spotfire Server configuration file. Changing whether recovered rules are automatically enabled When an analysis file is deleted from the library, any scheduled update or routing rule for that file fails. If the analysis file is then imported back to its previous location, the rule is recovered but it does not run because the rule is, by default, in the "disabled" state. You can switch the default for these recovered rules to "enabled". Setting the maximum execution time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can run before the server cancels the job. The default setting for this property is 259,200 seconds (72 hours). Setting the maximum inactivity time for an Automation Services job This Spotfire Server property indicates how long an Automation Services job can remain inactive before the server cancels the job. The default setting for this property is 600 seconds (10 minutes). Parent topic: Advanced proceduresHomeAdvanced proceduresScheduled updates and Automation Services rules