RIB software, RIB patches, and RIB API
|
|
Getting the RIB Software
|
2007-03-27
|
Prerequisites
RIB v3.0 requires several applications to be installed prior to installing RIB itself. You will need the following:
1. A database, currently MySQL
2. A servlet container, currently Tomcat
3. JDK
Also on any client machine that will use the RIB Java administration applet, you will need a web browser and the Java plugin. Typically these will already be present. To download the RIB software, please fill out the form below and then press the "Download RIB" button below the form. All information supplied in the form is kept stricly confidential.
RIB v3.0 installation instructions are included in the RIB archive and can be viewed at the following link: http://icl.cs.utk.edu/rib/custom/index.html?lid=41&slid=158
Additional information on using RIB, FAQ's and publications are available from the RIB web site: http://icl.cs.utk.edu/rib/
Beta3 includes the following updates since the release of the first beta:
- fixed the bug of incorrect counting of catalog objects
- fixed the bug of inconsistency between the cached config file and the actual config file on UNIX platform
- fixed the bug of random organization of rows and columns in the join matrix, rows and columns are now sorted according to the object names
|
|
|
|
RIB v2.x
|
2003-11-20
|
RIB v2.1.2 is available in source form. New features for RIB 2.1.2 include updated versions of all of RIB's components, including Perl, Apache, and MySQL. MySQL is now built as part of the distribution. Also new in this release is file upload and download ability. Be sure and get the patches for v2.1.2 and v2.1. RIB version 2.2 includes Apache version 2.0.47, MySQL version 4.0.14, and Perl version 5.8.0. When using this version you should check the vendors web site for any known security issues. RIB version 2.1 includes Apache version 1.3.12, MySQL version 3.23.24, and Perl version 5.6.0. When using this version you should check the vendors web site for any known security issues. RIB 2.1 has two components: a server and an administration interface. The server can be installed on most UNIX and Windows platforms. It contains the database that maintains your repository metadata and provides access to that data via the HTTP protocol. The administration interface runs in a web browser and requires version 1.1.2 of the Java plugin from Sun Microsystems. It is used by a repository maintainer to enter and manage metadata. The ideal configuration is to run the RIB server on a fast UNIX machine with a good network connection and to run the administration interface from a PC web browser, preferably Internet Explorer version 5 or greater.
|
|
|
|
RIB Patches
|
2003-06-30
|
- Improved interoperation feature
Being able to create/update "usable" interoperation objects in each local class Being able to include interoperation objects in the final join matrix Being able to recursively import objects that are related to one another - Modified file upload feature
Made the file upload procedure more user friendly Fixed the major bug of not being able to change the data model and some other minor bugs RIB v2.1.2 patch for Unix | RIB v2.1 patch for Windows
|
|
|
|
RIB API
|
2003-05-30
|
In the standard distribution of RIB, a repository administration Java applet and an HTML catalog serve as the default mechanisms for accessing the data objects stored in a RIB repository. The repository administration applet is primarily used for data entry and the HTML catalog is used for presentation of that data. The RIB Application Programmer's Interface (API) provides a specification that allows third party programs to access the data objects stored in RIB independently of those default mechanisms. Using the RIB API, application developers can interface existing programs to RIB or design new interfaces in circumstances where the current ones prove inadequate. The RIB API appears as a low-level network based API (Level 1 API). It provides network access to the underlying function calls in RIB. The arguments to those function calls are described in the API but must be constructed by the application developer. It is highly recommended that the API be tested in your environment using a test repository before using with a production repository. The API was written prior to several new features (eg., file upload capability) being added to the software and the API has not been tested since these features were added. The Level 1 API document is available via MS Word and in HTML. There are three reference implementations: C, Java, and Perl. Updated API for use with RIB version 3.0: C, Java, Perl.
|
|
|
License
Copyright © 2012 The University of Tennessee. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
· Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
· Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer listed in this license in the documentation and/or other materials provided with the distribution.
· Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. in no event shall the copyright owner or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.