Reference server + CTT configs should advertise the correct ServerProfileArray
Both
Applications/ConsoleReferenceServer/Quickstarts.ReferenceServer.Config.xml
and
Applications/ConsoleReferenceServer/Ctt.ReferenceServer.Config.xml
currently advertise only five facets in ServerProfileArray:
<ServerProfileArray>
<ua:String>http://opcfoundation.org/UA-Profile/Server/StandardUA2017</ua:String>
<ua:String>http://opcfoundation.org/UA-Profile/Server/DataAccess</ua:String>
<ua:String>http://opcfoundation.org/UA-Profile/Server/Methods</ua:String>
<ua:String>http://opcfoundation.org/UA-Profile/Server/ReverseConnect</ua:String>
<ua:String>http://opcfoundation.org/UA-Profile/Server/ClientRedundancy</ua:String>
</ServerProfileArray>
The reference server now genuinely implements many more facets — see
Docs/Profiles.md and
Docs/WhatsNewIn2.0.md. The CTT
configuration in particular should advertise the additional facets
that the CTT will exercise so the report covers them.
Acceptance criteria
- Audit which facets the reference server genuinely supports in each
of the two configurations (Quickstarts vs CTT), drawing on the
Functional Facets section of Docs/Profiles.md. Candidate
additions include (but are not limited to): Historical Raw Data,
Aggregates, Alarms & Conditions, Standard Event Subscription,
File Access, Auditing, Node Management, State Machine.
- For each candidate facet, verify the canonical OPC Foundation URI
on https://profiles.opcfoundation.org/ (do not fabricate
URIs — CTT will test against whatever is claimed).
- Add the verified URIs to
ServerProfileArray in both configs,
matching the actual capabilities of each (the CTT config exercises
more than the default Quickstarts profile).
- Once advertised, run UACTT against the updated configs and update
the certification report.
- Update
Docs/Profiles.md to (a) list the additional URIs the
reference server advertises and (b) drop the "look up the URI on
profiles.opcfoundation.org yourself" workaround that the
Configuration section currently has.
Notes
- The doc currently calls this out as an open follow-up; this issue
tracks closing it.
Reference server + CTT configs should advertise the correct
ServerProfileArrayBoth
Applications/ConsoleReferenceServer/Quickstarts.ReferenceServer.Config.xmland
Applications/ConsoleReferenceServer/Ctt.ReferenceServer.Config.xmlcurrently advertise only five facets in
ServerProfileArray:The reference server now genuinely implements many more facets — see
Docs/Profiles.mdandDocs/WhatsNewIn2.0.md. The CTTconfiguration in particular should advertise the additional facets
that the CTT will exercise so the report covers them.
Acceptance criteria
of the two configurations (Quickstarts vs CTT), drawing on the
Functional Facets section of
Docs/Profiles.md. Candidateadditions include (but are not limited to): Historical Raw Data,
Aggregates, Alarms & Conditions, Standard Event Subscription,
File Access, Auditing, Node Management, State Machine.
on https://profiles.opcfoundation.org/ (do not fabricate
URIs — CTT will test against whatever is claimed).
ServerProfileArrayin both configs,matching the actual capabilities of each (the CTT config exercises
more than the default Quickstarts profile).
the certification report.
Docs/Profiles.mdto (a) list the additional URIs thereference server advertises and (b) drop the "look up the URI on
profiles.opcfoundation.org yourself" workaround that the
Configurationsection currently has.Notes
tracks closing it.