"Embedded 2017 UA Server Profile" Profile

 Description This Profile is a FullFeatured Profile that is intended for devices with more than 50 MBs of memory and a more powerful processor. This Profile builds upon the Micro Embedded Device Server Profile. The most important additions are: support for security via the Security Policies and support for the Standard DataChange Subscription Server Facet. This Profile also requires that Servers expose all OPC-UA types that are used by the Server including their components and their super-types. This profile supersedes the "Embedded UA Server Profile".
 URI http://opcfoundation.org/UA-Profile/Server/EmbeddedUA2017

This page lists the conformance units of the selected profile with their name and description.
Conformance units that are inherited via included Profiles are not listed by default. Use the following radio buttons to change this default behaviour.

Base Information
Include  Name Opt.  Description  From Profile  Test Cases
Base Info Type System The Server exposes a Type System with DataTypes, ReferenceTypes, ObjectTypes and VariableTypes including all of the OPC UA (namespace 0) types that are used by the Server, as defined in Part 5. Items that are defined in Namespace 0 but are defined in other specification parts are tested as part of the other information models.   Open
Base Info Engineering Units The Server supports defining Variables that include the Engineering Units Property. This property makes use of the EUInformation data structure. This structure by default represents the UN/CEFACT "Codes for Units of Measurement". If a different EU representation is required then the EUInformation.namespaceUri will indicate the alternate namespace.   Open

Include  Name Opt.  Description  From Profile  Test Cases
Security Default ApplicationInstance Certificate An application, when installed, has a default ApplicationInstanceCertificate that is valid. The default ApplicationInstanceCertificate shall either be created as part of the installation or installation instructions explicitly describe the process to create and apply a default ApplicationInstanceCertificate to the application.   Open
Security – No Application Authentication The Server supports being able to be configured for no application authentication, just User authentication and normal encryption/signing:
– Configure Server to accept all certificates
– Certificates are just used for message security (signing and encryption)
– Users level is used for authentication
Security Policy Required Support at least Security Policy [A] and Security Policy [B].
Support of multiple Security Policies - even obsolete ones - is recommended. This will provide best interoperability and allows the end user to choose the required level of security.
Obsolete Security Policies shall not be enabled / usable without administrative intervention.