| DataSource Kind |
OPCUA |
| Server URL Type |
Displays an endpoint (URL) for a OPC UA server which is basically a physical address
available on a network that allows clients to access one or more services provided by a server.
Depending upon your choice,
- Discovery - The server URL is considered as the Discovery URL.
- Endpoint - The server URL is considered as the Endpoint URL. If the
provided Endpoint URL is correct, it skips the discovery process.
|
| Message Security Mode |
You can choose the message security mode on how the data must be transferred for the
connected OPC UA server from the drop-down list.The following are the message security mode options:
- Signed
- Signed and encrypted
- None
The default value is None.
Warning: Be careful while using the Security Mode as None.
|
| Security Policy |
You can choose the security policy, which relates to the Message Security Mode for the
connected OPC UA server from the drop-down list. The default value is None.
Important: It is recommended to use encryption for secure communications. For example,
the AES256 security policy. If the mode is set to None, messages
that are exchanged between the client and server application are unsecured and subject to security
threat.
|
| Protocol |
The protocol to be used. The default and the only currently supported value is
opc.tcp. |
| Message Encoding |
The data encoding format to be used. Currently only binary is supported. The default value is
BINARY. |
| Update Interval |
The Publishing Interval, in milliseconds, when the OPC UA server returns data change
notifications to the client. The default value is 1000 milliseconds. |
| Server Keep-Alive |
Used to calculate the maximum keep-alive count as follows.
Max keep-alive count = Sever Keep-Alive / Update Interval Maximum keep-alive count represents the number of Publishing Intervals that can be skipped, before the OPC Server sends an empty notification if there is no data to send.
The
default value is 5000 milliseconds. |
| Client Keep-Alive |
Used to calculate the lifetime count as follows.
Lifetime count = (Client Keep-Alive + Update Interval – 1) / Update Interval
Lifetime count defines the number of the Publishing Intervals to wait for a new Publish Request, before marking the client as inactive. The Subscription is then deleted by the OPC Server.
The
default value is 5000 milliseconds. |
| Queued PubReq Count |
The number of the Publish Requests to be queued with the OPC UA Server. The default value is
1. |
| User Name |
Enter the user name, if the OPC UA server authentication is enabled. If the message flow uses
username and password, the datasource stores password using secure storage vault at runtime. For
more information, see Using Eclipse secure storage vault. |
| Password |
Enter the password for the user name, if the OPC UA server authentication is enabled. |
| Client Private Key file |
Specify the absolute path of the clientPrivateKey.pem file. Applicable only
if the OPC UA server security settings are configured. |
| Private Key Password |
Enter the password you provided in the 5.a step of the
Generating self-signed SSL certificate topic. |
| Client Certificate file |
Specify the absolute path of the clientCertificate.pem file. Applicable only
if the OPC UA server security settings are configured. |
| Server Certificate file |
Specify the absolute path of the serverCertificate.der file. You can get a
server certificate from the PKI directory of the server. For example,
C:\Users\<username>\.acmfg\PKI\CA\certs\<serverCertificate.der>.
Applicable
only if the Server URL Type is Endpoint .
|
| Notes |
Enter notes for the datasource, if any. |