DBDependency - Download and Installation

1. Requirements

• JDK 1.2.2

  Get JDK 1.2.2 for your platform. I am using Blackdown's JDK 1.2.2 RC4.

• OpenJGraph

  Get the OpenJGraph release 0.7.0 for DBDependency 0.1.1. If you are using DBDependency 0.1.0, then use OpenJGraph 0.6.x. Extract the OpenJGraph archive. Should you decide to recompile the OpenJGraph sources, please read the README file distributed with the OpenJGraph archive.

• Apache Xerces-J

  DBDependency uses Apache's XML parser for Java to read and write its configuration. Extract the archive to a directory of your choice. I am currently using version Xerces 1.0.3, so get this version to make sure everything works okay. If you have success using other versions of Xerces-J, let me know.

• Oracle JDBC driver

  If you have Oracle JDeveloper 3.0, it already has the Oracle 8 and 8i JDBC drivers.

  If you have Oracle JDeveloper 2.0, note that the JDBC driver will not work against an Oracle8i Linux database, due to a bug with the drivers shipped with JDeveloper 2.0.

  If you have Oracle8i, use the JDBC drivers shipped with the Oracle8i database. You need to install this component using the Oracle Universal Installer.

• BEA WebLogic's MS SQL Server 6.5 JDBC driver

  I used WebLogic's Type 4 JDBC driver to connect to an MS SQL Server 6.5 database. For the connection to work, you must configure SQL Server to support TCP/IP connections, defaulted to port 1433.

  The JDBC-ODBC bridge will simply not work, because of a restriction that only allows one active result set per connection.

• Oracle database privileges

  The database user you will use to connect to the Oracle database from DBDependency must have SELECT privilege on the following views and its underlying tables: SYS.ALL_OBJECTS, SYS.ALL_USERS, and SYS.ALL_DEPENDENCIES.

  I believe that all users have SELECT privilege on these objects, but I would just like to point them out.

• MS SQL Server database privileges

  The database user you will use to connect to the SQL Server database from DBDependency must have SELECT privilege on the following tables: sysobjects, sysusers, and sysdepends.

  I believe that all users have SELECT privilege on these objects, but I would just like to point them out.

• X (for Linux and UNIX users)

  DBDependency is a Java Swing application, so you need X to be up and running.

2. Download

Alternatively, you may want to obtain the sources via anonymous CVS:

1. Export CVSROOT:

   export CVSROOT=:pserver:anonymous@cvs.dbdependency.sourceforge.net:/cvsroot/dbdependency

2. Then login:

   cvs -d$CVSROOT login

   When prompted for a password, simply press the Enter key.

3. Finally, do an export:

   cvs -d$CVSROOT export -r dbdependency-0_1_1 dbdependency

   If instead you used:

   cvs -d$CVSROOT co dbdependency

   ... the sources that you will be getting using checkout may include interim changes between releases, which may make or break your copy of DBDependency. So use export.

4. Logout:

   cvs -d$CVSROOT logout

3. Installation

1. Make sure that the user you will use to run DBDependency has read and execute privileges on all the installed softwre and libraries that are required as listed above.
2. Extract the DBDependency archive to a directory of your choice. The directory structure stored within the archive needs to be maintained after being extracted for the proper execution of the scripts.
3. Modify the environment variables in the scripts.

   For Linux/UNIX users, modify compileall.sh, mkjavadoc.sh, and run.sh.
   For Windows users, modify compileall.bat, mkjavadoc.bat, and run.bat.

   You need to modify the following environment variables that are indicated below to match your environment. These are used as part of the CLASSPATH when compiling and running DBDependency.

   • JAVA_BIN

     This needs to point to the /bin directory of your JDK 1.2 installation.

   • XERCES_PATH

     This needs to point to the directory where the Java archive xerces.jar is located within the Apache Xerces-J installation.

   • OPENJGRAPH_PATH

     This can either point to the /classes directory of the OpenJGraph installation or it can point to the Java archive stored under the /lib directory: /lib/openjgraph.jar.

   • ORACLE8I_JDBC_DRIVER

     This needs to point to the zip archive, named classes111.zip containing the Oracle JDBC drivers.

   • WEBLOGIC_JDBC_DRIVER

     This needs to point to the /weblogic/mssqlserver4/classes subdirectory under the WebLogic JDBC driver directory tree. You may also need to add the license directory as part of your classpath. Please read the documentation for BEA WebLogic's JDBC driver.

4. The archive already contains pre-compiled classes. If you like, you can recompile the sources by running compileall.sh (for Linux/UNIX users) or compileall.bat (for Windows users).

4. Running DBDependency

1. After you have succesfully installed DBDependency and modified the environment variables in the scripts to reflect your environment, execute run.sh (for Linux/UNIX users) or run.bat (for Windows users) from the main directory where the scripts are located.

   If it complains of not being able to find certain Java classes, make sure you have setup the environment variables in the script correctly.

2. At this point, you should get the DBDependency Frame window. Selected "Database" from the menu then select "Connect...". The application will read the configuration file config.xml for the list of predefined database connections.

   It should then display a dialog box prompting you for information to connect to a database. You can select one of the predefined connections, then select the "Edit" button to modify the parameters for the database connection, or create a new entry by selecting the "New" button.

   
   
   Database Connection dialog

   You should modify the URL to the database of a pre-defined connection as the existing URLs are specific only to my environment. You must also use a database username that has access to your RDBM's data dictionary.

   Any changes made will be saved to the configuration file. The password is never saved in the configuration file.

3. Select "Connect" from the dialog box. DBDependency will then close the Database Connection dialog and get information about the database such as the schemas and the available database objet types.

4. The tree control on the left side of the window will show you the available schemas in the database. Expanding one of the nodes will show you a list of database object types defined in the database repository. Expanding further the object types will show you the list of database objects of that type that are owned by the schema in the tree hierarchy.
5. Select one of the database objects in the tree control. DBDependency will then proceed to determine the first level dependencies of the selected database object. This process may take some time, depending on the number of dependents and dependees that the database object has. After it has finished, the dependencies will be displayed as a graph on the window.