MicroStrategy ONE
Intelligence Server Configuration Editor
To set the following governors in the Intelligence Server Configuration Editor, right-click the project source, select Configure MicroStrategy Intelligence Server, then select the category as described below.
Only the categories and settings in the Intelligence Server Configuration Editor that affect system scalability are described below. Other categories and settings that appear in the Intelligence Server Configuration Editor are described elsewhere in this guide, and in the Help for the edito
Server definition: General category in Intelligence Server configuration
Governor |
Description |
See page |
Number of network threads |
Controls the number of network connections available for communication between Intelligence Server and the client, such as Developer or MicroStrategy Web. |
Server definition: Advanced category in Intelligence Server configuration
Governor |
Description |
See page |
Backup frequency (minutes) |
Controls the frequency (in minutes) at which cache and History List messages are backed up to disk. A value of 0 means that cache and history messages are backed up immediately after they are created. |
|
Balance MicroStrategy Server threads |
Controls whether threads in Intelligence Server are allocated to processes such as object serving, element serving, SQL generation, and so on that need them most, while processes with lighter loads can return threads to the available pool. |
|
Cache lookup cleanup frequency (sec) |
Cleans up the cache lookup table at the specified frequency (in seconds). This reduces the amount of memory the cache lookup table consumes and the time Intelligence Server takes to back up the lookup table to disk. |
|
Project failover latency (min.) |
The amount of time (the delay) before the project is loaded on another server to maintain minimum level availability. |
|
Configuration recovery latency (min.) |
When the conditions that caused a project failover disappear, the failover configuration reverts automatically to the original configuration. This setting is the amount of time (the delay) before the failover configuration reverts to the original configuration. |
|
Enable performance monitoring |
Configures additional MicroStrategy-specific monitors in Windows Performance Monitor. |
|
Scheduler session time out (sec) | Controls how long the Scheduler attempts to communicate with Intelligence Server before timing out. By default, this is set to 300 seconds. |
Governing Rules: Default: General category in Intelligence Server configuration
Governor |
Description |
See page |
Maximum number of jobs |
The maximum concurrent number of jobs that can exist on an Intelligence Server. |
|
Maximum number of interactive jobs |
Limits the number of concurrent interactive (nonscheduled) jobs that can exist on this Intelligence Server. A value of -1 indicates no limit. |
|
Maximum number of scheduled jobs |
Limits the number of concurrent scheduled jobs that can exist on this Intelligence Server. A value of -1 indicates no limit. |
|
Maximum number of user sessions |
The maximum number of user sessions (connections) for an Intelligence Server. A single user account may establish multiple sessions to an Intelligence Server. |
|
User session idle time (sec) |
The time allowed for a Developer user to remain idle before their session is ended. A user session is considered idle when it submits no requests to Intelligence Server. |
|
Web user session idle time (sec) |
The time allowed for a Web user to remain idle before their session is ended. If designers will be building Report Services documents and dashboards in MicroStrategy Web, set the Web user session idle time (sec) to 3600 to avoid a project source timeout. |
|
For Intelligence Server and history list governing, exclude reports embedded in Report Services documents from the counts |
Do not include reports submitted as part of a document in the count of jobs for the job limits. |
|
Background Execution: Enable background execution of documents after their caches are hit. |
If selected, when a document cache is hit, Intelligence Server displays the cached document and re-executes the document in the background. If this option is cleared, when a document cache is hit, Intelligence Server displays the cached document and does not re-execute the document until a manipulation is performed. By default this option is cleared. |
|
Mobile APNS and GMC session idle time (sec) | Limits the time, in seconds, that mobile client connections remain open to download Newsstand subscriptions. A value of -1 indicates no limit. By default, this is set to 1800. |
Governing Rules: Default: File Generation category in Intelligence Server configuration
Governor |
Description |
See page |
XML Generation: Maximum number of XML cells |
The maximum number of XML cells in a report result set that Intelligence Server can send to the MicroStrategy Web products at a time. When this limit is reached, the user sees an error message along with the partial result set. The user can incrementally fetch the remaining cells. |
|
XML Generation: Maximum number of XML drill paths |
The maximum number of attribute elements that users can see in the drill across menu in MicroStrategy Web products. If this setting is set too low, the user does not see all the available drill attributes. |
|
XML Generation: Maximum memory consumption for XML (MB) |
The maximum amount of memory (in megabytes) that Intelligence Server can use to generate a report or document in XML. If this limit is reached, the XML document is not generated and the user sees an error message. |
|
PDF Generation: Maximum memory consumption for PDF files (MB) |
The maximum amount of memory (in megabytes) that Intelligence Server can use to generate a report or document in PDF. If this limit is reached, the PDF document is not generated and the user sees an error message. |
|
Excel Generation: Maximum memory consumption for Excel files (MB) |
The maximum amount of memory (in megabytes) that Intelligence Server can use to generate a report or document in Excel. If this limit is reached, the Excel document is not generated and the user sees an error message. |
|
HTML Generation: Maximum memory consumption for HTML files (MB) |
The maximum amount of memory (in megabytes) that Intelligence Server can use to generate a report or document in HTML. If this limit is reached, the HTML document is not generated and the user sees an error message. |
Governing Rules: Default: Memory Settings category in Intelligence Server configuration
Governor |
Description |
See page |
Enable Web request job throttling |
A check box that enables the following governors: Maximum Intelligence Server use of total memory Minimum machine free physical memory |
Governing Memory for Requests from MicroStrategy Web Products |
Maximum Intelligence Server use of total memory (%) |
The maximum amount of total system memory (RAM + Page File) that can be used by the Intelligence Server process ( |
Governing Memory for Requests from MicroStrategy Web Products |
Minimum machine free physical memory (%) |
The minimum amount of physical memory (RAM) that needs to be available, as a percentage of the total amount of physical memory on the machine. If the limit is met, all requests from MicroStrategy Web products (for example, log in, report execution, search, folder browsing) are denied until the conditions are resolved. |
Governing Memory for Requests from MicroStrategy Web Products |
Enable single memory allocation governing |
A check box that enables the Maximum single allocation size governor. |
Governing Intelligence Server Memory Use with Memory Contract Manager |
Maximum single allocation size (MBytes) |
Prevents Intelligence Server from granting a request that would exceed this limit. |
Governing Intelligence Server Memory Use with Memory Contract Manager |
Enable memory contract management |
A check box that enables the following governors: Minimum reserved memory (MB or %) Maximum use of virtual address space (%) Memory request idle time |
Governing Intelligence Server Memory Use with Memory Contract Manager |
Minimum reserved memory (MBytes or %) |
The amount of system memory, in either MB or a percent, that must be reserved for processes external to Intelligence Server. |
Governing Intelligence Server Memory Use with Memory Contract Manager |
Maximum use of virtual address space (%) |
The maximum percent of the process' virtual address space that Intelligence Server can use before entering memory request idle mode. This setting is used in 32-bit operating systems and is no longer applicable. In 64-bit operating systems, to control the amount of memory available for Intelligence Server, use the Minimum reserved memory governor. |
Governing Intelligence Server Memory Use with Memory Contract Manager |
Memory request idle time (sec) |
The amount of time Intelligence Server denies requests that may result in memory depletion. If Intelligence Server does not return to acceptable memory conditions before the idle time is reached, Intelligence Server shuts down and restarts. |
Governing Intelligence Server Memory Use with Memory Contract Manager |
Temporary Storage Setting: Maximum RAM for Working Set cache (MB) |
The maximum amount of memory that can be used for report instances referenced by messages in the Working Set. |
Governing Rules: Default: Temporary Storage Settings category in Intelligence Server configuration
Governor |
Description |
See page |
Working Set file directory |
The location where the user's active working sets are written to disk if they have been forced out of the pool of memory allocated for the Maximum RAM for working set cache. The default is .\TmpPool |
|
Session Recovery and Deferred Inbox storage directory |
Specifies the where the session information is written to disk. The default is .\TmpPool |
|
Enable Web User Session Recovery on Logout |
If selected, allows Web users to recover their sessions. |
|
Session Recovery backup expiration (hrs) |
How many hours a session backup can remain on disk before it is considered expired. After it is expired, the user cannot recover the session. |
Governing Rules: Default: Import Data category in Intelligence Server configuration
Governor |
Description |
See page |
Number of connections by priority |
The number of connection threads to create for Import Data jobs, depending on whether the priority of the job is high, medium or low. You must determine the number of threads that quickly serves users without overloading the system. |
Governing Rules: Default: Catalog cache category in Intelligence Server configuration
Governor |
Description |
See page |
Enable catalog cache |
A check box that enables the Maximum use of memory (MB) governor. |
|
Maximum use of memory (MB) |
Limits the maximum amount of memory, in megabytes, used by the catalog cache. The default value is 25 MB |
|
History Settings: General category in Intelligence Server configuration
Governor |
Description |
See page |
Maximum number of messages per user |
The maximum number of History messages that can exist in a user's History List at any time. When the limit is reached, the oldest message is removed. |
|
Message lifetime (days) |
The length of time before a History List message expires and is automatically deleted. A value of -1 indicates that messages do not expire. |
|
Repository type |
Select File Based for History List messages to be stored on disk in a file system, or Database Based for History List messages to be stored in a database (recommended). |