CONTENTS

1. ORGANISAION PROFILE

2. INTRODUCTION
2.1 SYNOPSIS
2.2 OVERVIEW OF PROJECT.

3. SYSTEM STUDY
3.1 PROBLEM DEFINITION
3.2 SOFTWARE REQUIREMENTS
3.3 HARDWARE REQUIREMENTS

4. CONCEPTS & TECHNIQUES

5. SYSTEM ANALYSIS

6. DESIGN SPECIFICATION
6.1 TABLES
6.2 CONTEXT DIAGRAM
6.3 DATAFLOW DIAGRAMS

7. SYSTEM SPECIFICATION

8. SCREENS

9. RE SULTS AND ADVANTAGES

10. CONCLUSION

11. BIBLIOGRAPHY
INTRODUCTION
 SYNOPSIS

The Project entitled "ONLINE

SHOPPING" is a web-based application Software
developed in JAVA LANGUAGE using Java as front
end on Pentium machine.

The main aim of "ONLINE SHOPPING" is

to improve the services of Customers and vendors.
It maintains the details of customer payments,
product receipts, addition of new customers,
products and also updating, deletion for the
same. It also stores the details of invoices
generated by customer and payments made by them
with all Payments details like credit card.

The primary features of the project

entitled "ONLINE SHOPPING" are high accuracy,
design flexibility and easy availability. And
also it uses database tables Representing
entities and relationships between entities.
 OVERVIEW OF ONLINE SHOPPING

The central concept of the application is

to allow the customer to shop virtually using the
Internet and allow customers to buy the items and
articles of their desire from the store. The
information pertaining to the products are stores
on an RDBMS at the server side (store). The
Server process the customers and the items are
shipped to the address submitted by them.

The application was designed into two

modules first Os for the customers who wish to
buy the articles. Second is for the storekeepers
who maintains and updates the information
pertaining to the articles and those of the
customers?

The end user of this product is a

departmental store where the application is
hosted on the web and the administrator maintains
the database. The application which is deployed
at the customer database, the details of the
items are brought forward from the database for
the customer view based on the selection through
the menu and the database of all the products are
updated at the end of each transaction.

Data entry into the application can be

done through various screens designed for various
levels of users. Once the authorized personnel
feed the relevant data into the system, several
reports could be generated as per the security.
PROBLEM DEFINITION
 PROBLEM DEFINITION

To develop a web-based application to improve

the service to the customers and merchant which in
turn increases the sales and profit in "ONLINE
SHOPPING"

GOALS FOR THE SYSTEM AND THE PROJECT

The system is capable of maintaining details

of various customers, vendors, Products and storing
all the day to day transactions such as generation
of shipment address bills, handling customers and
product receipts, updating of stores.

CONSTRAINTS ON THE SYSTEM AND THE

PROJECT

ONLINE SHOPPING is developed in Java

1.2.2 using Java as front end and it could run
only on Java 1.2 and onward versions.
HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE : PENTIUM SERVER with Network

Of 586 Dx4 300Mhz.
8.3 GB HDD
64MB RAM.

SOFTWARE : JDK1.2.2,JAVASERVER 1.1.3,

SQL SERVER ODBC.

OPERATING SYSTEM : WINDOWS NT.

CONCEPTS AND TECHNIQUES
The Java Packages
Eight packages comprise the standard Java
development environment.

The Java Language Package

The Java language package, also known
as java.lang, contains classes that are core to
the Java language. The classes in this package
are grouped as follows:

Object

The granddaddy of all classes--the class

from which all others inherit.

Data Type Wrappers

A collection of classes used to wrap

variables of a primitive data type: Boolean,
Character, and Double, Float Integer and Long.

Strings

Two classes that implement character

data. The String and String Buffer Classes is a
thorough lesson on the use of both types of
strings.

System and Runtime

These two classes provide let your

programs use system resources. System provides
a system-independent programming interface to
system resources and Runtime gives you direct
system-specific access to the runtime
environment. Using System Resources Describes
both the System and Runtime classes and their
methods.

Threads

The Thread, Thread Death and Thread

Group classes supplement the multi-threading
capabilities so important to the Java language.

The java.lang package also defines the

runnable interface. Runnable makes it
convenient for Java class to be active without
sub classing the Thread class. Through an
example-oriented approach Threads of Control
will teach you about Java threads.

Classes

The Class provides a runtime description

of a class and the Class Loader class allows
you to load classes into your program during
runtime.

Math
The Math class provides a library of math
routines and values such as pi.

Exception, Error, and Throwable

When an error occurs in a Java program,

the program throws an object, which indicates
what the problem was and the state of the
interpreter when the error occurred. Only
objects that derive from the throwable class
can be thrown.

There are two main subclasses of

Throwable: Exception and Error. Exceptions are
a form of Throwable that "normal" programs may
try to catch. Errors are used for more
catastrophic errors--normal programs should not
catch errors. The java.lang package contains
the Throwable, Exception, and Error classes,
and numerous Subclasses of Exception and Error
that represent specific Problems. Handling
Error Using Exceptions shows you how to use
exceptions in your Java programs to handle
errors.

Process

Process objects represent the system

process that is created when you use Runtime to
execute system commands. The java.lang Packages
defines and implements the generic Process
class.

The compiler automatically imports this

package for you. No other packages are
automatically imported.

The Java I/O Package

The Java I/O Package (java.io) provides a

set of input and
Output streams used to read and write data to
files or other
Input and output sources. The classes and
interfaces defined
In java.io are covered fully in Input and
Output Streams.

The Java Utility Package

This Java package, java.util, contains a

collection of utility classes. Among them are
several generic data structures (Dictionary,
Stack, Vector, and Hash table) a useful object
for tokenizing a string and another for
manipulating calendar dates.
The java.util package also contains the
Observer interface and Observable class, which
allow objects to notify one another when they
change. The java.util classes aren't covered
separately in this tutorial although some
examples use these classes.

The Java Networking Package

The java.net package contains classes and

interface definitions that implement various
networking capabilities. The
Classes in this package include a class that
implement a URL, a connection to a URL, a
socket connection, and a datagram packet. You
can use these classes to implement client-
server applications and other networking
communication applications.
Custom Networking and Security has several
examples using these classes, including a
client-server example and an example that uses
datagrams.
The Applet Package

This package contains the Applet class --

the class that you must subclass if you're
writing an applet. Included in this
Package is the Audio Clip interface which
provides a very high level abstraction of
audio. Writing Applets explains the ins and
outs of developing your own applets.

The Abstract Window Toolkit Packages

Three packages comprise the Abstract

Window Toolkit:
Java.awt, java.awt.image, and java.awt.peer.

AWT Package
 The java.awt package provides graphical
user interface (GUI) elements that are used to
get input from and display information to the
user. These elements include windows, buttons,
scrollbars, and text items.

AWT Image Package

The java.awt.image package contains classes

and interfaces for managing image data, such as
setting the color model, cropping, color
filtering, setting pixel values, and grabbing
snapshots of the screen.

AWT Peer Package

The java.awt.peer package contains classes

and interfaces that connect platform-
independent AWT components to their platform-
dependent implementation (such as Motif widgets
or Microsoft Windows controls). Creating a User
Interface covers all three of the AWT packages.
 FEATURES OF JAVA

• Distributed

Java has an extensive library of routines

for coping with TCP/IP protocols like HTTP and
FTP Java applications can open and access
across the Net via URLs with the same ease as
when accessing local file system.

We have found the networking

capabilities of Java to be both strong and easy
to use. Anyone who has tries to do Internet
programming using another language will revel.
How simple Java makes onerous tasks will like
opening a socket connection.

• Robust

Java is intended for writing programs that

must be readable in a Variety ways. Java puts a
lot of emphasis on early checking for possible
problems, later dynamic checking, and
eliminating situations that are error prone...
The single biggest difference between Java has
a pointer model that eliminates the possibility
of overwriting memory and corrupting data.

The Java compiler detects many

problems that in other languages would only
show up at runtime. As for the second point,
anyone who has spent hours chasing a memory
leak cost by a printer bug will be very happy
with this feature of Java.

Java gives you the best of both worlds. You

need not pointers for everyday constructs like
string and arrays. You have the power of
pointers if you need it, for example, for like
lists. And you have always-complete safety,
Since you can never access a bad pointer or
make memory allocation errors.

Secure
Java is intended to be used in
networked/distributed environment toward that
end; a lot of emphasis has been placed on
security. Java enables the contraction of
virus-free, temper-free systems.

Here is a sample of what Java’s

security features are supposed to keep a Java
programming from doing:

1. Overrunning the runtime stack.

2. Corrupting memory outside its own process

space.

3. Reading or writing local files when invoked

through a security-conscious class loader like
Web browser.

Architecture Neutral

The compiler generates an architecture

neutral object file format- the compiled code is
executable on many processors, given the presence
of Java runtime system...The Java compiler does
this by generating byte code instructions which
have nothing to do with a particular computer
architecture. Rather they ere designed to be both
easy to any machine and easily translated into
native machine code on the fly.

Twenty years ago, the UCSD Pascal system did the

same thing in a commercial product and, even
before that, Nicholas Worth’s original
implementation of Pascal used the same approach.
By using bytecodes, performance takes major hit.
The designers of Java did an excellent job
developing a byte code instruction set those
workers well on today’s most common computer
architectures. And the codes have been designed
to translate easily into actual machine
instructions.

Portable

Unlike C and C++, they are no

"implementation dependent" aspects of the
specifications. The sizes of the primitive’s data
types are specified, as is the behavior of
arithmetic on them.
For example, an int in Java is always a
32-bit integer. In C/C++, int can mean a 16-bit
integer, a 32-bit integer, or any size the
compiler vendor likes. The only restriction is
that it must have at least as many bytes int and
cannot have more bytes than a long int.

The libraries that are a part of the

system define portable interfaces. For example,
there is an abstract window class and
implementations of it UNIX, Windows, and the
Macintosh.

Interpreted

The Java interpreters can execute Java

byte codes directly on any machine to which the
interpreter has been ported. Since linking is a
more incremental and lightweight process, the
development process can be much more rapid and
explanatory.

One problem is that the JDK is fairly slow

at compiling your source code to the bytecodes
that will, ultimately, be interpreted in the
current version.

High Performance

While the performance of interpreted

bytecodes is usually more than adequate, there
are situations higher performance is required.
The bytecodes can be translated on fly into
machine code for the particular CPU the
application is running on.

Native code compilers for Java are not yet

generally available. Instead there are just-in-
time (jit) compilers. These work by compiling the
byte codes

Into native code once, caching the results, and

the calling them again, if needed. This speeds up
code once, catching the results, and calling them
again, if needed. This speed up the loop
tremendously since once has to do the
interpretation only once. Although still slightly
slower than a true native code compiler, just-in-
time compilers can give you a 10-or even 20-fold
speedup for some programs and will almost always
be significantly faster than the Java
Interpreter.

Multithreaded

In a number of ways, Java is more

dynamic language than C or C++. It was designed
to adapt to an evolving environment. Libraries
can freely add new methods and instance variables
without any effect on their clients.... In Java,
finding out run time type information is
straightforward.

This is an important feature in those situations

where code needs to be added to a running
program. A prime example is code that is
downloaded from the Internet to run in browser.
PARADIGM OF JAVA

Java as a programming language evolved

keeping in view certain criteria and features.
It was built around a model that had these
features. Some of the features of this model we
have seen like the object oriented, architecture
neutral, robust, secure etc. Some additional
features are explaining below

Dynamic downloading of applets- Applets

should be downloadable on to a client machine as
and when required.

Elimination of fatter phenomenon - Java

based products could eliminate these by giving
the users only those features of a product that
the user needs at a time. The remaining features
of a product can remain on the server itself.

Supports Networks centric computing- Java should

be able to support low cost Network computers.

Supports CORBA& DCOM-Java supports Common Object

Request Broken Architecture (CORBA) and
Distributed Common Object Model (DCOM). This
ensures that certain standards for object
Programming are net. Supports Active X also.

JAVA APPLETS

Applets are a common way of writing Java

applications. Integrating web based sound and
graphics into applications is simplified by
using methods in Applet class. Applets are
essentially program that run from within a
browser. They appear as part of HTML documents
in the same way that pictures are presented.
The major difference is that instead of a static
graphics, the Java Applet is a complete running
program. An Applet is just like a widow
application, but without a classic window frame.
The range of programs that can be written as an
APPLET are reduced because of security
limitations imposed by the target browser.
Applets run only from with in Java-Enabled
browsers such as NETSCAPE, hot Java, and
INTERNET EXPLOSER.

ADVANTAGES OF APPLETS:

There are several advantages using Applets.

The most obvious is that you only need one copy
of your production class files on an HTML
server. This reduces the nightmare of
distributing and installing software by the tape
or disk. Internet and Intranet based software
also reduces the problems of LAN accesses to
software instead of accessing a disk by way of a
network-mounted disk. Files are accessed
through http and FTP.
WEB pages can also be used as a method of
presenting help to your users as well as keeping
them informed about the latest changes to your
programs. This enables due to keep in constant
touch your users.

DISADVANTAGES OF APPLET:

Running your application from a web browser

is not necessarily a good thing. Target users
must be running a version of web browser that
supports that Java. It also helps if uses have
an Internet connection of 28.8 k or higher on
relatively fast computers. Another large
problem is local file access. If the applet was
loaded from an http server, no local files can
be read or written to on the client machines.
Loading the applet from the users local disk
storage can alleviate this, but this defeats any
 Window
Frame
Object Component
Container Panel
Applet

of the web-based applet advantages mention

earlier.

Applets have reduced network access. If an

applet is loaded from networked machine. Only
that machine can be communicated with a via a
socket connection this prevents the applet from
communicating to other machines on web. This
security restriction is alleviated if the applet
is loaded from the users local disk.

Any Java based graphical application can be

easily converted into an applet. This id
because both frame and applet are executed from
the container class.

APPLET LIFE CYCLE:

There are four methods that give the

framework to build the applet
Init ()
Start ()
Stop ()
Destroy ()

Init (): - Used for initial setup such as

defining Layout, passing parameters and other
initializations.

Start (): - This is called immediately after

init () start () is called each time user return
to the pea or when the page is deconified.
Unlike start, init is called only once.

Stop (): - This method is called when the user

moves off the page on which the Applet sits or
when it is iconified. If an applet if not doing
time consuming activities like performing
animation, this need not be implemented.

Destroy (): - This method is called when the

browser shuts down. It is used to re-claim
resources.

JAVA VS C++: -

The syntax of Java looks very much like C+

+. Compared to c++, Java used similar syntax
for if and loops structures. The notion of a
constructor is all very similar to what C++
has.

The following are some of the differences

of Java over C++. If you understand these
differences you will see why Java is such a
beneficial programming language.

•Compare to C++ Java runs 20 times slower

because of platform independents.

•Every thing must be in a class. There are no

global functions or global data. If you want
the equivalent of global, make static methods
and static data within a class. There are no
structures or enumeration or unions. Only
class.

•The Char type uses the international 16-bit.

Unicode character set, so it can automatically
represent most national characters.

• All non-primitive types can only be created

using new. All primitive types can only be
created directly, without new. There are
wrapper classes for all primitive classes so
you can create equivalent heap-based objects
with new

•Java has no Preprocessors. If you want to use

classes in another library, you say import and
the name of the library. There are no
preprocessor-like macros.

•There are no Java pointers in the sense of C

and C++. When you create an object with new,
you get back a reference. For example
String s = new String ("peers");

•Java has no templates or other implementation

of parameterized types. There is a set of
containers : Vectors, stacks and Hash table
that hold object references, and through which
you can satisfy your container needs, but these
containers are not designed for efficiently
like the C++ standard template library(STL)
•Java has built-in support for comment document
action, so the source code file can also
contain its own documentation, which is
stripped out and reformatted into HTML using an
apart program. This is boon for documentation
maintenance and use.
•Java has standard libraries for solving
specific tasks. C++ relies on non-standard
 third-party libraries. These tasks include

- Networking
- Database Connection (via JDBC)
- Multithreading
- Distributed Objects (via RMI and CORBA)
- Compression
- Commerce

The availability and standard nature of

these libraries allow for more rapid
application development.

•Generally, Java is more robust, via

•Object handles initialized to null
•Handles are always checked and exceptions are
thrown for failure
•all array accesses are checked for bounds
violations
•Automatic garbage collection prevents memory
leaks
•Clean, relatively fool-proof exception
handling
•bytecodes verification of network applets

INTRODUCTION TO JDBC

What is JDBC and Why JDBC?

JDBC (Java Database Connectivity) is a

front-tool for connecting to a server and is
similar to ODBC in the respect. However, JDBC
can connect only Java clients and uses ODBC for
the connectivity. JDBC is essentially a low-
level Application, Programming Interface. It
is called a low-level API since any data
manipulation, storage and retrieval has to be
done by the program itself. Some tools that
provide a higher level abstraction are expected
shortly.

JDBC Driver types: -

There are four types of JDBC drivers each

having its own functionality. Please note
that, they do not substitute one another, each
having their own suitability aspects. They are
classified based on how they access data from
the database.

1.Native Jdbc driver:

A JDBC driver, which is partly written in
Java and most of each, implemented using native
methods to access the database. This is useful
in case of Java application that can run only
on some specific platforms. Writing these type
drivers is easier compare to writing other
drivers

2. All Java JDBC Net Drivers:

A JDBC net drivers which uses a common
network protocol to connect to an intermediate
server, which is turn employees native calls to
connect to the data base.
This approach is used for applets where the
request must go through the intermediate
server.

3. JDBC-ODBC bridge driver:

A bridge driver provided with JDBC can
convert. The Jdbc calls in to equaling ODBC
calls using the native methods. Since ODBC
provides for connection to any type of database
that is ODBC compliant, to connect a number of
databases simultaneously, it is very simple
matter. This approach is a recommended once
since using ODBC drivers, which are industry
standard as of now, would make an application
truly portable across the databases.
 Native
JDBC JDBC JDBC NET
Native JDBC Driver Manager
ODBCApplication
Protocol
Driver
ODBC
Bridge DRIVER
Jdbc driver

4. Native Protocol ALL Java Drivers: -

This type of Jdbc driver is written

completely in Java and can access the database
by making use of native protocols of the
database. This method of data access is
suitable in case of Intranets were carry every
thing can run as an application instead of an
applet.

JDBC ARCHITECTURE:

JDBC architecture is shown below.

Components of JDBC are
1. JDBC Driver Manager
2. JDBC Driver
3. JDB-ODBC Bridge
4. Applications.

Uses Native uses special Uses native

Calls to net protocols net protocols
 Access
The data to accessthe to access the
base database database

DATA BASE

JDBC Driver Manager: - Function of the driver

manager is to findout available drivers in the
system and connects the application to the
appropriate database. Whenever a connection is
requested. However, to help the driver manager
identify different types of drivers, each
driver should be registered with the driver
Manager.

JDBC Driver: - Function of the JDBC Driver is

to accept the SQL calls from the application
and convert them into native calls to the
database. However, in this process it may take
help some other drivers or even servers, which
depends on the type of Jdbc Driver we are
using. Also, it is possible that the total
functionality of the database server could be
built into the driver itself.

JDBC-ODBC Bridge: -

Sunsoft provides a special JDBC Driver

called JDBC-ODBC bridge driver, which can be
used to connect to any existing database, that
is ODBC complaint.

APPLICATION: Application is a Java Program

that needs the information to be modified in
some database or wants to retrieve the
information.

SERVLETS:

Client and Servers

To understand the World Wide Web and Server

Side programming must understand the division
between Web clients and Web servers and how HTTP
facilities the interaction between the two.
Putting in simple words, a server handles
request from various clients. For example,
suppose you are using a word processing program
to edit files on another compute. Your computer
would be the client because it is requesting the
files from another computer. The other computer
would be the server because it is handling your
computer's request. With networked computers,
clients and servers are very common. A server
typically runs on a different machine than the
client, although this not always the case. The
interaction between the two usually begins on
the client side. The client software request an
object or transaction from the server software,
which either handles the request an object or
transaction from the server software, which
either handles the request or denies it. If the
request is handled, the object is sent back to
the client software. On the World Wide Web
server are known as webservers, and clients are
known as Webbrowsers. Web browser’s request
documents from web servers, allowing you to view
documents on the World Wide Web. Some of the
most common browsers are Netscape Navigator,
Internet Explorer, and NCA's Mosaic. Like most
software companies that distribute Web Browsers,
these companies also distribute Web server
software (in our case we uses JWS Java Web
Browser). The process of viewing a document on
the web starts when a web browser sends a
request to web server in http request headers.
The Web server receives and views the http
request headers for any relevant information,
such as the name of the file being requested,
and sends back the file with HTTP response
headers. The web browser then uses the HTTP
response headers to determine how to display the
file or data being returned by the web server.
In the case of Servlets we would refer to a URL
with a default port at 8080. If the above said
server are Java Enabled Web Severs. HTTP is
defaulted at port 80 and in case of Servlets it
is defaulted at 8080 that could be changed.

WHY USE SERVLETS?

You may have noticed that the preceding CGI

example could just as easily been a simple HTML
file. In fact, you don't gain advantage from
making it a server side script. So why use any
server side scripting? Well, for the preceding
example, you wouldn't. It is just a simple
example CGI script. As you learn Servlets,
however, you will see that it allows you to
extend the functionality of Web documents to
produce dynamic and interactive pages.

1.An Invitation to Servlets:

This session provides answer to the questions

"What is Servlets" shows typical uses for
Servlets. It also gives a quick introduction to
HTTP and its implementation in the HttpSetvlet
class.

What is Servlets?

Servlets are modules of Java code that run in

a server application to answer client requests.
Servlets are not tied to a specific client-
server protocol but they are most commonly used
with Http and the word "SERVLET" is often used
in the meaning of "HTTP Servlets".

Servlets make use of the Java standard

extension classes in the packages javax.servlet
and javax.servlet.http (extension of the
Servlets framework for Servlets that answer HTTP
requests). Since Servlets are written in the
highly portable Java Language and follow a
standard framework, they provide a means to
create server extensions in a server and
operating system independent way.
Typical uses for HTTP Servlets include:
•Processing and/or storing data submitted an
HTML form.
•Providing synergic content, e.g. returning the
results of a database query to the client.
•Managing state information on top of the
stateless HTTP, e.g. for an online shopping
chart system which manages shopping charts for
many concurrent customers and maps every
request to the right customer.

The Servlet Environment:

Inter-Servlet communication

The inter Servlet communication method

which is described in this section can only be
used with Servlet engines which implement
version 1.0 or 2.0 of the Servlet API. It will
not work with Servlet engines, which comply
strictly, to version 2.1
 Servlets are not alone in a web server.
They have access to other Servlets in the same
Servlet context (usually a Servlet directory),
represented by an instance of
javax.servlet.servletContext. The Servlet
Context is available through the Servlet Config
object's get Servlet context method.

A Servlet can get a list of all othg3r

Servlets in the Servlet context by calling get
Servlet Names on the Servlet Context object. A
Servlet for a known name (probably obtained
through getServletNames) is returned by
getServlet. Note that this method can throw a
ServletException because it may need to load
and initialize the requested ServletException
if this was not already done.

After obtaining the reference to another

Servlet that Servlets methods can be called.
Methods, which are not declared in
javax.servlet.Servelet but in a subclass
thereof can, called by casting the returned
object to the required class type.

Note that in Java the identity of a class is

not only defined by the class name but also by
the Class Loader by which it was loaded. Web
servers usually load each Servlet with a
different class loader. This is necessary to
reload Servlets on the fly because single
classes cannot be replaced in the running JVM.
Only a classloader object with all loaded
classes can be replaced.

This means that classes, which are loaded

by a Servlet class loader, cannot be used for
inter-Servlet communication. A class literal
FooServlet (as used in a type cast like
"FooServlet foo ((FooServlet)
context.getServlet ("FooServlet")") which is
used in class BarServlet is different from the
class literal FooServlet as used in FooServlet
itself.
A way to overcome 5this problem is using a
supercalss or and interface which is loaded by
the system loader and thus shared by all
Servlets. In a Web Server, which is written in
Java, these classes are usually located in the
class path (as defined by the CLASSPATH
environment variable)

Sharing Data between Servlets

Version 2.1 of the Servlet API offers a new

way of sharing named objects between all the
Servlets in a Servlets in Servlet context (and
also other contexts, as you’ll see below) by
binding the objects to the ServletContext
object which is shared by several Servlets.

The ServletContext class has several methods

for accessing the shared objects:

Public void setAttributes (string name,

Object) adds a new object or replaces an old
object by the specified name. The attribute
name should follow the same naming convention
as a package name (e.g. a Servlet
com.foo.fooservlet could have an attribute
com.foo.fooservlet.bar).

Just like a custom ServletRequest

attribute an object which is stored as a
ServletContext attribute should also be
serializable to allow attributes to be shared
by Servlets which are running in different JVMS
on different machines in a load balancing
server environment.

Public Object getAtributes (String name)

returns the name object or null if the
attribute does not exist.

In addition to the user-defined attributes

there may also be predefined attributes, which
are specific to the Servlet engine and provide
additional information about a Servlet
(Context) environment.

Public environment getAtributes name ()

returns an Enumeration of the names of all
available attributes.

Public void remove Attribute (String name)

removes the attributes with the specified name
if it exists.

The separation of Servlets into Servlet

contexts depends on the Servlet engine. The
Servlet Context objects of a Servlet with a
known local URL can be retrieved with the
method public Servlet Context getContext
(String unipath) of the Servlets own Servlet
Context. This method returns null if there is
no Servlet for the specified path or if this
Servlet is not allowed to get the Servlet
Context for the specified path due to security
restrictions.

Compiling Servlets

Servlets can be compiled with the JDK and

other Java compilers, just like Applets and
Applications. If the Servlet packages
javax.servlet and javax.servlet.http are not
included with the compiler or your Servlet
engine you have to install them separately by
downloading the JSDK (Java Servlet Development
Kit) and including the JSDK classes in your
CLASSPATH environment variable.

They can also be worked out with Java Web

Server. Both JSDK and JWS follow the same
rules, except for JSDK providing supporting for
the other servers like IIS and other third
party vendors.
Introduction to world wide web

Internet:

The Internet is a network. Its consists of

thousands of interconnected networks consisting
of different types of computers. It is the
worldwide access to people and information.

The internet stemmed from the concept of

universal database: data that would not only be
accessible to people around the world, but
information that would link easily to others
pieces of information so that the relevant data
can be quickly found by a user.

In 1960s this was explored revolution all

aspects of human-information interaction. The
Internet first began in 1969 when the United
States Department of Defense researched ways of
communication via decentralized computer
networks. After that computers in government
and universities were voluntarily linked. This
quickly spread to other institutions around the
world where today there are an estimated 20
million computers linked together.

UNDERSTANDING INTERNET

A network in which computers are

connected using cables or some other direct
media are said to be in LAN. When a group of
LAN's are connected together they are called
Wan’s. These Wan's are connected via telephone
line, satellite links etc. Importantly these
LAN's are connected to form Wan’s through
special computers called Routers.

The job of a Router is to provide a link from

one network to other where networks can be
LAN’s to form Wan’s to become even larger
Wan's.
 HARDWARE REQUIREMENTS:

If Internet being accessed through a telephone

line
Then we need

•A computer with minimum requirements

•A modem
•A telephone

Taking a first issue of computers with

minimum requirements may put everyone
wondering what could be the requirements?

It would be safe enough to use the 486 or

higher processors for a computer to be fast
enough with at least 16MB to 64MB MEMORY.

INTRODUCTION TO HTML

WHAT IS World Wide Web?

The World Wide Web is a network of

information resources. The web realize on
three mechanism to make the resources readily
available to the widest possible audience:

1. A Uniform name is scheme for locating

resources on the web (E.g.: - URLs)

2. Protocols, for access to named resources

over the web (E.g.: - http).

3. Hypertext, for easy navigation among

resources (E.g.: - HTML)

The ties between the three mechanisms are

apparent throughout this specification.

Introduction to URLs

Every resource available on the web-TML

document, image, video clips, program, etc.
Has an address that may be an encoded by a
Uniform Resource Locator, or "URL"

URLs typically consist of three pieces:

1. The naming scheme of the mechanism used to

access the resource.

2. The name of the machine hosting the

resource.

3. The name of the resource itself, given as a

path.

Consider the URL that designates the

current html specification:
http://www.w3.org//TR/Pr-html4/cover.html

This URL may be read as follows:

They’re a document available via an http

protocol, residing on the machine www.w3.org
Accessible Via the path" TR/Pr-
html4/cover.html". Other schemes you may see
in HTML documents include "mailto " for E-mail
and FTP for FTP. Here is another example if a
URL.
• This one refers to a User's mailbox:
This is text....

For all comments, please send E-mail to

<A href="mailto:Joe@ omeplace.com>
JoeCool</a>.

Fragment Identifiers
Some URLs refer to a location within a
resource. This kind of URL ends with "#"
followed by an anchor identifier (called the
"fragment identifier").

Relative URLs

A relative URL doesn't contain any naming

scheme information. Its path generally refers
to a resource on the same on the same machine
as the current document. Relative URLs may
contain relative path components (".." means
one level up in the hierarchy defined by the
path), and may contain fragment identifiers.

Relative URLs are resolved to full URLs

using a base URL. As an example of relative
URL resolution, assume we have the base URL
http://www.ame.com/support/intro.html. The
relative URL in the following markup for a
hypertext link:

<A href="supplies.html"> Supplies </a>

In HTML, URLs play a role in these situations:

•Linking to another document or resource.

•Linking to an external style sheet for
inclusion in a page.
•Images objects and applets for inclusion in a
page.
•Image maps.
•Form submission
•Frames
•Citing an external reference.
•Referring to metadata conventions describing
a document.

What is HTML?
 To publish information for global
distribution, one needs a universally
understood language, a kind of publishing
mother tongue that all computers may
potentially understand. The publishing
language used by the World Web is HTML (from
HyperTextMarkupLanguage).

HTML gives authors the means to:

Publish online documents with headings, text,

tables, lists, photos, etc.
Retrieve online information via hypertext
links, at the click of a button.
Design forms for conducting transaction with
remote services, for use in searching for
information, making reservations, ordering
products, etc.

Include spreadsheets, video clips, sound

clip, and other applications directly in their
documents.

A brief History of HTML

HTML was originally developed by Tim

Berners-Lee while at CERN, and popularized by
the Mosaic browser developed at NCSA. During
the course of the 1990s it has blossomed with
the explosive growth of the Web. During this
time, HTML has been extended in a number of
ways. The Web depends on Web page others and
vendors sharing the same conventions for HTML.
This has motivated joint work on specification
for HTML.

HTML 2.0 (November 1995) was developed under

the aegis of the Internet Engineering Task
Force (IETF) to codify common practice in
late 1994. HTML+(1993) and [HTML 3.0] (1995)
proposed much richer versions of HTML.Despite
never receiving consensus in standard
discussions, these drafts led to the adoption
of a range of new features. The efforts of
the World Wide Web Consortium’s Html working
group to codify common practice in 1996
resulted in HTML 3.2(January 1997). Most
people agree that HTML documents should work
well across different browsers and platforms.
Achieving interoperability lowers costs to
content provides since that must develop only
one version of a document. If the effort is
not made, there is much greater risk that the
Web will evolve into a proprietary world of
incompatible formats, ultimately reducing the
Web's commercial potential for all
participants.

HTML has been developed with the vision

that all manner of devices should be able to
use information on the Web; PCs with graphics
displays of varying resolution and color
depths, cellular telephones, hand held
devices, devices for speech for output and
input, computers with high or low bandwidth,
and so on.

HTML 4.0

HTML 4.0 extends HTML with mechanism for

style sheets, scripting, frames, embedding
objects, improved support for right to left
and mixed direction text, richer tables, and
enhancements to forms, offering improved
accessibility for people with disabilities.

Internalization

This version of HTML has been designed with the

help of experts in the field of international
-libation, so that document may be written in
every language and web transported easily
around the world. This has been accomplished by
incorporating [RFC2070], which deals with the
internationalization of HTML. One important
step has been the adoption of the ISO? IEC:
10646 Standard (ISO10646) as the document
character set for HTML. This is the world's
most inclusive standard dealing with issues of
the representation of international characters,
test direction, punctuation, and other world
language issues.

HTML now offers greater support for

diverse human languages within a document.
This allows for more effective indexing of
documents for search engines, higher-quality
typography, better text-to-text-speech
conversion, correct hyphenation, etc.

Accessibility

As the Web community grows and its members

diversify in their abilities and skills, it is
crucial that the underlying technologies be
appropriate to their specific needs. HTML has
been designed to make Web pages more
accessible to those with physical limitations.
HTML 4.0 developments in the area of
accessibility include:

Encouraging the use of style sheets to achieve

layout effect.

Making it easier to provide alternate

descriptions of images for non-visual
browsers.
Providing labels for form fields.
Providing labeled hierarchical groupings for
form fields.

Providing the ability to associate a

longer text description with an HTML element.

Tables

Authors now have greater control over

structure and layout (e.g., column groups).
The ability of designers to recommend column
widths allows user agents to display table
data incrementally as it arrives rather than
waiting for the entire table before rendering.

Compound Documents

HTML now offers a standard mechanism for

embedding generic media objects and
applications in HTML documents. The OBJECT
element (together with its more specific
ancestor elements IMG and APPLET) provides a
mechanism for including images, video, sound,
mathematics, specialized applications, and
other objects in a document. It also allows
authors to specify a hierarchy of alternate
renderings for user agents that don't support
a specific rendering.

Style Sheets

Style Sheets simplify HTML markup and

largely relieve HTML of the responsibilities
of presentation. They give both authors and
users control over the presentation of
documents-font information, alignment, colors,
etc. The mechanism for associating a style
sheet with a document is independent of the
style sheet language.

Before the advent of style sheets,

authors and had limited control over
rendering. HTML 3.2 included a number of
attributes and elements offering control over
alignment, font size, and text color. Authors
also exploited tables and images as a means
for laying out pages. The relatively long time
it takes for users to upgrade their browser’s
means that these features will continue to be
used for some time. However, since style
sheets often more powerful presentation
mechanisms, the World Wide Web consortium will
eventually phases out many of HTML's
presentation elements and attributes.

COMPONENTS OF WWW: -

WEBPAGE: -

The part of the Web the user sees the

front-end" is known as a Web page, made up of
links, images, navigation tools text, etc.
Web documents are files of information
residing at a Web site. These documents are
usually coded in HyperTextMarkupLanguage
(HTML)

HOME PAGE: -

Home page is the first page of web

documents. Home page is the entry point for
that particular WWW site. Also, home page is
the page a browser loads. Every browser has
its own home page. However, the default
homepage for a browser can be changed.

LINK: -

A link can be anything on a page such as

text or graphics, is a gateway to another page
within the sight, sore to an entirely
different site.

WEB SITES: -
A group of related pages is a site. They are
the pages to go on he Web. Companies,
Government agencies, institutions,
individuals, etc maintain the web sites.

WEB SERVERS: -

Web sites are housed on a server, which is a

computer design to "serve" the file up to the
user in a proper format. It is also refer to
as the "Back-end" and is actually software
that runs at a web site and returns web
documents upon request by the web browser.
Servers run all the time and wait for users to
request information.
The web gets its name, in fact, from the
interdependent network of server’s worldwide.
The user's computer is a terminal, or end
point, in this network.

HEPERTEXT: -

The operation web realizes on hypertext

as its means of interacting with users.
Hypertext is basically the same regular text-
it can be stored read, searched or edited-
with an important extension: Hypertext
contains connections with in the text to other
documents. This new text would themselves
have links and a connection to others
documents. Continually selecting Hypertext is
like taking a free-associative tool of
information. In this way, hypertext links,
called hyper links, can create a complex
virtual web of connections.

GATEWAY PROGRAMS: -

Programs that accept and process request

from a web server and generate new web pages.
These programs add a new level of
interactivity on the web not possible by
simple HTML documents. These programs usually
Server
SERVER Client
Client

handle requests to run a certain program or

access information from a database.
SERVER

PROTOCAL: -

A protocol is a set of rules for two

computers to use when transferring data. While
the World Wide Web encompasses previously
existing protocols such as GOPHER and FTP,
also critical to the WWW proposal was the
development of new protocol, especially design
for the needs of a distributed hypertext
system. It is a fast, stateless, object
oriented protocol called hypertext transfer
Protocol

Handle
Client
Requests
Server
SYSTEM SPECIFICATION
The application ONLINE SHOPPING was
designed into two modules

1. For the customers who wish to buy the

articles?
2. For the storekeeper who maintains and
updates the information pertaining to the
articles and those of the customers.

BUSSINESS PROCESS MODEL

The end-user of this product is a

departmental store where the application is
hosted on the web and the administrator
maintains the database. The application which
is deployed at the departmental stores will
automate the customer details that are appended
to the customers database, the details of the
items are brought forward from the database for
the customers view based on the selection
through the menu and the database of all the
products are updated at the end of each
transaction.

Data entry into the application can be

done through various screens designed for
various levels of users. Once the authorized
personnel feed relevant data into the system,
several reports could be generated as per the
security.

If the customer wants to buy the product

he wants to enter into the shopping chart. He
selects the desired product, after that he
enter in to the order form he fills the order
form. After filling order form merchant
shipped the product to address specified by the
Customer.

Bill is send by merchant the address

specified by the customer, after that customer
gives the credit card number. Here marchant
can be stored the customer shipped address, and
customer details.

Initially marchant enter with login, which

is maintained in database, and also maintain
the product details in the database. Every
time he has access the insertion Updating and
deletion when and where ever he wants.

The central concept of the application is

to allow the Customer to shop virtually using
the Internet and allow customers to buy the
items and articles of their desire form the
store. The information pertaining to the
products are stored on an RDBMS at the server
side (store). The Server processes the
customer's request and the items are shipped to
the address submitted by them.

HTML is a formal set of specifications

used to define information, which can be added
to the content of a document as an aid
processing. The purpose of HTML is to specify
how the text should be processed. The purpose
of a browser becomes to act as a presentation
engine, to interpret HTML & display the
contents in appropriate manner.

Within Hyper text there will be an

indication of the start and end of the
paragraph, there will be no explicit
instructions about the size, fonts, color,
etc., It will contain the basic information
about the link but no specifications about how
to display the highlight the link. It left to
the browser how information should be
displayed.

The importance of HTML lies with Internet

because one doesn’t know about the end user
since there are different user types on the
NET. If HTML would be a language having
instructions about the colors, sizes & fonts it
would be subjected to a specific environment>
Secondly as the number of users grow day by day
one should think of minimizing the amount of
information to be passed from one system to the
other. Hence HTML would contain plan ext. file
would occupy less space than any other graphics
file but, having the addresses of those
locations.

If hypertext one must send information for

displaying the text and these instructions are
embedded in the text itself.

SYSTEM DESIGN
Design of software involves conceiving,
planning out and specifying the externally
observable characteristics of the software
product. We have data design, architectural
design and user interface design in the design
process. These are explained in the following
section. The goal of design process is to
provide a blue print for implementation,
testing and maintenance activities.

DATA DESIGN:

The primary activity during data design is

to select logical representations of data
objects identified during requirement analysis
and software analysis. A data dictionary
explicitly represents the relationships among
data objects and the constrains on the elements
of the data structure. A data dictionary
should be established and used to define both
data and program design.

FESIBILITY STUDY:

Feasibility study is conducted once the

problem is clearly understood. Feasibility
study is a high level capsule version of the
entire system analysis and design process. The
objective is to determine quickly at a minimum
expense how to solve a problem. The purpose of
feasibility is not to solve the problem but to
determine if the problem is worth solving. The
system has been tested for feasibility in the
following points.

1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.

1. Technical Feasibility: -

The project entitles "Project Monitoring

System" is technically feasibility because of
the below mentioned feature. The project was
developed in Java which Graphical User
Interface.

It provides the high level of reliability,

availability and compatibility. All these make
Java an appropriate language for this project.
Thus the existing software Java is a powerful
language.

2. Economical Feasibility: -

The computerized system will help in

automate the selection leading the profits and
details of the organization. With this
software, the machine and manpower utilization
are expected to go up by 80-90% approximately.
The costs incurred of not creating the system
are set to be great, because precious time can
be wanted by manually.

3. Operational Feasibility:

In this project, the management will know

the details of each project where he may be
presented and the data will be maintained as
decentralized and if any inquires for that
particular contract can be known as per their
requirements and necessaries.
Implementation:

Implementation is the stage where the

theoretical design is turned into a working
system. The most crucial stage in achieving a
new successful system and in giving confidence
on the new system for the users that it will
work efficiently and effectively.

The system can be implemented only after

thorough testing is done and if it is found to
work according to the specification.

It involves careful planning, investigation of

the current system and its constraints on
implementation, design of methods to achieve
the change over and an evaluation of change
over methods a part from planning. Two major
tasks of preparing the implementation are
education and training of the users and
testing of the system.

The more complex the system being

implemented, the more involved will be the
systems analysis and design effort required
just for implementation.

The implementation phase comprises of

several activities. The required hardware and
software acquisition is carried out. The
system may require some software to be
developed. For this, programs are written and
tested. The user then changes over to his new
fully tested system and the old system is
discontinued.

TESTING:
The testing phase is an important part of
software development. It is the process of
finding errors and missing operations and also
a complete verification to determine whether
the objectives are met and the user
requirements are satisfied.

Software testing is carried out in three

steps:

The first includes unit testing, where in

each module is tested to provide its
correctness, validity and also determine any
missing operations and to verify whether the
objectives have been met. Errors are noted
down and corrected immediately. Unit testing
is the important and major part of the
project. So errors are rectified easily in
particular module and program clarity is
increased. In this project entire system is
divided into several modules and is developed
individually. So unit testing is conducted to
individual modules.

The second step includes Integration

testing. It need not be the case, the software
whose modules when run individually and
showing perfect results, will also show
perfect results when run as a whole. The
individual modules are clipped under this
major module and tested again and verified the
results. This is due to poor interfacing,
which may results in data being lost across an
interface. A module can have inadvertent,
adverse effect on any other or on the global
data structures, causing serious problems.

The final step involves validation and

testing which determines which the software
functions as the user expected. Here also some
modifications were. In the completion of the
project it is satisfied fully by the end user.
Maintenance and Enhancement

AS the number of computer based systems,

grieve libraries of computer software began to
expand. In house developed projects produced
tones of thousand soft program source
statements. Software products purchased from
the outside added hundreds of thousands of new
statements. A dark cloud appeared on the
horizon. All of these programs, all of those
source statements-had to be corrected when
false were detected, modified as user
requirements changed, or adapted to new
hardware that was purchased. These activities
were collectively called software Maintenance.

The maintenance phase focuses on change

that is associated with error correction,
adaptations required as the software's
environment evolves, and changes due to
enhancements brought about by changing
customer requirements. Four types of changes
are encountered during the maintenance phase.

Correction
Adaptation
Enhancement
Prevention

Correction:
Even with the best quality assurance
activities is lightly that the customer will
uncover defects in the software. Corrective
maintenance changes the software to correct
defects.
Maintenance is a set of software
Engineering activities that occur after
software has been delivered to the customer
and put into operation. Software configuration
management is a set of tracking and control
activities that began when a software project
begins and terminates only when the software
is taken out of the operation.

We may define maintenance by describing

four activities that are undertaken after a
program is released for use:

Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance or Enhancement
Preventive maintenance or reengineering

Only about 20 percent of all maintenance

work are spent "fixing mistakes". The
remaining 80 percent are spent adapting
existing systems to changes in their external
environment, making enhancements requested by
users, and reengineering an application for
use.

ADAPTATION:

Over time, the original environment (E>G.,

CPU, operating system, business rules,
external product characteristics) for which
the software was developed is likely to
change. Adaptive maintenance results in
modification to the software to accommodate
change to its external environment.

ENHANCEMENT:

As software is used, the customer/user

will recognize additional functions that will
provide benefit. Perceptive maintenance
extends the software beyond its original
function requirements.

PREVENTION:

Computer software deteriorates due to

change, and because of this, preventive
maintenance, often called software re
engineering, must be conducted to enable the
software to serve the needs of its end users.
In essence, preventive maintenance makes
changes to computer programs so that they can
be more easily corrected, adapted, and
enhanced. Software configuration management
(SCM) is an umbrella activity that is applied
throughout the software process. SCM
activities are developed to

Identify change.
Control chug.

Ensure that change is being properly

implemented.
Report change to others that may have an
interest.
DESIGN SPECIFICATION
 TABLES

Table Name: PRODUCT

-----------------------------------------------------
Column Name Type
-----------------------------------------------------
Product Id Int
Product Name Varchar
Product Type Varchar
UnitPrice Float
 Quantity Varchar
Units in stock Int
Units on Order Int
-----------------------------------------------------

Table Name: CUSTOMER

------------------------------------------------
Column Name Type
------------------------------------------------
Order Number Int
Order Date Date
CustomerName Varchar
BillAddress Varchar
ShippingAddress Varchar
PhoneNumber Varchar
Email-Id Varchar
Amount Float
Shipped Status Varchar
------------------------------------------

Table Name: PRODTABLE

------------------------------------------------
Column Name Type
------------------------------------------------
ProdId Int
ProductName Varchar
Price Float
------------------------------------------------

Table Name: CREDITCARD

------------------------------------------------
Column Name Type
------------------------------------------------
CardType Varchar
CardNumber Varchar

------------------------------------------------
DATAFLOW DIAGRAMS
Merchant
Customer

CONTEXT DIAGRAM

Product details

Enhance
Update
Order
Delete

Customer Details

FIRST LEVEL DATA FLOW DIAGRAM FOR MARCHANT

 Enhance stores
Merchant

LOGIN TO ENHANCE STORES

Merchant Details

Store Details
 Delete
Or
Merchant Update

FIRST LEVEL DATA FLOW DIAGRAM FOR MARCHANT

LOGIN TO ENHANCE STORES

Merchant Details

Updated store
Details
Customer Product type

FIRST LEVEL DATAFLOW DIAGRAM FOR CUSTOMER

PROCESSING ON PRODUCTS

Product details

Customer
Details

Amount Payable
Customer Bill Shipment
Address Specified by the Customer
Order

SECOND LEVEL DATA FLOW DIAGRAM FOR BILL

SHIPMENT

Product details

Shipment
Address
INTERPRETATION OF THE RESULT

The system has been implemented and tested

successfully. It meets the information
Requirements specified to the great extent.
Although the system has been designed keeping
the
Present and future requirements in mind and
made very flexible. There are limitations of
the
System. Proper consideration has been given
for a wide range of new enhancements in
The future, through out the development of
system. The system is developed user friendly.

In future, if it is required to generate

reports other than provided by the system, it
can be simply
Achieved by a separate module to the main menu
without affecting the design of the system.

ADVANTAGES
• It simplifies the operation.

• It avoids a lot of manual work.

• Every Transaction is obtained and processed
immediately.
• Avoids errors by avoiding the manual work.
•User friendly screen to enter the data and
Enquire the database tables.
• Online help messages available to the
operating system.
• User can easily access the system without
much experience.
• Provide Hardware and software securities.
• Portable and flexible for further extension.
CONCLUSION

The central concept of the application is

to allow the customer to shop virtually using
the Internet and allow customers to buy the
items and articles of their desire from the
store. The information pertaining to the
products are stores on an RDBMS at the server
side (store). The Server process the customers
and the items are shipped to the address
submitted by them.
The application was designed into two
modules first Os for the customers who wish to
buy the articles. Second is for the
storekeepers who maintains and updates the
information pertaining to the articles and
those of the customers?
The end user of this product is a
departmental store where the application is
hosted on the web and the administrator
maintains the database. The application which
is deployed at the customer database, the
details of the items are brought forward from
the database for the customer view based on the
selection through the menu and the database of
all the products are updated at the end of each
transaction.
 Data entry into the application can be
done through various screens designed for
various levels of users. Once the authorized
personnel feed the relevant data into the
system, several reports could be generated as
per the requirements.
This system offers information relevant to
the user accessing the application thus
avoiding unnecessary overloading and at the
same time maintaining the security.
BIBILIOGRAPHY

HTML Publishing Bible - Alan Simpson.

Netscape Java Script - Peter& John

Kent.
The Complete Reference
OfJava -Patricknaughton

Java Network programming - RustyHarod.

Software Engineering - Fairly.

Analysis & Design

Of Information - James A. Senn.