REPORT

The project name is Location based services in Cellular Network. This

project is for accessing the services provided in some Base stations. We have
divided all areas into number of clusters. Inside each cluster there will be lot of
base stations and mobile nodes. Each base station have lot of services like
hospitals, theater, hotel and train etc.. If we want to access those services, then
we have to give the user name, password and mobile number for authentication.
Only authenticated users can access the services when they move from one
base station to other stations.
It is similar like mobile roaming from one place to another place. If any
person who have the mobile with him, moves from one base station to other one
he gets the tower of that particular base station. Since he has mobile with him, he
can easily identify the services provided in that base station easily. All the
services providing and authenticating the user are done by the administrator. He
has the power to add the clusters, base stations and services to those.
People whom are interested to access the services of his destination base
station have to register and view the services.
Modules are:
Administrator Module
User Module
Services Module

1. INTRODUCTION
1.1 OBJECTIVES
In this fast moving world everyone is working like a machine. They are not
interested to remember each and ever place around the world where they would
like to go. But it is essential to know information about that without spending lot
of time on that. Since we made survey on this and found a better choice of using
mobile communication.

In the present world most of the people having the

mobiles in their hands, if we satisfy their need by using with what they are having
in their hands means they will accept. To obtain that features we are developing
this location based cellular network.
This system provides the service to the members those whom were
registered already in this particular system. If any one newly wants to register in
this system it provides the registration facility also. By registering here he can
know the services like hospitals, Theater and Hotels etc.
The cellular networks are divided into number of clusters; each cluster has
some base stations to transfer signals from one station to another station. Every
base station has some mobile nodes to pass services information within the base
stations.
By selecting the destination base station from Brower screen we can
easily finds the services provided in that particular base station.
This is the platform that we have chosen to work upon for the following
reasons:

Because of its essential in day-to-day life.

Simplicity of its use.

Easy accessibility.

FEASIBILITY STUDY
An important outcome of the initial investigation of the system is that
the system is found to be feasible. Three key considerations are in the
feasibility analysis viz. economic, technical and operational.
Economical Feasibility:
Economic analysis is the most frequently used for evaluating the
effectiveness of the system. It is used to determine the benefits and saving
that are expected from the system and then compare them with the cost.
Operational feasibility:
The proposed system is user friendly and to operate. The system provides
the following advantages: Completely menu driven.
With appropriate error message for every screen, the user can easily
operate the system.
The system provides proper validation checks on the fields used in
the system.

2. PROBLEM DEFINITION AND METHODOLOGY

2.1 DEFINITION
The project Location based cellular network is used to know the
services provided by the destination base stations. This project has three
modules. They are

Administrator Module

User Module

Services Module

Administrator Module
This module will describe various functionalities of the Administrator. Each
Administrator will be given with one user name and password. With this the
Administrator has to enter into his module. If a Administrator login to his page
then he will be given his home page called the Admin page. In this page the
functionalities and controls of the Administrator will be given. These are the
tasks of this Administrator module. They are,
Add base station
Add cluster
Add service details
Add base station
This sub-module is used to add the base stations to each cluster. Here
the details of all the base stations will be given. These details comprise Base
station number, base station name, to which cluster we are adding this base
station.

Add cluster
This sub-module is used to add the clusters to each Area. Here the details of
the entire cluster will be given. These details comprise the clusters number
and clusters name.
Add service details
This sub-module is used to add the service details to each service. Here
the details of all the services will be given. These details comprise like
specific number, specific name, phone number, location etc to each
services.
User Module
This module provides the registration facility to the users those who want
to become a member. Users those who are already a member can only access
these services. To become a Member, he have to give details like username,
password and mobile number for authentication and personal details like first
name, last name, address, phone number and location etc. The registered users
are allowed to access the services only after getting exact user name, password
and mobile number.
Services Module
This module is developed to know the information about the services
present in the Base stations and its Mobile nodes. We are taking some areas and
dividing them into number of clusters each cluster has some Base station, each
of these base stations have lot of Mobile nodes. When we enter from our base
station to destination Base station, we can get list of services like hospitals,
Theater, Hotels etc. are shown to the user. He can select any service and get the
knowledge about that service.

3. DEVELOPMENT PROCESS AND DOCUMENTATION

3.1. REQUIREMENT ANALYSIS AND SPECIFICATIONS

3.1.1. HARDWARE REQUIREMENTS
Processor

Pentium III 800 MHz

Memory size

128 MB RAM

Storage

20 GB Hard Disk
1.44 MB - 3.5 Floppy Disk

Display

EGA/VGA Color Monitor

600 x 800 Pixels Resolution High Color (16 Bit)

Key Board

Any with minimum required keys

Mouse

Any

3.1.2 SOFTWARE REQUIREMENTS

Operating System :

Windows 2k family.

Front-End Tool

HTML, Java Script, J2EE

(Servlet, JSP, JDBC and Java Bean)

Web Server
Back-End Tool

:
:

Apache Tomcat 5.0.

Ms-Access

3.1.3 DATA DICTIONARY

Data dictionary is a repository that contains all the description of all data
produced by the software. It is an organized listing of all data elements that are
pertinent to the system.

Mnode (Mobile node)

Description: It stores the details of the mobile nodes.
Field Name
bno
mno
uname
pass

Field Type
Text
Text
Text
Text

Size
50
50
50
50

Constraints
No
No
No
No

cell

Text

50

No

ltime

Text

50

No

Remote

Text

50

No

Description
Base station number
Mobile node number
User name of the user
Password to the user
In which cell he presents
now.
Login time of the user.
It which Remote network
address he is.

Base(Base station)
Description: It stores the details of the Base station.
Field Name
bno

Field Type
Text

Size
50

Constraints
No

cno

Text

50

No

name

Text

50

No

Description
Base station number.
Mobile nodes present in a
particular Base station
Name of the Mobile node.

Cluster
Description: It stores the details of the Cluster.
Field Name
Plno
location

Field Type
Text
Text

Size
50
50

Constraints
No
No

Description
Cluster number.
Cluster name.

Mnodeinfo(user table)
Description: It stores the details of the User.
Field Name
mno
fame
lname
dod
sex
address
Phone
country
State

Field Type
Text
Text
Text
Text
Text
Text
Text
Text
Text

Size
50
50
50
50
50
50
50
50
50

Constraints
No
No
No
No
No
No
No
No
No

Description
Mobile node number.
First name of the user.
Last name of the user.
Date of birth of user.
Male or female
Address of user.
Phone number of user.
In which Country he is in.
In which state he is in.

Servicecat
Description: It stores the details of the Services.
Field Name
Sno
Name

Field Type
Text
Text

Size
50
50

Constraints
No
No

Description
Service number.
Service name.

Savail()
Description: It stores the details of the Cluster.
Field Name
Sano
Sno
Bno

Field Type
Text
Text
Text

Size
50
50
50

Constraints
No
No
No

Description
Saval number.
Service number.
Base station number.

Hospital
Description: It stores the details of the service-Hospital.
Field Name
Hosno
Bno
hosname
Hosloc
hospno

Field Type
Text
Text
Text
Text
Text

Size
50
50
50
50
50

Constraints
No
No
No
No
No

Description
Hospital number.
Base station number.
Name of the hospital.
Location of the hospital
Phone number of the

Dname
Spl

Text
Text

50
50

No
No

hospital.
Doctor Name
Doctors Specialization.

Hotels
Description: It stores the details of the service-Hotel.
Field Name
Hotno
Bno
Hotname
Hotloc
Cata
Price
hotpno

Field Type
Text
Text
Text
Text
Text
Text
Text

Size
50
50
50
50
50
50
50

Constraints
No
No
No
No
No
No
No

Description
Hotel number.
Base station number.
Name of the hotel.
Location of the hotel.
Category of the hotel.
Level of price (high/low)
Phone number of the hotel.

Theater
Description: It stores the details of the service-Theater.
Field Name
Thno
Bno
Thname
Thloc
capacity

Field Type
Text
Text
Text
Text
Text

Size
50
50
50
50
50

Constraints
No
No
No
No
No

Thpno

Text

50

No

Description
Hospital number.
Base station number.
Name of the hospital.
Location of the hospital.
Capacity of the theater.
Phone number of the
hospital.

Train
Description: It stores the details of the service-Train.
Field Name
Trno
Bno
Start
Destin
Atime
Dtime

Field Type
Text
Text
Text
Text
Text
Text

Size
50
50
50
50
50
50

Constraints
No
No
No
No
No
No

Description
Train number.
Base station number.
Starting place of train.
Destination place of train.
Arrival time of train.
Departure time of train.

SYSTEM DESIGN
Fundamental design Concepts
Fundamental design concepts are evolved over the past three decades.
Although the degree of interest in each concept has varied over the years, each
has stood the test of time. Each provides the software designer with a foundation
from which more sophisticated design methods can be applied. Fundamental
design concepts provide the necessary framework for getting it right.
Abstraction
Abstraction permits one to concentrate on a problem at some level of
generalization without regard to irrelevant low level details, use of abstraction
also permits one to work with concepts and terms that are familiar in the problem
environment without having to transform them to an unfamiliar structure. Two
types of abstraction are there, one is procedural abstraction and data abstraction.
A procedural abstraction is a named sequence of instructions that has a specific
and limited function. A data abstraction is a named collection of data that
describes a data object.
Modularity
Modularity is the single attribute software that allows a program to be
intellectually manageable. Software architecture embodies modularity, that is,
software is divided into named and addressable components, called modules
that are integrated to satisfy problem requirements.
Software Architecture
Software Architecture alludes to the overall structure of the software and
the ways in which that structure provides conceptual integrity for a system.
Control hierarchy also called program structure, represents the organization of
control. The tree structure used to represent the control hierarchy.

Structural Partitioning
The program structure should be partitioned both horizontally and
vertically. Horizontal partitioning defines separate branches of the modular
hierarchy for each major program function, Vertical partitioning called factoring,
suggest that control and work should be distributes top-down in the program
architecture. Top level modules should perform control functions and do little
actual processing work. Modules reside low in the architecture should be the
workers, performing all input, computational, an output tasks.
Data Structure
Data Structure is a representation of logical relationship among
individual elements of data. Because the structure of information will invariably
affects the final procedural design, data structure is very important as the
program structure to the representation

of the software architecture. Data

structure dictates the organization, methods of access, degree of associatively,

and processing alternatives for information. The organization and complexity of a
data structure are limited only by the ingenuity of the designer. Scalar item array
and linked list are some of the representations of the data structure.
Software Procedure
Program structure defines control hierarchy without regard to the sequence
of processing and decisions. Software procedure focuses on the processing
details of each module individually. Procedure must provide a precise
specification of processing, including sequence of events, exact, decision points,
repetitive operations and even data organization / structure. Information hiding
suggests that modules be characterized by design decisions that hide from all
others. In other words, modules should be specified and designed so that
information contained within module is inaccessible to other module.
Design is defining a model of the new system and continues by converting
this model to a new system. The method is used to convert the model of the
proposed system into computer specification. Data models are converted to a
database and processes and flows to user procedures and computer programs.
Design proposes the new system that meets these requirements .This new

system may be built by a fresh or by changing the existing system. The detailed
design starts with three activities, database design, user design and program
design. Database design uses conceptual data model to produce a database
design. User procedure design uses those parts of the DFD outside the
automation boundary to design user procedures.

Data Flow Diagram

The data flow diagram (DFD) is one of the most important tools used by
system analysts. Data flow diagrams are made up of a number symbols, which
represent system components. Most data flow modeling methods use four kinds
of symbols. These symbols are used to represent four kinds of system
components. Processes, data stores, data flows and external entities. Processes
are represented by circles in DFD. Data Flow represented by a thin line in the
DFD and each data store has a unique name and square or rectangle represents
external entities.
Unlike detailed flowchart, Data Flow Diagrams do not supply detailed
description of the modules but graphically describes a systems data and how the
data interact with the system.
To construct a Data Flow Diagram, we use,
Arrow
Circles
Open End Box
Squares
An arrow identifies the data flow in motion. It is a pipeline through which
information is flown like the rectangle in the flowchart. A circle stands for process
that converts data into information. An open-ended box represents a data store,
data at rest or a temporary repository of data. A square defines a source or
destination of system data.

Six rules for constructing a Data Flow Diagram

Arrows should not cross each other.
Squares, circles and files must bear names.
Decomposed data flow squares and circles can have same
names.
Choose meaningful names for data flow
Draw all data flows around the outside of the diagram.

3.1.4

DATA FLOW DIAGRAM

1. Admin Module
ADMIN

LOGI
N

ADD BASE
STATION

BASE STATION

ADD
CLUSTER
STATION
CLUSTERS

ADD
SERVICES

SERVICES

ADD SERVICE
DETAILS

SERVICE
DETAILS

2. User Module

User

Registratio
n
Login

Destination
Base Station

Select
Services

Services Report

3.2.1 DATABASE DESIGN

Database design takes a pivotal role in the development of any application
software. A database is a collection of tables is used to store the related
information it minimum redundancy to serve many users quickly and
efficiently. In this project the tables are designed efficiently (Not duplicate or
orphan records) by applying First, Second Normal form to reduce the
redundancy and not store the orphan records.
Normalization
Normalization is a step-By-step procedure of putting the relation in a form
that is free from all sorts of anomalies. The normalization theory is built
around the concept of the normal forms. The relation is said to be in a
particular form. If it is satisfies certain specified.
In this project, normalization is carried out for the reason given bellow

To reduce the redundancy

To structure the data

Unnormalized Form:
The unnormalized table is that which does not satisfy any constraints. The
table is in unnormalized form if it has multiply entries for a single
corresponding entry.

INPUT DESIGN
The following inputs are required in the proposed system for database as
well as for data manipulation. Input for following modules.

Administrator Module

User Module

Services Module

All the above modules are used in the following controls. They are
Buttons:
The most widely used control is the push button. A push button is a
component that contains a label and that generates an event when it is pressed.
Text Area:
Sometimes a single line of text input is not enough for a given task. To
handle this situation, the AWT includes a simple multi line editor called Text Area.
Text Field:
Text field class implements a single line text entry area, usually called an
edit control. Text field allows the user to enter strings and to edit the text using
the arrow keys, cut and paste keys and mouse selection.
Radio Button:
It is possible to create a set of mutually exclusive check boxes in which
one and only one check box in the group can be checked at any one time.
Drop_ down Box:
The drop_ down box class provides a compact, multiple- choice, scrolling
selection list. Unlike the choice object, which shows only the single selected item
in this menu?

Example:
ADD NEW USER
USER NAME:
LOGIN NAME

PASSWORD :
DOB

E-MAIL

SAVE

CANCE
L

OUTPUT DESIGN
Designing computer should proceed in well thought out manner. The term
output means any information produced by the information system whether
printed or displayed. When analyst design computer out put they identified the
specific output that is needed to meet the requirement. Computer is the most
important source of information to the users. Output design is a process that
involves designing necessary outputs that have to be used by various users
according to requirements.
Efficient intelligent output design should improve the system relationship
with the user and help in decision making. Since the reports are directly required
by the management for taking decision and to draw the conclusion must be
simple, descriptive and clear to the user. Options for outputs and forms are given
in the system menus.
When designing the output, system analyst must accomplish the following:
Determine the information to present.
Decide whether to display, print, speak the information and select
the output medium
Arrange the information in acceptable format.
Decide how to distribute the output to intended receipt.

IMPLEMENTATION
The implementation is the process of converting the design into actual
code. The implementation process is done after completing the designing task.
The goal is to provide the logical order for a creation of the modules and
creation of the system.
The implementation of any software requires perfect satisfaction of the
user. The proposed system takes into account the various difficult faced by the
users in operating system and provides user friendly operations.
The system is implemented in the server and checked for its performance
and accuracy. Successful implementation of the software is accomplished. This
project is to be done using J2EE as front end and Ms-Access as back end. This
project use JSP, HTML controls and events, connected through JDBC ODBC
source.

TESTING
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design, coding. The engineer
creates a serious of test cases that are intended to demolish the software that
has been built. In fact, testing is the one step in this software engineering
process, which could be viewed as destructive rather than constructive. The
testing process is divided into three major components as follows

Unit Testing

Integration Testing

Validation Testing

UNIT TESTING
The software is tested using the unit test method. Unit testing focuses
verification effort on the smallest unit of software design module. Using the
procedural design description as a guide, important control parts are tested to
uncover errors with in the boundary of the module.
Every module in the project is checked for verification.
Example:
Error
float avg;

Description
Variable avg may

Correction
float avg=0;

not have been

initialized.
avg=avg+Double.parseDouble
(rs1.getFloat(9)))

Give the missed

Missing Term

.
INTEGRATION TESTING

Term

This testing is the systematic technique for constructing the program structure
by performing the test in each module and later combining the entire individual module
to form a very large program.
Example:
Error:
The requested resource (http://localhost:8080/dhana/html/resource.html) is not
available.
Correction:
The requested resource should be specified for calling the correct page.
VALIDATION TESTING
Validation testing is the process of testing the input. Whether the given
inputs are valid or invalid.
Example:
The error message will be displayed whenever the wrong data entered
into the textbox. If (Prj_Id=XXX) then error message will be displayed. Because
it accept only number.

MAINTENANCE ISSUES

The term software maintenance is used to describe the software

engineering activities that occur following delivery of a software product to the
customer. The maintenance phase of the software life cycle is the time period in
which a software product performs useful work.
This project deals adaptive maintenance. Adaptive of software to a new
environment may involve moving the software to a different machine. Problem
correction involves modification and revalidation of software to correct errors.
The enhancement of this project can be accomplished easily. That is, any
new functional capabilities can be added to the project by simply including the
new module in the homepage and giving a hyperlink to that module. Adaptation
of this project to a new environment is also performed easily.
Adaptive Maintenance:
Adaptive maintenance results in the modification to the software to
accommodate changes to its external environment. In this project, dynamically
we can add new components when ever necessary. It is designed to
accommodate the new changes in further.
Adaptation of this software to a new environment may involve moving the
software to a different machine. Such as Windows 2000, Windows NT, Windows
98, Windows 95.
Re-Engineering:
Re-Engineering is entirely modifying the existing one. This project deals
with re-engineering concept because entirely modify the software in this project.
Benefits of software:

More security

Easy to access

Simplicity of its use.

CONCLUSION

The Location based cellular network has been developed to

overcome the problem faced in the present system. The developed package was
found to work out the operation effectively. The objectives of the system have
been achieved.
The goals that have been achieved are:

Ensure process time and increase throughput.

Simplifies the operation.

Avoid some manual work.

Reduce data redundancy and inconsistency.

User friendly input screens to enter data.

A consistent and efficient system has been successfully developed,

implemented and tested. The system has been developed using J2EE and MS
Access under Windows 2000. The system is very flexible and user friendly.
Further changes can be incorporated into the system easily. Adequate
documentation provides for maintenance and future enhancement.

5. BIBLIOGRAPHY

Java Server Pages

-James Goodwill, BPB Publications, I Edition.
Software Engineering
- Rogers Pressman, Mc Graw Hill Publications
Java2 complete reference
-Herbert Schildt
JavaScript
- David Flanagan (OReilly)

APPENDIX
SOFTWARE PROFILE
Windows 2000:
The computing world was presented with the first release of the
totally new and revolutionary operating system. Microsoft windows performance
and features that previously has been accessible only on $20,000 annotations
became instantly available to anyone with a high-end personal computer.
Windows is now Microsoft Corporations premier operating system. Designed
around powerful and well thought software architecture, the primary features that
allow Windows to use the full power of todays processors are:
Scalability:
Ability to run on a single pc with a single user up to a multi-user,
microprocessor and network installation.
The Windows GUI:
The familiar graphical user interfaces it presents to the world.
Technologies used:
J2EE:
J2EE is introduced in 1998 defines a multi-tier architecture for
Enterprise Information Systems (EIS).By defining the way in which the multi-tier
application should be developed; J2EE reduces the costs, in both time and
money, of developing large scale enterprise systems. The J2EE platform

specifies the logical application components within a system and defines the
roles played in the development process.
While developing a project, it is significant that the technologies using for
development must be reliable, flexible and robust. In case of a customer support
tool application like this, the matter is more important because it details with a
large number of clients and handles confidential data. After comprehensive
analysis, found that java and related technologies are more suitable for customer
support tool applications since java has many features set that allow it to be an
effective platform for customer support tool.
In addition, Sun has a strong understanding of the critical business
issues necessary to consider for customer tool. Another reason that java in
variety of application servers. Java 2 Enterprise Edition (J2EE) makes the java
language an even better in the customer arena because of some key features
like:

J2EE makes java a fully-fledged server-side development

platform.

J2EE has a solid infrastructure that provides a well-tested

implementation of much common applications needs such as
security and messaging.
J2EE standardizes development making it easier for companies to
commit to J2EE.
Java2 Enterprise Edition or J2EE is a package of specifier aligned to
enable the development of multiplier enterprise applications.
The specifications outline the various components needed within
J2EE enterprise systems the technologies for accessing and

providing services and even the roles played during the

development, deployment and runtime lifecycle.
J2EE handles many critical tasks of customer support tool such as
login maintenance and database maintenance and access.
J2EE Architecture:

JAVA CODE
Intermediate compilation
JAVA BYTE
CODE
Runtime VM interpretation

WIN32

HP-VX

Solaris

Application Components
Four application components are defined in J2EE Platform .They are
Application Components(Stand alone java clients)
Applets(java code which executes within a browser)
Web Components(JSPs, Servlets)
Server Components(EJBs, J2EE, API implementations)
Web Components

They are server side components generally used to provide the

presentation layer to be returned to a client. 2 types of web components existing
are Java Server Pages (JSPs) and Java, Servlets.

Java Server Pages:

There are two ways to achieving dynamic content generation. They are,
Programmatic content generation.
Template-based content generation
Java Servlets fall into the first category, while Java server pages belong to
typically comprise of
Static HTML/XML components
Special JSP Tags
Optionally, snippet of code written in Java Programming Language
called Scriplets.
Unlike a plain HTML page, which contains static content that always
remain the same, a Jsp page can change its content based on any number of
variable items, including the identify of the user, the users browser type,
information provided by the user, and selections made by the user.
A Jsp page contains standard markup language element such as HTML
tags, just like a regular web page. Jsp element that allow the server to insert
dynamic content in the page. Jsp elements can be used for a wide variety of
purposes, such as retrieving user preferences. Jsp pages share the Write Once,
Run anywhere characteristics of Java technology. Jsp technology is a key

component in the java 2 platform, enterprise edition, and Suns highly scalable
architecture for enterprise applications.
Jsp can use the full capability of Java components such as JDBC, RMI,
CORBA, JMS and JNDI. Java Server Pages are built on top of Java servlets and
are designed to increase the efficiency in which programmers and even nonprogrammers can create web content. The main advantages of using JSP are:
JSP pages can be used in the combination with servlets that handle
the business logic, the modal supported by Java servlet template
engines.

Java Server Page Process:

JSP pages are interpreted only once; to java byte-code and

reinterpreted only when the file is modified.

 JSP supports both scripting based and element based dynamic

content, and allows programmers to develop custom tag libraries to
satisfy application-specific needs.
JSP pages are pre-compiled for efficient server processing.
JSP run on all the main web servers.
It is true that both servlets and JSP pages have many features in common
and can be used for serving up dynamic web content. Naturally, this may cause
some confusion as to when to opt for one of the technologies over the other.
Java Server Pages provide a much cleaner separation of presentation from logic,
and are simpler to write. Together, JSP technology and servlets provide an
attractive alternative to other types of dynamic web scripting/programming that
offers platform independence, enhanced performance, and separation of logic
from display, ease of administration, extensibility into the enterprise and most
importantly, ease of use.
Server Components
Server components can be in form of EJBs (Enterprise Java beans).
EJBs executes within a container that manages the runtime behavior of EJBs.
Working with the Model View Controller
Typically entity beans are used to provide the model logic, while a mix of
entity beans and session beans are used to provide the control logic and web
components are used to Implement both control and presentation logic.
The Java Beans specification allows software components to be written in
java, which encapsulates the logic behind the web application and remove the
bulk of the script let code that would otherwise clutter up the jsp. The result Jsp

code that is simpler, easier to maintain, and which is more readily accessible to
non-programmers.
Java uses the beans specification to allow the creation of software
components that can be used by other developers and designers to build
specialist applications. Javas cross platform nature means that the same Java
bean should be reusable across any machine. This really frees us from
dependence on any particular platform

Server Specification
Introduction
This is the top-level entry point of the documentation bundle for the Tomcat 4
Servlet/JSP container. Tomcat 4 implements the Servlet 2.3 and JavaServer
Pages 1.2 specifications from Java Software, and includes many additional
features that make it a useful platform for developing and deploying web
applications and web services.
Select one of the links from the navigation menu (to the left) to drill down to the
more detailed documenation that is available. Each available manual is
described in more detail below.
Application Developers
The following documents are aimed at Application Developers who are
constructing web applications or web services that will run on Tomcat.

Application Developer's Guide - An introduction to the concepts

of a web application as defined in the Servlet 2.3 Specification.
Covers basic organization of your web application source tree, the
structure of a web application archive, and an introduction to the
web application deployment descriptor (/WEB-INF/web.xml).

Servlet/JSP Javadocs - The Servlet 2.3 and JSP 1.2 API

Javadocs.
Catalina Developers
The following documents are for Java developers who wish to contribute to the
development of the Catalina servlet container portion of Tomcat itself, or to better

understand its internal architecture and operation.

Functional Specifications - Requirements specifications for

features of the Catalina servlet container portion of Tomcat 4.

Javadocs - Javadoc API documentation for the Catalina servlet

container portion of Tomcat 4.
Configuring Tomcat
This section will acquaint you with the basic information used during the

configuration of the container.

All of the information in the configuration files is read at startup, meaning that
any change to the files necessitates a restart of the container.

SCREEN SHOTS
HOME PAGE

ADMINISTRATOR PAGE

ADMIN PAGE

SELECTING SERVIES TO ADD DETAILS

ADDING DETAILS TO TRAIN SERVICE

LOGIN PAGE TO USER

REGISTRATION PAGE

SERVICES PAGE

SELECTING DESTINATION BASE STATION SERVICE

SERVICE DETAILS PAGE