OPC UA Server Plug-in

You can configure the following properties in the OPC server settings:

Server Properties

The figure shows the configuration dialog for the general server properties. In this section, you define the name, communication ports, certificates, allowed authentication methods, and the endpoint address. In the lower section of the dialog, you also configure the allowed security profiles and control whether global variables and performance data are published in the address space.

Property	Description
Name	Defines the unique display name of the OPC UA server instance in the connection configuration. Use a name that clearly describes the server’s function or scope of application.
Port	Specifies the TCP port on which the OPC UA server is accessible for classic OPC UA connections. The port must be available on the target system and must not already be in use by another service.
HTTPS port	Also enables an HTTPS endpoint for the OPC UA server. After enabling it, use the input field to specify the HTTPS port through which the endpoint will be published. For information on authentication, security policies, and reverse proxy behavior, see the chapter OPC UA Server via HTTPS.
Deploy OPC UA Server via the Web Management Endpoint.	Additionally publishes the OPC UA server via the Web Management endpoint. Use this option if the server is to be accessible via the Web Management infrastructure. With Siemens Industrial Edge, the client must use the address without /opcrouter in order to establish the connection. For more information, see the chapter OPC UA Server via HTTPS.
Sample Rate (ms)	Determines the update interval for output values in milliseconds. After this interval has elapsed, the server provides new values for subscribed or read data points.
Server Certificate	Specifies the certificate the OPC UA server uses to authenticate itself to clients. The certificate is used for signed and encrypted connections. You can create a new certificate by clicking the plus icon.
Accepted Client Certificates	Specifies the certificate source from which client certificates are accepted. With All (unsafe), the server accepts all client certificates and thus does not perform a trusted preselection. With Router, only certificates from the OPC Router’s certificate management are used. With Windows, certificates from Windows Certificate Manager are used.
Enable Mutual TLS	Ensures that the TLS client certificate matches the client application’s identity. Enable this option only if your clients use consistent and managed application and client certificates.
Login: Allow anonymous login	Allows connections to be established without user authentication. Enable this option only in environments with correspondingly reduced security requirements or for testing purposes.
Endpoint Address	Displays the endpoint address generated from the current settings. OPC UA clients use this address to access the server. In container environments, an internal hostname or container identifier may appear here that is not directly accessible from outside the container. In this case, ensure that the port is exposed to the host and that clients use the host address, or that the client and OPC Router are on the same Docker network. For HTTPS and web management scenarios, also refer to the chapter OPC UA Server via HTTPS.

Security Settings

Setting	Description
None	Provides an endpoint without signing or encryption. Use this option only in protected test or development environments.
Basic128 Rsa15	Enables an endpoint with the Basic128Rsa15 security policy. Use the selection on the right to additionally specify the message mode, such as sign only or sign and encrypt.
Basic256 Sha256	Enables an endpoint with the Basic256Sha256 security policy. Use the selection on the right to additionally specify the message mode, such as sign only or sign and encrypt.

Data Provision

Data	Description
Global Variables	Publishes the OPC Router’s global variables in the OPC UA server’s address space. This allows clients to access these variables.
Performance Data	Publishes operational and diagnostic data from the OPC Router service in the address space. Use this data for monitoring, analysis, and troubleshooting.

Address Space:

In the upper section, you can import existing NodeSets from the UA Cloud Library or from your own sources and integrate them into this address space. For more information, see the NodeSets chapter.

Define the OPC UA address space to be provided:

The columns have the following meanings:

• Display Name: Name of the element in the address space.
• Type Definition: Type of the element, for example, object, folder, variable, or method.
• Data Type: Data type of the variable.
• Default Value: Initial value of the variable.
• Comment: Free-form text for documenting the element.

If a NodeSet contains methods, these are listed in the address space. The logic is not defined directly here, but rather via a connection to an OPC method trigger. The content of the method is determined by the data transfer configured in this connection. For details, see the chapter Using OPC Methods.

If data points are to be created at runtime or written via clients, also refer to the chapter Writing Data via the OPC UA Server.

User Management

The figure shows an overview of the created user accounts. Using the user management feature, you can define different users with various permissions, such as “Read Values” or “Write Values,” as well as edit or remove existing accounts.

In the dialog for editing a user, you define the login credentials and specify which actions the respective user is allowed to perform on the OPC UA server.

Advanced

The advanced properties group together update intervals and threshold values for sessions, subscriptions, messages, and data formats. These allow you to control the server’s resource behavior and specify the intervals at which the address space and stored item values are updated.

Property	Description
Address Space Update Interval	Specifies the interval at which changes to the address space are updated internally and take effect for clients. Smaller values increase timeliness but may increase system load.
Max Session Count	Limits the maximum number of client sessions that can be open simultaneously. Increase this value only if the expected number of clients requires it.
Max Subscription Count	Limits the maximum number of active subscriptions across all connected clients. This limits the load caused by monitoring and data reports.
Maximum String Length	Sets the maximum allowed length of string values in characters. Values exceeding this limit cannot be fully transmitted or processed.
Max ByteString Length	Sets the maximum allowed size of ByteString values in bytes. Use this limit to control memory usage and transmission size.
Max Array Length	Specifies the maximum allowed number of elements per array. This limit protects the server from oversized data structures.
Maximum Message Size	Limits the maximum size of an OPC UA message in bytes. This value determines the maximum size allowed for individual requests or responses.
Max Registration Interval	Sets the maximum time interval within which a client must renew its registration or communication before the connection is treated as invalid.
Interval for Saving Item Values	Determines the interval at which current item values are persistently saved. Use smaller values if you want current values to be available again more quickly after a restart.
Persisted Dynamic Data Points: Discard	Use the Discard button to discard previously persisted dynamic data points. Use this function if you want to remove OPC items that were created at runtime and persistently stored.

note

A server always starts with one object. The structure below that can be freely defined.