Product: TIBCO Spotfire®
For a Spotfire data function that uses a TERR script, what is the difference between Force Local and Force Server?
For a Spotfire data function that uses a TIBCO Enterprise Runtime for R (TERR) script, what is the difference between Force Local and Force Server?
A Spotfire data function can send its TIBCO Enterprise Runtime for R (TERR) script to the Spotfire Analyst desktop client's built-in local TERR engine for processing, or it can send the script (and its input data) out to a TIBCO Spotfire Statistics Services (TSSS) instance (via URL) for processing in the TSSS instance's TERR engine.
TSSS is a separate TIBCO product. It is not part of Spotfire Server. TSSS 7.5 (the current release) was used in testing Spotfire 7.5, 7.6, 7.7 and 7.8.
You do not need TSSS if you are only going to run your data functions using the Spotfire Analyst desktop client, but you will need TSSS if you want to run the data functions using Spotfire Web Player or Spotfire Automation Services, because the Web Player and Automation Services do not have their own built-in TERR engines.
The following brief discussion outlines the settings Spotfire uses to determine whether a data function's TERR script uses local TERR or a TERR engine on a TSSS server:
These are the three selections available for a Spotfire/TERR data function's "Run Location" parameter and what they do when the data function is run from the Spotfire Analyst desktop client:
Default = Use whatever the global "Use Locally-Installed TERR Engine" checkbox in the "Tools > Options > Data Functions" dialog is set to. (Use local TERR if it is checked, and use TERR on a TSSS instance if it is unchecked).
Force Local = Ignore that global checkbox and run the TERR script using the Spotfire desktop client's built-in local TERR engine, if it is available.
Force Server = Ignore the checkbox and run the TERR script using a URL connection to a TIBCO Spotfire Statistics Services (TSSS) instance, if a TSSS instance is available and the URL for it has been specified.