MOBILE AGENTS IN DISTRIBUTED MULTIMEDIA DATABASE SYSTEMS

(Synopsis)

ABSTRACT
The size of networks is increasing rapidly and this fact is not straitened to the internet alone. Many intra and interorganization networks are affected by this trend, too. A side effect of this growth is the increase of nework traffic. This development leads to new challenges and we have to think about new technologies. Mobile agent systems are one answer to these challenges.Mobile agents are an emerging technology attracting interest from the fields of distributed systems, information retrieval, electronic commerce and artificial intelligence.

A mobile agent is an executing program that can migrate during execution from machine to machine in a heterogeneous network. On each machine, the agent interacts with stationary service agents and other resources to accomplish its task, returning to its home site with a final result when that task is finished. Mobile agents are particularly attractive in distributed information-retrieval applications. By moving to the location of an information resource, the agent can search the resource locally, eliminating the transfer of intermediate results across the network and reducing end-to-end latency. Mobile agents are goal-oriented, can communicate with other agents, and can continue to operate even after the machine that launched them has been removed from the network.

The mobile feature enables the agent to travel to the host where the data are physically stored. This is obviously of great interest in a distributed multimedia database systems where we have in most cases large binary objects. This Project integrates mobile agent technology in a distributed database system. The advantage of this approach is the combination of mobile agent features (e.g. autonomy, mobility, enhancement of functionality) and database services such as recovery, transaction handling, concurrency and security. This projects aims at facilitating storage and retrieval of multimedia data from the distributed multimedia database using mobile agents based on host database which will provide the result to the user upon request.

INTRODUCTION
Recent times have seen exciting new developments in computer networking. Applications like the World Wide Web have made computer networks such as the Internet available to users outside of computer science departments all over the world. Information servers offering all sorts of interesting data are cropping up, and, as researchers are trying to find ways of reliable electronic payment, the net will soon be important as a virtual marketplace.Yet the sheer amount of data available to users in such a network will be difficult to handle. How will they be able to locate the information they need? How are they going to find the best offer for some service they require?

One possible solution brought forward to help in this situation consists of mobile agents - autonomous programs that move about the network on behalf of their owners while searching for information, negotiating with other agents, or even concluding business deals Agents can be loosely defined as programs that assist people and act on their behalf.Agents are programs that can act autonomously. Transportable (or "mobile") agents can migrate from host to host across the network and interact with other agents. Mobile agents are an emerging technology attracting interest from the fields of distributed systems, information retrieval, electronic commerce and artificial intelligence.

The concept of mobile agents implies a lot more. It is often considered as a new programming and architecture development

paradigm, i.e. as the next step after the client/server and objectoriented programming paradigms.Mobile agent technology has been the subject of much attention in the last years due mainly to the availability of technologies and standards for platform integration such as CORBA, JAVA RMI and OMG MASIF.

Review of Existing model & the proposed model EXISTING MODEL: Existing Model is local System computation i.e. each system , where the data is stored should have separate database Management System or the application takes lot of time and CPU cycle to retrieve Information ( Multimedia Data ) . To better understand mobile agents and their behavior, we must first look briefly at traditional network architectures. The following figure illustrates the network behavior of a typical client/server application.

FIGURE1.6 The typical client/server application communication

A client/server application typically consists of two pieces: a client piece and a server piece. Often, the client and server pieces are on separate machines and they communicate over a common network. When the client needs data or access to resources that the server provides, the client sends a request to the server over the network. The server in turn sends a response to the request. This handshake occurs again and again in a traditional client/server architecture. Each request/response requires a complete round trip across the network.

PROPOSED MODEL: The Proposed System is using Agents can able to do the same Application with less amount of Time and CPU cycle. Now compare the client/server architecture described to the mobile agent architecture illustrated in the next figure.

FIGURE1.7 The mobile agent paradigm(Architecure)

Just as in the client/server architecture, there is a client piece and a server piece. The difference lies in how the two communicate. When the client in the mobile agent architecture needs data or access to a resource that the server provides, the client doesnt talk to the server over the network. Instead, the client actually migrates to the servers machine. Once on the servers machine, the client makes its requests of the server directly. When the entire transaction is complete, the mobile agent returns home with the results.

4Functional Modules S.N0 MODULES 1. Client Application TOOLS USED HTML/DHTML/JavaScript

(Or) Java Swing / AWT 2. Server Agent (SA) Java, Jini, JMF 3. Query Agent (QA) Java, Jini, JMF 4. Database Agent (DA) Java, Jini, JMF TABLE 2.1 MODULES INVOLVED THE PROJECT 2.5 DEVELOPEMENT PHASES: Module/Functional Description: The Project is Functionally divided into 4 modules. They are: Client Application (CA) In the Client Application, there is a Client Agent, for communicating with the Server Agent (SA). User request will be received from the Client Agents user interface and forwarded to the Server Agent (SA). The Client Agent is also responsible for presenting the query results to the user. The Client Application supports Agents with the following missions (1) search MPEG audio files and MPEG video files by users specification. (2) stream and play audio files and video files on a remote location. It can decode two types of file formats including MPEG I Layer III audio and MPEG I video. Server Side Agent (SA) The SA is responsible for dispatching clients requests to the Query Agent (QA) or Database Agent (DA). If the client requests is a query it

will be forwarded to the Query Agent or if it is someother, it will be based on the clients request. Query Agent (QA) The Query Agent (QA) is responsible for making query to find out the site containing the requested multimedia data. Database Agent (DA) If a clients request is a list of multimedia data, it will be forwarded to the Database Agent (DA) for indexing and updating the multimedia meta-data database. Moreover the Database Agent (DA) will be asked to update the database if a multimedia data is removed from a particular site. METADATA: Metadata represent information about the data in individual databases and data repositories. They may represent relationships between individual media objects. These metadata descriptions may be extracted using various mappings/extractors associated with the various types of digital data.

SYSTEM ANALYSIS: Hardware & Software Requirements 1. Pentium III Processor 2. 128 MB RAM ( or More ) 3. Java Virtual Machine 4. Data Base Software 5. JINI Frame Work