FAQs for Configuring and Tuning MicroStrategy Web Products

How can I Configure MicroStrategy Web and the Library Server for SameSite Cookie support?

Chrome Web Browser version 80 and above introduces new changes which may impact embedding. For more information, see KB484005: Chrome v80 Cookie Behavior and the Impact on MicroStrategy Deployments.

How do I Configure my MicroStrategy Web Environment if I have a User Community of x Users? How much Hardware am I Going to Need?

This information is addressed in the MicroStrategy Knowledge Base.

How do Time-Out Settings in MicroStrategy Web and Intelligence Server Affect MicroStrategy Web Users?

Several settings related to session time-out may affect MicroStrategy Web users.

First, in the Intelligence Server Configuration Editor, under Governing Rules: Default: General, the value in the Web user session idle time (sec) field determines the number of seconds a user can remain idle before being logged out of Intelligence Server.

Second, in the web.config file, located by default in C:\Program Files (x86)\MicroStrategy\Web ASPx, the time-out setting determines the number of minutes after which the .NET session object is released if it has not been accessed. This time-out is independent of the Intelligence Server time-out above.

Below is the section of the web.config file that contains the time-out setting (line 5):

1
2
3
4
5
6
<sessionStatemode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="20"
/>

This setting does not affect Web Universal because it does not use .NET architecture.

A third setting is the MicroStrategy Web Administration setting Allow automatic login if session is lost. This setting is in the Security section of the Web Administration page. It enables users to be automatically reconnected to Intelligence Server if the session is lost.

This setting does not automatically reconnect the .NET session object.

The following table demonstrates how the previous settings interact in various combinations.

A fourth group of settings is whether Web user sessions can be backed up and recovered. That is, if the user was viewing a report, document, or dashboard when the session was ended, when the user logs back in to Web, they can click a link to return to that report, document, or dashboard. If this is enabled, you can configure where and for how long the session is stored on disk. After the session is expired, the user cannot recover the session.

To configure these settings, access the Intelligence Server Configuration Editor, select the Governing Rules: Default: Temporary Storage Settingscategory. To enable the feature, select the Enable Web User Session Recovery on Logout check box, and in the Session Recovery backup expiration (hrs) field, type the number of hours you want to allow a session to be stored. In Session Recovery and Deferred Inbox storage directory, specify the folder where the user session information is stored.

How can I Tune my MicroStrategy Web Server for Best Performance?

• Clustering multiple web servers improves performance. For more information about this, see Cluster Multiple MicroStrategy Servers.
• You can modify certain settings in the MicroStrategy Web server machine or application for best performance. Details for MicroStrategy Web and Web Universal follow:

MicroStrategy Web (ASP.NET)

The most significant things you can do:

• Tune Microsoft's Internet Information Services (IIS). For details, see the MicroStrategy Tech Notes TN11275 and TN7449.
• Increase the server machine's Java Virtual Machine heap size. For information on doing this, see MicroStrategy Tech Note TN6446.

MicroStrategy Web Universal (J2EE)

Tuning actions for the J2EE version of MicroStrategy Web Universal vary according to the Web server you are using. For tuning details, see the appropriate section in the Installation and Configuration Help.

See the documentation for your particular Web application server for additional tuning information. In general, these are the things you can do:

• Use the MicroStrategy Web server instead of the application server to serve static files (such as CSS, JavaScript).
• Precompile JSPs according to the platform you are using.
• Increase the application server's Java Virtual Machine heap size.