1. C. Aiftimiei- December 2003 ALICE DCDB @ NIPNE-HH Cristina Aiftimiei caifti@tandem.nipne.ro National Institute for Physics and Nuclear Engineering - Horia Hulubei dracula.nipne.ro & TYPO3

2. C. Aiftimiei- December 2003 Web site: dracula.nipne.ro

3. C. Aiftimiei- December 2003 dracula.nipne.ro & TYPO3  What is TYPO3? OTYPO3 is a Content Management System  What is a CMS? Ois a software, usually a database application, that will make it easy to create and maintain websites and manage all publishing formats associated with the World Wide Web  Much for nothing OTYPO3 is licensed under GNU/GPL. Therefore, TYPO3 requires no license costs unlike its commercial competitors. Noone keeps the best ideas for themselves which insures that wheel is not invented twice.  Large developer community O TYPO3 has a large world wide community of developers with clients from all types of business branches securing its continual development of any additional modern requirements of a CMS.

4. C. Aiftimiei- December 2003 TYPO3 - www.typo3.org  To cut a very long story short: TYPO3 is a web- application based on PHP and MySQL; it has everything you need for doing nearly everything you want to do on the web.

5. C. Aiftimiei- December 2003 dracula.nipne.ro & TYPO3 - examples (1)

6. C. Aiftimiei- December 2003 dracula.nipne.ro & TYPO3 - examples (2)

7. C. Aiftimiei- December 2003 ALICE DCDB @ NIPNE-HH Thanks to Wiktor Peryt and Tomasz Traczyk, Warsaw University of Technology

8. C. Aiftimiei- December 2003 ALICE DCDB - General Information  The DCDB project - conceived in the framework of the ALICE experiment.  Goal: to produce a database system and application environment for use in the initial construction of sub-detectors for ALICE and later to facilitate the operation of the completed ALICE detector.  Work on design of the general architecture of DCDB started at the beginning of 2001. Warsaw ALICE database group and the ALICE off-line project are in charge of the overall activities of the project.  The ALICE sub-detector construction is distributed among many European labs, also in USA and India. This is a specific task, related to tests of detector components, measurements of their properties and final assembly.  The movements of the sub-detector components between manufacturers and laboratories during various phases of the production; the physical location of the components with the proper ownership and related data - are data that have to be traced and stored in the database.  Component tests and measurements will produce large amounts of data - that need to be stored in the database for further analysis and use. The data comes directly from test benches with software based on the LabView suite. The most convenient and reliable solution should assure undisturbed, direct population of the database with these data, I.e without intermediate storage as disk files.

9. C. Aiftimiei- December 2003 DCDB Architecture Central database Satellite databases Central database: Placed at CERN (temporarly placed at WUT). Plays role of central repository Contains: - central inventory of components - copies of data from laboratories - metadata (e.g. dictionaries) Satellite databases: Placed in laboratories-participants Contain: - source data u produced at laboratories u delivered by manufacturers - working copies of data from central repository - partial copies of metadata (read-only) Communication: Passing messages in XML Mainly off-line (batch-processing) No satellite-satellite communication! Request-response model (like HTTP): - only satellite database can initiate communication

10. C. Aiftimiei- December 2003 Central database - satellite databases Central database – Usage characteristics very large data volume many concurrent users twenty-four-hour utilisation critical data (breakdown may be very costly) – Necessary features transaction processing 7 × 24 availability high reliability continuous administration by professional DBA team on-line backup data partitioning – Proper solution high-end commercial DBMS software is necessary Satellite databases – Usage characteristics average or small data volume only few concurrent users used only few hours per day not critical data (can be restored from backup or from central database) – Necessary features transaction processing should not need complex administration (no trained personnel at labs-participants) should be monitored remotely by developers off-line backup procedures are sufficient data may not need to be partitioned should not be costly! – Proper solution open-source database can be used

11. C. Aiftimiei- December 2003 Proposed technology – Central database Oracle RDBMS Advantages very stable and reliable built-in procedural language support for complex data types and BLOBs support for VLDB (very large databases), e.g. data partitioning 7 × 24 availability (on-line backup, etc.) Disadvantages quite expensive complex and difficult to administer – Satellite databases PostgreSQL Advantages free of charge quite easy to administer stable enough built-in procedural languages support for complex data types and BLOB objects Disadvantages not very fast (but fast enough for this particular application) no support for distributed processing (data replication, etc.) no support for heterogeneous systems no support for VLDB no 7 × 24 availability

12. C. Aiftimiei- December 2003 Satellite Database – data structures Dictionaries  Maintained in central repository  Supplied from central database to labs  Read-only in satellite databases

13. C. Aiftimiei- December 2003 Satellite Database – data structures Components’ data  Created and updated in satellite databases at labs  Copied to central repository

14. C. Aiftimiei- December 2003 Satellite Database – examples