Repository In A Box (RIB)

Transcription

1 Repository In A Box (RIB) August 18, 2003 Yuanlei Zhang To Be Covered» Brief overview of RIB» The RIB patches» RIB v2.2 The last Perl version release» RIB v3.0 Java version release 1

2 RIB History & Overview» RIB was developed (started in 1995) here at ICL to provide a toolkit for building and maintaining metadata repositories. It was an original product of the NHSE effort to promote software reuse within and between the federal government HPC agencies (eg., NASA, DoD, DoE, etc).» Primary Design Goals» Promote software reuse» Provide Interoperability RIB History & Overview cont.» Primary functions» Tools to build metadata repositories» Browseable, searchable HTML catalog» Centralized access for software information» Metadata based on IEEE standard for software cataloging on the Internet» Metadata encoded using XML» Interoperability» 2 or more repositories able to share information» Hierarchy provides common access point» Uses Basic Interoperability Data Model (BIDM)» Additional interoperability via RIBAPI 2

3 RIB Components RIB Server RIB Client Java Applet HTML HTTP Apache Perl MySQL The RIB Patches» New features Improved interoperation feature: Being able to create/update "usable" interoperation objects in each local class Improved join feature: Being able to include interoperation objects in the final join matrix Improved import feature: Being able to recursively import objects that are related to one another Modified file upload feature: Made the file upload procedure more user friendly Bugs fixed: Fixed the major bug of not being able to change the data model and some other minor bugs» To be applied to RIB for UNIX RIB 2.1 for Windows 3

4 RIB v2.2» The last Perl version release» Changes upon the previous version Updated RIB components (check with Don) Perl MySQL Apache Perl modules Integrated with the RIB patch OAI support» RIB v2.2 for UNIX is released and we are still working on the windows release RIB v3.0» Why re-write RIB in Java» What the Java version release would be like» How to implement» When things are expected to be done» Who is involved 4

5 Why» Reduce installation complexity MySQL, Apache, Perl, Java, plus RIB code» Reduce code maintenance complexity Too many files in too many places currently» Improve Reliability When server crashes now, it is difficult to determine the cause, Perl scripts are tough to debug» Address user customization issues at the design phase Uni-code support, uploaded file management, different views for different users, etc. What» What the Java version RIB could be Tomcat + JRE + hsqldb/mysql + RIB jar file, if the user has none of these components A single RIB jar file, if the user has the environment properly setup to deploy web applications RIB jar file + instructions on how to obtain various components, if the user only misses some of the components or wants to use components other than the default» Ideally, the Java RIB would be able to work with any popular servlet container (default is Tomcat) and database system (default is hsqldb/mysql) 5

6 How» Development and testing environment Tomcat 4.1.* MySQL 4.0.*/hsqldb Servlet 2.3 JDK 1.4.* NetBean 3.0 CVS version control» The translation from Perl to Java Perl modules (.pm files) Regular Java classes Perl scripts (.pl files) Java servlets When» Rough estimate of the re-write timeframe 3 to 4 months initial coding 1 to 2 months testing/revision 1 month additional user documentation and creating setup routines 6

7 Who» PIs: Dr. Jack Dongarra Dr. Shirley Moore» Supervision: Scott Wells» Programmers: Nathan Garner Don Fike Mei Ran Yuanlei Zhang END QUESTIONS? 7