OPC UA Server

Driver Plugin ID:

com.tibbo.linkserver.plugin.device.opcua-server

Property

Description

Bind Address

The IP address to which the OPC UA Server should bind. A value of 0.0.0.0 indicates that the server should bind to all available network interfaces.

Bind Port

The TCP port on which the OPC UA Server should listen for connections.

URL Path

An optional path segment to be appended to the server's URL.

Security Policies

List of security policies that are allowed to be used by clients when connecting to the server. Each policy has the following fields:

• Enabled: Indicates whether this specific security policy is enabled and available for clients to use. If unchecked, the policy will not be offered as an option during the connection process.

• Algorithm: Specifies the cryptographic algorithm used for this security policy. Examples include:

  • Basic128Rsa15

  • Basic256Rsa15

  • Basic256

  • Basic256Sha256

  • Aes128_Sha256_RsaOaep

  • Aes256_Sha256_RsaOaep

  • None - Allow connection with no encryption. The Mode field is ignored in this case.

• Mode: Defines the level of security applied by this policy. Options include:

  • Sign: Digitally signs messages to ensure integrity and authenticity. This protects against message tampering but does not encrypt the message content.

  • SignAndEncrypt: Provides both message signing and encryption for maximum security. This ensures confidentiality, integrity, and authenticity of the exchanged data.

Anonymous Authentication

No authentication is required. This allows any client to connect without providing credentials. Typically used for testing or in trusted environments.

Allow Username/Password Authentication

Clients must provide a valid username and password to authenticate.

Certificate Trust Policy

Defines how to verify certificates provided via an SSL/TLS connection.

Certificate

Alias of an SSL/TLS certificate to use for authentication. The certificate with that alias must exist in the Client Certificate storage of the Iotellect server.

Context Mask

A mask or a specific context path to include in the OPC UA address space. Use * to include all contexts.

Folder Node Path

The path within the OPC UA address space where the nodes for this context should be created. If empty, the path will be derived from the Iotellect context path.

Variables

A list of variables to include from the specified context. Each entry has the following fields:

• Group: The name of the variable group within the context. This allows you to expose a group of variables without needing to specify each variable by name. Ignored if Variable Name is specified.

• Variable Name: The name of the variable within the context that you want to expose as an OPC UA tag. You can use wildcards * to include all variables within a context.

• Field name: If a variable contains multiple fields (e.g., a data table), you can use this setting to specify which individual field should be exposed as a tag. If left empty, all fields will be exposed as separate tags under the variable name.

• Tag Path: This allows you to override the default tag path and specify a custom location within the OPC UA address space for the variable. If left empty, the tag path will be constructed using the context path (e.g., users.admin.devices.virtual.), the variable group (e.g., Waves), the variable name (e.g., Random), resulting in a tag path like users/admin/devices/virtual/Waves/Random.

• Tag Name: This allows you to override the default tag name and specify a custom name for the OPC UA tag. If left empty, the variable name will be used as the tag name.

Functions

A list of function names to expose from the specified context. Use * in Entity Name to include all functions.

• Enabled: Indicates whether this function is exposed to OPC UA clients.

• Anonymous Read: Specifies if the function can be read without authentication.

• Entity Type: Defines what is exposed:

  • Function - Exposes the single function specified by Entity Name.

  • Group and Sub Groups - Exposes all functions within the group specified by Entity Name and all of its subgroups.

  • Group - Exposes all functions within the group specified by Entity Name (but not subgroups).

• Entity Name: The name of the function or group to be exposed.

• Arguments and Results Presentation: Controls how function arguments and return values are formatted, options include:

  • JSON

  • Native Encoding

  • XML

  • Separate Values

• Data Table Presentation: Determines how data tables (if any are part of the function's arguments or results) are formatted. Options include:

  • JSON

  • Native Encoding

  • XML

Events

A list of event names to expose from the specified context. Use * in Entity Name to include all events.

• Enabled: Indicates whether this event is exposed to OPC UA clients.

• Entity Type: Defines what is exposed:

  • Event - Exposes the specific event identified by Entity Name.

  • Group and Sub Groups - Exposes all events within the group specified by Entity Name and all of its subgroups.

  • Group - Exposes all events within the group specified by Entity Name .

  • Entity Name: The name of the event or group to be exposed.

  • Data Table Presentation:are formatted:

    • JSON

    • Native Encoding

    • XML

Property

Description

Max Session Count

The maximum number of concurrent client sessions allowed by the server.

Max Session Timeout

The maximum duration (in milliseconds) an inactive session can remain open before the server automatically closes it.

Min Publishing Interval

The shortest allowed interval (in milliseconds) at which the server can publish data changes to subscribed clients.

Max Publishing Interval

The longest allowed interval (in milliseconds) at which the server can publish data changes.

Default Publishing Interval

The default interval (in milliseconds) at which the server will publish data if a client does not specify a different interval.

Min Subscription Lifetime

The shortest allowed duration (in milliseconds) for a subscription.

Max Subscription Lifetime

The longest allowed duration (in milliseconds) for a subscription.

Max Subscriptions

The maximum number of subscriptions allowed across all client sessions.

Max Subscriptions Per Session

The maximum number of subscriptions allowed within a single client session.

Max Password Length

The maximum allowed length for client passwords.

Max Monitored Items

The maximum number of monitored items (tags) allowed across all subscriptions.

Max Monitored Items Per Session

The maximum number of monitored items allowed within a single client session.

Min Supported Sample Rate

The fastest sampling rate (in milliseconds) supported by the server.

Max Supported Sample Rate

The slowest sampling rate (in milliseconds) supported by the server.

Max Array Length

The maximum number of elements allowed in an array value.

Max String Length

The maximum length of a string value.

Max Byte String Length

The maximum length of a byte string value.

Max Browse Continuation Points

The maximum number of browse continuation points the server can maintain.

Max Query Continuation Point

The maximum number of query continuation points the server can maintain.

Max History Continuation Points

The maximum number of history continuation points the server can maintain.

Max Nodes Per Read

The maximum number of nodes that can be read in a single read operation.

Max Nodes Per Write

The maximum number of nodes that can be written in a single write operation.

Max Monitored Items Per Call

The maximum number of Monitored Items that can be created, modified or deleted in a single service call.

Max Nodes Per Register Nodes

The maximum number of nodes that can be registered in a single register nodes operation.

Max Nodes Per History Read Data

The maximum number of nodes that can be read from history for data in a single operation.

Max Nodes Per History Read Events

The maximum number of nodes that can be read from history for events in a single operation.

Max Nodes Per History Update Data

The maximum number of nodes for which data can be updated in history in a single operation.

Max Nodes Per History Update Events

The maximum number of nodes for which events can be updated in history in a single operation.

Max Nodes Per Method Call

The maximum number of methods that can be called in a single method call operation.

Max Nodes Per Browse

The maximum number of nodes that can be browsed in a single browse operation.

Max Nodes Per Translate Browse Paths To Node Id

The maximum number of browse paths that can be translated to node IDs in a single operation.

Max Nodes Per Node Management

The maximum number of nodes that can be managed (added/deleted) in a single node management operation.