Abstract - Bluechip IT Solutions

ballooncadgeInternet and Web Development

Oct 31, 2013 (4 years and 8 months ago)



This project Load Balancing System is to handle traffic to any HTTP
web site. Clients from all over the world may be visiting the site
simultaneously and there by causing heavy load on the server, in particular,
on the J2EE
components that compose the site. All the requests from the
clients are first filtered by the Load Balancer filter. This filter finds the
maximum load on the J2EE components, and accordingly routes the client
requests. The filter also considers the number
of the incoming clients at any
one time. In Load Balancing System there is number is of filter is used to
balance the traffic on the server, some

filter components are available

Authentication Filters, Logging and Auditing Filters, Image Conversion Filter
Data compression Filters, Encryption Filters, Tokenizing Filters, Filters that
trigger resource access events, XSL/T Filters, Mime
type chain Filters,
Balancing Filters.

Assume there are N back
end servers available, named www.X.f
(where X is between 1 to N), and you want to use the cluster approach to solve
the resource problem. The goal then is to balance the traffic (addressed to
www.foo.com) onto these available servers so that the technical distribution is
totally transp
arent to the end user. Your Web
site visitors can still use canonical
URLs of the http://www.foo.dom/bar/quux/ form to reach the Web cluster, and
are not directly confronted with the fact that their requests are being served by
more than one machine. They
never see the underlying distribution.

Existing system

The Load balancing system is already available with every Application
servers like WEBLOGIC and WEB SPHERE. This Feature allows the Application
to redirect only specified number of requests to ea
ch process. The application
server can manage up to a limited number of clients. Clients from all over the
world may be visiting the site simultaneously and there by causing heavy load
on the server. Due to this data access cannot be done faster. All the p
can be done at the server only.

Existing System is unable to hold the traffic on the server. Some
time server has got so much of load on the server and unable to manage it.
System is unable to give proper request in time a
nd give response faster to
user cause of over load on the server.

Proposed system

The Balancing feature allows the Application server to restrict the
overload on the J2EE process. The application server can handle up to default
number of clients

if it is more than that it cannot handle. Load Balancing
system can handle more than the default value.

This option is not available at
present, and there is no tool which gives the complete information about the
internals of the container process.

So to make system aware of over load and manage the traffic on
the server, we need to implement the system which capable to take all the
responsibility and mange it.


In this system there are 4 modules


Load Balancer







Load Balancer:

In this module a user interface is developed which takes url to test
and number of clients and the deployment descriptor. This module uses java
swings package.

In this module

a sample web application is developed and a war file is
created to be deployed in web server.

In this section he define the WEB.XML file
where he put and which Type of filter he apply on the URL.

In this

section confirmation comes onc
e declare th
e WEB.XML file and
number of client to be execute URL at a time. If user are increase then an instance
is declare automatically and show popup message.

: In this module a

log f

is generated behind the process in this it show
about the client no, Response message, Response status.

Software Requirements

Operating System


Windows XP

Technology used






Web Server


Apache Tomcat 6




Hardware requirements:

Pentium processor


(P IV)
1.06 G
HZ or above

RAM Capacity



Hard Disk



ROM Drive

32 HZ


108 Standard