Sometime we come across to a situation where we have to change the setting of our project or Intelligence server. But we really do not know for which type of setting we first have to restart the server then only setting may be effected .
Today I'm found some of the settings that requires the I-server restart , in order for the changes to take effect.
1. Server Definition
2. For project level settings that require a server restart, unloading and then reloading a project will not make project-level setting changes take effect.
Today I'm found some of the settings that requires the I-server restart , in order for the changes to take effect.
Here are the list of services/setting that require MicroStrategy
Intelligence Server to be restarted whenever we have changed the settings.
In order to effect the changes to the I-server we always
have to first restart it .
Server Level Setting
At the server level, below are the settings from each
category.1. Server Definition
a. General
1. Number of network
threads
2. Content Server
Location Database Instance
b. Advanced
1. Backup Frequency
2. Cache lookup
cleanup frequency (minutes)
3. Time to run license
check (24 hr format)
4. Use MicroStrategy
Scheduler
5. Scheduler session
time out
6. Enable Performance
Monitoring
2. Statistics
1.
General
1. Complete Session
Logging
2. Single Instance
Session Logging
3. Single Instance
Session Logging Project Selection
3. Governing
0.
Default
1. General
1. User session idle
time
2. Web user session
idle time
2. Memory Settings
1. Enable Web request
job throttling
2. Maximum
Intelligence Server use of total memory
3. Minimum machine
free physical memory
4. Enable single
memory allocation governing
5. Maximum single
allocation size
6. Enable memory
contract management
7. Minimum reserved
memory (Mbytes)
8. Minimum reserved
memory (%)
9. Maximum use of
virtual address space
10. Memory request idle
time (sec)
3. Working Set
1. Working Set file
directory
2. Maximum RAM for
working set cache (*Please see Note 1)
4. Projects
.
General
1. Apply startup
configuration on save (* Please see Note 3)
5. History Settings
0. General
1. Maximum number of
messages per user
2. Repository Type
(Switch from File to Database Based)
3. History Directory
4. Database Instance
Important Notes :
1. Increasing the
'Maximum RAM for Working Set cache' setting does not require MicroStrategy
Intelligence Server to be restarted. Only when the value is to be decreased is
a restart required. This also applies to 'Maximum RAM usage' as well as
'Maximum number of caches' settings. Actually Maximum no. of caches setting is
used to limit the number of report caches including Matching,History,XML and
Matching History cache allowed in project at one time. The default value is
10,000. Any reduction in the value requires server restart because when we
reduce this and if a job is currently running , it will affect that process but if increase this
value then its just allows us for more caches so it will not affect any jobs
that may currently running .
2. When a setting is
not a runtime setting, MicroStrategy Desktop prompts users to restart
MicroStrategy Intelligence Server 9.x to effectively register the change.
3. Apply start-up
configuration on save: This option allows changes to be reflected immediately
across the cluster. If the check box is cleared, changes are saved on clicking
OK, but are not put into effect until Intelligence Server is restarted.
Project-level settings
Only a few settings that require a server restart so that
changes apply to server.
1. Database instances
1. Statistics
1. Statistics database
instance
2. Caching
a. Result Caches
1. Cache File
Directory
2. Cache encryption
level on disk
3. Maximum RAM Usage
(For both Datasets and Formatted Documents)
4. Maximum number of
caches (For both Datasets and Formatted Documents)
5. RAM swap multiplier
6. Maximum RAM for
report cache index
b. Auxiliary Caches
1. Objects
1. Server ->
Maximum RAM usage
2. Element cache
1. Server ->
Maximum RAM usage
2. Create element
caches per passthrough login
3. Create caches per
connection map
3. Intelligent Cubes
0. General
1. Intelligent Cube
file directory
2. Maximum RAM usage
3. Maximum number of
cubes
4. Create Intelligent
Cubes by database connection
5. Load Intelligent
Cubes on startup
6. Enabling or
modifying Dynamic Sourcing options
4. Security filter
1. General
1. Creation of a security filter
1. General
1. Creation of a security filter
Important Notes
:
1.
Changes to a database instance or database
connection do not require a restart of MicroStrategy Intelligence Server .
However, for any new settings to take
effect, all cached connections (appearing in the Database Connection Monitor)
must be disconnected. After a setting change, any cached database connections
will continue to use the old settings.2. For project level settings that require a server restart, unloading and then reloading a project will not make project-level setting changes take effect.
Comments