UAServer needs to be restarted when sideloading nodeset files

[barnstee]

It would be great if this is not required. Apparently, creating references to the core nodeset manager will do the trick.

[barnstee]

Chris, Randy, please collaborate on this issue while I am on vacation next week.

[muenchris]

Can you give a little background what you mean by sideloading? Is the all about new nodesets or updates to nodesets in use? One way would be to dynamically add a new NodesetManager to the Server with the new nodeset. I am not sure if this can be done one fly, but we can investigate. Updating an already loaded nodeset is more complicated - especially of there are already clients connected to it. One way to build this would be to use a similar approach as IIS does (creating a parallal nodesetmanager, timing-out or disconnected connected clients and only allow reconnects to the new nodeset manager). @randy-armstrong - do you have an idea how to do this?

[barnstee]

What I mean by sideloading is copying a nodeset file into the nodeset directory and restarting the translator. Then it works, but adding a nodeset during runtime without restarting the translator (or the server) is also supposed to work but this code (with a focus on registering the new namespaces) doesn't seem to be enough:

foreach (string ns in newNamespaceUris)
{
if (!existingNamespaceUris.Contains(ns))
{
lock (Lock)
{
existingNamespaceUris.Add(ns);

        // update the table used by this NodeManager
        SetNamespaces(existingNamespaceUris.ToArray());

        // register the new URI with the MasterNodeManager
        Server.NodeManager.RegisterNamespaceManager(ns, this);
    }
}

}

Also, I'm already raising a model change event to notify clients that the model has changed (search for RaiseModelChangedEvent()).

[barnstee]

Have a look at what CreateAddressSpace() does under the covers to create references to the core nodeset manager while loading nodes.

[barnstee]

check out

UA-EdgeTranslator/UAServer/UANodeManager.cs

Line 333 in d44382d

AddPredefinedNode(SystemContext, predefinedNodes[i]);

[muenchris]

I don't see any folder content monitor that would detect a new file or updated file in the "settings" or "nodeset" folder.

Therefore I assume you mean with "Sideloading" using the WoTFile OPC Methods, correct?

The "CreateAsset" function takes a File as a parameter. This is for new WoTFiles that can be added to the "settings" folder, correct?
After I pointed this to a valid WOT File, I got some weird behavior (Souce file showed up as text under "SupportedWoTBindings").

I am not clear how to use these Methods (for NodesetFileUpload or under "WoTFile" of an existing WoTfile:

• The "Open" only requires a mode 1 or 6 and a buffer length.
• The WoTFile and NodeSet is only reloaded on "CloseAndUpdate" that requires the handle given in the open function.
• Since these methods are under the branch of the WotFile, I was hoping that there is a method called "Reload" that just reloads the file and does the delta processing.
• I added a small code-block that reloads the current file in the directory if an OPCUAClient just calls "Open" and "CloseAndUpdate" without writing any data. This could be triggered by a file-system-level file-change event. But a client should not monitor the server's directories. Better would be if the server monitors the folder and then calls Open/CloseAndUpdate itself. This triggers a reload of the WoTFile but I am still not sure how to just trigger a nodeset sideload update.

Is there a sample that shows the prober use of the WoTFile Methods to trigger a nodeset sideloading?

[barnstee]

Fixed with 25959ce