Server settings in appsettings.json - Revision history

Ollvihe at 13:56, 31 March 2026

2026-03-31T13:56:20Z

← Older revision		Revision as of 13:56, 31 March 2026
Line 50:		Line 50:
	\|DropUnusedFiltersAfter		\|DropUnusedFiltersAfter
	\|		\|
	~~Duration~~ after which filters ~~that have not been used,~~ are dropped from the memory. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). When a calculation uses a filter, the filter's last used time is updated (also model's last used time is updated). This setting can be overridden for each model in the [[In-memory_Models_Management\|model settings]].		Specifies duration after which filters are dropped from the memory if they have not been used during that time. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). When a calculation uses a filter, the filter's last used time is updated (also model's last used time is updated). This setting can be overridden for each model in the [[In-memory_Models_Management\|model settings]].
	\|-		\|-
	\|DropUnusedAnalysisResultsAfter		\|DropUnusedAnalysisResultsAfter
	\|		\|
	~~Duration~~ after which query results (analysis results) ~~that have not been used,~~ are dropped from the memory. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours).		Specifies duration after which query results (analysis results) are dropped from the memory if they have not been used during that time. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). Default value is 00:30:00 (30 minutes).
	\|}		\|}

Ollvihe at 13:51, 31 March 2026

2026-03-31T13:51:10Z

← Older revision		Revision as of 13:51, 31 March 2026
Line 51:		Line 51:
	\|		\|
	Duration after which filters that have not been used, are dropped from the memory. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). When a calculation uses a filter, the filter's last used time is updated (also model's last used time is updated). This setting can be overridden for each model in the [[In-memory_Models_Management\|model settings]].		Duration after which filters that have not been used, are dropped from the memory. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). When a calculation uses a filter, the filter's last used time is updated (also model's last used time is updated). This setting can be overridden for each model in the [[In-memory_Models_Management\|model settings]].
			\|-
			\|DropUnusedAnalysisResultsAfter
			\|
			Duration after which query results (analysis results) that have not been used, are dropped from the memory. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours).
	\|}		\|}

Ollvihe at 23:34, 23 November 2025

2025-11-23T23:34:47Z

← Older revision		Revision as of 23:34, 23 November 2025
Line 64:		Line 64:
	\|-		\|-
	\|FirstName		\|FirstName
	\|~~Contact~~ person first name ~~(in the user organization)~~.		\|Customer contact person first name.
	\|-		\|-
	\|LastName		\|LastName
	\|~~Contact~~ person last name.		\|Customer contact person last name.
	\|-		\|-
	\|Email		\|Email
	\|~~Contact~~ person email address.		\|Customer contact person email address.
	\|-		\|-
	\|LicenseFilePath		\|LicenseFilePath
Line 76:		Line 76:
	\|-		\|-
	\|EMSAddress		\|EMSAddress
	\|Activation server address ''<nowiki>https://activation.qpr.com/</nowiki>'' that is contacted when the QPR ProcessAnalyzer Server is activated. Do not change this setting.		\|Activation server address ''<nowiki>https://activation.qpr.com</nowiki>'' that is contacted when the QPR ProcessAnalyzer Server is activated. Do not change this setting.
	\|-		\|-
	\|UseProxyServer		\|UseProxyServer
Line 85:		Line 85:
	\|-		\|-
	\|Country		\|Country
	\|~~User~~ country.		\|Customer country.
	\|-		\|-
	\|JobTitle		\|JobTitle
	\|~~Contact~~ person's job title.		\|Customer contact person job title.
	\|-		\|-
	\|PhoneNumber		\|PhoneNumber
	\|~~Contact~~ person's phone number.		\|Customer contact person phone number.
	\|-		\|-
	\|Address		\|Address
	\|~~User~~ address.		\|Customer address.
	\|-		\|-
	\|PostalCode		\|PostalCode
	\|~~User~~ postal code.		\|Customer postal code.
	\|-		\|-
	\|Region		\|Region
	\|~~User~~ region.		\|Customer region.
	\|-		\|-
	\|Organization		\|Organization
	\|~~User~~ organization.		\|Customer organization.
	\|}		\|}

Ollvihe at 23:32, 23 November 2025

2025-11-23T23:32:39Z

← Older revision		Revision as of 23:32, 23 November 2025
Line 64:		Line 64:
	\|-		\|-
	\|FirstName		\|FirstName
	\|Contact person first name (in the user organization~~) (used for QPR ProcessAnalyzer Server activation~~).		\|Contact person first name (in the user organization).
	\|-		\|-
	\|LastName		\|LastName
	\|Contact person last name ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|Contact person last name.
	\|-		\|-
	\|Email		\|Email
	\|Contact person email address ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|Contact person email address.
	\|-		\|-
	\|LicenseFilePath		\|LicenseFilePath
Line 85:		Line 85:
	\|-		\|-
	\|Country		\|Country
	\|User country ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|User country.
	\|-		\|-
	\|JobTitle		\|JobTitle
	\|Contact person's job title ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|Contact person's job title.
	\|-		\|-
	\|PhoneNumber		\|PhoneNumber
	\|Contact person's phone number ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|Contact person's phone number.
	\|-		\|-
	\|Address		\|Address
	\|User address ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|User address.
	\|-		\|-
	\|PostalCode		\|PostalCode
	\|User postal code ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|User postal code.
	\|-		\|-
	\|Region		\|Region
	\|User region ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|User region.
	\|-		\|-
	\|Organization		\|Organization
	\|User organization ~~(used for QPR ProcessAnalyzer Server activation)~~.		\|User organization.
	\|}		\|}

Ollvihe at 23:31, 23 November 2025

2025-11-23T23:31:55Z

← Older revision		Revision as of 23:31, 23 November 2025
Line 40:		Line 40:
	\|}		\|}

	Following settings are used by in-memory models:		Following settings are used by in-memory models (so these settings are not effective for Snowflake models):

	{\| class="wikitable" style="text-align: left"		{\| class="wikitable" style="text-align: left"
	!Setting		!Setting
Line 51:		Line 50:
	\|DropUnusedFiltersAfter		\|DropUnusedFiltersAfter
	\|		\|
	Duration after which filters that have not been used, are dropped from the memory. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). When a calculation uses a filter, the filter's last used time is updated (also model's last used time is updated).		Duration after which filters that have not been used, are dropped from the memory. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). When a calculation uses a filter, the filter's last used time is updated (also model's last used time is updated). This setting can be overridden for each model in the [[In-memory_Models_Management\|model settings]].

	This setting can be overridden for each model in the [[In-memory_Models_Management\|model settings]].

	~~Note that this setting doesn't concern Snowflake models~~.
	\|}		\|}

Ollvihe at 23:30, 23 November 2025

2025-11-23T23:30:42Z

← Older revision		Revision as of 23:30, 23 November 2025
Line 37:		Line 37:
	\|-		\|-
	\|UseXForwardedForAsClientIp		\|UseXForwardedForAsClientIp
	\|If QPR ProcessAnalyzer Server is running behind a web traffic load balancer (e.g. in Amazon Web Services), the following setting needs to be set to '''True'''. In that case, the client ip address is fetched from http request '''X-Forwarded-For''' (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) field instead of the source of the ip packet. Client ip address is needed for logging and as a security confirmation in addition to the session id. When there is no load balancer and thus X-Forwarded-For is not set, it's important to have this setting as '''False'''.		\|If QPR ProcessAnalyzer Server is running behind a web traffic load balancer (e.g. in Amazon Web Services), the following setting needs to be set to ''True''. In that case, the client ip address is fetched from http request ''X-Forwarded-For'' (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) field instead of the source of the ip packet. Client ip address is needed for logging and as a security confirmation in addition to the session id. When there is no load balancer and thus X-Forwarded-For is not set, it's important to have this setting as ''False''.
	\|}		\|}

Ollvihe at 23:29, 23 November 2025

2025-11-23T23:29:55Z

← Older revision		Revision as of 23:29, 23 November 2025
Line 57:		Line 57:
	Note that this setting doesn't concern Snowflake models.		Note that this setting doesn't concern Snowflake models.
	\|}		\|}
	¨

	Following settings are for the product activation:		Following settings are for the product activation:

Ollvihe at 23:29, 23 November 2025

2025-11-23T23:29:44Z

← Older revision		Revision as of 23:29, 23 November 2025
Line 39:		Line 39:
	\|If QPR ProcessAnalyzer Server is running behind a web traffic load balancer (e.g. in Amazon Web Services), the following setting needs to be set to '''True'''. In that case, the client ip address is fetched from http request '''X-Forwarded-For''' (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) field instead of the source of the ip packet. Client ip address is needed for logging and as a security confirmation in addition to the session id. When there is no load balancer and thus X-Forwarded-For is not set, it's important to have this setting as '''False'''.		\|If QPR ProcessAnalyzer Server is running behind a web traffic load balancer (e.g. in Amazon Web Services), the following setting needs to be set to '''True'''. In that case, the client ip address is fetched from http request '''X-Forwarded-For''' (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) field instead of the source of the ip packet. Client ip address is needed for logging and as a security confirmation in addition to the session id. When there is no load balancer and thus X-Forwarded-For is not set, it's important to have this setting as '''False'''.
	\|}		\|}
	¨
	Following settings are used by in-memory models:		Following settings are used by in-memory models:

Ollvihe at 23:29, 23 November 2025

2025-11-23T23:29:24Z

← Older revision		Revision as of 23:29, 23 November 2025
Line 38:		Line 38:
	\|UseXForwardedForAsClientIp		\|UseXForwardedForAsClientIp
	\|If QPR ProcessAnalyzer Server is running behind a web traffic load balancer (e.g. in Amazon Web Services), the following setting needs to be set to '''True'''. In that case, the client ip address is fetched from http request '''X-Forwarded-For''' (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) field instead of the source of the ip packet. Client ip address is needed for logging and as a security confirmation in addition to the session id. When there is no load balancer and thus X-Forwarded-For is not set, it's important to have this setting as '''False'''.		\|If QPR ProcessAnalyzer Server is running behind a web traffic load balancer (e.g. in Amazon Web Services), the following setting needs to be set to '''True'''. In that case, the client ip address is fetched from http request '''X-Forwarded-For''' (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) field instead of the source of the ip packet. Client ip address is needed for logging and as a security confirmation in addition to the session id. When there is no load balancer and thus X-Forwarded-For is not set, it's important to have this setting as '''False'''.
			\|}
			¨
			Following settings are used by in-memory models:

			{\| class="wikitable" style="text-align: left"
			!Setting
			!Description
	\|-		\|-
	\|ModelLoadOnStartup		\|ModelLoadOnStartup
Line 50:		Line 57:
	Note that this setting doesn't concern Snowflake models.		Note that this setting doesn't concern Snowflake models.
	\|}		\|}
			¨

	Following settings are for the product activation:		Following settings are for the product activation:

Ollvihe at 23:28, 23 November 2025

2025-11-23T23:28:10Z

← Older revision		Revision as of 23:28, 23 November 2025
Line 41:		Line 41:
	\|ModelLoadOnStartup		\|ModelLoadOnStartup
	\|Whether in-memory models having setting ''LoadOnStartup'' as '''true''' are loaded automatically during the server startup. By default, this setting should be set to '''True'''. This setting can be used to temporarily disable automatic model loading for all models when for example automatic model loading causes issues.		\|Whether in-memory models having setting ''LoadOnStartup'' as '''true''' are loaded automatically during the server startup. By default, this setting should be set to '''True'''. This setting can be used to temporarily disable automatic model loading for all models when for example automatic model loading causes issues.
	\|-
	~~\|ResponsePollingInterval~~
	\|Time (in milliseconds) after which pending requests return with an exception, and the request continues to run in the QPR ProcessAnalyzer Server. This behavior is needed by QPR ScriptLauncher which will then make a further request to query the progress of the task. Note that the UI doesn't support this behavior, so set the limit large enough so that it's not exceeded in normal usage, e.g. 10 minutes (600000 ms). The default values is 10 minutes. NOTE: This is a legacy setting which will be removed in future.
	\|-		\|-
	\|DropUnusedFiltersAfter		\|DropUnusedFiltersAfter