DataHub v9 does not support Windows XP and Server 2003
DataHub V9 requires .NET 4.6.1, which is only available on Windows 7 and later. Windows XP and Server 2003 are not supported.
Changes to OPC-UA certificate handling
DataHub v9 changes the way DataHub deals with OPC-UA certificates by removing a dependency on the windows machine certificate store that was stopping DataHub from registering with the LDS if the user permissions did not permit reading that store. We are not aware of any side-effects from this.
64-bit DataHub v9 needs 64-bit OPCEnum service
If you are upgrading to the 64-bit DataHub v9, you may find that you cannot configure connections to OPC DA servers. This requires a 64-bit version of OPC Core Components. Most OPC server products will install OPC Core Components (containing OPCEnum) when they are installed. They typically install a 32-bit version. The 32-bit version only supports 32-bit clients and servers.
The 64-bit version of DataHub V9 attempts to install a 64-bit version of the OPC Core Components that will support any combination of 32 and 64-bit clients and servers. The installation may not succeed if the installer already sees a 32-bit version installed. You can ensure that the 64-bit version gets installed by using the Windows Programs and Features interface to delete all installed copies of OPC Core Components, and then re-install DataHub.
Bit-depth for in-process OPC servers must match DataHub bit-depth
In-process OPC servers are typically 32-bit, so you need to use the 32-bit DataHub to connect to them. If you have a 64-bit in-process OPC server, then you must use the 64-bit DataHub.
Bit-depth for ODBC drivers must match DataHub bit-depth
The 64-bit DataHub v9 uses 64-bit ODBC drivers. All existing DSNs will fail to load. You need to create the DSNs as 64-bit instead of 32-bit. To open the 64-bit DSN editor, you can choose “Open DSN Administrator” from the DataHub database action configuration dialog.
Changes to DataHub Web Server folders
The DataHub Web server document root, default certificate file and log folders have all changed. The tunnel/Mirror default certificate file has changed. When DataHub starts, it looks for a configuration that was default for version 8 and automatically adjusts that to reasonable values for version 9.
Binary tunnel connections not supported in DataHub v9
DataHub v9 does not initiate or accept binary tunnel connections. When tunnelling between DataHub v9 and v6.4, v7 or v8 you must use the default (non-binary) text connections. Binary connections with DataHub v9 appear to succeed but no data values are delivered. The event log may contain error messages depending on the direction of the connection. This is made necessary by a change in the timestamp representation from 32 to 64 bits. Text connections (non-binary) are compatible between v7, v8 and v9.
DataHub v9 start up parameter now on by default
In DataHub v9 the installer now sets the default value of “Allow only one running instance” to TRUE.
Old Web Server demo pages removed in DataHub v9
The demonstration pages for the built-in web server have been removed in DataHub V9. The special URLs supporting AJAX and streaming AJAX application have been removed. The AJAX paths (/points and /ajax) are unauthenticated and represent a potential information leak. Streaming AJAX is no longer a useful technology.
Specifically, the following paths no longer exist:
For web applications that need to interact with DataHub you have 2 options:
- use a WebSocket connection
- create your own ASP page to generate custom JSON or XML content that your web application can poll.
Scripts need to be moved after upgrade to DataHub v9
After upgrading to DataHub version 9, the scripting tab may refer to scripts in the C:\Program Files (x86)\… folder. These scripts should be moved to another folder. We recommend creating a folder within the DataHub configuration folder and moving them there, typically:
C:\Users\<Windows Login>\AppData\Roaming\Cogent DataHub\scripts
where <Windows Login> is the user name you used to log in to Windows.