Custom configuration properties You can fine tune the behavior of the TERR service by setting custom configuration properties. Child Topics:Allowed engines You can specify the number of TERR engines that can run concurrently, and the number of TERR engines that are allocated in the TERR service queue. Engine pruning When the TERR service reaches a certain percentage of capacity of usage, then the TERR service begins pruning TERR engines to free service resources. Engine connection timeout You can specify the length of time a TERR engine takes to connect to a service.Engine timeout You can specify the length of time a TERR engine runs to complete a task before failing with a timeout error. You can also specify the length of time for a TERR session to exist. File size upload limit When planning for uploading files for the TERR service, 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 TERR service to provide informational progress. Manage Java options You can set certain Java command-line options for the TERR service for managing such settings as the Java heap size. Package library location You can set the location of packages that TERR can use in the TERR service configuration settings. 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 TERR engine is started. TERR engine ports TERR engines running under the TERR service require open ports to communicate. The first available port, and range to the last available port are determined by these two settings. (The defaults specify a range of 61000 to 62000.) JMX monitoring You can use an installation of Java Management Extensions (JMX) and the Remote Method Invocation (RMI) connector to monitor the TERR service. Containerized configuration The TERR service provides custom properties that are specific to the Linux operating system. Allowed engines You can specify the number of TERR engines that can run concurrently, and the number of TERR engines that are allocated in the TERR service queue. Engine pruning When the TERR service reaches a certain percentage of capacity of usage, then the TERR service begins pruning TERR engines to free service resources. Engine connection timeout You can specify the length of time a TERR engine takes to connect to a service.Engine timeout You can specify the length of time a TERR engine runs to complete a task before failing with a timeout error. You can also specify the length of time for a TERR session to exist. File size upload limit When planning for uploading files for the TERR service, 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 TERR service to provide informational progress. Manage Java options You can set certain Java command-line options for the TERR service for managing such settings as the Java heap size. Package library location You can set the location of packages that TERR can use in the TERR service configuration settings. 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 TERR engine is started. TERR engine ports TERR engines running under the TERR service require open ports to communicate. The first available port, and range to the last available port are determined by these two settings. (The defaults specify a range of 61000 to 62000.) JMX monitoring You can use an installation of Java Management Extensions (JMX) and the Remote Method Invocation (RMI) connector to monitor the TERR service. Containerized configuration The TERR service provides custom properties that are specific to the Linux operating system. Parent topic: Configuring the TERR serviceHomeConfiguring the TERR service Custom configuration properties
Custom configuration properties You can fine tune the behavior of the TERR service by setting custom configuration properties. Child Topics:Allowed engines You can specify the number of TERR engines that can run concurrently, and the number of TERR engines that are allocated in the TERR service queue. Engine pruning When the TERR service reaches a certain percentage of capacity of usage, then the TERR service begins pruning TERR engines to free service resources. Engine connection timeout You can specify the length of time a TERR engine takes to connect to a service.Engine timeout You can specify the length of time a TERR engine runs to complete a task before failing with a timeout error. You can also specify the length of time for a TERR session to exist. File size upload limit When planning for uploading files for the TERR service, 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 TERR service to provide informational progress. Manage Java options You can set certain Java command-line options for the TERR service for managing such settings as the Java heap size. Package library location You can set the location of packages that TERR can use in the TERR service configuration settings. 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 TERR engine is started. TERR engine ports TERR engines running under the TERR service require open ports to communicate. The first available port, and range to the last available port are determined by these two settings. (The defaults specify a range of 61000 to 62000.) JMX monitoring You can use an installation of Java Management Extensions (JMX) and the Remote Method Invocation (RMI) connector to monitor the TERR service. Containerized configuration The TERR service provides custom properties that are specific to the Linux operating system. Allowed engines You can specify the number of TERR engines that can run concurrently, and the number of TERR engines that are allocated in the TERR service queue. Engine pruning When the TERR service reaches a certain percentage of capacity of usage, then the TERR service begins pruning TERR engines to free service resources. Engine connection timeout You can specify the length of time a TERR engine takes to connect to a service.Engine timeout You can specify the length of time a TERR engine runs to complete a task before failing with a timeout error. You can also specify the length of time for a TERR session to exist. File size upload limit When planning for uploading files for the TERR service, 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 TERR service to provide informational progress. Manage Java options You can set certain Java command-line options for the TERR service for managing such settings as the Java heap size. Package library location You can set the location of packages that TERR can use in the TERR service configuration settings. 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 TERR engine is started. TERR engine ports TERR engines running under the TERR service require open ports to communicate. The first available port, and range to the last available port are determined by these two settings. (The defaults specify a range of 61000 to 62000.) JMX monitoring You can use an installation of Java Management Extensions (JMX) and the Remote Method Invocation (RMI) connector to monitor the TERR service. Containerized configuration The TERR service provides custom properties that are specific to the Linux operating system. Parent topic: Configuring the TERR serviceHomeConfiguring the TERR service Custom configuration properties