TIBCO Enterprise Runtime for R - Server Edition
TIBCO® Enterprise Runtime for R - Server Edition provides Spotfire clients with the ability to execute R code, using TERR, on the TERR service node.
A TERR service is required to execute data functions in Spotfire files from Spotfire Automation Services and Spotfire Web Player, because those services do not have TERR engines.
The TERR service itself is running the service as the same user account as is running the Node Manager on which the service runs. See Node Manager.
By default, TERR scripts executed by the TERR service on behalf of its users are executed in a different execution context, as explained here.
TERR service component | Default | Description |
---|---|---|
Service account | NT Authority\System (Windows) or
root (Linux)
|
Default:
NT Authority\System (Windows) or
root (Linux)
|
Log files | <node manager
installation>/logs
See the topic "TERR Service Logs" in the TIBCO® Enterprise Runtime for R - Server Edition for more information. |
Name | Default Port and Protocol | Function Description | Secure/Encrypted |
---|---|---|---|
Communication port |
9502/tcp
|
For secure (HTTPS) internal communication. Cannot be accessed directly. | Yes |
TERR engine ports |
61000/tcp ->
62000/tcp
|
Host-internal communication between the TERR service and the TERR engines. | No |
- Settings and Configuration Tasks for TERR Service
You can use these settings to limit the capabilities of running TERR data functions. - Script Security & Restricted Execution Modes
The following mechanisms control security of the TERR service and to prevent users from running malicious scripts on the server.
- Settings and Configuration Tasks for TERR Service
You can use these settings to limit the capabilities of running TERR data functions. - Script Security & Restricted Execution Modes
The following mechanisms control security of the TERR service and to prevent users from running malicious scripts on the server.