Maintenance of Student Information Using

Distributed Database Querying System Introduction

INTRODUCTION
1.1 Objective:
The problem involves developing a distributed database querying system. The
system has three databases. Oracle databases as used in this Implementation. However,
these databases could be of varying architectures like , MS Access , MYSQL ,SQLserver
and so on.The system has three Oracle databases on three different machines. The
database structures are as described in the problem statement earlier. Just above the
databases on each machine is a QueryDatabase object. The QueryDatabase object can
talk to the Database and make queries on it. Since the QueryDatabase objects are on the
same Machine as the database they are interacting with, it is assumed that the individual
Query Database objects would know the structure of the database they are querying. The
Query Database object talks to the database using JDBC (Java Database Connectivity)
calls. Unfortunately, the Access databases do not recognize JDBC calls. However, Access
understands another standard i.e. ODBC (Open Database Connectivity). Thus the Query
Database objects use a JDBC-ODBC bridge to connect to the database.

Each machine implements a server that implements a MyServer interface. These

servers have the job of binding the name of the particular machine with the RMI registry.
The servers implement among other things, a method called Process Data. The Process
Data method is the remote method that would be called using RMI.The execution stages
shall be as under:

1. A client takes a query from the user. This query is to be a pid of a student
whose Information is required.
2. The client should call the ProcessData method of the second machine
remotely and should pass it the query string and a result string (which is
initially null).
3. The ProcessData should call the corresponding QueryDatabase method and
store the results got into the result string. It then should call the ProcessData
of theThird machine remotely.
4. The ProcessData method on the third machine should do a similar job and
Should Call the ProcessData method on the first machine (on which the client
was run).

Dept. Of MCA 1 Intel Institute of Science

Maintenance of Student Information Using
Distributed Database Querying System Introduction
5. The third machine then should contact the Query Database object and should
get the results from the first database which should be appended to the result
String.
6. Finally, the ProcessData method on the first machine should write out the
result String to a file which should be named as query.

Modules:
Personal Info: This module stores the names of students, their phone numbers and a
unique pid. (Similar to VT)
Finance Info: This module stores the current Hokie account credit and insurance amounts
for each student (identified with the unique pid field)
Account Info: VT has decided to let students take copies and printouts up to a certain
limit. This database holds the current number of copies and printouts taken by each student
identified with the unique pid field
Schema management Module: This module manages the schema of the database
spreaded across in all the DBs. It helps if this system want to send the same amount of
data to interoperable systems then this schema document is submitted to other platforms to
make them understand that schema/structure in which data is organized.

1.2 Existing System:

In the earlier system the university used to maintain their Database in a single
centralized location where it became difficult to access data from users all over the n/w.
Each department needs their departmental information pertaining student. Because of due
to centralization of lot of network load imposed to access the database and as well as lot of
duplication of data exist in their machines. Access one department database information
from other departments was also insecure (loose of confidentiality).

1.3 Proposed System:

This system is aimed to maintain different department’s data in their respective
machines and people can access from all over the network without exposing data directly
outside the department. Each department maintains their own copy of the data in their
respective databases.

Dept. Of MCA 2 Intel Institute of Science

Maintenance of Student Information Using
Distributed Database Querying System Introduction
Develops couple of components that contain functions required to access required amount
of information from the database but not the entire data Components having functions, they
only access database The components are distributed components (RMI components)
Registers their object references into RMI Registry. Other department components lookup
and access functions of each departmental component functions Sends student id Fetch
information of the student from each department server and stores into client requested
initiated machine.

1.4 Scope of the System:

We can also implement internationalization (i18n) to support user interface in various/local
languages. of the System

Dept. Of MCA 3 Intel Institute of Science