--- title: "Info360.ini File Configuration" canonical: "https://help.innovyze.com/space/info360/15008190/Info360.ini%20File%20Configuration" format: markdown --- Info360 has several hidden server settings that can be controlled by the Info360.ini file. This file is located in the folder where Info360 is installed, which by default is C:\inetpub\wwwroot\Info360 Note: In version 6.4 and later, the file exists in the ..\Config\ subdirectory. The following sections outline the options that can be controlled from the Info360.ini file. > ⚠️ **Notice:** > ⚠️ > ⚠️ In order for any changes made to the Info360.ini file to take effect on the server, Windows IIS must be restarted on the machine that hosts Info360. ## Control Sections ### Info360Database
More information about this feature The fields in this section define the connection information to the Info360 database. | **Setting** | **Example Values** | **Description** | | --- | --- | --- | | ServerName | INNOVSERVERXXXX | This is the name of the server that hosts the Info360 database. This can be a remote  instance of SQL Server where other databases are hosted or a standalone local instance for Info360. | | Database | Info360 | Specify the name of the database | | IntegratedSecurity | **false** | This value **must be false**, meaning that Info360 will use specific a specific login account to access the database. | | UserName | account with admin rights | User name that Info360 will use to connect to the database. This account must have dbOwner rights to the database. | | Password | ********* | Password for logging in. Info360 will encrypt the password in this location for security reasons. If you update the text and save, then after Info360 runs it will encrypt the string.
*Make sure that this file is modifiable by Info360, otherwise this string will not be encrypted. | > ❌ **Warning:** > ❌ > ❌ Info360 requires that the account given for accessing the database is assigned dbOwner rights to that database.
### Global
More information about this feature | **Setting** | **Example Values** | **Description** | | --- | --- | --- | | SiteURL | [http://SW_Server/Info360](http://SW_Server/SCADAWatch) | The URL that gives access to Info360 is based on the Info360 installation location and local IIS settings. This URL is used by Info360 for the following:
- Token for ArcGIS/AGOL - Notifications pushed from server to client - URLS on Alerts are based on this siteURL - Licensing from browser - Multi-site cookies
Note: siteURL is case sensitive (even though IIS is not) so ensure that siteURL matches as per the folder name, not just what works in the browser. | | MultipleSitesMode | true / false | [Default = false] If you have more than one license and you want to host multiple sites from the same server, set this option to true. | | DBCommandTimeOut | 300 / 600 / 1800 | [Default = 600] Any query to the database that takes longer than this number of seconds will be aborted. | | ClientMode | Release / Debug | [Default = Release] Switching to "Debug" model will cause detailed recording in the log file for resolving issues. |
### Sensor Data
More information about this feature The following sensor data settings are primarily for server performance. In general, disabling sampling on the Info360 side and letting the Agent do the work in the background leads to the best performance. | **Setting** | **Example Values** | **Description** | | --- | --- | --- | | SensorDataStartPoint | 2017-01-01 | [Default = 1900-01-01] This parameter defines a global minimum start date for all sensor sampling queries. Individual sample start dates override this value if set at a later time. | | SensorDataRetrievalLimit | 500 / **1000** / 100000 / etc. | [Default = 1000] This is a restriction to set the maximum number of sensors that Info360 will load from the database for performance purposes. | | DisableSampling | true / **false** | [Default = false] By default, when a historic chart is opened and values are requested that aren't yet in the sampled Info360 database (TSData table), Info360 will initial sampling on the fly to retrieve the data. This can slow down the site.
To speed up performance, you can set this to true, and instead set up the [Agent](https://help-innovyze.atlassian.net/wiki/spaces/info360/pages/15008196/Administration#Administration-Agent) to perform all sampling in the background.
Note that setting this to true will block users from being able to view raw sensor data in Historic charts, which is a process that requires direct querying from the historian database. | | DisableUpdatableSensorSampling | true / **false** | [Default = false] Set this to true if you don't want the Info360 server to perform updatable sensor sampling. | | DisableMassBalanceSampling | true / **false** | [Default = false] Setting this to true will disable calculations of Mass Balance. Note that this will also disable manually running the calculations from the front end website. This setting prevents users from wiping out the stored calculations. | | DisableBizBlockSampling | true / **false** | [Default = false] Setting this to true will disable calculations of BizBlock. Note that this will also disable manually running the calculations from the front end website.
This setting prevents users from wiping out the stored calculations. | | RealtimeValue_UsingTSData | **true** / false | [Default = true] When true, gauge charts that display the current sensor value will simply use whatever is the latest value already stored in the Info360 database TSData table.
When false, Info360 will directly query the SCADA Historian to get the most up-to-date value available. In some cases this can cause extra load times and affect performance. | | SamplingFragment | 1day / 1week / **1month** / 1year | [Default = 1month] When sampling sensor data, Info360 will fragment the query timespan into these fragments. The reason for this is that some SCADA Historians set a limit on the number of data points that can be accessed at once. When the raw data point interval is very small, this value may need to be lowered to 1week or 1day. | | SamplingTimeGap | 500 / **2000** / 10000 | [Default = 2000 (2 seconds)] Time in milliseconds to wait before next sampling. This parameter will impact how frequently Info360 pings the historian database and samples data into the Info360 database. | | ProcessingTimeGap | **500** / 2000 / 10000 | [Default = 500 (1/2 second)] Time in milliseconds to wait before the next BB, MB, or Alert calculation. This number can be raised if significant calculations are being run on the web server and resources are limited. |
### Map
More information about this feature | **Setting** | **Example Values** | **Description** | | --- | --- | --- | | OfflineMap | true / **false** | [Default = false] When set to true, Info360 will downlaod and store map-processing javascripts and files from [arcgis.com](http://arcgis.com) locally rather than pulling data on demand. | | CacheAGOLSensorAttributes | **true** / flase | [Default = true] By default Info360 will locally cache the map layer attributes of the sensors so that clicking on sensors more efficiently brings up their data. Setting this to false will base | | GooglemapKey | AIzaSyAI7iS4tSiA... | In order to enable Map Dashlets, you must obtain your own free Google API key.
You can obtain your own API Key [here](https://developers.google.com/maps/documentation/javascript/get-api-key). This process requires a Google account. |
### UserAccount
More information about this feature These settings are implemented for security purposes related to users logging in. | **Setting** | **Example Values** | **Description** | | --- | --- | --- | | LogInAttemptLimit | **5** / 10 / -1 / etc. | [Default = 5] This is the number of consecutive failed log in attempts a user can make before their account will become frozen or locked as defined below. -1 means unlimited attempts; this is discouraged for safety reasons. | | FreezeTime | **5** / 60 / -1 / etc. | [Default = 5] Number of minutes that an account will be frozen for if they fail the login more than the LogInAttemptLimit. -1 means the account will be locked instead of frozen. An Admin will need to unlock the account to regain access. | | Inactivitylogout | 5 / 10 / **-1** / etc. | [[Default = -1](https://help-innovyze.atlassian.net/wiki/pages/createpage.action?spaceKey=info360&title=Default%20%3D%20-1&linkCreation=true&fromPageId=15008190)] Info360 will force the user to log out if the browser is left inactive for this specified number of minutes.
-1 means the account will not log the user out automatically. |
### Report
More information about this feature This section can be ignored if you do not have the suite license that provides access to the custom reporting module. | **Sett****ing** | **Example Values** | **Description** | | --- | --- | --- | | RegenerateReportData | 60 / **1440** / -1 / etc. | [Default = 1440] This defines the frequency at which custom reports will be updated from the database (as new data comes in). -1 means that the report data tables will be updated every time the user clicks to preview the report. |
### Logging
More information about this feature | **Setting** | **Example Values** | **Description** | | --- | --- | --- | | Storage | **file** / db / both | [Default = file] This setting defines where Info360 will store log information: a text file in the installation folder, the Info360 database, or both locations. | > ⚠️ **Notice:** > ⚠️ > ⚠️ In order to review the logged data from the software at the [Server Logs](https://help-innovyze.atlassian.net/wiki/display/info360/Administration#Administration-ServerLogs) page, logs must be stored in the database.