Configure the OPC UA client

Configure advanced properties of an OPC UA client.
Prerequisites
  1. To configure the OPC UA client
  2. In
    Project view
    , select an OPC UA client.
  3. In
    Properties
    , configure the OPC UA client settings.
    • Events
      :
      • None
        . Listen for no events.
      • All
        . Listen for all events.
      • Alarms
        . Listen for alarm events only.
    • Synchronize the Node IDs on start
      . Synchronize the NodeIDs of the OPC UA nodes that are imported at design time. Synchronize the NodeIDs with the same nodes on the OPC UA server to which the OPC UA client connects at runtime.
      TIP: If the situation on the server is not known, set
      Synchronize the Node IDs
       on start to
      True
      .
    • Max array length
      . The maximum number of elements in an array.
      TIP: If OPC UA clients have different
      Max array length
       values, the
      Max array length
       value of the first OPC UA client applies to all clients.
    • Server endpoint URL
      . The communication protocol and network address of the endpoint on the OPC UA server.
    • Verify server identity
      :
      • True
        . Accept the certificate only if the certificate is trusted.
      • False
        . Temporarily accept the certificate even if the certificate is not trusted.
    • Requested publishing interval
      .Specify the refresh interval for requesting data from the OPC UA server.
    • Requested sampling interval
      .Specify the sampling frequency for polling data from the field.
    • Runtime configurations
      . Add and configure settings for importing and synchronizing the server node with its child nodes.
      • Local destination node
        . Client node to import the server node with its child nodes.
      • Remote source node
        . Path to the server node expressed as a sequence of browse names separated by "/".
      • Content synchronization mode
        . Either:
        • No synchronization
          . Do not import the server node or synchronize the server and client nodes.
        • Import only
          . Import the server node but do not synchronize the server and client nodes.
        • Import and synchronize values
          . Import the server node and synchronize the variable values of server and client nodes.
        • Full synchronization
          . Import the server node and synchronize the structure and variable values of server and client nodes.
          TIP: You can only use
          Full synchronization
           if the OPC UA server is an
          FactoryTalk Optix Application
          .
      • Include remote source node
        . Imports the child nodes of the server node.
      • Enable event synchronization
        . Shows the events generated by the server node in the client node defined in
        Local destination node
        .
      • Event type
        . Event type of interest from the events generated by the server node defined in
        Remote source node
        .
    • Connection locale ID
      . Locale ID to use for the connection. If empty, defaults to the project locale ID.
    • Minimum message security mode
      :
      • None
        . Messages may be unsigned and unencrypted.
      • Signature
        . Messages must be signed or signed and encrypted.
      • Signature and encryption
        . Messages must be signed and encrypted.
    • Minimum security policy
      :
      • None
        . The OPC UA client does not require any specific security policy.
      • Basic256Sha256
        . The OPC UA client requires this policy or a more secure policy.
      • Aes128_Sha256_RsaOaep
        . The OPC UA client requires this policy or a more secure policy.
      • Aes256_Sha256_RsaPss
        . The OPC UA client requires this policy.
    • Client certificate file
      . The public
      DER
       certificate file of the OPC UA client (X509v3).
      TIP: The client certificate file must be in the
      FTOptixApplication/ProjectFiles/PKI/Own/Certs/
       folder.
    • Client private key file
      . The private
      PEM
       key file of the OPC UA client encoded with ASCII Base64.
      TIP: The client private key file must be in the
      FTOptixApplication/ProjectFiles/PKI/Own/Certs/
       folder.
    • Application URI
      . A URI that globally identifies the application instance.
    • Application name
      . A legible ID of the application instance, which may not be unique.
    • Product URI
      . A URI that globally identifies the software.
    • User identity type
      :
      • Anonymous
        . No information available on the user.
      • User/Password
        :
        • Username
          . The name of the user.
        • Password
          . Password of the user.
      • Certificate
        :
        • User certificate file
          . The public
          DER
           certificate file of the user (X509v3).
          TIP: The public certificate file of the user must be in the
          FTOptixApplication/ProjectFiles/PKI/Own/Certs/
           folder.
        • User private key file
          . The private
          PEM
           key file of the user encoded with ASCII Base64.
          TIP: The private key file of the user must be in the
          FTOptixApplication/ProjectFiles/PKI/Own/Certs/
           folder.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.