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.
Procedure
-
On the server computer, export and open the
configuration.xml file. For detailed instructions on working with this file, see
Manually editing the Spotfire Server configuration file.
-
In the
configuration.xml file, locate the following section:
<scheduled-updates>
...
<performance>
<load-on-exhausted-instances>false</load-on-exhausted-instances>
<update-exhausted-instances>true</update-exhausted-instances>
</performance>
...
</scheduled-updates>
-
To allow scheduled update analyses that are not cached to use exhausted Web Player instances, change the
load-on-exhausted-instances
value to "true".
-
To prevent scheduled update analyses that are cached from using exhausted Web Player instances, change the
update-exhausted-instances
value to "false".
Note: When a Web Player instance becomes available, the scheduled update is applied only if the rule is still scheduled at that time.
-
Save and close the file.
-
Import the file back to the
Spotfire database.
-
Restart the server.