The Exaquantum Adaptor requires the appropriate version of the Exaquantum SDK to be installed on the IFS OI Explorer server. This requires a license, which is a third party component.
Adaptor Parameters
The following tables list the adaptor's parameters, along with the name and type to be used in the Import/Export spreadsheet.
Parameter | Description | Name | Type |
Server | Fully qualified name of the server machine on which the historian is hosted. | Server | String |
User ID | User ID to use to connect to the historian. | UserID | String |
Password | Password for the User ID used to connect to the historian. | Password | EncryptedString |
Use Multi-Access | Determines whether the Multi Access Reader Class will be used for accessing the historian. | UseMultiAccess | Boolean |
Tag Fetch Prefix | By default, tag discovery will be run to search a folder named "Root". Setting this option allows tag discovery to be run against a different, named Exaquantum folder. | TagFetchPrefix | String |
Import Aggregation Tags | Determines whether tags under the "Aggregations" folder will be return during tag discovery. | ImportAggregationTags | Boolean |
Prerequisites
- The Exaquantum SDK needs to be installed on the IFS OI Server Machine. The version should match the version of the historian in use. If the Exaquantum SDK has breaking changes between versions, contact IFS OI Customer Support for help.
- The Exaquantum SDK uses DCOM to communicate across the network. The Windows Domain logon account used to access Exaquantum also needs to be used to run the IFS OI Data broker service (the service must run as this user).
- Your Exaquantum administrator will be able to advise on how to setup Exaquantum security.
- On the IFS OI Server, this same Windows Domain account will need to be given network permissions in the DCOM Config privileges on the IFS OI Explorer server.
Installation and Upgrade
This adaptor is included in the Explorer installer.
Release History
- Explorer 4.9.3
- First version of the Exaquantum Adaptor