This page collects the resources for Service Metadata Locator (SML) version 3.0, released in September 2016.
The Directorate-General for Informatics (DIGIT) is happy to announce the upgrade of the sample implementation of the SML software in order to fully support the CEF eDelivery SML specification. In version 3.0.0, the SML will also provide support for the e-SENS BDXL profile, as well as the PEPPOL SML specification. As the PEPPOL SML specification continues to be supported, current users of the SML software shouldn't suffer of any disruption of service. For each existing participant, an additional NAPTR record will be created. The SML managed service offered by DIGIT uses this sample implementation and therefore benefits from its features.
The SML 3.0.0 new release includes:
- Adds support for e-SENS BDXL specification
- Enhances compliance with PEPPOL SML specification
- Creates U-NAPTR and CNAME records for each participant
- Enables support for multiple business domains
- Enhances users and roles management
- Adds a new service to allow SMP to change their certificate
- Adds a new service to list all participants
This new version of this SML sample implementation is also known as Business Document Metadata Service Location application (BDMSL). It is released with additional documentation which can be found below.
This document covers the service interface of the CEF eDelivery SML sample implementation. It includes information regarding the description of the services available, the list of use cases, the information model and the sequence of message exchanges for the services provided.
This document is the Software Architecture document of the CEF eDelivery SML sample implementation. It intends to provide detailed information about the project: an overview of the solution, the different layers, the principles governing its software architecture
This document provides a brief description of the installation of the SML sample implementation component on a Tomcat/MySQL environment
European Union Public Licence
Known issues and limitations
- CRL verification on Tomcat can be improved
- The proxy configuration can be improved
- The list of valid codes for the default scheme should be externalised
- No restrictions on the minimum length and format of migration keys