Custom configuration properties
You can fine tune the behavior of the Spotfire Service for R by setting custom configuration properties.
- Allowed engines
You can specify the number of R engines that can run concurrently, and the number of R engines that are allocated in the Spotfire Service for R queue. - Compressed job contents and results
You can compress large data sets sent to R. You can also compress returned results for R data functions that are then sent to the Spotfire Service for R. - Docker container built for no internet access
If you are deploying a Spotfire Service for R to use in a system with no internet access, you must configure the container image so that it does not try to build an image on top of the one that you have initially built in a system with internet access. - Engine pruning
When the Spotfire Service for R reaches a certain percentage of capacity of usage, then the Spotfire Service for R begins pruning R engines to free service resources. - Engine timeout
You can specify the length of time a R engine runs to complete a task before failing with a timeout error. You can also specify the length of time for a R session to exist. - File size upload limit
When planning for uploading files for the Spotfire Service for R, you can set the file size limit for uploading using the properties setting for the Spring Boot framework. If you change this setting, consider how the file size might affect the speed at which files can be uploaded. - Logging level
By default, the logging level is set for the Spotfire Service for R to provide informational progress. - Manage Java options
You can set certain Java command-line options for the Spotfire Service for R for managing such settings as the Java heap size. - Package library location
You can set the location of packages that R can use in the Spotfire Service for R configuration settings. - R engine location
You can set the absolute path to the R engine that the Spotfire Service for R can use. - Safeguarding your environment
This custom property setting helps minimize the risk of malicious acts in your environment. - Startup script
You can specify a script to run before a container or R engine is started. - engine ports
R engines running under the Spotfire Service for R require open ports to communicate. The first available port, and the range to the last available port, are determined by these two settings. - JMX monitoring
You can use an installation of Java Management Extensions (JMX) and the Remote Method Invocation (RMI) connector to monitor the Spotfire Service for R. - Containerized configuration
The Spotfire Service for R provides custom properties that are specific to the Linux operating system.
- Allowed engines
You can specify the number of R engines that can run concurrently, and the number of R engines that are allocated in the Spotfire Service for R queue. - Compressed job contents and results
You can compress large data sets sent to R. You can also compress returned results for R data functions that are then sent to the Spotfire Service for R. - Docker container built for no internet access
If you are deploying a Spotfire Service for R to use in a system with no internet access, you must configure the container image so that it does not try to build an image on top of the one that you have initially built in a system with internet access. - Engine pruning
When the Spotfire Service for R reaches a certain percentage of capacity of usage, then the Spotfire Service for R begins pruning R engines to free service resources. - Engine timeout
You can specify the length of time a R engine runs to complete a task before failing with a timeout error. You can also specify the length of time for a R session to exist. - File size upload limit
When planning for uploading files for the Spotfire Service for R, you can set the file size limit for uploading using the properties setting for the Spring Boot framework. If you change this setting, consider how the file size might affect the speed at which files can be uploaded. - Logging level
By default, the logging level is set for the Spotfire Service for R to provide informational progress. - Manage Java options
You can set certain Java command-line options for the Spotfire Service for R for managing such settings as the Java heap size. - Package library location
You can set the location of packages that R can use in the Spotfire Service for R configuration settings. - R engine location
You can set the absolute path to the R engine that the Spotfire Service for R can use. - Safeguarding your environment
This custom property setting helps minimize the risk of malicious acts in your environment. - Startup script
You can specify a script to run before a container or R engine is started. - engine ports
R engines running under the Spotfire Service for R require open ports to communicate. The first available port, and the range to the last available port, are determined by these two settings. - JMX monitoring
You can use an installation of Java Management Extensions (JMX) and the Remote Method Invocation (RMI) connector to monitor the Spotfire Service for R. - Containerized configuration
The Spotfire Service for R provides custom properties that are specific to the Linux operating system.
Parent topic: Configuring the Service