EMPOVERING THE RMI IN JAVA APPROACH

Title of the Project: EMPOVERING THE RMI IN JAVA APPROACH SDLC Methodologies: Waterfall/Spiral Model
Course: Roll No: Name of the Student: Technology : Internal Guide: E-Mail ID: Mobile No (Student): JAVA

Abstract of the Project: Introduction:

With the explosive growth of internet and network services, there is always a proliferation for distributed application that seek to leverage the power of the internet. Remote method invocation is now increasingly being used in Internet based applications and hence it is important to study the performance parameters of RMI. RMI is the action of invoking a method of a remote interface on a remote object. The three methods of RMI namely General , Activation and Custom Socket Factory are to be evaluated empirically using parameters like Round trip time , Latency and Packets per Unit time. The graph plotted allows us to gain an insight into the performance aspects and other tradeoffs of RMI. The General method deals with invoking any method directly from memory of the remote machine. RMI Activation allows passive objects to be

brought into the active state by instantiating it on an as needed basis. Custom socket factory method allows customization of socket depending on the type and amount of data to be transferred over the channel. It is proposed to implement security for the data being transferred using Rijndael Algorithm that imparts security due to its high

resistance to attacks, code compactness and design simplicity. Search mechanism is also to be implemented in the GUI, which has user-friendly access to the three methods of RMI and displays the results of the evaluation.

EXISTING SYSTEM

Invocation of a remote object can be achieved by means of the existing methods namely: General, Activation and Custom Socket factory methods. In the General method, the server creates a number of remote objects, makes references to those remote objects accessible, and waits for clients to invoke methods on those remote objects. The client gets a remote reference to one or more remote objects in the server and then invokes methods on them. The Activation method allows objects to begin execution on an as-needed basis. This mechanism provides persistent references to objects and manages the execution of object implementations. The Socket Factory method allows customized implementation of sockets to cater to the user requirements. The amount and the type of data that can be sent over the channel can be specified.

PROPOSED SYSTEM

It is proposed to evaluate the performance of the three methods (General, Activation and Custom Socket Factory) by transferring different types of files such as text, image and video .These files are transferred using the three invocation methods and their performance is evaluated by analyzing the parameters: round trip time, latency and transmission rate. The observations are tabulated and graphs are drawn to facilitate the comparison of the three methods of remote invocation. This offers the user an insight into the best suitable method.

A Search mechanism is proposed to be implemented to locate methods when the host does not know where the method actually resides. This system is categorized into Keyword based search and Extension based search. A user friendly GUI that will hide the low level details is to be developed which will provide easier access to the three methods of invocation and will display the results of the actions performed.

Environment:
Operating System: - Microsoft Windows XP/2000 or Higher Clients: CONSOLE Development Tools: Netbeans 6.8 Documentation Tools: MS Office 2003/2007 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 User Interface: AWT & SWINGS Code Behind: AWT & SWINGS

Requirements:
Hardware Requirements: Number 1 Description PC With Minimum 20 GB Hard-Disk And 1GB RAM

Software Requirements: Number 1 2. 3. Description Windows XP/2000 Or Higher With MS-Office 2003/2007 AWT & SWINGS CONSOLE

Milestones:

No.

Milestone Name

Milestone Description

Remarks

Requirement s Specification

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of technology needed implement the project. the to

Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Technology Familiarizatio n

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. The scenarios should map to the requirement specification

High-level and Detailed Design

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).

Development of Front End Functionalitie s.

During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Integrating the Frontend with the Database

Integration Testing

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

The following steps will be helpful to start of the project:

Study and be comfortable with: JAVA AND SQL. Gather some knowledge of product hierarchies and maintenance before starting the design. Create a user database with different access levels. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.