Search
16 result(s) for Discovery Server
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services3.1.6 DiscoveryServerDiscoveryServer an application that maintains a list of OPC UA Applications that are available on the network and provides mechanisms for other OPC UA Applications to obtain this list
-
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model8.2 Rogue GDSremember when dealing with a GDS: It is important that Servers register with the Discovery Server they are configured to register with and that Servers do not blindly register with ... been configured to register with. Servers have to be aware that a Discovery Server could be a rogue Server . A Server registers all endpoints that it provides, ensuring that
-
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Modelused without security and is therefore vulnerable to denial of service (DOS) attacks. A Discovery Server should minimize the amount of processing required to send the response for this Service
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.2.1 DescriptionDescription This Service returns the Servers known to a Server or Discovery Server . The behaviour of Discovery Servers is described in detail in OPC 10000-12 . The Client may reduce ... number of results returned by specifying filter criteria. A Discovery Server returns an empty list if no Servers match the criteria specified by the Client . The filter criteria supported
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.5.1 DescriptionThis Service is implemented by Discovery Servers . This Service registers a Server with a Discovery Server . This Service will be called by a Server or a separate configuration utility. Clients ... will not use this Service . A Server shall establish a SecureChannel with the Discovery Server before calling this Service . The SecureChannel is described in 5.6 . The Administrator of the Server
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.6.1 DescriptionServers . This Service allows a Server to register its DiscoveryUrls and capabilities with a Discovery Server . It extends the registration information from RegisterServer with information necessary for FindServersOnNetwork . This Service ... this Service . Servers that support RegisterServer2 shall try to register with the Discovery Server using this Service and shall fall back to RegisterServer if RegisterServer2 fails with the status
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.4 ApplicationTypeapplication is a Client . CLIENTANDSERVER 2 The application is a Client and a Server . DISCOVERYSERVER 3 The application is a DiscoveryServer
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.31 RegisteredServerLocalDiscoveryServer starts. If a Semaphore file is specified but does not exist the Discovery Server shall remove the registration from any persistent data store. If the Server has registered with ... semaphoreFilePath, the Discovery Server shall check that this file exists before returning the ApplicationDescription to the Client . If the Server did not register with a semaphoreFilePath (it is null
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsProtocol ( NTP ) provides a standard way to synchronize a machine clock with a time server on the network. Systems running on a machine with a full featured operating system like ... this scenario, the OPC UA application will have to know the URL for a Discovery Server on a machine known to have the correct time. The OPC UA application
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services3.1.13 LocalDiscoveryServer (LDS)LocalDiscoveryServer (LDS) a DiscoveryServer that maintains a list of all Servers that have registered with it. Note 1 to entry: Servers normally register with the LDS on the same host
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services4.2.1 Overviewthat do not wish to be discovered openly should not register with a DiscoveryServer . In this case such OPC UA Application s should only publish a DiscoveryUrl via some
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services6.1 Overviewmultiple subnets. For this reason, there is a need for an enterprise wide DiscoveryServer called a GlobalDiscoveryServer . The GlobalDiscoveryServer (GDS) is an OPC UA Server which allows Clients to search
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.10.14 ApplicationConfigurationTypeProperty shall be present and the ServerCapabilities shall be set". If ApplicationType is DiscoveryServer then the ApplicationsNames Property shall not be present and the ServerCapabilities shall ... ApplicationUris . 0:ApplicationType "Client" "Server" or "ClientAndServer" "DiscoveryServer" "Client" 0:IsNonUaApplication Omitted or FALSE Omitted or FALSE Omitted or FALSE
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Servicesnetwork address from the perspective of all Clients which means the URLs returned by DiscoveryServer s are not affected by the location of the Client . In other networks the Administrator ... discussed in more detail in OPC 10000-4 . Administrators can set up a DiscoveryServer that is configured with the ApplicationDescriptions for Servers that are accessible to external Clients . This DiscoveryServer
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Servicesevents. GDS Supports the Global Discovery Server information model. LDS The ApplicationType is DiscoveryServer . Only used by a standalone LDS implementation. DI Supports the Device Integration (DI) information model
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global ServicesE.2 UDDIUDDI tModels Name domainKey uuidKey Server uddi:server.ua.opcfoundation.org uddi:AA206B41-EC9E-49a4-B789-4478C74120B5 DiscoveryServer uddi:discoveryserver.ua.opcfoundation.org uddi:AA206B42-EC9E-49a4-B789-4478C74120B5 The name of the businessService elements should ... available at any given time and will find it more convenient to place a DiscoveryServer in the registry instead