candidate CMS applications for participation of 3D service and requirements (part I)

Applications

• Framework( COBRA/CARF) metadata

• Configuration and setup (in COBRA/CARF) data
  

• file catalog and collection catalog. Could be distributed by 3D but not certain: depending on CMS event-data management model which is still to be defined by the CMS data management group. So no requirement collected.
  

Requirements on data distribution from COBRA metadata

• require entire server replication. Can be of the same technology.
  

• require distribution of  tables between databases.  Support copying tables between databases with the same and different technologies.
  

• require replicating part of a table between databases.  Support copying selected part of the table between databases with the same and different techologies.

• The basic tables will contain just C++ type string(mostly used), int, double. Clear definition of mapping of these C++ types on different database technologies (this might be on the application side)  and how to handle them when replicating data across different technologies is required.

• In particular for the string type: the case and length of the string data must be preserved during replication and distribution. String truncation and case changes are not allowed no matter the replication is across technology or not.