EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB16333: How to enable HTTP compression under Apache Tomcat in MicroStrategy Web Universal


Community Admin

• Strategy


System administrators may want to enable Hypertext Transfer Protocol (HTTP) Compression (Gzip) on their Apache Tomcat HTTP Connectors.

System administrators may want to enable Hypertext Transfer Protocol (HTTP) Compression (Gzip) on their Apache Tomcat HTTP Connectors. With HTTP compression, users can limit the amount of bandwidth distributed between the Strategy Web Server and the Strategy Web client machine. In particular, system administrators may wish to enable HTTP compression if the connection speed between the Strategy Web server and the client machine is particularly slow. With HTTP compression, the web files are compressed before they are shipped over the Internet. Once the files reach the client's machine, they are decompressed by the client's machine.
 
However, there are a few disadvantages to using file compression. First, the Web Server (Tomcat) will spend CPU time to compress the files before they are sent. Second, the client machine will spend time decompressing the files. In general, these two factors will not greatly impact the system because the amount of CPU time required is fairly low and since most current web browsers are designed to account for file compression.
 
Enabling HTTP Compression

  1. Open the server.xml file under TOMCAT_HOME/conf/server.xml
  2. Locate the HTTP connector (e.g. HTTP, HTTPS) that will have compression enabled and aggregate the value to the Connector node. The example below enables compression for the non-SSL HTTP connector on port 8080:
    <Connector port="8080" maxHttpHeaderSize="8192"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" redirectPort="7552" acceptCount="100"
    connectionTimeout="20000" disableUploadTimeout="true"
    compression="on" />
  3. Save the changes and restart Tomcat.

Note: For more information about the Tomcat HTTP Connector and what options there are regarding compression, refer to the Apache Tomcat Configuration Reference:
https://tomcat.apache.org/tomcat-7.0-doc/config/http.html
Additionally, this issue may persists in 10.4.8. If this is the case, please upgrade to Strategy 2019 or later.
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

December 2, 2019