Functional tests of a prototype for the CMS-ATLAS common non-event data handling framework

Since the 2014 the experiments ATLAS and CMS have started to share a common vision for the Condition Database infrastructure required for the forthcoming LHC runs. The large commonality in the use cases to be satisfied has allowed to agree to an overall design solution which could meet the requirements for both experiments. A first prototype implementing these solutions has been completed in 2015 and made available to both the experiments. The prototype is based on a web service implementing a REST api with a set of functions for the management of conditions data. The objects which constitute the elements of the data model are seen as resources on which CRUD operations can be performed via standard HTTP methods. The choice to insert a REST api in the architecture has several advantages: 1) the conditions data are exchanged in a neutral format ( JSON or XML), allowing to be processed by different technologies in different frameworks. 2) the client is agnostic with respect to the underlying technology adopted for the persistency ( allowing RDBMS and No-SQL back-ends) The implementation is using standard technologies available in Java for server based applications. This choice has the benefit to easy the integration with the existing java-based applications in use in both experiments, notably the FronTier service in the distributed computing environment. In this contribution, we describe the tests of this prototype performed within the CMS computing infrastructure, with the aim to prove the support of the main use cases and to suggest future improvements. Since the Data Model reflected in this prototype is very close to the layout of the current CMS Condition Database, the tests have been possible with the existing condition data, with no additional manipulation. The strategy for the integration of the prototype has consisted in replacing the inner Condition Database software layer with a plugin capable of accessing the web service and to decode the retrieved the data into the appropriate object structures used in the CMS offline software. This strategy has been applied to run a test suite on the specific physics data samples, used by the experiment for the software release validation