Hello,

There is no example of reading all NodeIds, Values or Attributes of a Server. This is not a typical thing that a Client application would need to do and it can take a lot of time depending on the number of Nodes on the Server’s AddressSpace. What is your use case for reading all this information from a Server?

To read from all Nodes of a Server, you need to browse its AddressSpace recursively starting from the Root Node. You can get a list of ReferenceDescriptions by calling client.getAddressSpace().browse(ExpandedNodeId nodeId) where client is an instance of UaClient class and nodeId is the ExpandedNodeId of the Node you wish to browse for References. You can then get the ExpandedNodeId of the Referenced Node by calling reference.getNodeId() where reference is a ReferenceDescription returned by the browse method previously. You can now use that ExpandedNodeId in readAttribute and readValue methods of UaClient class to read Attributes and Value of the Node and to browse the Node for more ReferenceDescriptions. You can repeat this recursion until browse returns no ReferenceDescriptions.

When implementing a recursion to read an entire AddressSpace, it is important to keep in mind that there can be multiple BrowsePaths leading to same Nodes. The recursion could get stuck in an infinite loop so it is important to keep a list of Nodes that have already been processed to avoid processing them again. Nodes are uniquely identified by their NodeIds so you can keep a list of NodeIds of Nodes that have been processed.

Also note, that only Nodes of Variable and VariableType NodeClasses have Value Attribute. You can check the NodeClass of the Node from a ReferenceDescription by calling reference.getNodeClass().