Changes
</gallery>
== Bindings ==
</gallery>
== Configuring content compression ==Web service responses can be compressed in order to improve performance and reduce web traffic. This can be easily done from the web server side in IIS manager.{{Hint|In case the compression modules are not yet installed, please refer to [[Categoryhttps:How-To|Configure Microsoft IIS for UBIK//www.iis.net/configreference/system.webserver/httpcompression?showTreeNavigation=true this]]for instructions.}}[[Category<gallery widths="400" heights="300" >File:InstallingHowTo_IIS_Compression_01.png|Configure Microsoft IIS 1 - Entries for UBIK]]compression settings[[CategoryFile:Web serviceHowTo_IIS_Compression_02.png|2 - Enable compression in generalFile:HowTo_IIS_Compression_03.png|3 - Configure Microsoft IIS for what & when to compressFile:HowTo_IIS_Compression_04.png|4 - Configure what to compress</gallery>* It is possible to configure when to compress service responses like shown in Figure.3. The "dynamicCompressionDisableCpuUsage" tells the service to stop compressing when the CPU load reaches above 90%; And the "dynamicCompressionEnableCpuUsage" tells the service to start compressing when the CPU load drops below 50%. These parameters should work well in most cases but can be modified if necessary;* {{UBIK}} service responses are in formats of either "text/xml"(text/*) or "application/json". So just make sure they are configured to be compressed like shown in Figure.4. If there are no such entries, just right click and add them accordingly;* There are 10 different levels of compression, ranging from 0~9 where 9 is most CPU intensive but produces the best compress rate. The default level is 0 and this can be changed (e.g. to level 9) with the following command: C:\Windows\System32\Inetsrv\Appcmd.exe set config -section:httpCompression -[name='gzip']].dynamicCompressionLevel:9<gallery widths="700" heights="140" >File:HowTo_IIS_Compression_05.png|5 - Change compression levels</gallery>Here are some test results of the transferred content size and duration under different compression levels. {| class="wikitable" | width = "50%" | style="text-align:right;"|-! style="text-align:right;"| Compression Level !! style="text-align:right;"| Meta Definitions !! style="text-align:right;"| One Content Level !! style="text-align:right;"| Branch Download|-| Level 0|| 4,732,058 bytes || 23,470 bytes || 318,847,597 bytes (9 minutes)|-| Level 4|| 3,050,115 bytes || 7,915 bytes || 79,384,336 bytes (5 minutes)|-| Level 9|| 2,851,318 bytes || 5,681 bytes || 48,037,714 bytes (4 minutes)|-|} Ideally, one should always use level 9. However, if the server is not powerful enough and is already struggling with high CPU load without compression, one can use some lower compression level. In a lot of cases, level 4 offers a good leverage.
== Create new Web Application ==
</gallery>
== Additional prerequisites ==
