Hello,
Does anyone happen to know a way to change the name of an OPC UA Server?
The goal is to modify the OPC UA server name to comply with the company's naming conventions.
After some investigation, it seems that the name is hardcoded.
So I’m reaching out to see if anyone might know a tricky workaround (as recommended by Inductive support).
If you're asking how to set the name of your own Ignition gateway it's done in,
Config | SYSTEM | Gateway Settings | System Name.
There's also the loopback connection name,
Config | OPC CLIENT | OPC Connections | Name.
I'm not trying to do either of those.
My goal is to modify the name of the OPC UA server mounted by Ignition.
The OPC UA server name is exposed for discovery (by external OPC UA clients).
I am not sure why you're trying to change the string here. This isn't the place you customise device names, this is a field specified that explains the service that is running on the host at that port. The company's naming conventions will govern the hostname/dns name/FQDN, which is important.
Your request is similar to asking Rockwell how to change the device type string on a ControlLogix to return Modicon...
Even in the screenshot above you clearly see the hierarchy showing the host by hostname: localhost
The string "Ignition OPC UA Server" explains that the service that is serving the OPCUA server is made by Inductive Automation and is a product called Ignition. This is important to keep, as you might have multiple OPCUA servers on one host.
It is also key to realise that UA Expert doesn't show you all the metadata that is available from discovery, your'e seeing a couple of choice bits that Unified Automation chose to put on that screen.
This is the configuration of the OPC UA Client name in Ignition when connecting to its own server...
Thank you for your detailed response.
I will discuss this with our customer to better understand their concerns and determine whether it truly makes sense.
I’ll keep you informed if we come up with any relevant arguments.
I don’t see any kind of work around because it is hardcoded.
I think this is a good analogy in terms of how we view this server name and why it’s not configurable. Same for product URI, though there is perhaps an argument to be made that hardcoding both are not necessary.
