Search

16 result(s) for DiscoveryUrls

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.5.2.1 Description
  shall have a value specified for gatewayServerUri in their ApplicationDescription (see 7.2 ). The discoveryUrls provided in ApplicationDescription shall belong to the Gateway Server. Some Discovery Servers may return multiple records
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.5.6.1 Description
  Service is implemented by Discovery Servers . This Service allows a Server to register its DiscoveryUrls and capabilities with a Discovery Server . It extends the registration information from RegisterServer with information
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.2 ApplicationDescription
  gatewayServerUri String A URI that identifies the Gateway Server associated with the discoveryUrls . This value is null or empty if the Server can be accessed directly. This field ... Discovery Services defined in 5.5 . Alternate discovery profiles are defined in OPC 10000-7 . discoveryUrls [] String A list of URLs for the DiscoveryEndpoints provided by the application. If the applicationType
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.31 RegisteredServer
  this case. gatewayServerUri String The URI of the Gateway Server associated with the discoveryUrls . This value is only specified by Gateway Servers that wish to register the Servers that they ... Gateway Server this parameter shall be null or empty. discoveryUrls [] String A list of DiscoveryEndpoints for the Server . The list shall have at least one valid entry. semaphoreFilePath String
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.3.2 Simple Discovery with a DiscoveryUrl
  Simple Discovery with a DiscoveryUrl Every Server has one or more DiscoveryUrls that allow access to its Endpoints . Once a Client obtains (e.g. via manual entry into a form
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.3.3 Local Discovery
  FindServers Service on the LDS to obtain a list of Servers and their DiscoveryUrls . The Client would then call the GetEndpoints service for one of the Servers returned. The discovery
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.3.4 MulticastSubnet Discovery
  LocalDiscoveryServer with the MulticastExtension on its local host and requests a list of DiscoveryUrls for Servers and DiscoveryServers available on the MulticastSubnet . The discovery process for this scenario is illustrated
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  4.4.3 Global Discovery for Reverse Connections
  Global Discovery Process for Reverse Connections The ClientUrls are returned in the DiscoveryUrls parameter of the ApplicationDescription record and have the 'rcp+' prefix. DiscoveryUrls without the prefix are used
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.5 ApplicationRecordDataType
  Client supports reverse connect then the ServerCapabilities shall include RCP and all DiscoveryUrls shall begin with the rcp+ prefix which indicates that reverse connections are supported. If the application does ... ApplicationType is ClientAndServer the ServerCapabilities may include RCP and all DiscoveryUrls that support reverse connect have the rcp+ prefix. If the same URL supports normal connections and reverse connection then
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.6 RegisterApplication
  Servers that support transparent redundancy shall register as a single application and pass the DiscoveryUrls for all available instances and/or network paths. Servers that support non-transparent redundancy shall register
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.9.3 StartSigningRequest
  specified in the CSR. The domains shall include the domain(s) in the DiscoveryUrls known to the CertificateManager . This Method shall be called from an encrypted SecureChannel and from
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.9.4 StartNewKeyPairRequest
  DomainNames The domain names to include in the Certificate . If not specified the DiscoveryUrls are used to create suitable defaults. PrivateKeyFormat The format of the private key. The following values ... includes in the Certificate . If it is null or empty the GDS uses the DiscoveryUrls of the Server to create a list. For Clients the DomainNames are omitted from
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.22 EndpointDataType
  used to serialize a single Endpoint configuration. It is defined in Table 110 . The DiscoveryUrls associated with the Endpoint . They are reported as part of the ApplicationDescription returned by FindServers ... QueryApplications ( 6.5.10 ). If multiple Endpoints are specified the DiscoveryUrls from each Endpoint are collected into a single list with any duplicates removed. If this list is empty the Endpoint
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  A.1 Firewalls and Discovery
  external Clients . This DiscoveryServer would have to substitute its own Endpoint for the DiscoveryUrls in all ApplicationDescriptions that it returns when a Client calls FindServers . This would tell the Client
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  C.1 DNS Server (SRV) Record Syntax
  mDNS specification. mDNS uses DNS SRV records to advertise the services (a.k.a. the DiscoveryUrls for the Servers ) available on the network. An SRV record has the form: _service._proto.name TTL class
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  C.2 DNS Text (TXT) Record Syntax
  Capabilities supported by a Server should be less than 10. The MulticastExtension shall convert DiscoveryUrls to and from these SRV records