Installing Cogent DataHub v9 on a system running an earlier version of the DataHub
Note: Cogent DataHub v9 contains new features that may not be supported by your target operating system. Please see our Installation Notes for more details.
Installing DataHub v9 on a system running an earlier version
When you install DataHub v9 on a system running DataHub v7 or v8 the installer will ask you to uninstall the earlier version. DataHub v9 will be installed and will use the existing configuration files from the earlier installation.
When you install DataHub v9 on a systems running OPC DataHub v6.4, then you will be asked if you want to copy the configuration from the earlier version, but it will not replace the earlier version. You can run OPC DataHub v6.4 and Cogent DataHub on the same system, though there may be conflicts that require you to modify your configuration.
If you want to make a backup of your current DataHub configuration, you can do that by copying the contents of the DataHub configuration directory. The location of this directory will depend on which operating system you are running. See this link to documentation for more details.
See below for more information about copying your local WebView pages and media to DataHub v9.
Tunnelling between DHv9 and DHv8, DHv7 or DHv6.4
You can tunnel between v9 and v7, v8 and v6.4. When tunneling between V9 and V6.4 you may run into a known issue with licensing that appears when the network of DataHub connections is not a simple star configuration.
You can tunnel using WebSocket between v9, v8 and v7, but you can only tunnel between v9 and v6.4 using a non-SSL connection.
You can tunnel through a proxy between v9 and v7 as long as v9 is the client initiating the connection.
There is one known issue relating to tunnelling in DataHub v9. Binary tunnel connections between DataHub v7/v8 and v9 will fail. They 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. Binary tunnel connections are configured by selecting the Transmit point changes in binary option, which is off by default. So, unless you specifically select this option, your normal (non-binary) tunnel connections will be work between DataHub v6.4/v7/v8 and v9.
Moving WebView pages and media to DataHub v9
When you upgrade to v9, DataHub will attempt to copy your old WebView pages to a new folder in order to make them visible in WebView v9. If you would like to do this manually, here is what’s involved.
Default Configuration Folder
User-generated content is now stored in the DataHub configuration folder, not the Program Files folder. The default configuration folder for DataHub is:
where <Windows Login> is the user name you used to log in to Windows. You can change the configuration folder using the -H command-line option on DataHub, or by setting it through the DataHub Service Manager application.
Assuming you log in to WebView as the admin user, your personal WebView v8 pages can be found here: C:\Program Files (x86)\Cogent\Cogent DataHub\Plugin\WebServer\html\Silverlight\Pages\Users\admin
These pages need to be copied into the following location for use with WebView v9: <Configuration Folder>\WebContent\Content\Organizations\Local\Users\admin\Pages
Similarly, any personal images you added to WebView v8 will now be found in: C:\Program Files (x86)\Cogent\Cogent DataHub\Plugin\WebServer\html\Silverlight\Images
These images need to be copied into the following location for use with WebView v9: <Configuration Folder>\WebContent\Content\Organizations\Local\Users\admin\Images
You must do the same for Media and Script files.
If you have created publicly accessible pages, images, etc. then you will find the v8 files in: C:\Program Files (x86)\Cogent\Cogent DataHub\Plugin\WebServer\html\Silverlight\Pages
These need to be copied to: <Configuration Folder>\WebContent\Content\Organizations\Local\Pages
Images, media files, and scripts need to be similarly copied.
If you have created custom WebView controls, they will only work in Silverlight. You need to recompile these controls separately for Desktop WebView. Controls and ControlAssemblies are now differentiated between Silverlight and WPF versions. For examples, if you have created a custom control DLL called MyCustomControl.dll, you would install it in DataHub v8 in: C:\Program Files (x86)\Cogent\Cogent DataHub\Plugin\WebServer\html\Silverlight\ControlAssemblies\Company\MyCustomControl.dll
In DataHub v9, you can install it in one of two locations: C:\Program Files\Cogent\Cogent DataHub\Plugin\WebServer\html\Content\Common\ControlAssemblies\Company\Silverlight\MyCustomControl.dll
Or <Configuration Folder>\WebContent\Content\Organizations\Local\ControlAssemblies\Company\Silverlight\MyCustomControl.dll
You must similarly distinguish XAML and XML files for your custom controls if they are different between Silverlight and WPF versions.
If you need assistance moving your custom controls, please contact Skkynet’s technical support team at firstname.lastname@example.org.