OData

Описание

Overview:

• There is a new web service interface, called iHistory, that is introduced for Wonderware Historian 2014 R2. This is based on several industry standards and includes extensions that will be familiar to many Wonderware Historian users. Though the initial interface exposes different kinds of data from on-premise Historian (alarm & event history) and Wonderware Online (process history).

Note:

• There are two parts to the OData interface, Alarm/Event history and Process History. The first part was released and fully supported in 2014 R2, but the second was not—it was mostly there, but not very scalable or fully tested until the patch.

• Using oData to Expose Different Kinds of Data from Alarm, Event, and Process History

Включение HTTPS для обмена информацией между Historian Server и клиентами по oData

[Issue] Enabling HTTPS for WW Historian OData 
[Resolution] Please review this attached tech note TN1163 Creating an Encrypted Connection (HTTPS) with OData for Historian Client. 
https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn1163

Extract 
Typically, customers using the Open Data (OData) protocol can connect Wonderware Historian Client to a Managed Historian server using an unencrypted (HTTP) connection. It is possible to use an encrypted connection (HTTPS) for OData, but in that case, you must first install and configure an SSL client certificate. 
This document describes the steps for installing and configuring an SSL client certificate. 

[Steps] Followed steps in tech note. 
1. On Historian Server, Bind certificate to port 32567 

netsh http add sslcert ipport=0.0.0.0:32567 appid={12345678-db90-4b66-8b01-88f7af2e36bf} certhash=072a61565b1d741d77fa4cc2a89f26c1934076b5 

2. Add regkey OWINHostCmdArgs (string type) with value -port 32567 -secured 1 
3. Stopped and started WWHistorian from SMC 
4. Checked aahOWINHostLocal.exe service runs with command line – “C:\Program Files (x86)\Wonderware\Historian\x64 \aahOWINHostLocal.exe” -port 32567 -secured 1