Integration/Tutorials/Customizing-Izenda-Settings.md
... ...
@@ -106,4 +106,22 @@ In general, most custom code will be placed in the **Global.asax** file. Custom
106 106
107 107
##What if my global.asax is already integrated or I cannot use it?
108 108
109
-In the case that you will not be using the **global.asax** file or that you are using a different **global.asax** than Izenda's, you can set the license key at the start of the user's session to obtain the same result. You will need to make sure that you set the license key before invoking any of the configuration methods or settings in Izenda Reports.
... ...
\ No newline at end of file
0
+In the case that you will not be using the **global.asax** file or that you are using a different **global.asax** than Izenda's, you can set the license key at the start of the user's session to obtain the same result. You will need to make sure that you set the license key before invoking any of the configuration methods or settings in Izenda Reports.
1
+
2
+##Web Farms/Gardens/Clusters/Load Balancers/Clouds/Azure
3
+
4
+You can use the following steps to allow proper operation of Izenda Reports on distributed cloud computing systems:
5
+
6
+1. Call the ``InitializeReporting()`` method from the OnPreInit() method of all pages that utilize the Izenda API except for rs.aspx. by default, the demo site already uses this configuration.
7
+2. Enable shared state management by setting the mode attribute of sessionstate to "sqlserver" or "stateserver" in the web.config file. Following is an example web.config showing where to place this option.
8
+
9
+```html
10
+<configuration>
11
+ <system.web>
12
+ <sessionState mode="StateServer"
13
+ stateConnectionString="tcpip=SampleStateServer:42424"
14
+ cookieless="false"
15
+ timeout="20"/>
16
+ </system.web>
17
+</configuration>
18
+```
... ...
\ No newline at end of file