MicroStrategy - Install Config


When deploying a project to a clustered environment, do we need to deploy the project to each Intelligent Server?

Symmetrical clustering is when all the nodes in the cluster contain all the projects. Asymmetrical clustering is when projects are only loaded onto one node of the cluster. If you are using Symmetrical then the project needs to be loaded into both nodes.

Check the Intelligence Server Configuration > Projects > General option and see which checkboxes are checked. If any of the projects are set to only load on one server during startup then you know that you are using Asymmetrical clustering.

How can I figure out if our clustered environment is configured appropriately?

Here is a simple test that you can do to verify the cluster:

  1. From Node A, send a report to History List
  2. Log into Node B and see the same message appear here as well
  3. From Node B, request the result of the above message
  4. If results are retrieved, then the setup is correct
  • TN6022 - MicroStrategy Intelligence Server Cluster Configuration Guide
  • TN 30728 - MicroStrategy Intelligence Server Cluster Failover Guide
  • TN 14607 - How to set up clustered Cache and Inbox sharing for the MicroStrategy Intelligence Server Universal
  • TN16018 - MicroStrategy Intelligence Server Clustering FAQ

Where is the trusted authentication token file?

MicroStrategy/WEB-INF/xml/<I-server Name>.token

How to configure trust relationship between MSTR Web and Intelligence Server?

  1. Go to MicroStrategy/servlet/mstrWebAdmin
  2. Click on the first icon (the one that has the Modify tooltip when you mouse over it) under the Properties column on the far right.
  3. Click on the Setup button
  4. Provide the username and password for the MicroStrategy administrator account
  5. Select the Standard username & password radio button
  6. Specify appropriate value for Web Server Application
  7. Click the Create Trust Relationship button.
  8. If the Intelligence Servers will be clustered, look for the .token file (MicroStrategy/WEB-INF/xml/<I-server Name>.token), copy this file, and rename the copy using appropriate machine name for the other Intelligence Servers.
  9. If you have multiple web servers, copy this set of .token file to the other web servers.
  10. Check each Intelligence Server:
    1. Launch the Intelligence Server Configuration Editor
    2. Drill down on Web SSO -> Configuration on the left hand side
    3. Verify that the URL is displayed on the right hand side, and the status column (on the right hand side, next to the URL) is set to Enabled. If this is set to Disabled, you can click on it and change it to Enabled.
    4. Go back to the MicroStrategy Web Administrator page, the user should edit the Intelligence Server connection properties and enable Trusted Authentication Request as a Login Mode and make it the default authentication method (If this is required only - trusted authentication could be used without making it the default authentication mechanism)

In a non-clustered environment, a trust token is generated to uniquely identify a trusted web server. This trust token is stored in the metadata on Intelligence Server side. The web server stores the token for the Intelligence Server in a token file, called ".token" under the MicroStrategy Web Services root deployment directory.

As outlined in technical note TN41359, a session with Intelligence Server must be established before a trust relationship can be created through the MicroStrategy Office configuration interface. The reason for this being the need to write the token into the metadata.

In a clustered environment, this initial session to create a trust relationship is established on any of the Intelligence Server nodes thanks to Intelligence Server load balancing. Therefore, when creating the trust relationship the token file will be named according to the Intelligence Server of the current session.

For example, when creating an initial session on WS1 using Standard authentication, a MicroStrategy session was created on Intelligence Server node 2 (I-SERVER_2). When creating the trust relationship through MIcroStrategy Office, the token for WS1 will be written into the common metadata for both Intelligence Server nodes. However, the token file created on the web server will be named I-SERVER_2.token.

As a consequence, when attempting to create a session using trusted authentication and this session goes to Intelligence Server 1 (I-SERVER_1) no valid token file will be found. Thus it is required to copy the .token file on the web server and rename the copy to reflect the machine name of the other Intelligence Server node(s). Since each Intelligence Server node runs on the same metadata database, the token file content is identical for all Intelligence Server nodes.

What is MicroStrategy Transaction Services?

MicroStrategy Transaction Services is an Intelligence Server extension that lets you embed write-back functionality into reports and dashboards for the purposes of decision-making or initiating a transaction. These transactions can include one-click approvals and denials, notes for tracking and directing business activity, and write-back to data sources in real time.

Users of MicroStrategy Web, MicroStrategy Mobile for iPhone, and MicroStrategy Mobile for iPad can employ these transaction capabilities from reports, dashboards, and MicroStrategy Mobile applications.

What is the MicroStrategy MultiSource Option?

MicroStrategy includes an extension to Intelligence Server referred to as MultiSource Option. With this feature, you can connect a project to multiple relational data sources. This allows you to integrate all your information from various databases and other relational data sources into a single MicroStrategy project for reporting and analysis purpose. All data sources included using the MultiSource Option are integrated as part of the same relational schema for a project.

What is MicroStrategy GIS Connectors?

MicroStrategy Geospatial Information System (GIS) Connectors let you integrate with ESRI to create sophisticated GIS applications. GIS lets business users visualize data in forms such as maps, globes, reports, and charts so that they can identify and analyze relationships, patterns, and trends in their data.

What is the RAM requirement for the Intelligence Server?

4GB or more.

The use of 4 GB of RAM is a minimum level of support for the MicroStrategy Product Suite, which does not take into account the performance of a production system. Performance testing has shown that 64 GB or more of RAM should be available to allow MicroStrategy Intelligence Server Universal to fully support and take advantage of the complete feature set of the MicroStrategy Product Suite, while obtaining system-wide high performance. This level of system resources allows MicroStrategy Intelligence Server Universal to fully utilize performance-improving technologies such as MicroStrategy OLAP Services, and to support optimal performance for MicroStrategy Report Services documents and dashboards and the other features of the MicroStrategy Product Suite.

What is the RAM requirement for MSTR Web?

4GB or more.

What is the hard disk requirement?

Three times the amount of RAM available to Intelligence Server. For example, an Intelligence Server that is provided 4 GB of RAM requires 12GB of hard drive space.

How to scale MSTR Intelligence Server?

Report caches store the results of previously executed reports. If a client (MicroStrategy Web, Developer, and so on) requests a report that is cached, Intelligence Server simply returns the cached report results to the client. For any ad hoc reports that are not cached, Intelligence Server must go through the entire report execution cycle before it can return the results. For this reason, report caching allows better response time while minimizing the load on the Intelligence Server.

The benefits of caching are more apparent for complex reports than for simple reports. While caching a complex report may significantly improve execution time, a report cache for a simple report may not make much difference in this regard.

Therefore, the more complex the ad hoc reporting is in your system, the greater the overall load on the Intelligence Server. Be sure to take this into account when sizing your Intelligence Server machine.

The process for element browsing is similar to ad hoc reporting. Element browsing takes place when you navigate through hierarchies of attribute elements, for example, viewing the list of months in the year attribute. By default, caching is enabled for element browsing. In addition, you can limit the number of elements to be retrieved at a time.

  • Employ in-memory Business Intelligence (OLAP cubes)
  • Design high performance dashboards
  • Optimize query efficiency
  • Implement effective caching strategies
  • Configure MicroStrategy for high performance

Increasing the processor speed of Intelligence Server enhances performance and reduces execution time for all analytical tasks and for requests from the Extensible Markup Language (XML) and Component Object Model (COM) application programming interfaces (APIs). If you see that the machine or machines are running consistently at a high capacity, for example, greater than 80%, it may be a sign that a faster processor would improve the system’s capacity.

Adding more processors to the Intelligence Server allows for a better load distribution among the processors. This provides an overall performance gain. If you notice that the processor is running consistently at a high capacity, for example, greater than 80%, consider increasing the number of processors.

If the physical disk is utilized too much on a machine hosting Intelligence Server, it can indicate that there is a bottleneck in the system’s performance. To monitor this on a Windows machine, use the Windows Performance Monitor for the object PhysicalDisk and the counter % Disk Time. If you see that the counter is greater than 80% on average, it may indicate that there is not enough memory on the machine.

What would more network bandwidth do for me?

You can tell whether or not your network is negatively impacting your system’s performance by monitoring how much of your network’s capacity is being used. To monitor this on a Windows machine, use the Windows Performance Monitor for the object Network Interface, and the watch the counter Total bytes/sec as a percent of your network’s bandwidth. If it is consistently greater than 60% (for example), it may indicate that the network is negatively affecting the system’s performance.

For very large result sets, increasing network bandwidth reduces bottlenecks created by network congestion. The result is larger data flow and faster query response time.

What is the advantage of using hyper-threading for a dual processor?

The advantage of using hyper-threading with a dual processor is that it decreases the overall CPU usage. The use of hyper-threading is recommended if you have a large number of users.

What is the disadvantage of using hyper-threading for a dual processor?

The disadvantage of using hyper-threading is that it increases the Intelligence Server execution time slightly. Therefore, for faster processing, the use of hyper-threading is not recommended.

What is the largest Intelligent Cube size that I can store in an Intelligence Server?

Intelligent Cubes must be stored in Intelligence Server memory for reports to access their data. While this can improve performance of these reports, loading too much data onto Intelligence Server memory can have a negative impact on Intelligence Server’s ability to process jobs. For this reason, it is important to govern how much Intelligent Cube data can be stored on the Intelligence Server.

What is the effect of logging statistics in term of performance?

Statistics logging—Statistics logging is very useful for analyzing and further refining the system configuration based on actual usage. However, logging all statistics all the time can create a noticeable increase in system response time. For this reason, you might choose to log only a subset of the statistics generated or only log statistics periodically.

What is the impact of the Backup frequency in term of performance?

Caches can be stored in memory and on disk. When you enable backup, you allow the Intelligence Server to write all cache files to disk. If the backup frequency is set to the default of zero, backup files are written to disk as soon as they are created. However, writing all cache files to disk all the time can cause a noticeable reduction in system performance. Set the backup frequency to a value that minimizes disk writes and optimizes memory usage for your system.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License