OPC UA Publisher tag

An OPC UA Publisher tag will publish values from I/O tags to the VTScada OPC UA Server. An OPC UA Server configuration is not complete unless it has one OPC UA Server tag and at least one OPC UA Publisher tag. Without a configured OPC UA Publisher tag, the VTScada OPC UA Server will not start.

IO tags can link to an OPC UA Publisher tag to publish values to the VTScada OPC UA Server. An application may have more than one Publisher tag. This may be helpful if, for example, you want to group devices logically, would like to publish values to a specific namespace, or with different permissions enabled or to enforce realm access.

The VTScada OPC UA Server runs as a separate executable on the same machine as your app. Your app contains an OPC UA Server tag and one or more OPC UA Publisher tags. Connect to the VTScada OPC UA Server with other apps or OPC UA clients.

A simplified concept diagram of VTScada's OPC Server

Settings tab

The Settings tab is where you configure:

  • The OPC UA Server tag that works in tandem with this Publisher tag
  • Where published values are addressed in the OPC UA server space
  • A login prefix that is unique to the VTScada application on the controlling machine
  • Optional security restrictions
  • Alarm event feed

Configuration fields for OPC UA Server selection, Namespace URI, Application Prefix, Allow Users from this Realm, Allow anonymous reads, Allow Writes, Show Alarm Event Feed.

OPC UA Server

Select an OPC UA Server tag.

Namespace URI

An OPC UA Server’s address space is subdivided into namespaces. The OPC UA server maintains a mapping of namespace URIs to numbers and this forms part of the address of a node within the address space. Each OPC UA Publisher tag is configured with a Namespace URI.

Namespace mappings are stored locally at the Configuration Folder address configured in the OPC UA Server tag. This is done to retain namespace mappings across restarts of the OPC UA Server. Hence, we do not recommend deleting or changing the configuration folder without preserving the original namespaces.xml file.

VTScada uses the unique tag name of a VTScada tag for the corresponding node in the OPC UA address space. This is guaranteed to be unique within your VTScada application, however, it is possible that a tag in a different VTScada application could have the same unique tag name.
For this reason, we recommend using a different namespace URI for different applications so that if they share the same OPC UA Server, there is no risk of name collision.

Application Prefix

An identifier of your choosing. This identifier must be prefixed to the user credentials from OPC UA Clients to the server. It serves as a differentiator in the event that more than one VTScada application is using the same OPC UA Server.

Allow users from this Realm

If your application uses security realms, only IO tags publishing through this Publisher will be available to users from this realm. In this way, realm users are restricted to the tags they can see in the OPC UA Server. Global (i.e. non-realm) users have access to all application tags in the OPC UA Server. You can configure multiple Publisher tags associated with the same realm or different realms, as required

If your application does not use realms, leave this blank.


OPC UA Client global credentials typically appear as, application-prefix:username

Realm user app login credentials typically appear as, realm:username

OPC UA Client credentials within a specified realm appear as, application-prefix:realm:username

For example, app:opsrealm:johnsmith

The sample dialog displays authentication settings with 'username/password' selected, opposed to Anonymous and X509 Certificate. The Username field has a fabricated entry of "app-prefix:realmname:username". The password field is obfuscated.
Note, that while a colon is used as the delimiter by default, this is changeable in your application's security options. If more than one application shares the same OPC UA Server, both applications must be configured to use the same delimiter.

Allow anonymous read access

Enable to allow anonymous users read-only access. OPC UA Clients still require to be authenticated using a certificate, but anonymous users on an approved client can access IO tags published through this Publisher. This checkbox applies where an authenticated client is in use by an anonymous user. In such cases, read-only access is enforced.

Allow writes

Enable to allow clients to write to IO tags if the tag can be written to and only for users that have OPC UA Write permission.

Show alarm event feed

Enable publishing of an alarm event feed to the OPC UA server. One alarm and event feed will appear in the OPC UA Server address space per Namespace URI.

OPC UA Server tag

OPC UA Server Configuration

OPC UA Alarms & Events