Follow these guidelines to ensure that prerequisites native to any Windows operating system are satisfied prior to installing Info360.

Configure Server

  • Info360 requires a machine Windows Server 2012 + or Windows 7 Pro 64bit or above with the following recommended specifications:
    • 2.5+ gigahertz CPU (2 Core/Socket)
    • 8+ GB RAM
    • 100 GB Hard drive space (or wherever the database is stored)
  • Enable IIS 7 or higher on the machine. Refer to Microsoft web documentation for more information.

Install SQL Server

Info360 uses SQL Server (version 2012 or newer) to connect to SCADA historian databases and store data that is accessible to the network.

  • Info360 requires a local SQL login; it cannot use Windows domain user authentication as a web service. This login requires permissions to read, write, and create tables in the database.
  • SQL Express (free) can be used, however there is a database size limit.
  • User experience with SQL Server is not required. Info360 creates and maintains its SQL DB by itself.
  • If SQL Server is already being used with other databases, then the DB Admin must create a database for Info360 as well as a log in for Info360 with db_Owner permissions. This is required for Info360 to access and create its own tables.

Note: In addition, most SCADA Historians require an ODBC or OLEDB connection. This can be set after installation but it is required before importing data to Info360.

Install the following components as necessary

  • .NET 3.5 framework - This is used for licensing Info360.
  • URL Rewrite - This is a Microsoft IIS feature used in the Info360 application.
  • Google Chrome - This is the preferred browser for using Info360.
  • Install Historian Client:
    • If Wonderware - Not required (as data can be fetched over SQL Server)
    • If iHistorian -  Install the client that comes with installation media.
    • If OSI PI - Classic OLEDB Provider (not enterprise). This may require purchase.
    • If ClearSCADA - Install the client that comes with installation media.
    • [During the initial phase Info360 will be pulling a lot of data so we may be requesting to raise the data request limit on the historian, if applicable.]

Ensure Web Access to the following URL

Info360 uses web components from a few outside sources and will require access to these URL's to perform properly.

Source Domain

Full List of URL's

Uses in Info360

*.arcgisonline.com

Only used if basing the web map on published ArcGIS Online services.

Not necessary if using shapefiles.

*.googleapi.com

Only used for Map Dashlets

*.gstatic.com

Only used for Map Dashlets

Establish Remote Access for Innovyze

Innovyze staff will carry out the configuration remotely through Windows RDP or similar.

  • Provide Innovyze some form of VPN connection for remote access.
  • Local Admin rights are preferred so that Innovyze can perform patch updates to Info360 components through the project.

Turn on Windows Web Server (IIS) and .NET Features

The following steps show the step-by-step process on Windows Server.

For non-server machines, similar features can be turned on by going to Control Panel -> Programs and Features -> Turn Windows Features On or Off.

  1. On the Server Manager, choose to Add Roles and Features under the Manage icon.  



  2. Review and click Next.  



  3. Choose Role-based or feature-based installation.  



  4. Choose to select a server from the server pool, and select the desired computer/server.  



  5. Turn on Web Server (IIS) as a Server Role.  



  6. Select to include management tools for IIS.  



  7. Continue.  



  8. Under Features, turn on the latest .NET Framework along with WCF Services.  



  9. Continue to Web Server Role (IIS).  



  10. Turn on the following common HTTP Features and all of the Application Development tools.  



  11. Confirm that you have included all the features shown in the screen shot below.



The above steps are a one-time process needed for the machine that will host a Info360 site. Contact us if questions arise.