What is the Downloadable EVE-Demo?

• View synchronization after schema changes
• Quality and Cost of View Rewritings
.

In addition to the functionality presented there, this version of the EVE-Demo also include a computation of the QC-Value of a view. After each view synchronization, you see a list of all possible view rewritings for each view defined in the system (cf. Figure 1). You can also see the composition and final value for the QC-Value in each case. In order to proceed, you need to select a version for each view and the press the OK button. The rewriting (version) you have picked will be used and you can review its effect on the view extent in the later screens.

Figure 1: The QC-Value Screen.

Disclaimer!

System Requirements

• A sufficiently fast machine running Java 1.1.2 or later (on PCs, a Pentium 166 should do.)
• A database server that is reachable from the Java-capable machine. Currently, we support only Oracle Server and MS Access. We have two packages, prepared to run with (only) Oracle database or (only) Access databases. You can use both together (since it's a distributed database system) if you edit the configuration files (MKB.release)
• A JDBC-driver that connects to the Oracle database (normally, this is a file called classes111.zip that is somewhere in your Java-classpath). This file is not available online anymore, but rather resides somewhere in your standard Oracle installation (in a directory that may look something like ./oracle/product/8.1.5/jdbc/lib).

or
• The Microsoft ODBC-package (check for ODBC32 in your Control Panel) with a working driver for MS Access 97.

Installation (Oracle-Version)

1. Download the archive file.
2. Unzip and untar the archive into a directory (e.g., by gtar -zxvf EVE_Code.release.tar.gz). If you are on a Windows machine, you can unpack the archive using WinZIP.
3. Create a database account for EVE and create the tables necessary for the demo using eve_makefile.sql. In SQLPlus* for Oracle, you need to type @eve_makefile on the command line.
4. Edit MKB.release in the main directory. Change the connect strings in the database definitions to your requirements. You need the database server name, port number (generally 1521 or 1526 under Oracle), instance name, username, and password.
5. Edit eve.properties to the same information (this is necessary for the demo to run without requiring you to reset the database manually after each system start).
6. If you have problems with paths and/or libraries (you need the classes111.zip library from Oracle that is packaged with any Oracle instance), edit starteve to suit your needs.
7. Run the system by running the starteve script (or starteve.bat on Windows NT/95).
8. Since EVE implements a distributed data warehouse, you may split the eve_makefile.sql file and distribute the tables according to their distribution into information sources (cf. MKB.release file) if you have more than one database server or account. You need to adapt the connect information in MKB.release accordingly. Note that the automatic reset using reset.sql may not work properly in that case and you may have to reset the tables by hand if you do any schema changes in EVE.

Installation (MS Access-Version)

1. Download the archive file.
2. Unzip the file somewhere using WinZIP or a similar software.
3. Create two ODBC Connections using the ODBC-Program in your Control Panel. Their names should be LOCAL and ACCESS and they should point (click on SELECT) to the files local.mdb and evedemo.mdb in the top directory of the archive you have just unpacked. Do not delete the *bak.mdb-Files as they are needed for resetting the database.
4. Edit MKB.release in the main directory. Change the connect strings in the database definitions to your requirements. You need the database server name, port number (generally 1521 or 1526 under Oracle), instance name, username, and password.
5. If you have problems with paths and/or libraries, make sure that you're running Java 1.1.x. The demo should work on Java 1.2 if you add the old classes.zip library to the classpath (since we are using Swing classes under the 1.1-classpath), but this has not been tested under Windows.
6. Run the system by running starteve.bat.
7. Since EVE implements a distributed data warehouse, you may distribute the tables according to their distribution into information sources (cf. MKB.release file) if you have more than one database file. You need to adapt the connect information in MKB.release accordingly. Note that the automatic reset using resetdb.bat may not work properly in that case and you may have to reset the tables by hand if you do any schema changes in EVE.

Troubleshooting

If the demo crashes before you see any windows on the screen, your databases may not connect properly. Check if they are active (ODBC-Test or login to Oracle with SQLPlus*) and if the correct database names and connect information is in the MKB.release-file. Note that you have to give the Type of a database in that file. The code for Oracle is ORACLE, for Access it's MS_ACCESS (with an underscore), both are case-sensitive.

If you have trouble with Java versions, try to recompile the demo. Also, the demo has been written using Swing-Classes from the Java-1.1-Version, and therefore will not work immediately under Java 1.2. You can try to add an old classes.zip file to your classpath (works on Linux at least) or you may have to change all the import-statements in the source files.

You may also have to re-create the MKB-file parser using mkMKBParser. For this to work, you need running versions of the JavaTreeBuilder (jtb 1.2) and JavaCC (Version 0.8pre1 or later). Then, you can recompile EVE using makeeve(.bat). You may have to edit that file according to your requirements.

The (JavaDOC) documentation is available in the html directory and can be (re-)generated using the makedoc file if you have javadoc working on your system. You can also access the javadoc files directly from this webpage.

If you still have problems, let us know.