Category: Java Based Projects

Download All Java Projects (J2EE, JDBC, Servlets, JavaScript, JSP), Java Presentations and PPT’s,Final year Java projects,CSE Java Projects. Information technology third year and final year students can download Java Based Projects for final year students, Java Based Projects topics and list of projects with source code and reports for free download.

Posted on

Hybrid Model For JIT-Oriented Web Service Discovery Project Abstract

Introduction to Hybrid Model For JIT-Oriented Web Service Discovery Project:

In the present situation, the location of a specific web service in a limited time for any user busy in a particular job has become a very challenging task. Web service discovery is a procedure of finding out a machine-process able explanation of a web service that might have been earlier anonymous and which satisfies specific operational measure. Most of the Web Service Discovery procedures have not succeeded to find out the definite services.

The supposed system assists in offering effective web service discovery and refines the unnecessary services, with the help of Just-In-Time (JIT) ideology. JIT offers effective services to consumers on the basis of their context. The final goal of JIT is to remove the insignificant services so that the user receives the significant services. Effectiveness can be strengthened by understanding the context.  The knowledge of the context intents to know the definite services relying on the consumer’s position for the consumer needs to be met to the highest level. By grading the services, refining can be carried out. The recommended structure matches the consumer context to the service context in order to remove the insignificant services.

There are two varied procedures of web service discovery systems-Non-Semantic web service discoverer and Semantic web server discoverer. The services are compared on the basis of keywords in Non-Semantic web service discovery. It is tough for a consumer to get the wished results as number of significant services regained with regard to the keywords might be few and number of significant services might be many. In Semantic web service discovery procedures, every service contains semantic knowledge regarding services and it would be brought on the basis of semantic explanation.

Just-In-Time (JIT) is a building ideology that removes wastage related to time, labor and place for storing. It offers solely the wished services to the users.

Download Hybrid Model For JIT-Oriented Web Service Discovery Project Abstract.

Posted on

Defending Against Sybil Attacks Using Sybil limit Protocol Project Report

Introduction to Defending Against Sybil Attacks Using Sybil limit Protocol Project:

There is always a threat to open-access distributed systems like peer-to-peer systems from Sybil attacks, where a ill-willed user creates many fake identities known as Sybil nodes. Unless a reliable central authority is organized to bond identities to real persons, safeguarding against Sybil attacks is a serious problem. 

Amidst the limited dispersed approaches, our recent SybilGuard protocol uses a key perception on social networks to restrict the number of Sybil nodes acknowledged. In spite of its encouraging efforts, SybilGuard can permit many number of Sybil nodes to be acknowledged. Moreover, SybilGuard believes that social networks are fast-mingling, which has not been accepted in the actual world. 

This project deals with the SybilLimit protocol that uses the similar perception as SybilGuard, but provides a refined and close to reality results. In our trial for a million-node system, the number of Sybil nodes acknowledged is decreased by a factor or about 200 times. When the approaches based on fast-mingling social networks are regarded, SybilLimit’s assurance is at most a log and factor away from maximum. Ultimately, on the basis of three large-scale real-world social networks, the foremost proof that real-world social networks are really fast-mingling has been offered by us. This proves the basic supposition behind SybilLimit’s and SybilGuard’s approach. 

Hardware Requirements: 

The system should have a Pentium IV 2.0GHz or above Processor, a RAM of 1 GB or above, a HDD of 40 GB and above and a Display of 64 x 480(SVGA). It should have Multimedia support, a keyboard and a mouse.

Software Requirements: 

The system needs a platform of Windows 9x/NT/2000/XP, a Frontend ASP.NET and a Backend Microsoft SQL Server.

Download Defending Against Sybil Attacks Using Sybil limit Protocol Project Report.

Posted on

Dynamic Search Algorithm in Unstructured Peer-to-Peer Networks Project Abstract

Introduction to Dynamic Search Algorithm in Unstructured Peer-to-Peer Networks Project:

In unorganized peer-to-peer networks, creating effective search algorithms is a major challenge. Two usual types of search algorithms include flooding and random walk(RW). Flooding conducts an aggressive search that involves utmost nodes. As it produces several query messages, it can’t be scaled. On the other hand, RW conducts a conventional search and produces a limited query messages but consumes a lengthy search time.

Therefore Dynamic Search(DS) algorithm is suggested, which is a  generalized form of Flooding and Random Walk. When it comes to short-term search, DS follows flooding, whereas it follows RW during long-term search. In order to refine the performance of the search, DS unites with the knowledge-based search mechanisms. The performance of DS is calculated by few performance measures such as success rate, search time, query hits, query messages, query efficiency etc. As shown by the outcome, DS offers  a good tradeoff  within performance and price. According to the power-law graphs, DS functions 25 times better than flooding and 58 times better than RW  and as per the bimodal topologies, it functions 186 times better than flooding and 120 times better than RW. 

Dynamic Search algorithm has benefits such as reduced search time and combines both flooding and random walk technique. These algorithms take the benefit from the knowledge gained from the earlier search outcomes and on the basis of the knowledge, they route query messages with various weights. 

Hardware Requirements: 

The hardware requirements include any Processor above 500 MHz, a RAM of 128 Mb, a Hard Disk of 10 Gb, a Compact Disk of 650 Mb, a standard keyboard and  mouse and a VGA and High Resolution Monitor as an output device. 

Software Requirements: 

The software requirements involve Windows Family as an Operating System, JDK1.5 as a Language, Microsoft Sql Server as a Database and Java Swing as Front end.

Download Dynamic Search Algorithm in Unstructured Peer-to-Peer Networks Project Abstract.

Posted on

SRS Online Airline Ticket Reservation System

The chief objective of the project lies in creating a website that helps the passenger to reserve online air tickets via an efficient and simple GUI. Not only booking tickets but also comparing online fares from a city to another, is made easy for the passenger. 

Intended Audience: 

  • This project mainly aims at the people with a desire to travel by air and an Internet access.
  • Secondly, it targets people equipped with hand-held devices as the site would be made a WAP-enabled. That would allow the site to receive requests from other optional devices such as PDA’s and WAP-enabled browsers.
  • Thirdly, the passengers eager to compare the airfares for their opted source and destination cities are targeted. 

Cool features of our site: 

  1. Dynamic Bandwidth Calculation: By calculating the user’s bandwidth, the user is redirected to Graphical Version or Text-Version, as per his bandwidth.
  2. Sitemap: A sitemap of the whole site is offered for the easy access of the site. It involves all the links of the pages on the basis of the utility of the pages.
  3. Flash Images of Flights: Flight detail images have been created along with flash to highlight the seating arrangement of the flight. It helps the passenger know the seating arrangement, emergency exit doors and toilet particulars prior to entering the flight.
  4. Airport Layouts: The details of the airport layouts beforehand help the passengers in collecting their tickets directly instead of wasting time in searching for the counter.
  5. Points Based System: The regular customers are given concessions on the basis of the points they score by shopping on the site. 

The technologies used for designing the website include Server Technologies like Web server and Database server and Software Technologies like Java Server Pages, Java Beans etc.

Download SRS Online Airline Ticket Reservation System.

Posted on

Text Editor Project in Java

Introduction to Text Editor Project:

For editing plain text files, a program called text editor is used. A plain text file is shown and edited by displaying all the characters the way they are involved in the file. The control characters of the used character set are the sole characters employed for mark-up. In real, it is newline, tab and form feed. ASCII is the most frequently used character set because of more frequent use of plain text files for programming and configuration and less frequent use of them for documentation (for instance, detailed instructions, user guides) as compared with the past. 

Text Editor is software that edits plain text and comprises of Java Swings and AWT. This project has all the frames prepared in Swing. These days, most of the programmers use Swing. Swing offers stronger and manageable GUI components as compared to AWT. Modern Java GUI is represented by Swing. 

Swing was a result of the shortcomings in Java’s original GUI subsystem: the Abstract Window Toolkit. AWT is a fundamental set of controls, windows and dialog boxes that aid a usable but restricted graphical interface. 

Text Editor Features: 

The text editor provides the fundamental features of an editor such as string searching, multiple font colors, various fonts and dock which includes the options most frequently used such as cut, copy paste etc. 

Text Edito System Analysis and Design: 

This phase involves the software development process and its entire structure. This phase also depicts the number of classes required for the package architecture, the database design and the data structure design. After the creation of the software development model, Analysis and Design play a vital role in the entire development cycle. Even a small flaw in the designing stage could prove to be very harmful in the later stages of the development of the software.

Download Text Editor Project in Java.

Posted on

Colloquium Report on Web Based Operating System

Introduction to Web Based Operating System:

A Web Operating System refers to a user interface (UI) which lets the people in accessing applications that are stored fully or partially on the web. It doesn’t connect directly with the hardware of the computer but it may copy the user interface of conventional computer operating systems such as Windows. The availability of a conventional OS is compulsory on a computer. Web OS rely upon the conventional operating systems to function so they can’t substitute the computer’s fundamental OS.

The user side of Web OS software runs on the computer’s OS irrespective of it being a Web browser or a system-specific client. The Web OS is designed to look and perform quite similar to that of a desktop OS, by the programmers. Though it looks similar to a conventional OS, yet it doesn’t regulate computer’s software or hardware.

The main uses of Web OS include its simple and easy to carry from one place to other because of its light weight. No software is required by the user and he is not the administrator as the application’s programmer plays the role of an administrator. Moreover it allows every user to use a new version of any OS at once and the application lies at a single place.

Outcome of study:

On the whole, it can be concluded that technology has advanced beyond our expectations. This can be proved by the fact that OS can be used without it being present in our desktop. After covering various aspects of Web OS, it is found that Web OS is an amazing program which can be easily operated and researched. The benefits and functions of Web OS can be appreciated by the users, once they get used to it. It is christened to be a personal desktop for the generations to come.

Download Colloquium Report on Web Based Operating System.

Posted on

HIET Integrated Library Management System

Introduction to HIET Integrated Library Management System:

The main aim of HIET Integrated Library management system is to arrange a platform for the college libraries to change their functioning by adopting a digital medium which means computerizing their functioning. So far in India, the small and medium scale college libraries hold paper records, which require a lot of maintenance and even the search for the important information proves to be a time consuming task. 

HIET Integrated Library not only makes the long process simple but also keeps the proceedings of the library moving fast. It would help in increasing the library’s efficiency from top to bottom, that means from data entry to record maintaining. The chief aim of this integrated library is to facilitate its members and users with searching and reserving the books which are given by other users and requesting new books. 

This library originated in order to fulfill the needs of small and medium scale libraries. All the requirements for the smooth working of a library are met with software which involves making data entry for new books, search and update book records, registering a new user, editing and deleting records etc. The administrator can access the user login and book history when required. The software allows the  librarian to form new user groups and edit their access levels and functions and it also enables the users to keep a track of the books issued and fines due. It also enables them to select the books and magazines of their choice. 

Hardware Requirements:

The Hardware requirements of the system are CPU equivalent or above Intel Celeron 800 MHz, a RAM 256 MB or higher and a Hard Disk of minimum 4 GB. 

Software Requirements:

The Software Requirements are JAVA(jdk 5.0 onwards), any Windows OS(XP or later), Microsoft Access as the data base and Microsoft Word for Documentation.

Download HIET Integrated Library Management System.

Posted on

Mobile Agent Based Fault Tolerance System Implementation Procedure in Java

The actual procedure followed to implement the proposed design as mentioned in the previous chapter is explained in this chapter. As mentioned the proposed design is implemented using Java and the all the required screens are designed using the Java swings and the data base is created in Oracle SQL. This chapter summarizes all the important classes and tables used along with the flow of the application are clearly described in this chapter.

Classes used in the application

Every aspect across java programming is an object and these objects can be inherited in the form of class and the objects of the class can be created to initiate the core functionality used across the class. Following are the classes created in this project with respect to initiate the flow of the application. All the classes used across this application are created using the Java swings framework and the flow of the business logic is as listed below

  • AddClient.java
  • Administration.java
  • CommonUtil.java
  • First.java
  • LinkStatusForm.java
  • MasterServer.java
  • MobileAgent.java
  • ReceiveData.java
  • SecondFrame.java
  • SendDataForm.java
  • ServerModule.java
  • UKprogg.java

All the java files are created with an extension of .java and the corresponding logic used across these java files are as given below 

AddClient.java 

Required logic to add the clients to the servers is given in this class. As per the design few clients can be added to the server and the corresponding procedure is coded in this class. Java swing frame work is used to create this logic and all the basic components of the swing class like text fields, layouts and gaps are used to create the basic layout out the of the screen and is as shown in the appendix section. A separate client id is issued to the newly added client and assigned to the desired server and the corresponding logic used here is that the server id is tracked against adding the required client and the newly added client is to the serve and the server is identified with the server id. Once the client is added, a new row is added to the client table and the corresponding query used here is Initially the number of clients are calculated and if this count is as per the defined handled clients for the server, then only the client is added to the desired server else the client is added to the next available server.  Once the required constraints are satisfied the client is added to the client table and the rows are incremented by 1 against the table.  Whenever the client is added to the server and the database is updated, the link status of the server and the client is also updated and set to on the corresponding logic is written.

When the client is added to the server, the corresponding client IP address and the client name are also updated against the database table client. 

Administration.java 

Administration.java class is used to create the user interface for all the administration activities and the coding procedure followed is explained in this section. The key administration tasks used in this project are to start or stop the master server, check the status of the links, start the distribution mode of the network and initiate the mobile agent for detecting the faults across the distributed networks. Administrator can check the status of the links between the clients and the server at any point of time and they are provided an option with respect to this.  A link status form is opened at the user interface and the administrators can view the status of the desired links at this window and even this window is created using the swings. Distributed network option is also available to the administrator and they can initiate the distributed mode of the network.  Admin is provided with an Mobile agent button and the users can click on the button to start the mobile agent, where this agent collects the information related to the distributed network faults and suggests the options for the fault recovery options. The key java code used to create this logic is as given below 
A new object is created in the private methods to initiate the administrator requests and thus the overall functionality of the admin module is coded in this java class.

CommonUtil.java

This class is used to created the frequently used java functions like the database functions and thus if at all a new instance of the database is required an object is created for this class and initiated to dump the complete coding logic in this case.  Following are the important methods used in this class and the corresponding description of the methods are also given below

getConnection

This method is used create the connection to the database and the basic JDBC drivers are used to create the connection to the database using the Connection class across java. Once the connection is established, the corresponding statements and other parameters are initiated. Oracle thin driver is used to create the bridge to the database in this class and the user name and password to access the database are also provided in this method

getServerNameByServerId 

This method can be used to get the server name by providing the server if as the required parameter.  A separate global server is used as the required table and the server information is recorded in this table and thus the information is fetched from the database and the corresponding query used for this process is as given below 
getServerIdByServerName 

This method can be used get the server  name by providing the server name as the required parameter and the value is fetched from the global server database table. Following is the query used to get the required information from the table 

getClientIdByClient_name 

This method can be used to fetch the required client id with the help of client name and the client name is provided as the required parameter to the method.  Below is the query is used to get the required client information with the help of client name 

getClientNameByClientId 

This method can be used to get the client name by providing the client id as the required parameter and this name is fetched from the database table known as client and the actual query is used in this context is as given below 

LinkStatusForm.java 

As mentioned the administrator can check the status of the links from the desired server and the client and the corresponding code is given in this java class. User interface is provided in such a way that the users can select the desired from the dropdown list and also can select the client id from the list and the swing components are used to create this interface.  All the ids of servers and clients are fetched from the corresponding database tables and the required logic is given in this class. Once the users selects these values, these values are given as the input to the query built and this query is fired on the status table to get the current status of the desired server and client and the corresponding coding logic used is as shown below 

Thus the current status of the client and the server can be fetched using this logic and the query as shown above. 

MasterServer.java 

Master server is initiated across this project and the corresponding logic used is given in this java class. From the master server user can start the desired server and in this project two servers are created and named as Server A and Server B and once the user clicks on the desired button, the actual server operations are started. Java swings are used as the required framework and all the key components are added to get the required interface to the application. The actual action performed by user is captured using the action events provided with the swings package and based on the action performed the corresponding server is started and the key coding logic used in this context is as shown below 

From the above code it is clear that if server A is selected the corresponding ID is tracked and the actual server module is started and this procedure is repeated for both the servers as shown in the above code. 

MobileAgent.java 

This is the important class used among all the classes created in this application. Mobile agent is the java class that captures all the link failure information and displays to the administrator and the administrator can set the status to On again using this class and the corresponding functionality used. User is also provided the required suggestion to check the alternative paths across this process and the corresponding functionality is provided in this class. The link status information is fetched from the database and the corresponding logic is used as given below 

 From the above code it is clear that the required information is gathered from the database table link_status and the status values are iterated in a loop using the result set object available with the JDBC package and the fetched values are displayed to the users in a tabular form and required rows are added to this table using this information fetched from the database table.  A vector object is used to store all the values retrieved from the database and the loop is iterated against this loop. 

ReceiveData.java 

As mentioned in the design of this project, clients and servers can receive the data from the any other servers and clients and the required programming logic is given in this java class. All the data received from any other client or server is displayed to the users in the form a table and the required logic is written using the java swings framework and the corresponding components in the swing framework. Database connections are established to gain the access to the information related to all the received data by a particular client or server. A table with name datapackets is created in the database and that particular information is gained from this table and displayed to the users in a tabular form. All the data received is fetched from the table and stored in a vector object and thus a loop is iterated using the JDBC result set object and the corresponding values are displayed to the user and the corresponding screenshot is as shown in the next chapter. The actual coding logic used for this java class is as shown below 

SendDataPage.java 

As mentioned in the design chapter, any client or server can send to the desired client and server and the required programming logic is created in this java file. A window is created across this section and the users can type the desired message to be sent and actual number of packets is also calculated using this logic. A separate text field is created in this class and the client or server can add the required message to the text area and the data entered is sent to the desired client or server and the number of packets sent is also calculated in this class and the corresponding coding done is as given below 

From the above code given it is clear that all the data sent is saved in the database table datapackets  and the inserted text is converted to the desired format and the corresponding client and server information are added as well. A prepared statement is created and the query is inserted to the prepared statement and executed to insert these values in to the database table. 

Following are the database tables used in this application

  • Globalserver
  • Client
  • Link status
  • Data packets 

All the important classes are explained in this chapter and the corresponding code is also provided. The actual results achieved against this implementation are given in the next chapter. 

Posted on

Distributed Network Computing Model

To make this application a distributed network, a separate distributed network module is created in this application and few assumptions are made in this context. In this module, a predefined metrics are defined in this context like the number of clients to be added and the amount of data to be sent and if these metrics are exceeded then an alternative sever is chosen to add the clients and also process the client request and following are the conditions to be applied in this context

  • A sever can handle only 6 clients and if more clients are added to the server, these clients are automatically added to the next server
  • If both the servers has 6 clients each and more clients need to be added, an extra server is created and the new client is added to that server
  • Each server can process a maximum of 6 client requests to send or receive data and if this limit is exceeded, automatically the next available server is chosen in this context
  • All the servers updates the data to the master server as mentioned above

Client module

A detailed explanation to the server module and the distributed network module is given above and the design aspects of the client module are given in this section. As mentioned above, a single server can handle not more than 6 clients and these clients can communicate with each other or to their server or the other servers when the load on their corresponding server is high. Following are the key functions of the client module

Send data

Clients can send data to the desired server or client as per the requirements. Whenever the client wants to send the data, users are provided with the option to choose the desired destination and this destination can be either another client or server. Initially the users are provided with the list of options and these options only include the peer clients and their corresponding server and if any case the distributed network conditions are violated, users is given a warning message that the server is busy and now the users can choose another server to process their request. While sending the data, users are provided with a browse button and a text area field so that they can choose the desired file or write some request at the sending option and they can click on the send button to send the data. Once the data is send to the server or any other client, the corresponding details are stored across the database.

Receive data

Clients can receive the data either from the server or the client and to achieve this separate functionality is designed in this context. Whenever a client or server sends the data to a particular client, a separate link is provided to the users with respect to check all the data received against that client. Whenever the users click on the link, a table is generated showing all the details of the received data against the sender and the table contains the columns like sender Id, the date or time when the data was send and the description of the data. User can check the desired sender details to download the data and once done the data is saved across the database. 

This paper is written and submitted by sai

Posted on

Distributed Networks Project abstract on Mobile Agent Based Fault Tolerance System

Distributed networking is widely used these days and apart from the list of advantages provided with the distributed networks, there are few limitations across these networks and the key among them are faults that occur frequently across the networks.

Among these faults link failures and switching the mode of distributed networking are important to be considered and there are many fault recovery techniques across the literature and most of them are static in nature and can’t detect the dynamic link failures across the network.

The main aim of this project is to evaluate the role of mobile agent based fault tolerance system for the distributed networks and to make this proposed application, a simple java based application is used. Swings framework is used to create the user interface and Oracle SQL is used as the database to handle the tables.

Two servers and a master server are created and each server can handle two clients and the faults like link failures and distributed network off are inserted in this project and from the results it is clear that the mobile agent can handle the dynamic link failures and improve the overall performance of the distributed network.

This paper is written and submitted by sai