Live Data Logon view

Live Data grid - Live Data Logon view

This view is used to specify connections to one or more telemetry databases.

The view is displayed by double-clicking a live data configuration object in the Model Group window, then selecting the Live Data Logon tab.

Notes:

• Data in this view can be entered manually or updated in bulk from CSV files (using the Open Data Import Centre) or directly from Info360 (see Connecting to Info360 telemetry).
• The telemetry feeds are linked to live data points in the Live Data Point view. Live data points are in turn associated with a network object in the control via the Live Data Point ID field.
• To test that a connection has been set up correctly, you can right-click a grid row and select Test connection.

Item	Description
Left-most column	If clicked, selects the whole row. A forward triangle indicates the current row. An asterisk indicates where a new object can be created by entering its details (in this case, a connection name).
Fields	Connection Name User name for the connection. Database Type Drop-down list of supported database types and connection methods: JET Oracle SQL Server ODBC (IT administrators, see ODBC connection information below) PI Note: InfoWorks WS Pro requires the classic PI OLEDB provider and not the Enterprise OLEDB provider. Both providers can be installed side by side and do not interfere with each other. However, some of the functionality required byInfoWorks WS Pro is available only through the classic provider. CSV (IT administrators, see CSV database connection information below) iHistorian ClearSCADA SQL Server (ODBC) JET (ACE) Info360 PI Web API Info360.com Generic (Rest) – a bespoke REST API Note: The Generic (Rest) connector allows your company to implement a special REST API to connect to your own telemetry system. The page Implementing the Generic (Rest) API for telemetry will give suitable guidance to your IT department. Time Zone Leave blank if all telemetry data for this connection is in local time. This setting cannot take account of daylight saving changes to local time. If the telemetry data for this connection is in Coordinated Universal Time (UTC), choose this option from the dropdown list. Telemetry data in UTC is not affected when local time is adjusted for daylight saving. If the telemetry data is coming from different time zones, set the UTC minus or UTC plus time zone for each connection. Results will be coordinated. You can return to a blank field by selecting it and pressing Delete. Client / Driver Enabled when Database Type is set to SQL Server or SQL Server (ODBC). Note: Ignore the value in this field for all other database types. Available options are: SQL Server 2005 SQL Server 2008 SQL Server 2012 OLE DB Driver 18 for SQL Server ODBC Driver 11 for SQL Server (valid only for SQL Server (ODBC) databases) ODBC Driver 13 for SQL Server (valid only for SQL Server (ODBC) databases) Net Service Name Enabled when Database Type is set to Oracle. The name that was used to identify this particular Oracle database instance on your PC. Server Enabled when Database Type is set to SQL Server, PI, iHistorian, ClearSCADA, PI Web API, or Generic (Rest). Name of the server on which the telemetry database is stored. For PI Web API: This field is used for the server name, for example devdata.osisoft.com This must be the server name only; the rest of the URL must not be entered. InfoWorks WS Pro will prepend and append characters to construct a URL of the form https://devdata.osisoft.com/piwebapi Connection is made using HTTP/TLS. By convention, this defaults to port 443. If the server is configured to use a different port, you can enter this as part of the server name, for example devdata.osisoft.com:1234 (This method of specifying the port is widely used for http and not specific to InfoWorks WS Pro). For Generic (Rest): This will contain the base URL, as provided by your IT department, similar to https://MyTelemetry:3000 Database Enabled when Database Type is set to SQL Server or PI Web API. Name of the telemetry database. Logon Type Enabled when Database Type is set to SQL Server, Oracle, ODBC, PI, iHistorian, ClearSCADA or PI Web API. Logon type can be: Trusted - uses the Windows NT username and password as authentication when accessing the database Username / Password - requires username and password to be entered in the grid Username Enabled when Database Type is set to Info360 or when Logon Type is set to Username / Password. Username to log on to database. Password Enabled when Database Type is set to Info360 or when Logon Type is set to Username / Password. Password to logon to database. The password will be displayed as asterisks in the grid view. Command Timeout (s) Timeout, in seconds, for obtaining values from the data feeds. For PI Web API: The value in this field will be used for each request made to the server. Updates of data that bring back more than 1000 data points will require multiple requests (although if there is a problem, the timeout will most likely occur on the first request and update will fail at that point). Maximum Feed Failures ~ Creation User Enabled when Database Type is set to Oracle or PI Web API. Note: The text entered in the Creation User field is case sensitive. Filename/Folder Enabled when Database Type is set to JET, CSV, or JET (ACE). For JET: This is the name of the telemetry database (including the path to the database). Tip: It is highly recommended to specify a UNC path as multi-user installations are the typical configuration. However, paths with drive letters can be used if the telemetry database is local (for demonstration purposes for example). For CSV: This is the location of the folder containing the CSV data files. Connection String Enabled when Database Type is set to ODBC or PI Web API. For ODBC: This parameter is required by ODBC and sets the string used to open the live data source. For PI Web API: A single parameter can be entered here: no_cert This is case insensitive and must be spelt as shown. If this is used, the certificates on the server will not be validated. Schema Enabled when Database Type is set to ODBC. Defines the schema to use. The schema can be: typed in by the user selected from a list of schemas by choosing Select schema from the context menu. See below for more details. The schema is database dependent. (In Oracle it is the creation user, in SQL Server it is dbo or sys, and in Access there is no schema.) Info360 URL Enabled when Database Type is set to Info360. This is the Info360 server URL. If http://demo.server/scadawatch is the address of the Info360 server appearing in your web browser, /api/ should be appended to the end of it in the Info360 URL field. In other words, this field should read http://demo.server/scadawatch/api/.
Main context menu options	Copy Copies the value(s) of the selected cell(s) to the clipboard. Several cells can be selected in the same row. Test connection Tests the connection to the corresponding telemetry database. Select schema Opens the Select Schema dialog, for choosing the schema to use from the telemetry database. Valid for ODBC database types only. Properties Displays the Live Data Logon Object Properties window showing the properties for a single live data.

ODBC connection information

Connection using the Microsoft ODBC Administrator program

• Use the 32-bit or 64-bit version of the Microsoft ODBC Administrator program (odbcad32.exe), as appropriate, to configure the ODBC adaptors.
• The File DSN method of setting data sources in the ODBC Administrator program is probably the most useful because the file can be stored in a network location.
• The database type must be set to ODBC.
• The logon type should be set to Username / Password and the username and password set and saved in this view.
• A value must be set for command timeout(s).
• The string used to open the live data source must be set as the connection string. Examples:
  • DSN=Newtown where Newtown is the user data source entered in the File DSN tab or the System DSN tab of the ODBC Administrator program.
  • FILEDSN=d:\ora.dsn where ora.dsn is the Oracle user data source specified in the File DSN tab of the ODBC Administrator program. Also, the path must be specified in the field when using File DSN.
• Connection strings can be used for testing purposes, because ODBC can connect to Excel spreadsheets and CSV files:
  • When using Excel spreadsheets, the worksheet names will appear as choices in the table names (Table Name field) in the Live Data Feed view .
  • When using CSV files, the file names will appear as choices in the table names (Table Name field) in the Live Data Feed view.

Connection to Microsoft Azure datawarehouse

• You can connect to the cloud-based Microsoft Azure datawarehouse via the ODBC connection type.
• You should create an ODBC data source (ODBC Driver 12/13 for SQL Server) and specify the Azure connection, username and password in the DSN configuration.
• You will then be able to select the created ODBC data source from within live data configuration.

CSV database connection information

• This database type is recommended only for testing.
• The CSV database type can make use of text files containing date, time, and value data in one of two formats:
  • UK date format - for example, 12/02/2012 09:00:00,0.481 (alternatively without seconds: 12/02/2012 09:15,0.483).
  • ISO date format - for example, 2011-04-21T00:00:00,2.13 (alternatively 2011-04-21 00:05:00,2.15).
• The Database Type field must be set to CSV.
• The Filename / Folder field must contain the location of the text file. You cannot browse to this location in the grid, so copy from Windows File Explorer and paste it into the cell.
• On the Live Data Feed view:
  • You must enter values for Offset, Factor, TimeWindow (min), and Adaptor.
  • For the Table Name field, you must choose a file with CSV data in it. This drop-down list contains any files in the location you entered in the Filename / Folder field on the Live Data Logon page.
• You can test that the data will be read correctly:
  • On the Live Data Feed page, right-click any cell for the CSV feed that you want to test, then choose Test feed.
  • On the Test Feed dialog, enter a time range that corresponds to the data in the CSV file you want to test, then click Test Time Range. A dialog reports the results.
  • Click OK. If there any results, they are shown in the Results section of the Test Feed dialog.