OPC UA Protocol

OPC UA

OPC UA is a technical specification used in the automation field for communication between different devices and systems, enabling cross platform, cross language, and cross network operations, providing a reliable and secure data exchange foundation for the Industrial Internet of Things. IoTDB supports OPC UA protocol, and IoTDB OPC Server supports both Client/Server and Pub/Sub communication modes.

OPC UA Client/Server Mode

• Client/Server Mode：In this mode, IoTDB's stream processing engine establishes a connection with the OPC UA Server via an OPC UA Sink. The OPC UA Server maintains data within its Address Space, from which IoTDB can request and retrieve data. Additionally, other OPC UA Clients can access the data on the server.

• Features：

  • OPC UA will organize the device information received from Sink into folders under the Objects folder according to a tree model.

  • Each measurement point is recorded as a variable node and the latest value in the current database is recorded.

OPC UA Pub/Sub Mode

• Pub/Sub Mode： In this mode, IoTDB's stream processing engine sends data change events to the OPC UA Server through an OPC UA Sink. These events are published to the server's message queue and managed through Event Nodes. Other OPC UA Clients can subscribe to these Event Nodes to receive notifications upon data changes.

• Features：

  • Each measurement point is wrapped as an Event Node in OPC UA.

  • The relevant fields and their meanings are as follows:

    Field	Meaning	Type (Milo)	Example
    Time	Timestamp	DateTime	1698907326198
    SourceName	Full path of the measurement point	String	root.test.opc.sensor0
    SourceNode	Data type of the measurement point	NodeId	Int32
    Message	Data	LocalizedText	3.0

  • Events are only sent to clients that are already listening; if a client is not connected, the Event will be ignored.

IoTDB OPC Server Startup method

Syntax

The syntax for creating the Sink is as follows:

create pipe p1
    with source (...)
    with processor (...)
    with sink ('sink' = 'opc-ua-sink',
               'sink.opcua.tcp.port' = '12686',
               'sink.opcua.https.port' = '8443',
               'sink.user' = 'root',
               'sink.password' = 'root',
               'sink.opcua.security.dir' = '...'
              )

Parameters

key	value	value range	required or not	default value
sink	OPC UA SINK	String: opc-ua-sink	Required
sink.opcua.model	OPC UA model used	String: client-server / pub-sub	Optional	client-server
sink.opcua.tcp.port	OPC UA's TCP port	Integer: [0, 65536]	Optional	12686
sink.opcua.https.port	OPC UA's HTTPS port	Integer: [0, 65536]	Optional	8443
sink.opcua.security.dir	Directory for OPC UA's keys and certificates	String: Path, supports absolute and relative directories	Optional	Opc_security folder/<httpsPort: tcpPort>in the conf directory of the DataNode related to iotdb If there is no conf directory for iotdb (such as launching DataNode in IDEA), it will be the iotdb_opc_Security folder/<httpsPort: tcpPort>in the user's home directory
sink.opcua.enable-anonymous-access	Whether OPC UA allows anonymous access	Boolean	Optional	true
sink.user	User for OPC UA, specified in the configuration	String	Optional	root
sink.password	Password for OPC UA, specified in the configuration	String	Optional	root

示例

create pipe p1
    with sink ('sink' = 'opc-ua-sink'，
               'sink.user' = 'root',
               'sink.password' = 'root');
start pipe p1;

Usage Limitations

1. DataRegion Requirement: The OPC UA server will only start if there is a DataRegion in IoTDB. For an empty IoTDB, a data entry is necessary for the OPC UA server to become effective.

2. Data Availability: Clients subscribing to the server will not receive data written to IoTDB before their connection.

3. Multiple DataNodes may have scattered sending/conflict issues：

   • For IoTDB clusters with multiple dataRegions and scattered across different DataNode IPs, data will be sent in a dispersed manner on the leaders of the dataRegions. The client needs to listen to the configuration ports of the DataNode IP separately.。

   • Suggest using this OPC UA server under 1C1D.

4. Does not support deleting data and modifying measurement point types: In Client Server mode, OPC UA cannot delete data or change data type settings. In Pub Sub mode, if data is deleted, information cannot be pushed to the client.

IoTDB OPC Server Example

Client / Server Mode

Preparation Work

1. Take UAExpert client as an example, download the UAExpert client: https://www.unified-automation.com/downloads/opc-ua-clients.html

2. Install UAExpert and fill in your own certificate information.

Quick Start

1. Use the following SQL to create and start the OPC UA Sink in client-server mode. For detailed syntax, please refer to: IoTDB OPC Server Syntax

   create pipe p1 with sink ('sink'='opc-ua-sink');

2. Write some data.

   insert into root.test.db(time, s2) values(now(), 2)

   ​The metadata is automatically created and enabled here.

3. Configure the connection to IoTDB in UAExpert, where the password should be set to the one defined in the sink.password parameter (using the default password "root" as an example):

   
   

4. After trusting the server's certificate, you can see the written data in the Objects folder on the left.

   
   

5. You can drag the node on the left to the center and display the latest value of that node:

   

Pub / Sub Mode

Preparation Work

The code is located in the opc-ua-sink 文件夹 under the iotdb-example package.

The code includes:

• The main class （ClientTest）
• Client certificate-related logic（IoTDBKeyStoreLoaderClient）
• Client configuration and startup logic（ClientExampleRunner）
• The parent class of ClientTest（ClientExample）

Quick Start

The steps are as follows:

1. Start IoTDB and write some data.

   insert into root.a.b(time, c, d) values(now(), 1, 2);

   ​The metadata is automatically created and enabled here.

2. Use the following SQL to create and start the OPC UA Sink in Pub-Sub mode. For detailed syntax, please refer to: IoTDB OPC Server Syntax

   create pipe p1 with sink ('sink'='opc-ua-sink',
                             'sink.opcua.model'='pub-sub');
   start pipe p1;

   ​ At this point, you can see that the opc certificate-related directory has been created under the server's conf directory.

   

3. Run the Client connection directly; the Client's certificate will be rejected by the server.

   

4. Go to the server's sink.opcua.security.dir directory, then to the pki's rejected directory, where the Client's certificate should have been generated.

   

5. Move (not copy) the client's certificate into (not into a subdirectory of) the trusted directory's certs folder in the same directory.

   

6. Open the Client connection again; the server's certificate should now be rejected by the Client.

   

7. Go to the client's <java.io.tmpdir>/client/security directory, then to the pki's rejected directory, and move the server's certificate into (not into a subdirectory of) the trusted directory.

   

8. Open the Client, and now the two-way trust is successful, and the Client can connect to the server.

9. Write data to the server, and the Client will print out the received data.

   

Notes

1. **stand alone and cluster:**It is recommended to use a 1C1D (one coordinator and one data node) single machine version. If there are multiple DataNodes in the cluster, data may be sent in a scattered manner across various DataNodes, and it may not be possible to listen to all the data.

2. No Need to Operate Root Directory Certificates: During the certificate operation process, there is no need to operate the iotdb-server.pfx certificate under the IoTDB security root directory and the example-client.pfx directory under the client security directory. When the Client and Server connect bidirectionally, they will send the root directory certificate to each other. If it is the first time the other party sees this certificate, it will be placed in the reject dir. If the certificate is in the trusted/certs, then the other party can trust it.

3. It is Recommended to Use Java 17+:
   In JVM 8 versions, there may be a key length restriction, resulting in an "Illegal key size" error. For specific versions (such as jdk.1.8u151+), you can add Security.setProperty("crypto.policy", "unlimited");; in the create client of ClientExampleRunner to solve this, or you can download the unlimited package local_policy.jar and US_export_policy to replace the packages in the JDK/jre/lib/security. Download link: https://www.oracle.com/java/technologies/javase-jce8-downloads.html.