High Performance OPC UA Server SDK
1.5.0.296
|
This section describes compliance certification and how to use the CTT with the HP SDK.
The OPC Foundation does not allow to certify SDKs directly, so the HP SDK itself cannot be certified and an application is not certified automatically because it is built with a certain SDK. Only final products can be certified by the OPC Foundation, for this reason we can only certify our demoserver built with the SDK to proof that it is possible to develop a compliant application using the SDK. The SDK handles a lot of the CTT testcases, so applications built with the SDK will pass most testcases automatically, however a few subjects like data handling must be implemented in every application individually and thus each application must be certified individually.
The demoserver of the HP SDK is not yet certified, however as of version 1.5 applications may have a chance to get certified up to the Standard 2017 UA Server Profile.
None of the HP SDK example clients are certified and there are currrently no plans to do so.
The CTT is the Compliance Test Tool provided by the OPC Foundation and the main factor of the certification. It can be downloaded from the OPC Foundation website by members to run before certification themselves. The following sections explain how to use the CTT with the HP SDK demoserver, which might be used as base for own certfifications.
This documentation applies to CTT 1.04.9.396, other versions of the CTT may yield different results.
The standard profile is the biggest of the full featured server profiles. A configuration for the demoserver that can be loaded in the CTT (see Configuration of the CTT) is provided here. In the CTT Profiles tab Standard 2017 UA Server must be selected.
The server must be started with the configuration file settings_standard.conf included in the SDK:
uaserverhp -c settings_standard.conf
The micro embedded profile is a rather small one of the full featured server profiles, it requires support only for few subscriptions and does not require UA Security. A configuration for the demoserver that can be loaded in the CTT (see Configuration of the CTT) is provided here. In the CTT Profiles tab Micro Embedded Device 2017 Server must be selected.
The SDK includes the settings_micro.conf which sets quantities according to the Micro Embedded Profile, however some of the CTT scripts were not written with such limited servers in mind an will falsely report errors. To make certification easier we provide a second configuration file settings_micro_ctt.conf, which is based on the above settings file but increases a few limits:
uaserverhp -c settings_micro_ctt.conf
In case the selected profile includes UA Security a few more steps are required:
copyToServer | bin |
---|---|
ApplicationInstance_PKI | pki_store_0 |
–trusted | –trusted |
—crl | —crl |
—certs | —certs |
–issuers | –issuer |
—crl | —crl |
—certs | —certs |
X509UserIdentity_PKI | pki_store_user |
–trusted | –trusted |
—crl | —crl |
—certs | —certs |
–issuers | –issuer |
—crl | —crl |
—certs | —certs |
There are a few testcase failing which we believe are errors in the test scripts, these isssues are reported to the OPC Foundation and will be fixed in future versions of the CTT. Depending on the configuration of the server and the exact setup of CTT and server these may or may not happen during a specific CTT run, some are sporadic and may happen only every n-th run. The following list includes links to the mantis bug tracker of the OPC Foundation, so people with an account can view them in detail, others may still provide the link during certification to reference a specific issue.