ABSTRACT

A multi database system (MDBMS) is a facility that allows users to access data located in multiple autonomous database management systems (DBMSs) at different sites. To ensure global atomicity for multi database transactions, a reliable global atomic commitment protocol is a possible solution. In this protocol a centralized transaction manager (TM) receives global transactions, submits sub transactions to the appropriate sites via AGENTS. An AGENT is a component of MDBS that runs on each site; AGENTS after receiving sub transactions from the transaction manager perform the transaction and send the results back to TM. We have presented a unique proof-of-concept, a JAVA application for an Agent Based Transaction Manager that preserves global atomicity. It provides a user friendly interface through which reliable atomic commitment protocol for global transaction execution in multi database environment can be visualized. We demonstrated with three different test case scenarios how the protocol works. This is useful in further research in this area where atomicity of transactions can be verified for protocol correctness.

TABLE OF CONTENTS

Title page

Certification

Dedication

Acknowledgement

Abstract

Organization of the work

Table of contents

CHAPTER ONE

INTRODUCTION

1.1 Statement of the problem

1.2 Purpose of study

1.3 Aims and objective

1.4 Scope of delimitation

1.5 Limitations

1.6 Assumptions

1.7 Definition of terms

CHAPTER TWO

LITERATURE REVIEW

2.0 LITERATURE REVIEW

CHAPTER THREE

DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM

3.1 Fact finding methods used

3.2 Organization structure

3.3 Objective of the existing system

3.4 Input, process, output analysis

3.5 Information flow diagram

3.6 Problem of the existing system

3.7 Justification for the new system

CHAPTER FOUR

DESIGN OF THE NEW SYSTEM

4.1 Output specification and Design

4.2 Input specification and Design

4.3 File design

4.4 Procedure chart

4.5 System flow chart

4.6 System requirement

CHAPTER FIVE

IMPLEMENTATION

5.1 Program design

5.2 Program flowchart

5.3 Pseudo code

5.4 Source program

5.5 Test program

CHAPTER SIX

Documentation

CHAPTER SEVEN

Recommendation

Conclusions

References