Hi,

Note that there is a difference in what SDK supports “out of the box” and what SDK supports when combined with application specific code (i.e. stuff that you have to do). See https://www.prosysopc.com/products/opc-ua-java-sdk/technical-details/, some have the “* Requires application implementation” in them. Redundancy very heavily requires them (depending on the modes/kinds of redundancy).

Also note that some of the facets … might not mean what you expect. See https://reference.opcfoundation.org/Core/docs/Part7/ for the list of Profiles and Facets. Though I think some of them only have a clear definition at https://profiles.opcfoundation.org/.

Also, please read https://reference.opcfoundation.org/v104/Core/docs/Part4/6.6.2/ about redundancy, it might or might not be what you expect. For example, for Cold redundancy you can have 2 sets of hardware and run the SDK’s SampleConsoleServer on both to simulate it. Have the second hardware be powered of. Connect the client to the first server. Cause some simulated failure of the first hardware. Now then, per my understanding the “cold redundancy” is achieved if you have a mechanism in place to note failure of the first hardware and “go press power on button” of the second hardware and connect to that instead.

So, in short we do not have a demo, but that might also not apply to even all redundancy modes. Most of the stuff is just make a duplicate Client/Server and have some magical out of band communication way to detect failure.