Hi,

Yes, but care should be taken not to make NodeIds of existing nodes. The String-NodeIds are a bit safer in this regard as it can represent hierarchical paths thus there is less chance of conflicts (UUIDs would be best, but they are not very human-readable). SDK doesn’t handle conflicts well i.e. createInstance/NodeBuilder is not transactional. If it fails halfway in the process then half the nodes are already added and rolling this back manually can be .. a bit of a pain.

Anyway, probably easiest is to override com.prosysopc.ua.server.NodeManagerUaNode.createNodeId(UaNode parent, QualifiedName of_the_child_node) by subtyping NodeManagerUaNode. There are also other createNodeId versions, but this is the one NodeBuilder calls, but if you wish to only have numeric ids you could override all of them. Note that SDK also uses these internally when making e.g. subnodes below structure datatype’d nodes.

If you need more control e.g. that the numeric should be based on specific InstanceDeclaration of a type etc. it is more complicated, but technically doable by making an UaNodeBuilderConfiguration (given in NodeBuilder constructor) that returns InstantiationStrategy that ignore the NodeId part of InstantiationStrategy.createInstance(InstantiationParameters) (or basically meaning you make new InstantiationParameters with the nodeid you want to have).