OPC UA Client Application Operations in OpcCmd: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Example: | Example: | ||
If you execute the commands listed in the example below, you will get an overview of available client operations. | If you execute the commands listed in the example below, you will get an overview of available client application operations. | ||
# At the {{Style=label|OpcCmd>}} prompt, enter <code>uaClient getService uaClientApplication</code>, or shortened: <code>uac gs uaca</code>.<br/>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.<br/>All following commands are entered at the {{Style=label|uaClientApplication>}} prompt. You can enter <code>-?</code>, <code>-h</code> or <code>--help</code> (possibly preceded by the command name) at any time to obtain help for this prompt (or its commands). | # At the {{Style=label|OpcCmd>}} prompt, enter <code>uaClient getService uaClientApplication</code>, or shortened: <code>uac gs uaca</code>.<br/>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.<br/>All following commands are entered at the {{Style=label|uaClientApplication>}} prompt. You can enter <code>-?</code>, <code>-h</code> or <code>--help</code> (possibly preceded by the command name) at any time to obtain help for this prompt (or its commands). | ||
| Line 7: | Line 7: | ||
# <code>findGdsRegistrations opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo</code> (<code>findGdsRegistrations</code> can be shortened to <code>fgr</code>). | # <code>findGdsRegistrations opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo</code> (<code>findGdsRegistrations</code> can be shortened to <code>fgr</code>). | ||
< | <code>obtainNewCertificate opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo</code> | ||
obtainNewCertificate opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo | |||
? | ? | ||
refreshTrustLists opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo | <code>refreshTrustLists opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo</code> | ||
<code>unregisterFromGds opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo</code> | |||
</ | <code>removeInstanceCertificate</code> | ||
# You can check the parameters of the client instance certificate by entering <code>getInstanceCertificate</code>, or shortened: <code>gic</code>. | # 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. | # 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 21:07, 14 January 2021
Example:
If you execute the commands listed in the example below, you will get an overview of available client application operations.
- 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. You can enter-?,-hor--help(possibly preceded by the command name) at any time to obtain help for this prompt (or its commands). registerToGds opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo(registerToGdscan be shortened tortg).findGdsRegistrations opc.tcp://opcua.demo-this.com:58810/GlobalDiscoveryServer -eu appadmin:demo(findGdsRegistrationscan be shortened tofgr).
obtainNewCertificate 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.