About "persisting NodeIds"

Unified Architecture topics related to OPC UA Specification, compliant behavior and any technical issues of OPC UA, like Security, Information Model, Companion Specs DI, PLCopen, ADI, ...

Moderator: Support Team

Post Reply
Jiny
Jr. Member
Jr. Member
Posts: 1
Joined: 20 May 2015, 02:40

About "persisting NodeIds"

Post by Jiny »

Hi,

I have seen the "persisting NodeIds" in the description of the "Session Client Renew NodeIds" in part7.
I have not find the definition for "persisting NodeIds".
What is the "persisting NodeIds"? When and how to use "persisting NodeIds"?

I am looking forward your answer. Thank you!

Best Regards,
Jiny

User avatar
Support Team
Hero Member
Hero Member
Posts: 2529
Joined: 18 Mar 2011, 15:09

Re: About "persisting NodeIds"

Post by Support Team »

Hi,

This refers to clients who store NodeIds received from servers for later use. An example is a HMI OPC UA client that displays a temperature value from an OPC UA server in a machine user interface. Such a client stores the NodeId of the temperature variable in the HMI configuration and uses the stored NodeId whenever the HMI is started and connects to the OPC UA Server.

The key feature tested by the conformance unit is that a client handles changing namespace index by reading the namespace table of the server, looking up the NamespaceURI used by the NodeId when stored and applies the right index, even if it was changed based on a server reconfiguration.

Best Regards,
Unified Automation Support Team

Post Reply