Abstract

It is now-a-days very important for the people to send or receive articles like
imported furniture, electronic items, gifts, business goods and the like. People depend
vastly on different transport systems which mostly use the manual way of receiving and
delivering the articles. There is no way to track the articles till they are received and there
is no way to let the customer know what happened in transit, once he booked some
articles. In such a situation, we need a system which completely computerizes the cargo
activities including time to time tracking of the articles sent. This need is fulfilled by
Courier anagement !ystem software which is online software for the cargo
management people that enables them to receive the goods from a source and send them
to a re"uired destination and track their status from time to time.
#
1. INTRODUCTION
Courier anagement !ystem is a software for the cargo offices where the
customer can approach the office and book an article or good. The manager$clerk can use
this software to enter the details of the customer and goods along with the source and
destination points. The details of loading the goods into the physical transport system are
also recorded by the system. The system has %&I for the users to manage not only daily
transactions but also to keep the historical data in the database for future reference.
The other user of the system is administrator who can manage the vehicles
information as well as employees' information. (e can also create new branch based on
based on branch re"uests and can decide the route for the cargo to take on a particular
day so that delivery happens at the customer's nearest point. )lso it provides the
management reports like monthly goods bookings, loadings, deliveries, demurrages and
receivers particulars.
1.1 Objective
This pro*ect deals with the +Courier management'. The system is used for daily
activities such as booking, loading, delivery, status check, and managing branches. It is
very difficult to do this process manually. (ence it is recommended to computerize the
process by developing the relative software as the world is turning into information and
technology, computerization becomes necessity in all walks of life.
1.2 Existing System
The e-isting system is a manual one in which users are maintaining ledgers,
books etc to store the information like goods booking details, loading particulars,
deliveries particulars, details of receivers of items at all branches, and customer details as
well as employee details. It is very difficult to maintain historical data. )lso regular
investments need to purchase stationarevery year.
.
Disadvantages ! Existing System"
The following are the disadvantages of current system
#. It is difficult to maintain important information in books
.. ore manual hours need to generate re"uired reports
/. It is tedious to manage historical data which needs much space to keep all the
previous year's ledgers, books etc.
0. 1aily transactions are to be entering into different books immediately to avoid
conflicts which are very difficult.
2. 3o co-ordination between different branches because we are not storing the data
at centralized location.
1.# $r%sed System
The new system titled 4Courier anagement !ystem5 is hence proposed to
remove all the problems in the e-isting system discussed above.
Proposed system is a software application which avoids more manual hours that
need to spend in record keeping and generating reports. This application keeps the data in
a centralized way which is available to all the users simultaneously. It is very easy to
manage historical data in database. 3o specific training is re"uired for the employees to
use this application. They can easily use the tool that decreases manual hours spending
for normal things and hence increases the performance. )s the data is centralized it is
very easy to maintain the status of the goods booked in all branches.
Advantages ! $r%sed System"
The following are the advantages of proposed system
#. 6asy to manage all the daily transactions
.. Centralized database helps in avoiding conflicts between different braches
/. )voids human errors
0. Provides better customer support from any branch
2. Can generate re"uired reports easily
7. 6asy to manage historical data in a secure manner
8. 6asy to use %&I that does not re"uires specific training.
/
2. S&STE' ANA(&SIS AND DESI)N
!ystem analysis is the performance management and documentation of
activities related to the life cycle phases of any software namely9

The !tudy Phase
The 1esign Phase
The 1evelopment Phase
The Implementation Phase
The Testing Phase
!oftware )nalysis starts with a preliminary analysis and later switches on to a
detailed one. 1uring the preliminary analysis the )nalyst takes a "uick look at what is
needed and whether the cost benefits. 1etailed analysis studies in depth all the cornered
factors, which builds and strengthens the software.
2.1 SRS
The introduction of the !oftware :e"uirements !pecification ;!:!< provides an
overview of the entire !:! with purpose, scope, definitions, acronyms, abbreviations,
references and overview of the !:!. The aim of this document is to gather and analyze
and give an in-depth insight of the complete re"uirements of our pro*ect by defining the
re"uirements in detail. 3evertheless, it also concentrates on the capabilities re"uired to
run out pro*ect on different high-level software features.
2.1.1 *+nctina, Re-+irements
The system after careful analysis has been identified to present itself with the
following modules9
6mployee Information = >ranches odule
%oods booking, ?oading = 1eliveries module
:eceivers = :eporting module
:outes information module
0
Em%,yee In!rmatin . /ranc0es 'd+,e
This module maintains the information about all the employees who have been
e-isted in the company. The employee has created by admin user. The employee may
turn up as a user by the admin user. This module contains all the information of the
employees. 6ach and every employee details will be included in the module. This module
maintains the information related to the e-isting branches that is part of the organization.
This module contains all the information about the branches. If at all the new branch is
re"uired or the company has get any re"uests for the new branches from the others then
only the admin user can respond and add the new branches. (e is only the responsible
person to cancel the branches. The admin user can view the details of all the branches
which are already e-isted. The manager user also can view the details of all the branches
which are already e-isted.
)ds b1ing2 (ading . De,iveries md+,e
This module maintains the information related to the >ookings of the goods. )ll
the booking details means every item has its own id, ?: 3o, Customers name, details of
the customer, >ranch I1, >ranch ?ocation, >ooking date and all the details will be
included in this module. If any user enters into his account then this module shows the
functionalities of this module. It will display the two functionalities related to this module
i.e., one is %oods Particulars and the other one is @iew >ookings. )ll the particulars of
%oods will be included in %oods Particulars functionality, and the @iew >ookings
contains the details of the all the bookings. Aor the booking of every item one booking
form is displaying in the application. Bnly manager user can fill the details of all the
fields in the booking form. )lso manager user can view the details of all the bookings.
The admin user also can view the details of all the bookings. This module maintains the
information related to the loading of the items. )ll loading details means ?: 3o of the
particular item, aterial code, 3o of Items, 1estination, @ehicle 3o, :eceivers name,
1ate of loading all these details will be included in this module. If any user enters into his
own account then this module will display the two functionalities related to this module.
I.e. one is ?oading 1etails and the other one is @iew ?oadings. Bne form is available in
the ?oading 1etails functionality. )ll the details of loadings will be included in loading
2
details functionality and all loadings will be included in the view loadings functionality.
Aor loading of every item the corresponding user should fill the form. Bnly the manager
user can fill the loading details form. )lso he can view the details of all loadings. The
admin also can view the details of all the loadings. This module maintains information
related to the deliveries. )ll delivery details means ?: 3o, aterial particulars, 3o of
Items, >ooking >ranch, 1ate of loading, 1ate of delivery, 1elivered at >ranch all these
details will be included in this module. Chenever the user enters into his account then the
1eliveries module will display the following functions. Bne is 1eliveries 1etails and the
other one is @iew 1eliveries. The deliveries details function contains one form related to
the details of all deliveries. Bnly the manager user can add the new delivery and also he
can view the details of all the deliveries. The admin user also can view the details of all
the deliveries.
Receivers . Re%rting md+,e
This module maintains the information related to all the receivers information. )ll
the information related to receivers means ?: 3o, :eceivers name, booked at branch,
aterial particulars, 3o Bf Items, Charges of 1emurrages all these details will be
included in this module. Chenever the user enters into his account then the receiver's
information module will display the following functions. Bne is :eceivers 1etails and
the other one @iew :eceivers. The :eceivers details function contains one form related to
the details of receivers. Bnly the manager user can add all the details related to receivers
and also he can view the details of all the receivers' information. The admin user also can
view the details of all the receivers' information. This module contains the specific
information related to all the management reports. Chenever the user enters into his
account then the :eporting module contains the following management reports. )ll the
>ookings, >ranches, :outes, ?oadings, 1eliveries, 1emurrages, and %oods !tatus
reports will be included in this module. )ll the admin user and the manager user can view
or generate all the management reports.
7
R+tes in!rmatin md+,e
This module maintains the specific information related to the :outes. )ll the
information related to :outes means :oute I1, :oute 3o, Place and )reas Covering all
these information will be included in this module. Chenever the user enters into his
account then the :outes information module will display the following functions. Bne is
)dd new :oute, @iew :oute details and the final one is cancel the :oute. Bnly the
)dmin user can add or remove the details of routes and also he can view the details of all
the routes. The manager user also can view the details of all the routes.
2.1.# 3ard4are Re-+irements
Pentium I@ Processor or later
# %> :)
0D %> (ard 1isk !pace
6thernet card with an Internet
2.1.5 S!t4are Re-+irements
Cindows EP Professional Bperating !ystem.
Internet e-plorer 7.D or 3etscape navigation
y!"l
Fava.
(T?
8
2.2 System Ana,ysis and Design
!ystem design is the second step in the system life cycle, in which overall design
of the system is achieved. The functionalities of the system is designed and studied in this
phase. The first step is designing of program specification. This determines the various
data inputs to the system, data flow and the format in which output is to be obtained.
1esign phase is a transmission phase because it is a transition from user oriented
document to computer data. The activity in the design phase is the allocation of functions
to manual operations, e"uipment and computer programs. Alow charts are prepared in the
study time and is decomposed until all functions in the system perform evidently.
1esign is a multi-step process that focuses on data structures, software
architecture, procedural details ;algorithms etc.< and links between the modules. The
design process goes through logical and physical stages. In logical design reviews are
made linking e-isting system and specification gathered. The physical plan specifies any
hardware and software re"uirement, which satisfies the local design.
odularization of task is made in this phase. The success of any integrated
system depends on the planning of each and every fundamental module. &sually a pro*ect
is revised in step by step se"uence. Inter-phase management of such module is also
important. !oftware design methodology changes continually as new methods, better
analysis and broader understanding evolve.
@arious techni"ues for software design do e-it with the availability of criteria for
design "uality. !oftware design leads three technical activities-design, code and test.
6ach activity transforms information, which validates the software. The design system
converts theoretical solution introduced by the feasibility study into a logical reality.
G
System Design
2.2.1 ER Diagrams
H
2.2.2 Tab,e Design
The pro*ect has been identified to contain twelve data base tables which are
practically as follows9
Tab,e Name" >ranches
*ie,d Name Data Ty%e Si6e
>:)3C( I1 I3T 2
:6I&6!T I1 I3T 2
)PP?IC)3T 3)6 @):C(): #DD
>:)3C( 3)6 @):C(): 2D
>:)3C( ?B)C)TIB3 @):C(): #DD
P(B36 3B @):C(): 2D
)3)%6: @):C(): #DD
):6)! CB@6:I3% @):C(): #DD
Tab,e Name" 1eliveries
*ie,d Name Data Ty%e Si6e
16?I@6:I6! I1 I3T 2
?: 3B I3T 2D
)T6:I)?
P):TIC&?):!
@):C(): #DD
3B BA IT6! I3T 2D
>BBJ61 )T >:)3C( @):C(): #DD
1)T6 BA ?B)1I3% 1)T6
1)T6 BA 16?I@6:K 1)T6
16?I@6:61 )T
>:)3C(
@):C(): #DD
@6(IC?6 3B @):C(): #DD
#D
16?I@6:K !T)T&! @):C(): #DD
Tab,e Name" 1emurrages
*ie,d Name Data Ty%e Si6e
16&::)%6 I1 I3T 2
?: 3B I3T 2D
)T6:I)? @):C(): #DD
C&!TB6: 3)6 @):C(): #DD
3B BA IT6! I3T 2D
1)T6 BA 16?I@6:K 1)T6
A)I: C():%6! TKP6 @):C(): #DD
C():%6! BA 16&::)%6 A?B)T
C():%6! A?B)T
Tab,e Name" 6mployeemaster
*ie,d Name Data Ty%e Si6e
6P I1 I3T .D
6P?BK66 3)6 @):C(): 2D
:B?6 @):C(): 2D
1)T6 BA FBI3 1)T6
!)?):K A?B)T
Tab,e Name" %oods>ooking
*ie,d Name Data Ty%e Si6e
>BBJI3% I1 I3T 2
?: 3B I3T #D
C&!TB6: 3)6 @):C(): 2D
P(B36 3B @):C(): 2D
)T6:I)?
P):TIC&?):!
@):C():
#DD
##
3B BA IT6! I3T 2D
>:)3C( I1 I3T 2
>BBJ61 )T >:)3C( @):C(): #DD
>:)3C( ?BC)TIB3 @):C(): #DD
1)T6 BA >BBJI3% 1)T6
16!TI3)TIB3 @):C(): #DD
>:)3C( 3)6 @):C(): #DD
:B&T6 3B @):C(): #DD
C():%6! C)T6%B:K @):C(): #DD
C():%6! A?B)T
%BB1! !T)T&! @):C(): #DD
Tab,e Name" ?oadingparticulars
*ie,d Name Data Ty%e Si6e
?B)1I3% I1 I3T 2
?: 3B I3T #D
)T6:I)? @):C(): #DD
3B BA IT6! I3T 2D
16!TI3)TIB3 @):C(): #DD
@6(IC?6 3B @):C(): #DD
@6(IC?6 TKP6 @):C(): #DD
:6C6I@6: 3)6 @):C(): #DD
1)T6 BA ?B)1I3% 1)T6
A)I: C():%6! TKP6 @):C(): #DD
?B)1 !T)T&! @):C(): #DD
#.
Tab,e Name" ?ogin
*ie,d Name Data Ty%e Si6e
&!6: I1 @):C(): 2D
P)!!CB:1 @):C(): 2D
)&T( I3T ##
Tab,e Name" aterialparticulars
*ie,d Name Data Ty%e Si6e
)T6:I)? I1 I3T #D
?: 3B I3T #D
)T6:I)?
P):TIC&?):!
@):C(): #DD
3B BA IT6! I3T #D
TBT)? C6I%(T I3T #D
C():%6! C)T6%B:K @):C(): .D
C():%6 A?B)T
Tab,e Name" 3ewbranchre"uests
*ie,d Name Data Ty%e Si6e
:6I&6!T I1 I3T .D
)PP?IC)3T 3)6 @):C(): #DD
)PP?IC)3T )11:6!! @):C(): #2D
P(B36 3B @):C(): #DD
1)T6 BA )PP?K 1)T6
)B&3T 16PB!IT A?B)T
>:)3C( )11:6!! @):C(): #DD
!T)T&! @):C(): #DD
Tab,e Name" :eceivers
*ie,d Name Data Ty%e Si6e
#/
:6C6I@6:! I1 I3T 2
?: 3B I3T 2D
:6C6I@6:! 3)6 @):C(): #DD
>:)3C( 3)6 @):C(): #DD
:6C6I@6:! P(B36 3B @):C(): #DD
>BBJ61 )T @):C(): #DD
)T6:I)? P):TIC&?):! @):C(): #DD
3B BA IT6! I3T 2D
1)T6 BA :6C6I@6 1)T6
C():%6! BA 16&::)%6 A?B)T
C():%6 A?B)T
Tab,e Name" :outes
*ie,d Name Data Ty%e Si6e
:B&T6 I1 I3T 2
:B&T6 3B I3T 2D
P?)C6 @):C(): #DD
):6)! CB@6:I3% @):C(): .2D
Tab,e Name" @ehicles
*ie,d Name Data Ty%e Si6e
@6(IC?6 I1 I3T 2
@6(IC?6 3B @):C(): #DD
@6(IC?6 P):TIC&?):! @):C(): #DD
TKP6 BA @6(IC?6 @):C(): #DD
:63T P6: 1)K A?B)T
1:I@6: 3)6 @):C(): #DD
!T)T&! @):C(): #DD
2.# Ana,ysis Diagrams
2.#.1 Use Case Diagram
#0
2.5 (gic Design
2.5.1 Se-+ence Diagram !r (gin
#2
2.5.2 Se-+ence Diagram !r )ds b1ing
#7
2.5.# Se-+ence Diagram !r Ne4 /ranc0 Re-+est
#8
2.5.5 Activity Diagram
#G
2.5.7 State C0art Diagram
#H
2.5.8 C,ass Diagram
.D
2.5.9 *,4 C0art
.#
2.5.: Cm%nent Diagram
..
2.5.; De%,yment Diagram
./
.0
#. I'$('ENTATION
#.1 'd+,e Screens
#.1.1 Screens0t !r vie4ing ,gin %age
This is the login page of Courier anagement !ystem. This page consists of user id and
password
.2
#.1.2 Screens0t !r vie4ing admin 0me %age
Bnce the admin enters the correct username and password, admin home page will be
displayed.
.7
#.1.# Screens0t !r add ne4 +ser
)dmin can add the users by entering the details of the user in the add new user page.
.8
#.1.5 Screens0t !r vie4ing +sers ,ist
)dmin can see details of the users by clicking on view user list option.
.G
#.1.7 Screens0t !r add ne4 ve0ic,e detai,s
)dmin can add new vehicle details by entering the details in add new vehicle page.
.H
#.1.8 Screens0t !r vie4 re-+esting !r ne4 branc0es
)dmin can check the new branch re"uests by click in the view new branch re"uests page.
/D
#.1.9 Screens0t !r generating ne4 branc0es
)dmin checks the new branch re"uests and generate the new branch by entering the
details of new branch.
/#
#.1.: Screens0t !r adding ne4 r+tes
)dmin checks the new branch re"uests and generate the new branch by entering the
details of new branch.
/.
#.1.; Screens0t !r generating r+tes detai,s based n r+te n
)dmin can generate route details based on the route no. also can generate the other
reports.
//
#.1.1< Screens0t !r 0me %age ! /ranc0 'anager=C,er1
Bnce the user enters the correct username and password, user home page will be
displayed.
/0
#.1.11 Screens0t !r re-+esting !r ne4 branc0
>ranch anager can send the re"uest to the admin for new branch.
/2
#.1.12 Screens0t !r b1ing detai,s entering
&ser make booking by entering the details of article in the booking details entry page.
/7
#.1.1# Screens0t !r entering ,ading detai,s
&ser enter the loading details by entering the details of article and vehicle when the
loading of article to the vehicle details.
/8
#.1.15 Screens0t !r vie4 de,ivery detai,s
&ser can check the delivery details in the view deliverer page.
/G
#.1.17 Screens0t !r generating re%rts
The branch manager also can generate all the reports.
/H
5. TESTIN)
5.1 Intrd+ctin t Testing
Testing is a process, which reveals errors in the program. It is the ma*or "uality
measure employed during software development. 1uring software development. 1uring
testing, the program is e-ecuted with a set of test cases and the output of the program for
the test cases is evaluated to determine if the program is performing as it is e-pected to
perform.
5.2 Sam%,e Test Cases
5.2.1 >?e Test Cases
S N Test case Descri%tin Act+a, va,+e Ex%ected va,+e Res+,t
#
?ogin
;)dmin, >ranch manager,
clerk<
6ntering into
their respective
home pages
:espective (ome
Pages with
Bptions
True
. 6ntering data in to
database
)sks for the
@alid 1ata 6nter
1ata stored
successfully
True
/
%enerating :eports
)dmin and
>ranch manager
can generate the
reports
%enerated all
reports
successfully
True
0
)ccessing the stored data
)s per the
permissions
)dmin, >ranch
manager and
clerk can access
the stored data
!hows the stored
data according to
permissions
True
5
0D
Testing Screen s0at t test t0e system 4it0 va,id +sername and %ass4rd
If we provide the valid user id and password to test the system. It accept and go to the
home page of the user.
0#
Testing Screen ! s+ccess!+, admin ,gin.
This is the home page of Courier anagement !ystem. this page will displayed after
successful login of admin.
0.
5.2.2 @?e Test Cases
S N Test case Descri%tin Act+a, va,+e Ex%ected va,+e Res+,t
#
?ogin
;)dmin, >ranch manager,
clerk<
Credentials
should be same as
saved in 1ata>ase
Cith wrong
credentials no
member can be
logged in
Aalse
. 6ntering data in to database
Bnly valid format
data can store.
Bther than that
formats data can't
be stored
Aalse
/
)ccessing the stored data
)s per the
permissions
)dmin, >ranch
manager and clerk
can access the
stored data
If )dmin or
manager try to
access the data
with out access
permission. ItLs
not allow.
Aalse
7

0/
Testing Screen s0at t test t0e system 4it0 inva,id +sername and %ass4rd
If we provide the invalid user id and password to test the system. It will not accept and it
gives an alert.
00
Testing Screen s0at t test t0e system 4it0 inva,id +sername and %ass4rd
If user enters wrong user name and $ or wrong password, then the application prompts the
user with a message 4Invalid username or password5
02
7. CONC(USION
7.1 Cnc,+sin
The entire pro*ect has been developed and deployed as per the re"uirements stated
by the user, it is found to be bug free as per the testing standards that is implemented.
)ny specification-untraced errors will be concentrated in the coming versions, which are
planned to be developed in near future. The system at present does not take care of the
money payment methods, as the consolidated constructs need !!? standards and are
critically to be initiated in the first face, the application of the credit card transactions is
applied as a developmental phase in the coming days. The system needs more elaborative
technicality for its inception and evolution.
07
Re!erences
/1s"
AA?A Tec0n,gies
F)@) Complete :eference
Fava !cript Programming by Kehuda !hiran
astering F)@) !ecurity
F)@). 3etworking by Pistoria
F)@) !ecurity by !cotl oaks
(ead Airst 6F> !ierra >ates
F.66 Professional by !hadab siddi"ui
F)@) server pages by ?arne Pekowsley
F)@) !erver pages by 3ick Todd
3T'(
(T? >lack >ook by (olzner
AD/C
Aava Database $rgramming 4it0 AD/C by $ate, mss.
!oftware 6ngineering by :oger Pressman
Beb Sites"
#. www.google.com
.. www.wikipedia.com
/. www.tutorialspoint.com
0. www.w/schools.com
08
A$$ENDIC A
A1 S!t4are Envirnment
In our pro*ect most probably we are using !ervlets = Fava !erver Pages ;F!P< to
write the code. !ome times for the &ser Interface we have used (T? for the front end
pages. )nd also we have to use the web container ;Tomcat< to linkup the (T?-
!ervlets. ?et us discuss about each of them.
Aava"
Fava is a computer programming language that is concurrent, class-based, ob*ect-
oriented, and specifically designed to have as few implementation dependencies as
possible. It is intended to let application developers Mwrite once, run anywhereM
;CB:)<, meaning that code that runs on one platform does not need to be recompiled to
run on another. Fava applications are typically compiled to byte code ;class file< that can
run on any Fava virtual machine ;F@< regardless of computer architecture. Fava is, as of
.D#0, one of the most popular programming languages in use, particularly for client-
server web applications, with a reported H million developers. Fava was originally
developed by Fames %osling at !un icrosystems ;which has since merged into Bracle
Corporation< and released in #HH2 as a core component of !un icrosystemsN Fava
platform. The language derives much of its synta- from C and COO, but it has fewer low-
level facilities than either of them.
Serv,ets"
The servlet is a Fava programming language class used to e-tend the capabilities
of a server. )lthough servlets can respond to any types of re"uests, they are commonly
used to e-tend the applications hosted by web servers, so they can be thought of as Fava
applets that run on servers instead of in web browsers. These kinds of servlets are
the Fava counterpart to other dynamic Ceb content technologies such as P(P and )!P
.36T. )nd !ervlet /.# is the latest version of the !ervlets
!ervlets are most often used to9
Process or store data that was submitted from an (T? form
Provide dynamic content such as the results of a database "uery
0G
anage state information that does not e-ist in the stateless (TTP protocol, such
as filling the articles into the shopping cart of the appropriate customer
Technically speaking, a MservletM is a Fava class in Fava 66 that conforms to the
Fava !ervlet )PI, a standard for implementing Fava classes which respond to re"uests.
!ervlets could in principle communicate over any clientPserver protocol, but they are
most often used with the (TTP protocol. Thus MservletM is often used as shorthand for
M(TTP servletM. Thus, a software developer may use a servlet to add dynamic content to
a web server using the Fava platform. The generated content is commonly (T?, but
may be other data such as E?. !ervlets can maintain state in session variables across
many server transactions by using (TTP cookies, or &:? rewriting.
To deploy and run a servlet, a web container ;here Tomcat< must be used. ) web
container ;also known as a servlet container< is essentially the component of a web server
that interacts with the servlets. The web container is responsible for managing the
lifecycle of servlets, mapping a &:? to a particular servlet and ensuring that the &:?
re"uester has the correct access rights.
Aava Server $ages DAS$sE"
Fava !erver Pages ;F!P< is a technology that helps the software developers
create dynamically generated web pages based on (T?, E?, or other document
types. :eleased in #HHH by !un icrosystems.
F!P is similar to P(P, but it uses the Fava programming language. To deploy and
run Fava !erver Pages, a compatible web server with a servlet container, such as )pache
Tomcat or Fetty, is re"uired. )rchitecturally, F!P may be viewed as a high-
level abstraction of Fava servlets. F!Ps are translated into servlets at runtime, each F!PNs
servlet is cached and re-used until the original F!P is modified.
F!P can be used independently or as the view component of a server-side model P
view P controller design, normally with Fava>eans as the model and Fava servlets ;or a
framework such as )pache !truts< as the controller. This is a type of odel
. architecture.
F!P allows Fava code and certain pre-defined actions to be interleaved with static
web markup content, with the resulting page being compiled and e-ecuted on the server
to deliver a document. The compiled pages, as well as any dependent Fava libraries, use
0H
Fava byte code rather than a native software format. ?ike any other Fava program, they
must be e-ecuted within a Fava virtual machine ;F@< that integrates with the serverNs
host operating system to provide an abstract platform-neutral environment.
F!Ps are usually used to deliver (T? and E? documents, but through the use
of Butput !tream, they can deliver other types of data as well.
The Ceb container creates F!P implicit ob*ects like page Conte-t, servlet
Conte-t, session, re"uest = response.
Beb Cntainer"
Ceb container ;also known as a !ervlet container< is the component of a web
server that interacts with Fava servlets. ) web container is responsible for managing the
lifecycle of servlets, mapping a &:? to a particular servlet and ensuring that the &:?
re"uester has the correct access rights. ) web container implements the web component
contract of the Fava 66 architecture, specifying a runtime environment for web
components that includes security, concurrency, lifecycle management, transaction,
deployment, and other services. ) web container provides the same services as
a F!P container as well as a federated view of the Fava 66 platform )PIs.
6-amples of Ceb Container9
)pache Tomcat
%lassAish
F>oss
Fetty
Faminid
Cinstone
In our pro*ect, we are using Tomcat web server, so let us discuss about it.
A%ac0e Tmcat9
)pache Tomcat ;or simply Tomcat, formerly also Fakarta Tomcat< is an open
source web server and servlet container developed by the )pache !oftware Aoundation
2D
;)!A<. Tomcat implements the Fava !ervlet and the Fava !erver Pages ;F!P<
specifications from !un icrosystems, and provides a Mpure FavaM (TTP web server
environment for Fava code to run in. In the simplest config Tomcat runs in a single
operating system process. The process runs a Fava virtual machine ;F@<. 6very single
(TTP re"uest from a browser to Tomcat is processed in the Tomcat process in a separate
thread.
)pache Tomcat includes tools for configuration and management, but can also be
configured by editing E? configuration files.
Tomcat 0.E was released with Catalina ;servlet container<, Coyote ;a (TTP
connector< and Fasper ;a F!P engine<.
Cata,ina"
Catalina is TomcatNs servlet container. Catalina implements !un icrosystemsN
specifications for servlet and Fava !erver Pages ;F!P<. In Tomcat, a :ealm element
represents a MdatabaseM of usernames, passwords, and roles ;similar to &3IE groups<
assigned to those users. 1ifferent implementations of :ealm allow Catalina to be
integrated into environments where such authentication information is already being
created and maintained, and then use that information to implement Container anaged
!ecurity as described in the !ervlet !pecification.
Cyte"
Coyote is TomcatNs (TTP Connector component that supports the (TTP #.#
protocol for the web server or application container. Coyote listens for incoming
connections on a specific TCP port on the server and forwards the re"uest to the Tomcat
6ngine to process the re"uest and send back a response to the re"uesting client. It can
e-ecute F!PNs and !ervlets.
Aas%er"
Fasper is TomcatNs F!P 6ngine. Fasper parses F!P files to compile them into Fava
code as servlets ;that can be handled by Catalina<. )t runtime, Fasper detects changes to
F!P files and recompiles them.
2#
)s of version 2, Tomcat uses Fasper ., which is an implementation of the !un
icrosystemsNs F!P ..D specification. Arom Fasper to Fasper ., important features were
added9
F!P Tag library pooling - 6ach tag markup in F!P file is handled by a tag handler
class. Tag handler class ob*ects can be pooled and reused in the whole F!P servlet.
>ackground F!P compilation - Chile recompiling modified F!P Fava code, the
older version is still available for server re"uests. The older F!P servlet is deleted once
the new F!P servlet has finished being recompiled.
:ecompile F!P when included page changes - Pages can be inserted and included
into a F!P at runtime. The F!P will not only be recompiled with F!P file changes but also
with included page changes.
F1T Fava compiler - Fasper can use the 6clipse F1T ;Fava 1evelopment Tools<
Fava compiler instead of )nt and *avac.
C,+ster"
This component has been added to manage large applications. It is used for load
balancing that can be achieved through many techni"ues. Clustering support currently
re"uires the F1J version #.2 or later.
3ig0 avai,abi,ity"
) high-availability feature has been added to facilitate the scheduling of system
upgrades ;e.g. new releases, change re"uests< without affecting the live environment.
This is done by dispatching live traffic re"uests to a temporary server on a different port
while the main server is upgraded on the main port. It is very useful in handling user
re"uests on high-traffic web applications.
Beb A%%,icatin"
It has also added user as well as system based web applications enhancement to
add support for deployment across the variety of environments. It also tries to manage
session as well as applications across the network.
Tomcat is building additional components. ) number of additional components
may be used with )pache Tomcat. These components may be built by users should they
need them or they can be downloaded from one of the mirrors.
2.
3T'(
(yperte-t arkup ?anguage ;(T?<, the languages of the Corld Cide Ceb
;CCC<, allows users to produces web pages that included te-t, graphics and pointer to
other web pages ;(yperlinks<.
(T? is not a programming language but it is an application of I!B !tandard
GG8H, !%? ;!tandard %eneralized arkup ?anguage<, but !pecialized to hyperte-t and
adapted to the Ceb. The idea behind (yperte-t one point to another point. Ce can
navigate through the information based on out interest and preference. ) markup
language is simply a series of items enclosed within the elements should be displayed.
(yperlinks are underlined or emphasized works that load to other documents or
some portions of the same document. (tml can be used to display any type of document
on the host computer, which can be geographically at a different location. It is a versatile
language and can be used on any platform or desktop. (T? provides tags ;special
codes< to make the document look attractive.
(T? provides are not case-sensitive. &sing graphics, fonts, different sizes,
color, etc... Can enhance the presentation of the document. )nything that is not a tag is
part of the document itself.
/asic 3tm, Tags
QR-- --S !pecific Comments.
Q)STTTQ$)S Creates (yperte-t links.
Q>STTTQ$>S Creates hyperte-t links.
Q>igSTT..Q$>igS Aormats te-t in large-font
Q>odySTT.Q$>odyS contains all tags and te-t in the (tml-
document
QCenterSTTQ$CenterS Creates Te-t
Q11STTT..Q$11S 1efinition of a term.
QT)>?6STTQ$T)>?6S creates table
QTdSTTT..Q$TdS indicates table data in a table.
QTrSTTT..Q$TrS designates a table row
QThSTTT.Q$ThS creates a heading in a table.
2/
Advantages
) (T? document is small and hence easy to send over the net.It is small
because it does not include formatted information.
(T? is platform independent
(T? tags are not case-sensitive.
AA?A Scri%t
Fava!cript is a compact, ob*ect-based scripting language for developing client and
server internet applications. 3etscape 3avigator ..D interprets Fava!cript statements
embedded directly in an (T? page. )nd ?ivewire enables you to create server-based
applications similar to common gateway interface ;cgi< programs.
In a client application for 3avigator, Fava!cript statements embedded in an
(T? Page can recognize and respond to user events such as mouse clicks form Input,
and page navigation.
Aor e-ample, you can write a Fava!cript function to verify that users enter valid
information into a form re"uesting a telephone number or zip code. Cithout any network
transmission, an (tml page with embedded Fava !cript can interpret the entered te-t and
alert the user with a message dialog if the input is invalid or you can use Fava!cript to
perform an action ;such as play an audio file, e-ecute an applet, or communicate with a
plug-in< in response to the user opening or e-iting a page.
20