Hi,

1. UaModeler can generate code to be used with the SDKs, see https://www.prosysopc.com/products/opc-ua-modeler/ and/or output models in the NodeSet2 XML format.

2. At the moment you will need an SDK (like https://www.prosysopc.com/products/opc-ua-java-sdk/). At least currently we do not have a ready application level product that would enable importing the NodeSet2 files.

The Modbus Server installation contains the model (on windows at C:\Program Files (x86)\ProsysOPC\ModbusServer\app\model).

But in general if I may ask, what are you trying to do or achieve?

There is more than one way to interpret that. Do you just need to push the data from an UA server (that you would already have) to IoT Hub? Or do you need an actual UA server product to be able to do that by itself? Or something else? From where your data comes from (DB, PLC etc.)?

There is a lot of models already, see e.g. https://opcfoundation.org/developer-tools/specifications-opc-ua-information-models, most of them are there (but e.g. these are not http://www.euromap.org/en/i40/…..nterfaces/)

OPC UA is “self-describing”, i.e. type information is available from the server’s address space (see the Types folder). Therefore most of the time the clients do not exactly need to be aware of the model as all it provides is obtainable from the address space. But for example in our Java SDK you could use the codegen that comes with the SDK to create model specific classes making it easier to develop a client application that connects to servers using that model. Or you could skip that and operate on a more generic “UaNode” instances. It depends what you want from the application.

But generally for making UA server applications you will need an SDK, which you would then use as part of making your application (maybe including using the information models). It is not exactly “modifying source code of the server”, more like writing the source code of your application using SDK as software libraries (e.g. our Java SDK is just a .jar file like any other java library).

Alternatively if you can find a ready product that can import NodeSets, then you can skip the development part. But at least currently we do not have such ready products (but it is quite easy to do that with our SDKs, however..). A future Simulation Server version probably will eventually be able to import and simulate NodeSets (at least that is one of the goals we have), however outside of pure simulation the data must come from somewhere and must have some kind of logic mapped to that (as typically it would not be useable as-is for the model). That is non-trivial and generally an area under research. So I would say most of the time you’ll probably need to code some application specific logic, which in most cases then again would need the SDK.

If you have just a server, you should be able to use https://docs.microsoft.com/en-us/azure/iot-accelerators/overview-opc-publisher (and https://sandervandevelde.wordpress.com/2018/11/06/getting-started-with-opc-ua-on-azure-iot-edge/, found by googling “azure iot hub opc ua”, seems they use our simulation server in there).

Note that UA 1.04 added a concept “PubSub” (which is now part 14 of the specification). That doesn’t yet have a lot of support, but it should allow in the future for UA Servers to act as publishers to push data via AMQP/MQTT etc. to the cloud if needed. However e.g. our Java SDK does not yet support it (hopefully it does before the end of this year).

P.S.
I’m not aware that even this would support importing NodeSets, but it can do all kinds of things, https://www.kepware.com/en-us/products/kepserverex/