SAM Architecture/Components

• A file and event catalog.
• A suite of servers which together interoperate to receive requests from the end user, resolve the requests into lists of files to be accessed, perform global i/o resource optimization and regulation, log all 'events' in the system, interact with the database to record interesting facts and status and to recover context on startup.
• User code to specify the mode of access and the data to be accessed (read) as a 'Project Definition', to resolve this definition into files, and to gain access to the data. User code to write files to be cataloged by SAM and written to tape (when required).
• User/Administrator code to configure and run the system and provide information and statistics about progress of individual projects, users, or the entire system.

Development of the SAM System involved creating embryonic components for all parts of the system.  SAM is currently divided into numerous small cvs packages. Some of these packages contain only the interface definition (IDL) between components of the system.
 

cvs package	description	code exists	comments
sam	umbrella package - allowing users to setup one product and get a host of others setup for them. See ups dependencies for what it sets up.	x	V1 Released.
sam_doc	Documentation and web pages, currently served up as web site. Not really used by individual users. See the SAM Home Page for sam_doc contents.	x	V1 Released.
sam_optimizer	global regulator and optimizer of Enstore jobs	x	random-wait to authorize Entore job submission
sam_station	suite of 3 different servers assoc. with a station: Project Master, Stager, Station Master(dummy).	x	Cutting for V1.
sam_logger	logs systemwide 'events', for debugging and for detailed rate and latency information.	x	Socket interface
sam_db_server	provides read/write access to database	x	V1 Released.
sam_info_server	provides summary (and raw) information from log file and from database.	x	only uses log file currently
sam_user	user libraries, example code and scripts for accessing physics data, defining and starting projects, storing files and getting information about a particular user/consumer or project.	x	Cutting for V1.
sam_project_editor	Web available Java GUI for creating project definitions, point-in-time sets of files for the definitions called project snapshots and analysis projects. To see it in action, see SAM web site.	x	V1 Released.
sam_monitor	Java Application to display system state, throughputs and latencies from log file. Used by SAM administrators.	x	(Initially called 'sam_admin', but not any longer!).
sam_admin	A suite of utilities to assist sam administrators and shifters with various tasks, including: making standard plots of SAM statistics, maintaining the autodestination map, registering new users, nodes, or stations, etc.	x
sam_test_harness	scripts to set up a test configuration, test user loads and check/report functioning of system	x	Captured SC98 test suite scripts
sam_farm	specialized farm interface scripts
sam_db	file and event catalog definition and creation	x	V1 Released.
sam_db_package	database stored procedures (PL/SQL)	x	V1 Released.
sam_db_admin	web forms to maintain the relatively static supporting tables in the db, deployed on the SAM Db Admin web site.	x	V1 Released.
db_server_gen	Code to generate db server base level code for tables based on dictionaries.	x	V1 Released.
sam_config	data files related to the startup of the system, naming service bootstrap, etc.	x	Naming Service IOR lives here
sam_util	some utility libraries used by more than one component of SAM	x
sam_db_server_idl	interfaces implemented by sam_db_server	x
sam_station_idl	interfaces implemented by sam_station servers	x
sam_info_server_idl	interfaces implemented by sam_info_server	x
sam_optimizer_idl	interfaces implemented by sam_optimizer	x

For more details on the role and contents of each package, click here.

For more information, contact sam-design@fnal.gov