Eurostat Unit B3 – IT and standards for data and metadata exchange SDMX for IT Experts NSI Web Service Jorge Nunes Raynald Palmieri 18-20 February 2014 Eurostat Unit B3 – IT and standards for data and metadata exchange

Table of Contents NSI Web Service NSI Web Service overview. The web service provider.

SDMX-RI Components MSDB Store DDB Firewall Firewall Firewall DB Server       DB Server MSDB Store Workstation App Server Mapping Assistant NSI-WS External Client Test Client NSI-Client DB Server DDB Internal Network Secure DMZ DMZ Internet

NSI Web Service Input Output SOAP (SDMX Query): Soap message including the SDMX Query inside. Output SOAP (SDMX-ML Dataset): Soap message including the SDMX-ML Dataset. Input SOAP (SDMX Query): Soap message including the SDMX Query inside. Output SOAP (SDMX-ML Dataset): Soap message including the SDMX-ML Dataset.

SDMX-RI web services overview web service provider query parser data retriever structure retriever data generator Dissemination Database Mapping Store DB 5

Versions of NSI Web Service Java version. Requires JEE servlet container: Tomcat, Weblogic. .NET version Requires Microsoft IIS. In case the developer does not wish to change or even observe the source code of the “Web Service Provider” it can be used as service reference. The "Web Service Provider" could be located anywhere as long as the caller has http access to it. Web Service Provider module is a building block that can be re-used within any dissemination environment requiring its functionality. In case it is re-used as a package, SDMX internal model has to be attached to the API since the output created is on SDMX Query instance with the structure of the internal SDMX Model. *The "Web Service Provider" component is released as open-source software (OSS), thus it can be either re-used as is (as a packaged) or by using its source code (in case modifications are needed).

Web Service Solution Mapping must be already configured STEP 1 Load SDMX Structures (CategoryScheme, DataFlow, DSD) STEP 2 Map local database schema (Dataset) STEP 3 Map local Concepts to SDMX ones (Mapping Set) STEP 4 Map local Codes to SDMX ones (Transcoding) 7

NSI Web Service Example hands-on following the instructions of the documentation provided. 8

SDMX-RI Web Services Evaluation 1. Which of the modules has the capacity to connect to the data bases? The Data Retriever The Query Parser SDMX Data Model SDMX Data Generator 2. Can this modules work independent each other? No, we need the four modules and the SDMX Model as it is to make a complete solution. Yes, we can take each module independent and use it for different projects but not changing the source code itself. Use one of the modules implies to use the others because the output and input parameters are related between the different modules. Any of the answers is correct. 3. Where is the XML data file (dataset) created? Query Parser module. Data Generator module. Data Retriever module. The user has to create a client application to convert any output of the solution to a XML data file. 4. If any of the source codes of the modules is changed and we want to create a complete solution with all of them… We can create a SDMX Internal Model to use it as parameter between the modules. The SDMX Intermal model already created must be used. We don’t need to use nothing else than the four modules, and all the other parameters are normal .NET objects.