Difference between revisions of "OPC UA Client Application Operations in OpcCmd"
| Line 2: | Line 2: | ||
At the {{Style=label|OpcCmd>}} prompt, enter <code>uaClient getService uaClientApplication</code>, or shortened: <code>uac gs uaca</code>. | At the {{Style=label|OpcCmd>}} prompt, enter <code>uaClient getService uaClientApplication</code>, or shortened: <code>uac gs uaca</code>. | ||
| + | The program responds with the name of the client application (""OPC Command-line Tool"), which will be used for registrations to GDS. If this is the first time the program is run, it also creates its self-signed client certificate. | ||
| − | uaClientApplication | + | All following commands are entered at the {{Style=label|uaClientApplication>}} prompt. |
| − | |||
<pre> | <pre> | ||
| Line 27: | Line 27: | ||
</pre> | </pre> | ||
| + | |||
| + | You can check the parameters of the client instance certificate by entering <code>getInstanceCertificate</code>, or shortened: <code>gic</code>. | ||
| + | |||
| + | If you want to force the application to generate a new self-signed client certificate, you can do so by entering <code>removeInstanceCertificate</code>, or shortened: <code>ric</code>. This might be useful e.g. for repeated testing against a GDS, if you have already received a client certificate from GDS (signed by a certificate authority), and want to revert to the initial state. At the next OPC UA operation, the application will generate a new self-signed certificate for itself, and use it for subsequent operations. | ||
Revision as of 20:53, 14 January 2021
Example:
At the OpcCmd> prompt, enter uaClient getService uaClientApplication, or shortened: uac gs uaca.
The program responds with the name of the client application (""OPC Command-line Tool"), which will be used for registrations to GDS. If this is the first time the program is run, it also creates its self-signed client certificate.
All following commands are entered at the uaClientApplication> prompt.
rtg opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo registerToGds opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer --EndpointUser appadmin:demo findGdsRegistrations opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo obtainNewCertificate opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo refreshTrustLists opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo refreshTrustLists opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo unregisterFromGds opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo removeInstanceCertificate
You can check the parameters of the client instance certificate by entering getInstanceCertificate, or shortened: gic.
If you want to force the application to generate a new self-signed client certificate, you can do so by entering removeInstanceCertificate, or shortened: ric. This might be useful e.g. for repeated testing against a GDS, if you have already received a client certificate from GDS (signed by a certificate authority), and want to revert to the initial state. At the next OPC UA operation, the application will generate a new self-signed certificate for itself, and use it for subsequent operations.
