OPC UA: allow a host name override
Allow a hostname override when connecting to the OPC UA endpoint. We have some use cases where the URL returned by two independent OPC UA servers has the same name. This prevents the Connector from connecting to the correct endpoint. Allow an IP address to be specified in the config, which would be used to connect instead of the URL hostname.
In version 2.0.x, it is also available in the Data Source configuration. See UseDnsNameAndPortFromDiscoveryUrl in the UserGuide for details
This can be achieved by setting UseDnsNameAndPortFromDiscoveryUrl = False in App.OpcUa.Config and restarting the connector for the changes to take effect.
Example of the implementation in UAExpert attached.
Article describing this more in depth
In order to let Clients having endpoints located in segregated network with unkown host/DNS to use the discovery functionality from the OPC UA instead of manually force the connection adding the hostname and the IP of the source in a dedicated file of the OS that hosts the connector.
Osisoft will as consequence obtain adavantages expanding their Cients sector (more and wider Client sector with different architecture will use their products).
Allow the discovery from the OPC UA endpoints located in segregated network with unkown host/DNS. Now, the name resolution needs to be done manually through the “hosts” file of the OS that hosts the connector...