Minutes of SupportDB Internal Meeting

Date:12/2/98

Present:

OverView of Database Access Methods

Everything inherits from a D0 object
D0 objects know how to archive themselves from and to:
- Files (DSPack)
- Msql
- Oracle (desired but not implemented?)

IDL used to specify Calibration Objects and Database Definitions
Code is parsed by a generator
- Generated code uses OCI to talk to Oracle
- Generated code 'managed' by a template class

CDF and D0 are solving different problems, it is not surprising they have different solutions despite the apparent similarity of the D0 SAM Server and the CDF Calibration Server
IDL is inadequate for modeling all of the problems we are interested in.
Unclear which ORB is best for what application
Can we actually implement all of this in time for it to be a wise use of resources
One view of SAM Server Architecture

This is a conceptual view of how the existing SAM Server could be generalized into a more generic server.
Another view of SAM Server Architecture

The existing SAM Server can be divided into components, to implement the previous diagram.
A View of the CDF Calibration Code Generating Architecture
This has been prototyped by CDF
- Very specific to CDF Calibration Database Schema
- Makes lots of simplifying assumptions so IDL works as modeling language
- Needs run information from a "Higher Level", such as what SAM is to provide D0

Determine if problems with C++ exceptions are real or artifacts of the benchmark programs. (Jim K.)
Adapt D0 Sam Server to serve up CDF Calibration object containers (Dennis B.)
Prototype an object server in Java to compare with existing python server (Dennis B.)
Identify a mapping language (IDL, ODL, Persistence, other) to make implementation of El Photo Grande possible.
Meet again in two weeks to discuss findings