|Download Help (Windows Only)|
Compared with classic OPC, OPC Unified Architecture (UA) offers expanded security across servers and clients by utilizing private keys and public keys. A certificate file contains a pair of keys: a public key and a private key. The public key and private key must have the same name.
By default, the OPC UA server or client trusts the certificate file it uses. You can use an existing certificate file. Ensure that the public key and private key have the same name and reside in the same folder. If you do not specify a certificate file for the OPC UA server or client to use, LabVIEW creates a certificate file, Default OPC UA, to use when you create a LabVIEW OPC UA server or client at run time. You also can use the Create Certificate VI to create a certificate file. If you do not specify a name for the certificate file, this VI creates a certificate file with the default name Default OPC UA.
The following table shows the location of the certificate file that LabVIEW creates at run time or when you use the Create Certificate VI.
|Operating System||File Path to the Certificate File||Note|
|Windows XP/Server 2003 (32-bit)||C:\Documents and Settings\All Users\Application Data\National Instruments\certstore\opcua\||You can find public keys and private keys in the file path to the certificate file.|
|Windows 7/Vista/Server 2008 (64-bit)||C:\ProgramData\National Instruments\certstore\opcua\|
|NI ETS||c:\ni-rt\system\opcuacer\||You can find public keys in the file path to the certificate file.|
|Wind River VxWorks||/c/ni-rt/system/opcuacer/|
|NI Linux Real-Time||/var/local/natinst/certstore/opcua/|