Contains OPC UA application registration information.
Object Model
Syntax
'Declaration<ComVisibleAttribute(False)> Public Interface IUAApplicationElement
'UsageDim instance As IUAApplicationElement
[ComVisible(false)] public interface IUAApplicationElement
[ComVisible(false)] public interface class IUAApplicationElement
Remarks
In This Topic
OPC UA Discovery allows QuickOPC to find available OPC UA servers, and determine how to make connections to them. There are several approaches to discovery, and they can be combined together to achieve the desired functionality. Clients and servers can be on the same host, on different hosts in the same subnet, or even on completely different locations in an administrative domain.
QuickOPC provides following kinds of discovery:
- OPC UA Local Discovery. Obtains information about the servers on a specified host using OPC UA Local Discovery Server (LDS) running on that host.
- OPC UA Network Discovery. Also known as MulticastSubnet Discovery. The information is obtained from a Local Discovery Server with Multicast Extensions (LDS-ME), which uses the mDNS protocol to exchange the information about OPC UA servers with other LDS-ME-s on the network (or multiple networks).
- OPC UA Global Discovery. Obtains information about applications available in an administrative domain by interrogating an OPC UA Global Discovery Server (GDS).
It is also possible to access the discovery functionality in a common way, using Generalized OPC UA Discovery.
Flattened and unflattened results
By default, the results (the application element collection) of many of the methods described in this chapter are returned flattened. This means that a single OPC UA application may appear multiple times in the resulting collection, and each time it will have precisely one DiscoveryUriString associated with it.
Alternatively, you can use method overloads with the additional 'flat' argument, and set it true, in order to receive unflattened result. In this case, each OPC UA application will be contained just once in the resulting collection, but it may have one or more discovery URL in its DiscoveryUriStrings property. In this case, do not use the DiscoveryUriString property, because it will contain an empty string if the application has more than one discovery URL.
Requirements