Actions
Exchange values between different OPC UA Servers
Hi,
It seems like the ServerRedundancyType has been changed in v1.05 specification, is that correct?
The NonTransparentRedundancyType has been removed and RedundantServerDataType[] has been added. But in 1.05 specification "part 4 chapter 6.6.2 Server Redundancy" it still refers to the NonTransparentRedundancyType.
"The ServerRedundancy Object defined in OPC 10000-5 indicates the mode supported by the Server. The ServerRedundancyType ObjectType and its subtypes TransparentRedundancyType and NonTransparentRedundancyType defined in OPC 10000-5 specify information for the supported Redundancy mode."
It is also changed in the nodeset-file for 1.05 which makes the backward compatibility missing or do I miss something?
How should an OPC UA client handle this when reading it from an OPC UA server supporting non-transparent redundancy when the OPC UA client doesn't know if the OPC UA server has implement it according to 1.04 or 1.05?
How should an OPC UA server expose this when it has OPC UA clients where some of them have implement non-transparent redundancy according to the 1.04 and some according to 1.05?
Will the serverId property, in 1.05, in the RedundantServerDataType replace the ServerUriArray, in 1.04, in the NonTransparentRedundacyType? Is it implied that the serverId string is an URI when supporting non-transparent redundancy?
Regards
Mikael
https://reference.opcfoundatio.....4/docs/6.3
and
https://reference.opcfoundatio.....5/docs/6.3
seem to be identical.
It is not clear what the issue is.
Hi,
The changes in the ServerRedundancyType between 1.04 and 1.05 can be seen here:
https://reference.opcfoundatio.....docs/6.3.7
https://reference.opcfoundatio.....docs/6.3.7
The questions remains.
Regards
Mikael
None of the types have been removed. The references in the table were redundant documentation so the table was changed.
The link to the supertype is defined in each type declaration.
The RedundantServerArray is still a Mandatory Property on TransparentRedundancyType
It has been added to the base type as an Optional Property which is non-breaking change.
1 Guest(s)
Devices in use: Desktop (25), Phone (3)
Usage