Last revision: 12/3/2018
We recommend that you read the following important information before reading this document.
Our Wonderware HMI SCADA YouTube channel contains instructional and promotional videos on our various product lines. Please follow the links below:
Platform Connectivity and Device Integration Playlist
https://www.youtube.com/playlist?list=PLJq4rR8tWINwTpCnlHqjUUlysBClU-YqU
Wonderware HMI SCADA Channel Main Page
https://www.youtube.com/user/wonderwarehmi
This document contains important information about the Wonderware Operations Integration - Core Communications Driver. Carefully review this document for known issues in this version and for changes, if any, to the Core Communications Driver.
This release of the Core Communications Driver is an upgrade for consumption with System Platform 2017 Update 3 release.
Third Party/Open Source Software Disclosure
The OI Core incorporates Third Party/Open Source Software components whose licenses and copyright notices can be found at the following folder on the target machine:
On 32-bit operating systems: \Program Files\Wonderware\OSSLicenses_OICore.pdf
On 64-bit operating system: \Program Files(x86)\Wonderware\OSSLicenses_OICore.pdf
New Product Name
The OI Core is now OI Core Communications Driver. However, you may see “OI Core” in some instances of documents, SMC tree hierarchy, upgrade path, and so on.
Secure SuiteLink Connection
To ensure a higher level of confidentiality and privacy, SuiteLink communication between OI Servers and SuiteLink client can now be encrypted. If OI Core Communications Driver 3.0 is installed on an existing installation of WSP 2017 Update 3, the SuiteLink communication will be encrypted if the SuiteLink client supports encryption. Alternatively, you can install the SuiteLink 3.0 to provide the encrypted communication for SuiteLink in OI Servers. For a SuiteLink client to use encrypted communication, it must be running on WSP 2017 Update 3 or with SuiteLink 3.0 installed.
To ensure interoperability and compatibility with the previous versions of SuiteLink, the secured SuiteLink infrastructure continues to support and allow both encrypted and non-encrypted communication.
For more information about Secured SuiteLink connection, refer to the OI Core Communications Driver Help.
Support for Non-Admin Mode (Standard User)
To ensure a higher level of security, the configuration and modification of OI Servers are now restricted to administrative users.
User without administrative right (Standard user) is permitted only to view the configuration and diagnostics of OI servers.
The OI Core Communications Driver can be installed standalone, as well as bundled in the installation of the Wonderware System Platform (WSP). The OI Servers will always be compatible with the latest release of System Platform. For a detailed information on product and platform compatibility, refer to the Technology Matrix section of the Global Customer Support (GCS) Site.
For a list of supported operating systems for the communication drivers, refer to the Technology Matrix, available at the Global Customer Support (GCS) Site:
The Technology Matrix is a searchable database that contains the latest product information. Enter the product name in the search bar, then select the release to view:
To run an OI Server, the following hardware configurations are the minimum recommended:
Note: For every additional 5 connections (Up to 10,000 I/O @ 1000 ms each), add 1 GB RAM and 1 Cores.
Installation Checklist
The OI Core Communication Driver must be installed prior to the installation of any OI Server communication driver.
Before installing the communication driver, please ensure the following:
Installation Procedure
Download OI Gateway Communications Driver from the Connectivity Hub section of the Global Customer Support.
The GCS Connectivity Hub contains the product downloads, documents, and videos.
Note: The downloaded files could be blocked. Since the Windows regards downloaded files as potentially unsafe, it blocks the file from executing after the downloaded. Check your Downloaded Zip or ISO file to ensure that the downloaded file is not blocked. If it is blocked, you must unblock it before extracting.
To install the OI Server, double-click Setup.exe and follow the installation instructions. When setup is complete, the message "Setup was successful" is displayed.
OPC connectivity, DCOM, Windows Firewall, and Anonymous Access
Our software no longer supports Anonymous Login setting in DCOM configuration for OPC connections. In order to ensure proper communication between both nodes, you need to ensure DCOM, Windows Firewall, and user credential settings are configured properly. For additional details, refer to the section OPC connectivity, DCOM, Windows Firewall, and Anonymous Access in the OI Core Communications Driver Help.
The OI Core Communications Driver supports silent (command line) installation. The prerequisite products that are installed during the silent installation includes:
Before initiating the silent installation of OI Core, it is strongly recommended that you stop all the DAServers and OI Servers.
Silent Installation Syntax
The basic syntax of the silent installation command consists of the full path to the Silent_Install_Setup.bat file (typically the DVD drive designation on your local computer), and the command line switch.
<DVD>: CD-OIEngine>Silent_Install_Setup.bat /<argument>
The usage instructions can be retrieved by the following command line. It returns the supported operations - install and uninstall.
<DVD>: CD-OIEngine>Silent_Install_Setup.bat /?
To install/uninstall the OI Core
Installation: C: CD-OIEngine>Silent_Install_Setup.bat /install
Uninstallation: C: CD-OIEngine>Silent_Install_Setup.bat /uninstall
Note: The silent installation process installs the OI Core along with the prerequisite products. However, the uninstallation process uninstalls only the OI Core and the dependent components. All the prerequisites and independent components should be uninstalled manually.
The following issues are resolved in this release.
CR Number |
Description |
L00149304 |
SR 14414227: Unable to perform the write operation, with a Gateway PlugInOPC warning message. |
L00149334 |
SR 223110309: Unable to run more than one instance of an OI Server if there is a Activation Based Professional OI Server license and a standard ArchestrA.lic OI Server license on the same machine. |
L00150193 |
SR 223110320: When a system with multiple instances of OI servers was rebooted, all the instances would not automatically start. |
L00150293 |
SR 31613603: When some production lines were down, the logger displayed an exception message. |
The following table lists known issues at the time of release.
L00151094 - Digital Signature Issue |
Installing and activating OI-ABCIP or OI-SIDIR after the OI-Core 3.0 is installed, logs an error message in the logger. Please contact Schneider Electric Software technical support regarding licensing error VerifyFileSignature(C:\Program Files (x86)\Wonderware\OI-Server\CommonFiles\bin\SELicensing.dll) Workaround: This error message does not have any functional impact. You may ignore the error. |
Accessing web help |
While accessing the web-help from a node hierarchy/ Auto-Build, the browser prompts to run the ActiveX controls. Workaround: As a workaround, click Allow Blocked Content to view the contents of the help page. |
Legacy DAServer and OI Server Coexistence |
In some scenarios, legacy DAServer and pre-OI Core 2.1 Series OI Servers might have connectivity issues when installed with post-OI Core 2.1 OI Servers. Scenario 1: Upgrading to OI Core G-2.1 in an environment with legacy DAServers or pre-OI Core 2.1 Series OI Servers installed is not an issue and requires no additional installation or configuration steps. Scenario 2: Installing a legacy DAServer or pre-Core G-2.1 Series OI Server after installing OI Core G-2.1 can result in connectivity issues. These servers require minor configuration changes. Workaround: Run the Change Network Account utility after the new drivers (DAServers or OI Servers) are installed. |
Coexistence with System Platform versions between 2012 R2 and 2014 R2 (Any version pre-dating System Platform 2017) |
If System Platform is installed in the same node AFTER the OI Core 2.1 is installed, Application Server may not work properly. Workaround: Run the Change Network Account utility after the System Platform installation. |
Centralized (Activation-Based) Licensing - Failed to release the acquired licenses |
In some scenarios, closing the SMC failed to release the acquired activation-based license back to the license server. Scenario: Consider an OI Server (such as multi-instance) is configured and set to a valid License Server node. Performing a cloning operation will acquire a license. However, upon exiting the SMC, the license is not released back to the License Server, even if the OI Server is not activated. Workaround: Activate and then deactivate the OI Server to release the license back to License Server. Open SMC and ensure that the acquired activation-based license is not shown as "In Use". |
The Wonderware Operations Integration - Core Communications Driver documentation set includes the following guides. These documents can be accessed from the Help menu in the SMC.
Note: The AVEVA Enterprise License Manager Help can be accessed through the License Manager application (available only for the new license framework). For earlier versions of the license framework, see License Utility Guide.
The documentation describing how to use this product are included on the CD in PDF format. Viewing these guides requires the installation of Adobe's Acrobat Reader. This utility is not included on this CD, but it can be downloaded for free from the Adobe's Web site at the following Web address:
www.adobe.com/products/acrobat/readstep2.html
After downloading the file from Adobe, you must run the executable to install it on your computer. Follow the typical installation routine. After installation, you can either open the Acrobat Reader and select a user's guide from the File menu, or double-click a user's guide on the CD in Windows Explorer.
|
Copyright © 2018 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |