Search

18 result(s) for FindServers

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.5.1 Overview
  using the RegisterServer Service. Clients can later discover any registered Servers by calling the FindServers Service on the Discovery Server . The discovery process using FindServers is illustrated in Figure ... establishment of a SecureChannel (with MessageSecurityMode NONE ) for FindServers and GetEndpoints is omitted from the figure for clarity. Figure 9 - Discovery process The URL for a DiscoveryEndpoint shall provide
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.5.3.1 Description
  Description This Service returns the Servers known to a Discovery Server . Unlike FindServers , this Service is only implemented by Discovery Servers . The Client may reduce the number of results returned
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.3.1 Description
  only for use with Session -less invocation. These Endpoints shall support GetEndpoints and FindServers in addition to the SessionlessInvoke Service. The Server returns Bad_ServiceUnsupported for the other Services
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.4 Auditing for Discovery Service Set
  Clients and Services that are invoked by OPC UA Servers . The FindServers and GetEndpoints Services that are called by OPC UA Clients may generate audit entries for failed Service invocations
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.6.2.4.5.1 General
  list shall provide the ApplicationDescription for all Servers in the RedundantServerSet through the FindServers Service . This information is needed by the Client to translate the ServerUri into information needed
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.3 Time synchronization
  correct time. The OPC UA application or a separate background utility would call the FindServers Service and set its clock to the time specified in the ResponseHeader . This process
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.2.3 Hosts without a LocalDiscoveryServer
  separate LDS. Such Servers shall become their own LDS or LDS-ME by implementing FindServers and GetEndpoints Services at the well-known address for an LDS. If implementing
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.3.1 Overview
  band discovery (i.e. entry into a GUI) of a DiscoveryUrl for a Server ; Calling FindServers on the LDS installed on the Client host; Calling FindServers on a remote LDS, where
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.3.3 Local Discovery
  Client finds a LocalDiscoveryServer then it will call the FindServers Service on the LDS to obtain a list of Servers and their DiscoveryUrls . The Client would then call the GetEndpoints
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.3.4 MulticastSubnet Discovery
  calls FindServersOnNetwork and then connects directly to the Server . When a Client calls FindServers it only receives the Servers running on the same host as the LDS. Clients running
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.3.5 Global Discovery
  Servers that meet the filter criteria provided. The QueryApplications Method is similar to the FindServers service except that it provides more advanced search and filter criteria. The discovery process
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  5.1 Overview
  standalone LocalDiscoveryServer installed. The LocalDiscoveryServer shall expose one or more Endpoints which support the FindServers and GetEndpoints services defined in OPC 10000-4 . In addition, the LocalDiscoveryServer shall provide ... least one Endpoint which implements the RegisterServer service for these applications. The FindServers Service returns the information for the LocalDiscoveryServer and all Servers that are known
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  5.3.2 Single MulticastSubnet
  receive the same set of applications. When a Client calls FindServers it only receives the applications running on the same host
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  5.3.4 No MulticastSubnet
  discover applications uses an out of band mechanism to find the HostName and call FindServers on the LDS of that host . FindServersOnNetwork may also work but it will never return ... more than what FindServers returns. Clients could also use a GDS if one is available
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.10 QueryApplications
  This is more useful to some Clients because it matches the return type of FindServers . Any Client is able to call this Method , however, the set of results returned
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.22 EndpointDataType
  associated with the Endpoint . They are reported as part of the ApplicationDescription returned by FindServers (see OPC 10000-4 ) and by QueryApplications ( 6.5.10 ). If multiple Endpoints are specified the DiscoveryUrls ... this list is empty the Endpoint is not included in the ApplicationDescription returned by FindServers or QueryApplications . The DiscoveryUrls returned to Clients includes one of the URLs in the DiscoveryUrls
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  A.1 Firewalls and Discovery
  Endpoint for the DiscoveryUrls in all ApplicationDescriptions that it returns when a Client calls FindServers . This would tell the Client to call the DiscoveryServer back when it wishes to connect
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.2.1 Locating Server
  Server is located following the standard procedure as defined in OPC 10000-12 , i.e., FindServers , GetEndpoints , OpenSecureChannel , CreateSession and ActivateSession on the Server Address with the specified SecurityMode