Online Hotel Management System

INDEX

1. Introduction

2. System Analysis

a. Existing System

b. proposed System

3. Feasibility Report

a. Technical Feasibility

b. Operational Feasibility

c. Economical Feasibility

4. System Requirement Specification Document

a. Overview

b. Modules Description

c. Process Flow

d. SDLC Methodology

e. Software Requirements

f. Hardware Requirements

5. System Design

a. DFD

b. E-R diagram

c. UML

d. Data Dictionary

6. Technology Description
7. Coding

8. Testing & Debugging Techniques

9. Output Screens

10. Reports

11. Future Enhancements

12. Conclusion

13. Bibliography
INTRODUCTION
Application For Online Hotel Management Systemproviding user with list of various hotels
available in the city considered. It then allows the user to select the item from a list of varied
continental dishes. User also enjoys the freedom to exploit the recipe by changing the ingredients
on request. The order also has a special option for the diabetic and blood pressure patients. This
order is then added to the cart along with any previous orders made and then the bill is paid with
credit card online. User is then thrown with a map to locate his habitat to deploy the order at
doorstep. The other functions of the website include the ability of user to book a table for dinner,
banquet hall or arrange a party as per his responses to the available options. Then the lists of
hotels or restaurants appear which have the required facilities.
SYSTEM ANALYSIS
Existing System
 It can manual system and maintaining records difficult.

 Complexity in management of hotels.

 The existing system may not provide security to Data Base.

 Maintain employees, room types, facilities details is risky tasks.

 This system is not providing secure registration and profile management of all the users
properly.

 Maintaining inventory details are inefficiently.

 Maintaining customer orders are poor.

Proposed System
The development of this new system contains the following activities, which try to automate the
entire process keeping in the view of database integration approach.

 Automates information related to all hotels.

 Avoid mismanagement (verify users profiles, registration of all employees, room types,
customer orders, facilities )

 We can maintain all type of users details properly.

 Rich user interface.

 Maintaining order details are nice.

 Maintaining items, customer booking details are efficiently.

FEASIBILITY STUDY
FEASIBILITY REPORT

TECHNICAL FEASIBILITY:
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at
this point in time, not too many detailed design of the system, making it difficult to access issues
like performance, costs on (on account of the kind of technology to be deployed) etc. A number
of issues have to be considered while doing a technical

analysis.

i) Understand the different technologies involved in the proposed system:

Before commencing the project, we have to be very clear about what are the technologies
that are to be required for the development of the new system.

ii) Find out whether the organization currently possesses the required technologies:

o Is the required technology available with the organization?

o If so is the capacity sufficient?

For instance –
“Will the current printer be able to handle the new reports and forms required for the new
system?”

OPERATIONAL FEASIBILITY:
Proposed projects are beneficial only if they can be turned into information systems that will
meet the organizations operating requirements. Simply stated, this test of feasibility asks if the
system will work when it is developed and installed. Are there major barriers to Implementation?
Here are questions that will help test the operational feasibility of a project:
  Is there sufficient support for the project from management from users? If the current
system is well liked and used to the extent that persons will not be able to see reasons for
change, there may be resistance.

 Are the current business methods acceptable to the user? If they are not, Users may
welcome a change that will bring about a more operational and useful systems.

 Have the user been involved in the planning and development of the project?

 Early involvement reduces the chances of resistance to the system and in

 General and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships encountered. In the existing manual
system, the new system was considered to be operational feasible.

ECONOMIC FEASIBILITY:

Economic feasibility attempts 2 weigh the costs of developing and implementing a new system,
against the benefits that would accrue from having the new system in place. This feasibility study
gives the top management the economic justification for the new system.

A simple economic analysis which gives the actual comparison of costs and benefits are much
more meaningful in this case. In addition, this proves to be a useful point of reference to compare
actual costs as the project progresses. There could be various types of intangible benefits on
account of automation. These could include increased customer satisfaction, improvement in
product quality better decision making timeliness of information, expediting activities, improved
accuracy of operations, better documentation and record keeping, faster retrieval of information,
better employee morale.
SYSTEM REQUIREMENT SPECIFICATION
 OVERVIEW

STUDY OF THE SYSTEM

In the flexibility of uses the interface has been developed a graphics concepts in
mind, associated through a browser interface. The GUI’s at the top level has been
categorized as follows

1. Administrator User Interface Design.

2. Employeer User Interface.

3. Customer User Interface.

4. General User Interface.

Number of Modules
1. General Information and Users Registration Modules.

2. Customer Information Module

3. Employees Module.

4. Hotels and Items Modules.

5. Booking Rooms and Facilities Module.

6. Orders and Shipping Module.

7. Credit Cart Module.

Modules Description

1. General Information and Users Registration Modules

In this module a general user get the Hotel information ,Booking Types Details,
item details and registration details, services details, about us ,contact us details.

2. Customer Information Module:

This module contains the personal information like name, id, address etc., of users. If
user wants to view the data and modify the personal details the of users. He can view the
item, room types, search item details, view facility details. The customer search the items
and make orders to hotel and check the orders whether he had given orders or not.

3. Employees Module:

In this module the employee who belong to hotel can view the his personal details if
he want ,he can modify. The main functionalities of employee is view the orders of
customers and grant orders for particular customer, view booking types, facility types,
hotel profile, view Items, orders.

4. Hotels and Items Modules:

The Administrator for this organization will add new hotels, and facilities
available in this i.e add facilities in the hotels are done by administrator. The hotel details
can view all the general persons and customer who want to bookings and orders the
items. In hotel different type of items and their rates and discounts will available , so
these details can view the all types of user.

5. Booking Rooms and Facilities Module:

 In this module the administrator can add new booking types ,these booking for
room details like how many rooms are available and each room cost is depend on the
room type like (general , deluxe , super), and number of rooms are assigned to each
room types, cost for each room all these details are entered by administrator. Include all
above booking room type ,this organization gives the information of all facilities which
are available in hotels ,these hotel details are introduced by administrator.

6. Orders and Shipping Module:

Based on facilities to the customers may request or orders for items and booking
rooms ,so when employees view orders he can accepts the customer request based on a
availability.

7. Credit Cart Module:

In this module according to the customer requirement that is booking rooms and
orders items can done through on line so can not pay money by hand ,but he can choose
alternate to pay amount by creadit cart which can provide by third party application
PROCESS FLOW
SDLC METHDOLOGIES
This document play a vital role in the development of life cycle (SDLC) as it describes the
complete requirement of the system. It means for use by developers and will be the basic
during testing phase. Any changes made to the requirements in the future will have to go
through formal change approval process.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of
Software Development and Enhancement. This model was not the first model to discuss
iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each
phase starts with a design goal and ends with a client reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye toward
the end goal of the project.

The steps for Spiral Model can be generalized as follows:

 The new system requirements are defined in as much details as possible. This usually
involves interviewing a number of users representing all the external or internal users
and other aspects of the existing system.

 A preliminary design is created for the new system.

 A first prototype of the new system is constructed from the preliminary design. This
is usually a scaled-down system, and represents an approximation of the
characteristics of the final product.

 A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

 4. Constructing and testing the second prototype.

 At the customer option, the entire project can be aborted if the risk is deemed too
great. Risk factors might involved development cost overruns, operating-cost
miscalculation, or any other factor that could, in the customer’s judgment, result in a
less-than-satisfactory final product.

 The existing prototype is evaluated in the same manner as was the previous prototype,
and if necessary, another prototype is developed from it according to the fourfold
procedure outlined above.

 The preceding steps are iterated until the customer is satisfied that the refined
prototype represents the final product desired.

 The final system is constructed, based on the refined prototype.

 The final system is thoroughly evaluated and tested. Routine maintenance is carried
on a continuing basis to prevent large scale failures and to minimize down time.
The following diagram shows how a spiral model acts like:

Fig 1.0-Spiral Model

 ADVANTAGES

 Estimates(i.e. budget, schedule etc .) become more relistic as work progresses,

because important issues discoved earlier.

 It is more able to cope with the changes that are software development generally
entails.

 Software engineers can get their hands in and start woring on the core of a project
earlier.

APPLICATION DEVELOPMENT

N-TIER APPLICATIONS

N-Tier Applications can easily implement the concepts of Distributed Application Design and
Architecture. The N-Tier Applications provide strategic benefits to Enterprise Solutions. While
2-tier, client-server can help us create quick and easy solutions and may be used for Rapid
Prototyping, they can easily become a maintenance and security night mare

The N-tier Applications provide specific advantages that are vital to the business continuity of
the enterprise. Typical features of a real life n-tier may include the following:

 Security

 Availability and Scalability

 Manageability

 Easy Maintenance

 Data Abstraction
The above mentioned points are some of the key design goals of a successful n-tier application
that intends to provide a good Business Solution.

DEFINITION

Simply stated, an n-tier application helps us distribute the overall functionality into various tiers
or layers:

 Presentation Layer

 Business Rules Layer

 Data Access Layer

 Database/Data Store

Each layer can be developed independently of the other provided that it adheres to the standards
and communicates with the other layers as per the specifications.

This is the one of the biggest advantages of the n-tier application. Each layer can potentially
treat the other layer as a ‘Block-Box’.

In other words, each layer does not care how other layer processes the data as long as it sends the
right data in a correct format.
 Fig 1.1-N-Tier Architecture

1. THE PRESENTATION LAYER

Also called as the client layer comprises of components that are dedicated to presenting
the data to the user. For example: Windows/Web Forms and buttons, edit boxes, Text
boxes, labels, grids, etc.

2. THE BUSINESS RULES LAYER

This layer encapsulates the Business rules or the business logic of the encapsulations. To
have a separate layer for business logic is of a great advantage. This is because any
changes in Business Rules can be easily handled in this layer. As long as the interface
between the layers remains the same, any changes to the functionality/processing logic in
this layer can be made without impacting the others. A lot of client-server apps failed to
implement successfully as changing the business logic was a painful process.

3. THE DATA ACCESS LAYER

 This layer comprises of components that help in accessing the Database. If used in the
right way, this layer provides a level of abstraction for the database structures. Simply put
changes made to the database, tables, etc do not affect the rest of the application because
of the Data Access layer. The different application layers send the data requests to this
layer and receive the response from this layer.

4. THE DATABASE LAYER

This layer comprises of the Database Components such as DB Files, Tables, Views, etc.
The Actual database could be created using SQL Server, Oracle, Flat files, etc.
In an n-tier application, the entire application can be implemented in such a way that it is
independent of the actual Database. For instance, you could change the Database
Location with minimal changes to Data Access Layer. The rest of the Application should
remain unaffected.
 SOFTWARE REQUIREMENT AND
HARDWARE REQUIREMENT

SOFTWARE REQUIREMENTS

Operating System : Windows XP/2003 or Linux

User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Web Applications : JDBC, Servlets, JSP
IDE/Workbench : My Eclipse 6.0
Database : Oracle 10g
Server Deployment : Tomcat 5.x

HARDWARE REQUIREMENTS

Processor : Pentium IV
Hard Disk : 40GB
RAM : 512MB or more
SYSTEM DESIGN
DATA FLOW DIAGRAMS
DATA FLOW DIAGRAMS:

A graphical tool used to describe and analyze the moment of data through a system manual or
automated including the process, stores of data, and delays in the system. Data Flow Diagrams
are the central tool and the basis from which other components are developed. The
transformation of data from input to output, through processes, may be described logically and
independently of the physical components associated with the system. The DFD is also know as
a data flow graph or a bubble chart.

DFDs are the model of the proposed system. They clearly should show the requirements on
which the new system should be built. Later during design activity this is taken as the basis for
drawing the system’s structure charts. The Basic Notation used to create a DFD’s are as follows:

1. Dataflow: Data move in a specific direction from an origin to a destination.

2. Process: People, procedures, or devices that use or produce (Transform) Data. The physical
component is not identified.

3. Source: External sources or destination of data, which may be People, programs,

organizations or other entities.

4. Data Store: Here data are stored or referenced by a process in the System.
CONTEXT LEVEL DIAGRAM

E-R DIAGRAM
 FACILTYMASTER
ROOMTYPEMSTR
FACILTYID

FACILDTLS
ROOMT YPEID STDAT E
ENDDATE
ROOMT YPENAME ADITIONALCHARG
COST4ROOM FACILITYNAME
NOOFROOMS FACILITYST ATUS
HOTELID (FK)
FACILT YID (FK)
ROOMDESC
HOTELMASTER ROOMSTATUS

HOTELID

HOTELNAME
HPLOT NO
HST REET

CUSTBOOKINGDTLS
HCITY
HST ATE
HPIN
HST DATE
QUESTIONMASTER
BOOKID
HINCHRGID (FK)
HOTELMAILID
HOTELCONTACT NO BOOKTYPEID (FK)
QUESTIONID ROOMT YPEID (FK)

DEPARTMENTMASTER
NOOFROMS4BOOK
QUESTIONDESC CUSTID (FK)
CARTID
DEPARTMENTID REGIST ERDATE
BKGFROMDATE
BKGFROMTIME
DEPTNAME BKGTODAT E
DEPTLOCAT ION BKGTOTIME
DEPTINCHARGEEMPID BKAMT
DEPTDESCRIPTION STATUS

BOOKTYPEMSTR
BOOKTYPEID

BOOKTYPENAME
COST4HOUR
BOOKTYPEDESC
STATUS
ORDERDTLS

ORDERID (FK)
CUSTID (FK)

QUALIFICATIONMASTER ITEMID (FK)

SHIPINGID (FK)
HOT ELID (FK)
CUSTOMER
QUALID TOTALCOST CUSTID
CARTID
STATUS
QUALFULLNAME CFSTNAME
QUALABBR CMIDNAME
QUALDESC CLST NAME
CDOB
CDOJ

SHIPINGMASTER
CHNO
CST REET
CCITY
SHIPINGID CST ATE
CCOUNTRY
CPHNO
SHIPINGCOST CEMAILID
SHIPEDDATE CUSERNAME
EMPLOYEESMASTER SHIPINCHRGID (FK)
SHIPCPLTEDDATE
CPASSWORD
CPIN
EMPID
ORDERMSTR ITEMMASTER LOGINTYPE

ITEMID
EMPFSTNAME ORDERID
EMPLSTNAME
EMPMIDNAME ITEMNAME
DOB ORDERT YPE ITEMTYPENAME
DOJ ODRQUANTITY ITEMDESC
ADDRESS ODRDAT E ITEMCOST4U
SALARY ODRSTATE DISCUNT
EMPQUALID (FK)
EMPDEPTID (FK)
EMPDESGID (FK)
EMPGENDER
MSTATUS
EMPPHOT O
EMPPHNO
EMAILID
INCHARGEID
DESIGNATIONMASTER QUESTIONID (FK)
ANSWER
LOGINTYPE
DESIGNATIONID USERNAME
PASSWORD
DESIGNATIONNAME PASSMODIFIEDDATE
DESIGNATIONABBR PERFORMANCERANK
DESIGNATIONDESC
UML DIAGRAMS
CLASS DIAGRAMS
CLASS DIAGRAM
Class diagrams describe the structure of the system in terms of classes and
objects. The servlet api class diagram will be as follows.

JSP: Implicit Objects

CLASS COLLABORATIVE DIAGRAME
 FacilityDAO
+flag: boolean = false
CustomerDAO +con: Connection = null
ItemDAO
+flag: boolean = false +AddFacility(fmodel: FacilityModel): boolean
+con: Connection = null +flag: boolean = false
+UpdateFacilityDetails(fmodel: FacilityModel): boolean
+con: Connection = null
<<create>>+CustomerDAO() +DeleteFacilityDetails(fmodel: FacilityModel): boolean
+addCustomerProfile(addcust: CustomerModel): boolean +getFacilityTypes(): CoreHash +addItem(additem: ItemModel): boolean
+UpdateCustomerProfile(updatecust: CustomerModel): boolean +getAllFacilityDetails(docu: String): CoreHash +UpdateItem(additem: ItemModel): boolean
+getAllCustProfile(image: String): CoreHash +getPerFacilityDetails(docu: String, fcilid: int): FacilityModel +addCustOrdersDetails(addorders: ItemModel): boolean
+getPerticularCustProfile(image: String, cstid: int): CustomerModel +UpdateCustOrdrShipingDetails(updateorders: OrderModel): boolean
+getCustProfile(username: String): CustomerModel +getAllItemDetails(): CoreHash
+getPerticularItemDetails(itemid: int): ItemModel
+getItemCostDetails(itemid: int): ItemModel
+getCostOrderShips(): CoreHash
+getEachCustOrderShipsDetails(ordrid: int): OrderModel
BookTypeDAO AbstractDataAccessObject RoomDAO
+flag: boolean = false +mCon: Connection +flag: boolean = false
+con: Connection = null -mProps: Properties +con: Connection = null
+addBookingType(btype: BookTypeModel): boolean +getProperties(): Properties +AddRoomTypes(rmodel: RoomTypeModel): boolean
+UpdateBookingType(btype: BookTypeModel): boolean +setProperties(aProps: Properties) +UpdateRoomTypes(rmodel: RoomTypeModel): boolean
+getAllBookingTypes(): CoreHash +getConnection(): Connection +getAllRoomTypesDetails(): CoreHash
+getEmptyBookingRoomTypes(): CoreHash +getSequenceID(tableName: String, pkid: String): int +getPertRoomTypesDetails(roomtypeid: int): RoomTypeModel
+getBookingTypesDetails(booktypeid: int): BookTypeModel +getAvailNoOfRoomDetails(roomtypeid: int): RoomTypeModel
+CustOrderForBooking(botype: BookTypeModel): boolean
+getCustBookingDetails(custid: int): CoreHash
+getAllCustBookingDetails(): CoreHash

EmpRegistrationDAO
HotelDAO
+con: Connection = null
+flag: boolean = false
-flag: boolean
+con: Connection = null
<<create>>+EmpRegistrationDAO()
<<create>>+HotelDAO()
+addemp(emodel: EmpModel): boolean
+addHotel(addhotel: HotelModel): boolean
+UpdateEmpProfileDetails(emodel: EmpModel): boolean
+UpdateHotelDetails(addhotel: HotelModel): boolean
+addgeneralmanager(emodel: EmpModel): boolean
+getHotelNames(): CoreHash
+getQualification(): CoreHash
+getAllHotelDetails(): CoreHash
+getDeptNames(): CoreHash
+getEachHotelDetails(hid: int): HotelModel
+getUserDeptNames(): CoreHash
+getSuppliersNames(): CoreHash
+getDesigNames(): CoreHash
+getTendersNames(): CoreHash
+getDesigNamesOfUsers(): CoreHash
+getManager(): CoreHash
+getGeneralManager(): CoreHash
+getInchargeName(): EmpModel
+getAllInchargeName(): CoreHash
+addquestion(pmodel: EmpModel): boolean
+getquestionbase(): CoreHash
+getEmployeeAbsDetails(): CoreHash
+getAllEmployeesProfiles(images: String): CoreHash
+getEmployeesPersonalProfiles(images: String, loginname: String): EmpModel
+getEmployeesPersonalIdName(loginname: String): EmpModel
+getEmployeeProfileDetailsById(images: String, employeeid: int): EmpModel
USECASE DIAGRAMS
SYSTEM DIAGRAM

System

Admin

Employee Online Hotel Management System

Customer

General User
Administrator

Login
AddHotels

Profile <<extend>>
ViewHotels

<<extend>>
Hotels AddFacilitiesTypes

<<extend>>
ViewFacilitiesTypes

<<extend>>
Facilities
<<extend>> DeleteFacilitiesTypes
Administrator

<<extend>> AddBookingTypes
Bookings

<<extend>>
ViewBookingTypes

<<extend>>
Items
AddItems

<<extend>>

Logout ViewItems
Employee:

Login

Profile

<<extend>>
ViewHotels
Hotels

Bookings <<extend>> viewCustomerBooking Details

ViewBookingTypes
<<extend>>
Facilities
Employees

ViewFacilitiesTypes

<<extend>>
Items

ViewItems

<<extend>>

Orders ViewCustomerOrders

Logout
Customer

Login

ViewAllHotels

Profile <<extend>>

<<extend>> ViewRoomTypes

Hotels
<<extend>> ViewBookingoomTypes

<<extend>> SearchRooms
Bookings
<<extend>>

ViewBookingoomTypes
<<extend>>

Customer
ViewCustomerBookingRooms

<<extend>>
SearchItems

Items

<<extend>> ViewAllItems

<<extend>>

Facilities ViewFacilitiesTypes

Logout
General User

AboutUS

ContactUS

Services

Registration

Login

General User
ViewAllHotels

ViewBookingoomTypes

ViewAllItems
OPERATIONAL LEVEL SEQUENCE &
COLLABORATION DIAGRAMS
Administrator:

Administrator Home Profile Hotel Facility Booking Items Logout

Authentication
1 : Login()

2 : Validation()

3 : Fail()
4 : SuccessFul()

5 : ViewProfiles()
6 : ModifyProfiles()

7 : AddHotels()
8 : ViewHotels()
9 : ModifyotelDetails()

10 : AddRoomTypes()
11 : ViewRoomTypes()
12 : ModifyRoomTypes()

13 : AddFacilities()
14 : ViewFacilities()
15 : ModifyFacilities()

16 : AddBookingTypes()
17 : ViewBookingTypes()
18 : ModifyBookingTypes()

19 : AddItems()

20 : ViewAllItems()
21 : ModifyItemDetails()

22 : Logout()

23 : Login()
 Hotel
Items

21 : ModifyItemDetails()
11 : ViewRoomTypes()
9 : ModifyotelDetails()
Booking 20 : ViewAllItems()
19 : AddItems() 12 : ModifyRoomTypes()
8 : ViewHotels()
17 : ViewBookingTypes()
18 : ModifyBookingTypes() 10 : AddRoomTypes()
Logout

16 : AddBookingTypes()
15 : ModifyFacilities()
7 : AddHotels()

Facility
23 : Login()
13 : AddFacilities() 22 : Logout()
14 : ViewFacilities()

Home
Administrator
6 : ModifyProfiles()

5 : ViewProfiles() 4 : SuccessFul() 1 : Login()

Profile

2 : Validation() 3 : Fail()

Authentication
Employee:

Home Profile Items Hotels Orders BookingTypes Facility Logout

Employee Authentication

1 : Login()
2 : Validation()

3 : Successful()
4 : Fail()
5 : ViewProfile()
6 : ModifyProfileDetails()

7 : ViewAllItems()

8 : ViewHotels()

9 : ViewAllCustomerOrders()
10 : AcceptstheRequests()

11 : ViewAllBookingTypes()

12 : ViewAllFacilityTypes()

13 : Logout()

14 : Login()
 Orders Items Profile

7 : ViewAllItems()
6 : ModifyProfileDetails()
9 : ViewAllCustomerOrders()
Hotels

10 : AcceptstheRequests() 5 : ViewProfile()

Facility
8 : ViewHotels()

12 : ViewAllFacilityTypes()
Logout
13 : Logout()
BookingTypes

11 : ViewAllBookingTypes() Home

14 : Login()
3 : Successful()

2 : Validation()

4 : Fail()
Employee
Authentication
1 : Login()
Customer:

Customer Authentication Home Profile Hotel facilities Bookings Items Logout

1 : Login()
2 : validation()

3 : Fail()
4 : Successful()
5 : ViewProfile()

6 : ModifyProfile()

7 : ViewHotelDetails()

8 : ViewFacilities()

9 : ViewBookingTypes()

10 : ViewItems()

11 : SearchItems()

12 : MakeOrdersItems()

13 : ViewOrdersList()

14 : Logout()

15 : Login()
 Bookings Items
facilities 13 : ViewOrdersList()

9 : ViewBookingTypes()
12 : MakeOrdersItems()
8 : ViewFacilities()
Profile 10 : ViewItems()
6 : ModifyProfile()

5 : ViewProfile() 11 : SearchItems()

14 : Logout() Logout
7 : ViewHotelDetails()
Hotel Home
15 : Login()

4 : Successful()

3 : Fail() Customer

2 : validation()

1 : Login()
Authentication
General User

GeneralUser Registration AboutUs ContactUS Services ViewItems ViewBookingType Facility

1 : Registration()

2 : ViewAboutusDetails()

3 : ViewContacts()

4 : ViewServices()

5 : ViewAllItemDetails()

6 : ViewBookingTypes()

7 : ViewFacilities()
 Registration 1 : Registration()
7 : ViewFacilities()
GeneralUser
Facility
2 : ViewAboutusDetails()

3 : ViewContacts() 6 : ViewBookingTypes()ViewBookingType

AboutUs
4 : ViewServices() 5 : ViewAllItemDetails()

ContactUS Services ViewItems

ACTIVITY DIAGRAMS
Adminisrator:

Aministrator
Eneter username,password

Authentication
Validation
fail

Successful

Home Profile Hotel Items BookingTypes Facilities Logout

Employee

Employee Enter Username,password

Authentication
Validation
Fail

Successful

Home Profile Hotel BookingTypes Facilities Items Orders Logout

Customer

Customers

Authentication Eneter Username,password

Fail

Validation

Yes

Home Profile Hotels BookingTypes Items Facilities

COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
DATA DICTIONARY
BOOKTYPEMSTR

CARTMSTR

CUSTBOOKINGDTLS

CUSTOMER
DEPARTMENTMASTER

DESIGNATIONMASTER
EMPLOYEESMASTER

FACILTYMASTER
HOTELMASTER

ITEMMASTER

ORDERDTLS
ORDERMSTR

QUALIFICATIONMASTER

QUESTIONMASTER

ROOMTYPEMSTR
SHIPINGMASTER

USERAUTHDETAILS
TECHNOLOGY DESCRIPTION
HTML

HTML, an initialism of Hypertext Markup Language, is the predominant markup language for
web pages. It provides a means to describe the structure of text-based information in a document
— by denoting certain text as headings, paragraphs, lists, and so on — and to supplement that
text with interactive forms, embedded images, and other objects. HTML is written in the form of
labels (known as tags), surrounded by angle brackets. HTML can also describe, to some degree,
the appearance and semantics of a document, and can include embedded scripting language code
which can affect the behavior of web browsers and other HTML processors.

HTML is also often used to refer to content of the MIME type text/html or even more broadly as
a generic term for HTML whether in its XML-descended form (such as XHTML 1.0 and later) or
its form descended directly from SGML

Hyper Text Markup Language

Hypertext Markup Language (HTML), the languages of the World Wide Web (WWW), allows
users to produces Web pages that include text, graphics and pointer to other Web pages
(Hyperlinks).
HTML is not a programming language but it is an application of ISO Standard 8879, SGML
(Standard Generalized Markup Language), but specialized to hypertext and adapted to the Web.
The idea behind Hypertext is that instead of reading text in rigid linear structure, we can easily
jump from one point to another point. We can navigate through the information based on our
interest and preference. A markup language is simply a series of elements, each delimited with
special characters that define how text or other items enclosed within the elements should be
displayed. Hyperlinks are underlined or emphasized works that load to other documents or some
portions of the same document.
HTML can be used to display any type of document on the host computer, which can be
geographically at a different location. It is a versatile language and can be used on any platform
or desktop.
HTML provides tags (special codes) to make the document look attractive. HTML tags are not
case-sensitive. Using graphics, fonts, different sizes, color, etc., can enhance the presentation of
the document. Anything that is not a tag is part of the document itself.

Basic HTML Tags:

<! -- --> specifies comments

<A>……….</A> Creates hypertext links

<B>……….</B> Formats text as bold

<BIG>……….</BIG> Formats text in large font.

<BODY>…</BODY> Contains all tags and text in the HTML document

<CENTER>...</CENTER> Creates text

<DD>…</DD> Definition of a term

<DL>...</DL> Creates definition list

<FONT>…</FONT> Formats text with a particular font

<FORM>...</FORM> Encloses a fill-out form

<FRAME>...</FRAME> Defines a particular frame in a set of frames

<H#>…</H#> Creates headings of different levels( 1 – 6 )

<HEAD>...</HEAD> Contains tags that specify information about a document

<HR>...</HR> Creates a horizontal rule

<HTML>…</HTML> Contains all other HTML tags

<META>...</META> Provides meta-information about a document

<SCRIPT>…</SCRIPT> Contains client-side or server-side script

<TABLE>…</TABLE> Creates a table

<TD>…</TD> Indicates table data in a table

<TR>…</TR> Designates a table row

<TH>…</TH> Creates a heading in a table

Attributes

The attributes of an element are name-value pairs, separated by "=", and written within the start
label of an element, after the element's name. The value should be enclosed in single or double
quotes, although values consisting of certain characters can be left unquoted in HTML (but not
XHTML).Leaving attribute values unquoted is considered unsafe.

Most elements take any of several common attributes: id, class, style and title. Most also take
language-related attributes: lang and dir.

The id attribute provides a document-wide unique identifier for an element. This can be used by
stylesheets to provide presentational properties, by browsers to focus attention on the specific
element or by scripts to alter the contents or presentation of an element. The class attribute
provides a way of classifying similar elements for presentation purposes. For example, an HTML
document (or a set of documents) may use the designation class="notation" to indicate that all
elements with this class value are all subordinate to the main text of the document (or
documents). Such notation classes of elements might be gathered together and presented as
footnotes on a page, rather than appearing in the place where they appear in the source HTML.

An author may use the style non-attributal codes presentational properties to a particular element.
It is considered better practice to use an element’s son- id page and select the element with a
stylesheet, though sometimes this can be too cumbersome for a simple ad hoc application of
styled properties. The title is used to attach subtextual explanation to an element. In most
browsers this title attribute is displayed as what is often referred to as a tooltip. The generic
inline span element can be used to demonstrate these various non-attributes.
The preceding displays as HTML (pointing the cursor at the abbreviation should display the title
text in most browsers).

Advantages

 A HTML document is small and hence easy to send over the net. It is small
because it does not include formatted information.
 HTML is platform independent.
 HTML tags are not case-sensitive.
JavaScript

JavaScript is a script-based programming language that was developed by Netscape

Communication Corporation. JavaScript was originally called Live Script and renamed as
JavaScript to indicate its relationship with Java. JavaScript supports the development of both
client and server components of Web-based applications. On the client side, it can be used to
write programs that are executed by a Web browser within the context of a Web page. On the
server side, it can be used to write Web server programs that can process information submitted
by a Web browser and then update the browser’s display accordingly

Even though JavaScript supports both client and server Web programming, we prefer JavaScript
at Client side programming since most of the browsers supports it. JavaScript is almost as easy to
learn as HTML, and JavaScript statements can be included in HTML documents by enclosing the
statements between a pair of scripting tags

<SCRIPTS>.. </SCRIPT>.

<SCRIPT LANGUAGE = “JavaScript”>

JavaScript statements

</SCRIPT>

Here are a few things we can do with JavaScript:

 Validate the contents of a form and make calculations.

 Add scrolling or changing messages to the Browser’s status line.
 Animate images or rotate images that change when we move the mouse over
them.
 Detect the browser in use and display different content for different browsers.
 Detect installed plug-ins and notify the user if a plug-in is required.

We can do much more with JavaScript, including creating entire application.

JavaScript Vs Java
JavaScript and Java are entirely different languages. A few of the most glaring differences are:

 Java applets are generally displayed in a box within the web document; JavaScript can
affect any part of the Web document itself.
 While JavaScript is best suited to simple applications and adding interactive features to
Web pages; Java can be used for incredibly complex applications.

There are many other differences but the important thing to remember is that JavaScript and
Java are separate languages. They are both useful for different things; in fact they can be used
together to combine their advantages.

Advantages

 JavaScript can be used for Sever-side and Client-side scripting.

 It is more flexible than VBScript.
 JavaScript is the default scripting languages at Client-side since all the browsers
supports it.
Java Technology

Initially the language was called as “oak” but it was renamed as “Java” in 1995. The primary
motivation of this language was the need for a platform-independent (i.e., architecture neutral)
language that could be used to create software to be embedded in various consumer electronic
devices.

 Java is a programmer’s language.

 Java is cohesive and consistent.
 Except for those constraints imposed by the Internet environment, Java gives the
programmer, full control.
 Finally, Java is to Internet programming where C was to system programming.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands the Universe of
objects that can move about freely in Cyberspace. In a network, two categories of objects are
transmitted between the Server and the Personal computer. They are: Passive information and
Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the
areas of Security and probability. But, Java addresses those concerns and by doing so, has
opened the door to an exciting new form of program called the Applet.

Java can be used to create two types of programs

Applications and Applets : An application is a program that runs on our Computer under the
operating system of that computer. It is more or less like one creating using C or C++. Java’s
ability to create Applets makes it important. An Applet is an application designed to be
transmitted over the Internet and executed by a Java –compatible web browser. An applet is
actually a tiny Java program, dynamically downloaded across the network, just like an image.
But the difference is, it is an intelligent program, not just a media file. It can react to the user
input and dynamically change.
Features of Java Security

Every time you that you download a “normal” program, you are risking a viral infection. Prior to
Java, most users did not download executable programs frequently, and those who did scan them
for viruses prior to execution. Most users still worried about the possibility of infecting their
systems with a virus. In addition, another type of malicious program exists that must be guarded
against. This type of program can gather private information, such as credit card numbers, bank
account balances, and passwords. Java answers both these concerns by providing a “firewall”
between a network application and your computer.

When you use a Java-compatible Web browser, you can safely download Java applets without
fear of virus infection or malicious intent.

Portability

For programs to be dynamically downloaded to all the various types of platforms connected to
the Internet, some means of generating portable executable code is needed .As you will see, the
same mechanism that helps ensure security also helps create portability. Indeed, Java’s solution
to these two problems is both elegant and efficient.

The Byte code

The key that allows the Java to solve the security and portability problems is that the output of
Java compiler is Byte code. Byte code is a highly optimized set of instructions designed to be
executed by the Java run-time system, which is called the Java Virtual Machine (JVM). That is,
in its standard form, the JVM is an interpreter for byte code.

Translating a Java program into byte code helps makes it much easier to run a program in a wide
variety of environments. The reason is, once the run-time package exists for a given system, any
Java program can run on it.

Although Java was designed for interpretation, there is technically nothing about Java that
prevents on-the-fly compilation of byte code into native code. Sun has just completed its Just In
Time (JIT) compiler for byte code. When the JIT compiler is a part of JVM, it compiles byte
code into executable code in real time, on a piece-by-piece, demand basis. It is not possible to
compile an entire Java program into executable code all at once, because Java performs various
run-time checks that can be done only at run time. The JIT compiles code, as it is needed, during
execution.

Java Virtual Machine (JVM)

Beyond the language, there is the Java virtual machine. The Java virtual machine is an important
element of the Java technology. The virtual machine can be embedded within a web browser or
an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of
the loading process, a class loader is invoked and does byte code verification makes sure that the
code that’s has been generated by the compiler will not corrupt the machine that it’s loaded on.
Byte code verification takes place at the end of the compilation process to make sure that is all
accurate and correct. So byte code verification is integral to the compiling and executing of Java
code.

Overall Description

Java Source Java byte code JavaVM

Java .Class
Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first box indicates that the
Java source code is located in a. Java file that is processed with a Java compiler called javac. The
Java compiler produces a file called a. class file, which contains the byte code. The .Class file is
then loaded across the network or loaded locally on your machine into the execution
environment is the Java virtual machine, which interprets and executes the byte code.

Java Architecture

Java architecture provides a portable, robust, high performing environment for development.
Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then
interpreted on each platform by the run-time environment. Java is a dynamic system, able to load
code when needed from a machine in the same room or across the planet.

Compilation of code

When you compile the code, the Java compiler creates machine code (called byte code) for a
hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed to execute the
byte code. The JVM is created for overcoming the issue of portability. The code is written and
compiled for one machine and interpreted on all machines. This machine is called Java Virtual
Machine.

Compiling and interpreting Java Source Code

Java
PC Compiler
Java
Interpreter
Source
(PC)
Code
Macintosh Byte code Java
………..
Compiler Interpreter
………..
(Macintosh)
SPARC
(Platform Java
……….. Compiler Independe Interpreter
nt)
(Spare)

…………

During run-time the Java interpreter tricks the byte code file into thinking that it is running on a
Java Virtual Machine. In reality this could be a Intel Pentium Windows 95 or SunSARC station
running Solaris or Apple Macintosh running system and all could receive code from any
computer through Internet and run the Applets.

Simple
Java was designed to be easy for the Professional programmer to learn and to use effectively. If
you are an experienced C++ programmer, learning Java will be even easier. Because Java
inherits the C/C++ syntax and many of the object oriented features of C++. Most of the
confusing concepts from C++ are either left out of Java or implemented in a cleaner, more
approachable manner. In Java there are a small number of clearly defined ways to accomplish a
given task.

Object-Oriented

Java was not designed to be source-code compatible with any other language. This allowed the
Java team the freedom to design with a blank slate. One outcome of this was a clean usable,
pragmatic approach to objects. The object model in Java is simple and easy to extend, while
simple types, such as integers, are kept as high-performance non-objects.

Robust

The multi-platform environment of the Web places extraordinary demands on a program,

because the program must execute reliably in a variety of systems. The ability to create robust
programs was given a high priority in the design of Java. Java is strictly typed language; it
checks your code at compile time and run time.
Java virtually eliminates the problems of memory management and de-allocation, which is
completely automatic. In a well-written Java program, all run time errors can –and should –be
managed by your program.
Java Database Connectivity

What Is JDBC?

JDBC is a Java API for executing SQL statements. (As a point of interest, JDBC is a
trademarked name and is not an acronym; nevertheless, JDBC is often thought of as standing for
Java Database Connectivity. It consists of a set of classes and interfaces written in the Java
programming language. JDBC provides a standard API for tool/database developers and makes it
possible to write database applications using a pure Java API.

Using JDBC, it is easy to send SQL statements to virtually any relational database. One can write
a single program using the JDBC API, and the program will be able to send SQL statements to
the appropriate database. The combinations of Java and JDBC lets a programmer write it once
and run it anywhere.

What Does JDBC Do?

Simply put, JDBC makes it possible to do three things:

 Establish a connection with a database
 Send SQL statements
 Process the results.

JDBC versus ODBC and other APIs

At this point, Microsoft's ODBC (Open Database Connectivity) API is that probably the most
widely used programming interface for accessing relational databases. It offers the ability to
connect to almost all databases on almost all platforms.

So why not just use ODBC from Java? The answer is that you can use ODBC from Java, but this
is best done with the help of JDBC in the form of the JDBC-ODBC Bridge, which we will cover
shortly. The question now becomes "Why do you need JDBC?" There are several answers to this
question:
 1. ODBC is not appropriate for direct use from Java because it uses a C interface. Calls
from Java to native C code have a number of drawbacks in the security, implementation,
robustness, and automatic portability of applications.
2. A literal translation of the ODBC C API into a Java API would not be desirable. For
example, Java has no pointers, and ODBC makes copious use of them, including the
notoriously error-prone generic pointer "void *". You can think of JDBC as ODBC
translated into an object-oriented interface that is natural for Java programmers.
3. ODBC is hard to learn. It mixes simple and advanced features together, and it has
complex options even for simple queries. JDBC, on the other hand, was designed to keep
simple things simple while allowing more advanced capabilities where required.
4. A Java API like JDBC is needed in order to enable a "pure Java" solution. When ODBC
is used, the ODBC driver manager and drivers must be manually installed on every client
machine. When the JDBC driver is written completely in Java, however, JDBC code is
automatically installable, portable, and secure on all Java platforms from network
computers to mainframes.
Two-tier and Three-tier Models

The JDBC API supports both two-tier and three-tier models for database access.

In the two-tier model, a Java applet or application talks directly to the database. This requires a
JDBC driver that can communicate with the particular database management system being
accessed. A user's SQL statements are delivered to the database, and the results of those
statements are sent back to the user. The database may be located on another machine to which
the user is connected via a network. This is referred to as a client/server configuration, with the
user's machine as the client, and the machine housing the database as the server. The network can
be an Intranet, which, for example, connects employees within a corporation, or it can be the
Internet.
 JAVA
Client machine
Application

JDBC
DBMS-proprietary protocol

DBMS Database server

Java applet or
Client machine (GUI)
Html browser

HTTP, RMI, or CORBA calls

Application
Server (Java)
Server machine (business
JDBC DBMS-proprietary protocol
Logic)

Database server

DBMS

In the three-tier model, commands are sent to a "middle tier" of services, which then send SQL
statements to the database. The database processes the SQL statements and sends the results back
to the middle tier, which then sends them to the user. MIS directors find the three-tier model very
attractive because the middle tier makes it possible to maintain control over access and the kinds
of updates that can be made to corporate data. Another advantage is that when there is a middle
tier, the user can employ an easy-to-use higher-level API which is translated by the middle tier
into the appropriate low-level calls. Finally, in many cases the three-tier architecture can provide
performance advantages.

Until now the middle tier has typically been written in languages such as C or C++, which offer
fast performance. However, with the introduction of optimizing compilers that translate Java
byte code into efficient machine-specific code, it is becoming practical to implement the middle
tier in Java. This is a big plus, making it possible to take advantage of Java's robustness,
multithreading, and security features. JDBC is important to allow database access from a Java
middle tier.
JDBC Driver Types

The JDBC drivers that we are aware of at this time fit into one of four categories:

 JDBC-ODBC bridge plus ODBC driver

 Native-API partly-Java driver
 JDBC-Net pure Java driver
 Native-protocol pure Java driver

JDBC-ODBC Bridge

If possible, use a Pure Java JDBC driver instead of the Bridge and an ODBC driver. This
completely eliminates the client configuration required by ODBC. It also eliminates the potential
that the Java VM could be corrupted by an error in the native code brought in by the Bridge (that
is, the Bridge native library, the ODBC driver manager library, the ODBC driver library, and the
database client library).

What Is the JDBC- ODBC Bridge?

The JDBC-ODBC Bridge is a JDBC driver, which implements JDBC operations by

translating them into ODBC operations. To ODBC it appears as a normal application
program. The Bridge implements JDBC for any database for which an ODBC driver is
available. The Bridge is implemented as the

Sun.jdbc.odbc Java package and contains a native library used to access ODBC. The Bridge
is a joint development of Innersole and Java Soft.
JDBC connectivity

The JDBC provides database-independent connectivity between the J2EE platform and a wide
range of tabular data sources. JDBC technology allows an Application Component Provider to:

 Perform connection and authentication to a database server

 Manager transactions
 Move SQL statements to a database engine for preprocessing and execution
 Execute stored procedures
 Inspect and modify the results from Select statements
Database:

A database management system (DBMS) is computer software designed for the purpose of
managing databases, a large set of structured data, and run operations on the data requested by
numerous users. Typical examples of DBMSs include Oracle, DB2, Microsoft Access, Microsoft
SQL Server, Firebird, PostgreSQL, MySQL, SQLite, FileMaker and Sybase Adaptive Server
Enterprise. DBMSs are typically used by Database administrators in the creation of Database
systems. Typical examples of DBMS use include accounting, human resources and customer
support systems.

Originally found only in large companies with the computer hardware needed to support large
data sets, DBMSs have more recently emerged as a fairly standard part of any company back
office.

Description

A DBMS is a complex set of software programs that controls the organization, storage,
management, and retrieval of data in a database. A DBMS includes:

 A modeling language to define the schema of each database hosted in the DBMS, according
to the DBMS data model.
 The four most common types of organizations are the hierarchical, network, relational
and object models. Inverted lists and other methods are also used. A given database
management system may provide one or more of the four models. The optimal
structure depends on the natural organization of the application's data, and on the
application's requirements (which include transaction rate (speed), reliability,
maintainability, scalability, and cost).
 The dominant model in use today is the ad hoc one embedded in SQL, despite the
objections of purists who believe this model is a corruption of the relational model,
since it violates several of its fundamental principles for the sake of practicality and
 performance. Many DBMSs also support the Open Database Connectivity API that
supports a standard way for programmers to access the DBMS.
 Data structures (fields, records, files and objects) optimized to deal with very large
amounts of data stored on a permanent data storage device (which implies relatively slow
access compared to volatile main memory).

 A database query language and report writer to allow users to interactively interrogate the
database, analyze its data and update it according to the users privileges on data.
 It also controls the security of the database.
 Data security prevents unauthorized users from viewing or updating the database.
Using passwords, users are allowed access to the entire database or subsets of it
called subschemas. For example, an employee database can contain all the data about
an individual employee, but one group of users may be authorized to view only
payroll data, while others are allowed access to only work history and medical data.
 If the DBMS provides a way to interactively enter and update the database, as well as
interrogate it, this capability allows for managing personal databases. However, it
may not leave an audit trail of actions or provide the kinds of controls necessary in a
multi-user organization. These controls are only available when a set of application
programs are customized for each data entry and updating function.

 A transaction mechanism, that ideally would guarantee the ACID properties, in order to
ensure data integrity, despite concurrent user accesses (concurrency control), and faults (fault
tolerance).
 It also maintains the integrity of the data in the database.
 The DBMS can maintain the integrity of the database by not allowing more than one
user to update the same record at the same time. The DBMS can help prevent
duplicate records via unique index constraints; for example, no two customers with
the same customer numbers (key fields) can be entered into the database. See ACID
properties for more information (Redundancy avoidance).

The DBMS accepts requests for data from the application program and instructs the operating
system to transfer the appropriate data.
When a DBMS is used, information systems can be changed much more easily as the
organization's information requirements change. New categories of data can be added to the
database without disruption to the existing system.

Organizations may use one kind of DBMS for daily transaction processing and then move the
detail onto another computer that uses another DBMS better suited for random inquiries and
analysis. Overall systems design decisions are performed by data administrators and systems
analysts. Detailed database design is performed by database administrators.

Database servers are specially designed computers that hold the actual databases and run only the
DBMS and related software. Database servers are usually multiprocessor computers, with RAID
disk arrays used for stable storage. Connected to one or more servers via a high-speed channel,
hardware database accelerators are also used in large volume transaction processing
environments.

DBMSs are found at the heart of most database applications. Sometimes DBMSs are built
around a private multitasking kernel with built-in networking support although nowadays these
functions are left to the operating system.
SQL

Structured Query Language (SQL) is the language used to manipulate relational databases. SQL
is tied very closely with the relational model.

In the relational model, data is stored in structures called relations or tables.

SQL statements are issued for the purpose of:

Data definition: Defining tables and structures in the database (DDL used to create, alter and
drop schema objects such as tables and indexes).

Data manipulation: Used to manipulate the data within those schema objects (DML Inserting,
Updating, Deleting the data, and Querying the Database).

A schema is a collection of database objects that can include: tables, views, indexes and
sequences

List of SQL statements that can be issued against an Oracle database schema are:

 ALTER - Change an existing table, view or index definition (DDL)

 AUDIT - Track the changes made to a table (DDL)
 COMMENT - Add a comment to a table or column in a table (DDL)
 COMMIT - Make all recent changes permanent (DML - transactional)
 CREATE - Create new database objects such as tables or views (DDL)
 DELETE - Delete rows from a database table (DML)
 DROP - Drop a database object such as a table, view or index (DDL)
 GRANT - Allow another user to access database objects such as tables or views (DDL)
 INSERT - Insert new data into a database table (DML)
 No AUDIT - Turn off the auditing function (DDL)
 REVOKE - Disallow a user access to database objects such as tables and views (DDL)
 ROLLBACK - Undo any recent changes to the database (DML - Transactional)
 SELECT - Retrieve data from a database table (DML)
 TRUNCATE - Delete all rows from a database table (can not be rolled back) (DML)
 UPDATE - Change the values of some data items in a database table (DML)
SERVLETS

Introduction
The Java web server is JavaSoft's own web Server. The Java web server is just a part of a larger
framework, intended to provide you not just with a web server, but also with tools. To build
customized network servers for any Internet or Intranet client/server system. Servlets are to a
web server, how applets are to the browser.

About Servlets

Servlets provide a Java-based solution used to address the problems currently associated with
doing server-side programming, including inextensible scripting solutions, platform-specific
APIs, and incomplete interfaces.

Servlets are objects that conform to a specific interface that can be plugged into a Java-based
server. Servlets are to the server-side what applets are to the client-side - object byte codes that
can be dynamically loaded off the net. They differ from applets in that they are faceless objects
(without graphics or a GUI component). They serve as platform independent, dynamically
loadable, pluggable helper byte code objects on the server side that can be used to dynamically
extend server-side functionality.

For example, an HTTP Servlets can be used to generate dynamic HTML content. When you use
Servlets to do dynamic content you get the following advantages:

 They’re faster and cleaner than CGI scripts

 They use a standard API (the Servlets API)
 They provide all the advantages of Java (run on a variety of servers without
needing to be rewritten).

Attractiveness of Servlets

There are many features of Servlets that make them easy and attractive to use. These include:

 Easily configured using the GUI-based Admin tool

 Can be loaded and invoked from a local disk or remotely across the network.
  Can be linked together, or chained, so that one Servlets can call another Servlets,
or several Servlets in sequence.
 Can be called dynamically from within HTML pages, using server-side include
tags.
 Are secure - even when downloading across the network, the Servlets security
model and Servlets sandbox protect your system from unfriendly behavior.

Advantages of the Servlet API

One of the great advantages of the Servlet API is protocol independence. It assumes nothing
about:

 The protocol being used to transmit on the net

 How it is loaded
 The server environment it will be running in

These qualities are important, because it allows the Servlet API to be embedded in many
different kinds of servers. There are other advantages to the Servlet API as well. These include:

 It’s extensible - you can inherit all your functionality from the base classes made
available to you.
 It’s simple, small, and easy to use.
Features of Servlets:

 Servlets are persistent. Servlet are loaded only by the web server and can maintain
services between requests.
 Servlets are fast. Since Servlets only need to be loaded once, they offer much better
performance over their CGI counterparts.
 Servlets are platform independent.
 Servlets are extensible. Java is a robust, object-oriented programming language,
which easily can be extended to suit your needs
 Servlets are secure.
 Servlets can be used with a variety of clients.
Loading Servlets:

Servlets can be loaded from three places

From a directory that is on the CLASSPATH. The CLASSPATH of the JavaWebServer

includes service root/classes/ which is where the system classes reside.

From the <SERVICE_ROOT /Servlets/ directory. This is *not* in the server’s class path. A
class loader is used to create Servlets from this directory. New Servlets can be added - existing
Servlets can be recompiled and the server will notice these changes.

From a remote location, for this a code base like http: // nine.eng / classes / foo / is required in
addition to the Servlets class name. Refer to the admin GUI docs on Servlet section to see how to
set this up.

Loading Remote Servlets

Remote Servlets can be loaded by:

1. Configuring the Admin Tool to setup automatic loading of remote Servlets

2. Setting up server side include tags in. shtml files
3. Defining a filter chain configuration

Invoking Servlets

A Servlet invoker is a Servlet that invokes the "service" method on a named Servlet. If the
Servlet is not loaded in the server, then the invoker first loads the Servlet (either from local disk
or from the network) and the then invokes the "service" method. Also like applets, local Servlets
in the server can be identified by just the class name. In other words, if a Servlet name is not
absolute, it is treated as local.

A client can invoke Servlets in the following ways:

 The client can ask for a document that is served by the Servlet.
 The client (browser) can invoke the Servlet directly using a URL, once it has been
mapped using the Servlet Aliases section of the admin GUI.
  The Servlet can be invoked through server side include tags.
 The Servlet can be invoked by placing it in the Servlets/ directory.
 The Servlet can be invoked by using it in a filter chain.

Java Server Pages (JSP)

Java server Pages is a simple, yet powerful technology for creating and maintaining dynamic-
content web pages. Based on the Java programming language, Java Server Pages offers
proven portability, open standards, and a mature re-usable component model .The Java
Server Pages architecture enables the separation of content generation from content
presentation. This separation not eases maintenance headaches; it also allows web team
members to focus on their areas of expertise. Now, web page designer can concentrate on
layout, and web application designers on programming, with minimal concern about
impacting each other’s work.

Features of JSP

Portability:

Java Server Pages files can be run on any web server or web-enabled application server that
provides support for them. Dubbed the JSP engine, this support involves recognition,
translation, and management of the Java Server Page lifecycle and its interaction
components.

Components

It was mentioned earlier that the Java Server Pages architecture can include reusable Java
components. The architecture also allows for the embedding of a scripting language directly
into the Java Server Pages file. The components current supported include Java Beans, and
Servlets.

Processing
 A Java Server Pages file is essentially an HTML document with JSP scripting or tags. The
Java Server Pages file has a JSP extension to the server as a Java Server Pages file. Before
the page is served, the Java Server Pages syntax is parsed and processed into a Servlet on the
server side. The Servlet that is generated outputs real content in straight HTML for
responding to the client.

Access Models:

A Java Server Pages file may be accessed in at least two different ways. A client’s request
comes directly into a Java Server Page. In this scenario, suppose the page accesses reusable
Java Bean components that perform particular well-defined computations like accessing a
database. The result of the Beans computations, called result sets is stored within the Bean as
properties. The page uses such Beans to generate dynamic content and present it back to the
client.

In both of the above cases, the page could also contain any valid Java code. Java Server
Pages architecture encourages separation of content from presentation.

Steps in the execution of a JSP Application:

1. The client sends a request to the web server for a JSP file by giving the name of the JSP
file within the form tag of a HTML page.

2. This request is transferred to the JavaWebServer. At the server side JavaWebServer

receives the request and if it is a request for a jsp file server gives this request to the JSP
engine.
3. JSP engine is program which can under stands the tags of the jsp and then it converts
those tags into a Servlet program and it is stored at the server side. This Servlet is loaded
in the memory and then it is executed and the result is given back to the JavaWebServer
and then it is transferred back to the result is given back to the JavaWebServer and then it
is transferred back to the client.
Eclipse IDE

Eclipse is an open-source software framework written primarily in Java. In its default form it is
an Integrated Development Environment (IDE) for Java developers, consisting of the Java
Development Tools (JDT) and the Eclipse Compiler for Java (ECJ). Users can extend its
capabilities by installing plug-ins written for the Eclipse software framework, such as
development toolkits for other programming languages, and can write and contribute their own
plug-in modules. Language packs are available for over a dozen languages.

Architecture

The basis for Eclipse is the Rich Client Platform (RCP). The following components constitute
the rich client platform:

 OSGi - a standard bundling framework

 Core platform - boot Eclipse, run plug-ins
 the Standard Widget Toolkit (SWT) - a portable widget toolkit
 JFace - viewer classes to bring model view controller programming to SWT, file buffers,
text handling, text editors
 the Eclipse Workbench - views, editors, perspectives, wizards

Eclipse's widgets are implemented by a widget toolkit for Java called SWT, unlike most Java
applications, which use the Java standard Abstract Window Toolkit (AWT) or Swing. Eclipse's
user interface also leverages an intermediate GUI layer called JFace, which simplifies the
construction of applications based on SWT.

Eclipse employs plug-ins in order to provide all of its functionality on top of (and including) the
rich client platform, in contrast to some other applications where functionality is typically hard
coded. This plug-in mechanism is a lightweight software componentry framework. In addition to
allowing Eclipse to be extended using other programming languages such as C and Python, the
plug-in framework allows Eclipse to work with typesetting languages like LaTeX, networking
applications such as telnet, and database management systems. The plug-in architecture supports
writing any desired extension to the environment, such as for configuration management. Java
and CVS support is provided in the Eclipse SDK.

The key to the seamless integration of tools with Eclipse is the plugin. With the exception of a
small run-time kernel, everything in Eclipse is a plug-in. This means that a plug-in you develop
integrates with Eclipse in exactly the same way as other plug-ins; in this respect, all features are
created equal.

The Eclipse SDK includes the Eclipse Java Development Tools, offering an IDE with a built-in
incremental Java compiler and a full model of the Java source files. This allows for advanced
refactoring techniques and code analysis. The IDE also makes use of a workspace, in this case a
set of metadata over a flat filespace allowing external file modifications as long as the
corresponding workspace "resource" is refreshed afterwards. The Visual Editor project allows
interfaces to be created interactively, hence allowing Eclipse to be used as a RAD tool.

The following is a list of notable projects and plugins for the Eclipse IDE.

These projects are maintained by the Eclipse community and hosted by the Eclipse Foundation.
SAMPLE CODE
JSP:

<%@page import="com.dts.project.dao.EmpRegistrationDAO"%>
<%@page import="com.dts.core.util.CoreHash"%>
<%@page import="java.util.Enumeration"%>
<%@page import="com.dts.project.model.EmpModel"%><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- saved from url=(0041)http://www.telemarketing.com/services.asp -->
<HTML xmlns="http://www.w3.org/1999/xhtml">
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8"/>

<META name="description" content=""/>

<META name="keywords" content=""/>
<META name="robots" content=""/>
<TITLE> Telemarketing Services - How to Choose the Right Telemarketing Services.</TITLE>
<LINK rel="shortcut icon" type="image/x-icon" href="#"/>
<LINK href="images/styles2.css" rel="stylesheet" type="text/css"/>
<SCRIPT src="images/scripts.js" language="JavaScript" type="text/JavaScript"></SCRIPT>
<!--BEGIN ROI TRACKING Code-->

<script language="JavaScript" src="scripts/gen_validatorv31.js" type="text/javascript"></script>

<script language="JavaScript" type="text/javascript" src="scripts/ts_picker.js"></script>
<script language="JavaScript1.1" src="scripts/pass.js">

</script> <script type="text/javascript" src="scripts/image.js"> </script>

<script type="text/javascript" src="scripts/general.js"> </script>
<script type="text/javascript" src="scripts/adi.js"> </script>
<script type="text/javascript" src="scripts/form_validation.js"> </script>
<script type="text/javascript">

function inDate(){

var date=new Date();

document.addhotel.stdate.value=date.getDate()+"-"+(date.getMonth()+1)+"-"+date.getYear();
document.getElementById('exprId').innerHTML=0;
}
function offDate(){

var day=document.forms.register.elements("day");
var dayvalue=day.options[day.selectedIndex].value;
var month=document.forms.register.elements("month");
var monthvalue=month.options[month.selectedIndex].value;
var year=document.forms.register.elements("year");
var yearvalue=year.options[year.selectedIndex].value;
var append1=dayvalue+"-"+monthvalue+"-"+yearvalue;

var append=append1.split("-");

born = new Date(bD[2], bD[1]*1-1, bD[0]);

years = Math.floor((now.getTime() - born.getTime()) / (365.25 * 24 * 60 * 60 * 1000));

if(years>21){
document.register.doj.value=date.getDate()+"-"+(date.getMonth()+1)+"-"+date.getYear();;
}
else{
document.register.doj.value="";
alert('Date Of Join Must Be Greater Then 21');

}
<%-- var date=new Date();--%>
<%-- var checkdate=date.getDate()+"-"+(date.getMonth()+1)+"-"+date.getYear();--%>
<%-- bD=checkdate.split("-");--%>
<%-- --%>
<%-- born = new Date(bD[2], bD[1]*1-1, bD[0]);--%>
<%-- years = Math.floor((date.getTime() - born.getTime()) / (365.25 * 24 * 60 * 60 * 1000));--%>
<%-- if(years>21){--%>
<%-- document.register.doj.value=date.getDate()+"-"+(date.getMonth()+1)+"-"+date.getYear();--%>
<%-- document.getElementById('exprId').innerHTML=0;--%>
<%-- }--%>
<%-- else{--%>
<%-- alert ('Date Of Join Must Be Greater Than 21');--%>
<%-- }--%>
}

function calAgeTo(){

var day=document.forms.register.elements("day");
var dayvalue=day.options[day.selectedIndex].value;
var month=document.forms.register.elements("month");
var monthvalue=month.options[month.selectedIndex].value;
var year=document.forms.register.elements("year");
var yearvalue=year.options[year.selectedIndex].value;

var append=dayvalue+"-"+monthvalue+"-"+yearvalue;

now = new Date()

bD = append.split('-');

if(bD.length!=3){
alert('Date Is Not Valid');
document.getElementById('AgeId').innerHTML="";

}
else if(bD.length==3){
born = new Date(bD[2], bD[1]*1-1, bD[0]);
years = Math.floor((now.getTime() - born.getTime()) / (365.25 * 24 * 60 * 60 * 1000));

document.getElementById('AgeId').innerHTML=years;
}
}
function DOBcalc() {

<%--if(!register.doj.value==""){--%>
<%-- var DOjmdy = (register.doj.value).split('-'); --%>
<%-- Bjdate = new Date(DOjmdy[2],DOjmdy[0]-1,DOjmdy[1]); --%>
<%-- var bb=Bjdate.getFullYear();--%>
<%-- var DOBmdy = (register.dobirth.value).split('-'); --%>
<%-- --%>
<%-- Bdate = new Date(DOBmdy[2],DOBmdy[0]-1,DOBmdy[1]); --%>
<%-- var bDate=Bdate.getFullYear();--%>
<%-- var AgeValue=21;--%>
<%-- var Final=bb-AgeValue;--%>
<%-- if(Final>=bDate){}--%>
<%-- else{--%>
<%-- alert('Check The Joining Date Plz\n Must Be Greater Than ');--%>
<%-- --%>
<%-- }--%>
<%-- }--%>
var date=new Date();
register.doj.value=date;

}
function disEnable(){
register.hQual.disabled=false;
}
</script>

<script>
//var x_win = window.self;

function goOn() {
var port=document.adduser.port.value;
var host=document.adduser.host.value;
var username=document.adduser.username.value;
window.location.href='http://'+host+':'+port+'/ADV/ChekUserAction?username='+username;

}
function trim(str){
while(str.chatAt(str.length-1)==" ")
str=str.substring(0,str.length-1);
while(str.chatAt(0)==" ")
str=str.substring(1,str.length);

return str;
}

function checkUserName(){
var temp = document.adduser;

if ( temp.username.value.length <8 || temp.username.value.length >20) {

alert(" a username should contain between 8 and 20 character");
 return false;
}
return true;
}

function checkPass(){
var temp = document.adduser;
if (temp.password.value.length <5 || temp.password.value.length >15) {
alert("a password should contain between 5 and 10 character");

return false;
}
return true;
}

</script>

<script language=javascript>
function checkMailId(mailids)
{
var arr = new Array('.com','.net','.org','.biz','.coop','.info','.museum','.name','.pro'
,'.edu','.gov','.int','.mil','.ac','.ad','.ae','.af','.ag','.ai','.al',
'.am','.an','.ao','.aq','.ar','.as','.at','.au','.aw','.az','.ba','.bb',
'.bd','.be','.bf','.bg','.bh','.bi','.bj','.bm','.bn','.bo','.br','.bs',
'.bt','.bv','.bw','.by','.bz','.ca','.cc','.cd','.cf','.cg','.ch','.ci',
'.ck','.cl','.cm','.cn','.co','.cr','.cu','.cv','.cx','.cy','.cz','.de',
'.dj','.dk','.dm','.do','.dz','.ec','.ee','.eg','.eh','.er','.es','.et',
'.fi','.fj','.fk','.fm','.fo','.fr','.ga','.gd','.ge','.gf','.gg','.gh',
'.gi','.gl','.gm','.gn','.gp','.gq','.gr','.gs','.gt','.gu','.gv','.gy',
'.hk','.hm','.hn','.hr','.ht','.hu','.id','.ie','.il','.im','.in','.io',
'.iq','.ir','.is','.it','.je','.jm','.jo','.jp','.ke','.kg','.kh','.ki',
'.km','.kn','.kp','.kr','.kw','.ky','.kz','.la','.lb','.lc','.li','.lk',
'.lr','.ls','.lt','.lu','.lv','.ly','.ma','.mc','.md','.mg','.mh','.mk',
'.ml','.mm','.mn','.mo','.mp','.mq','.mr','.ms','.mt','.mu','.mv','.mw',
'.mx','.my','.mz','.na','.nc','.ne','.nf','.ng','.ni','.nl','.no','.np',
'.nr','.nu','.nz','.om','.pa','.pe','.pf','.pg','.ph','.pk','.pl','.pm',
'.pn','.pr','.ps','.pt','.pw','.py','.qa','.re','.ro','.rw','.ru','.sa',
'.sb','.sc','.sd','.se','.sg','.sh','.si','.sj','.sk','.sl','.sm','.sn',
'.so','.sr','.st','.sv','.sy','.sz','.tc','.td','.tf','.tg','.th','.tj',
'.tk','.tm','.tn','.to','.tp','.tr','.tt','.tv','.tw','.tz','.ua','.ug',
'.uk','.um','.us','.uy','.uz','.va','.vc','.ve','.vg','.vi','.vn','.vu',
'.ws','.wf','.ye','.yt','.yu','.za','.zm','.zw');

var mai = mailids;

var val = true;
var beforeat="";
var afterat="";
var afterat2="";

var dot=mai.lastIndexOf(".");
var con=mai.substring(dot, mai.length);
con=con.toLowerCase();
con=con.toString();

for(var i=0;i<(arr.length);i++)
{
if(con == arr[i])
{
val=true;
break;
}
else
{
val=false;
}
}

var att=mai.lastIndexOf("@");
beforeat=mai.substring(0,att);
beforeat=beforeat.toLowerCase();
beforeat=beforeat.toString();
var asci1=beforeat.charCodeAt(0);

afterat=mai.substring(att+1, dot);
afterat=afterat.toLowerCase();
afterat=afterat.toString();

afterat2=mai.substring(att+1, mai.length);
afterat2=afterat2.toLowerCase();
afterat2=afterat2.toString();

if(beforeat=="" || afterat=="" || beforeat.length>30)

val=false;

if(afterat2.length>64 || afterat.length<2)
val=false;

if((afterat.charCodeAt(0))==45 || (afterat.charCodeAt(afterat.length-1))==45)
val=false;

if(val==true)
{
if(asci1 > 47 && asci1 < 58)
val=false;

if(asci1 < 48 || asci1 > 57)

{
for(var i=0; i<=beforeat.length-1; i++)
{
var asci2=beforeat.charCodeAt(i);
if((asci2<=44 || asci2==47) || (asci2>=58 && asci2<=94) || (asci2==96) || (asci2>=123
&& asci2<=127))
{
val=false;
break;
}
}
 for(var j=0; j<=afterat.length-1; j++)
{
var asci3=afterat.charCodeAt(j);
if((asci3<=44) || (asci3==46) || (asci3==47) || (asci3>=58 && asci3<=96) || (asci3>=123
&& asci3<=127))
{
val=false;
break;
}
}
}
}

if(val==false)
{
alert("Your maild "+mai+" is not valid");
return false;
}
else
{
return true;
}
}
</script>
<script language = "Javascript">
/**
* DHTML phone number validation script. Courtesy of SmartWebby.com (http://www.smartwebby.com/dhtml/)
*/

// Declaring required variables

var digits = "0123456789";
// non-digit characters which are allowed in phone numbers
var phoneNumberDelimiters = "()- ";
// characters which are allowed in international phone numbers
// (a leading + is OK)
var validWorldPhoneChars = phoneNumberDelimiters + "+";
// Minimum no of digits in an international phone no.
var minDigitsInIPhoneNumber = 10;

function isInteger(s)
{ var i;
for (i = 0; i < s.length; i++)
{
// Check that current character is number.
var c = s.charAt(i);
if (((c < "0") || (c > "9"))) return false;
}
// All characters are numbers.
return true;
}
function trim(s)
{ var i;
var returnString = "";
// Search through string's characters one by one.
// If character is not a whitespace, append to returnString.
for (i = 0; i < s.length; i++)
 {
// Check that current character isn't whitespace.
var c = s.charAt(i);
if (c != " ") returnString += c;
}
return returnString;
}
function stripCharsInBag(s, bag)
{ var i;
var returnString = "";
// Search through string's characters one by one.
// If character is not in bag, append to returnString.
for (i = 0; i < s.length; i++)
{
// Check that current character isn't whitespace.
var c = s.charAt(i);
if (bag.indexOf(c) == -1) returnString += c;
}
return returnString;
}

function checkInternationalPhone(strPhone){
var bracket=3
strPhone=trim(strPhone)
if(strPhone.indexOf("+")>1) return false
if(strPhone.indexOf("-")!=-1)bracket=bracket+1
if(strPhone.indexOf("(")!=-1 && strPhone.indexOf("(")>bracket)return false
var brchr=strPhone.indexOf("(")
if(strPhone.indexOf("(")!=-1 && strPhone.charAt(brchr+2)!=")")return false
if(strPhone.indexOf("(")==-1 && strPhone.indexOf(")")!=-1)return false
s=stripCharsInBag(strPhone,validWorldPhoneChars);
return (isInteger(s) && s.length >= minDigitsInIPhoneNumber);
}

function ValidatePnoneNumber(){
var Phone=document.addhotel.contactno;

if ((Phone.value==null)||(Phone.value=="")){
alert("Please Enter your Phone Number")
Phone.focus()
return false
}
if (checkInternationalPhone(Phone.value)==false){
alert("Please Enter a Valid Phone Number")
Phone.value=""
Phone.focus()
return false
}
return true
}
</script>

<SCRIPT language="javascript" src="images/track.asp"></SCRIPT>

<SCRIPT language="javascript">
<!--
if (typeof(ROIID) + '' != 'undefined')
{
TrackEvent('LandingPage', 0);
}
//-->
</SCRIPT>
<!--END ROI TRACKING Code-->
<SCRIPT language="JavaScript" type="text/javascript">
<!-- Yahoo! Inc.
var ysm_accountid = "1OGH0147L7RREN17UC00JA5NPI0";
document.write("<SCR" + "IPT language='JavaScript' type='text/javascript' "
+ "SRC=//" + "srv1.wa.marketingsolutions.yahoo.com" + "/script/ScriptServlet" + "?aid=" + ysm_accountid
+ "></SCR" + "IPT>");
// -->
</SCRIPT><SCRIPT language="JavaScript" type="text/javascript" src="images/ScriptServlet"></SCRIPT>

<SCRIPT src="images/urchin.js" type="text/javascript">

</SCRIPT>

<SCRIPT type="text/javascript">

_uacct = "UA-2950592-2";

urchinTracker();

</SCRIPT>

</HEAD>

<BODY onload="preloadImages();">
<TABLE cellpadding="0" cellspacing="0" align="center">
<TBODY><TR>
<TD colspan="2" align="center">
<CSACTIONDICT>
<SCRIPT type="text/javascript"><!--
var preloadFlag = false;
function preloadImages() {
if (document.images) {
pre_about_over = newImage('images/navbar/about_over.gif');
pre_automated_over = newImage('images/navbar/automated_over.gif');
pre_ebound_over = newImage('images/navbar/ebound_over.gif');
pre_fulfillment_over = newImage('images/navbar/fulfillment_over.gif');
pre_why_over = newImage('images/navbar/why_over.gif');
pre_inbound_over = newImage('images/navbar/inbound_over.gif');
pre_outbound_over = newImage('images/navbar/outbound_over.gif');
preloadFlag = true;
}
}

// --></SCRIPT>
</CSACTIONDICT>
 <DIV id="header">
<IMG src="images/masthead2.jpg" alt="Telemarketing.com" width="770" height="86"
usemap="#masthead3856a44"><MAP name="masthead3856a44"><AREA shape="rect" coords="5,5,296,80"
href="#" alt="Telemarketing.com"></MAP>

<tr bgcolor="green">
<td height="30" colspan="6" class="navText style1" id="navigation">

<DIV id="navbar">
<% String role=(String)session.getAttribute("role");
if(role!=null){
if(role.equalsIgnoreCase("admin")){
%>
<jsp:include page="AdminOptions.html"/>
<%}else if(role.equalsIgnoreCase("employee")){ %>

<jsp:include page="EmployeeOptions.jsp"/>

<%}else if(role.equalsIgnoreCase("customer")){ %>

<jsp:include page="CustomerOptions.jsp"/>
<%}
else { %>

<jsp:include page="LoginForm.jsp?status=session expired login again...."/>

<%} }else{
response.sendRedirect("LoginForm.jsp?status=session expired login
again...." );
}
%>

</DIV>

</TD>
</TR>
<TR>
<TD width="151" valign="top">
<DIV id="navigation">
<IMG src="images/services.jpg" width="151"></IMG>
<IMG src="images/partner.jpg"><BR></BR>

<A href="#" title="Call Centers" target="new"><IMG

src="images/answernet_sm.jpg"></A><P>

</P></DIV>
</TD>
<TD valign="top">
<DIV id="content">
<table>
<tbody>
<table align="center" width="200" border="0">
<center>
<form name="addhotel" action="./AddHotelAction" method="" onSubmit="return validate()">
<center> <% if(request.getParameter("status")!=null)
{%>
<strong><font color=red><%=request.getParameter("status")%></font></strong>
<%}%></center>

<tr>
<td>Hostel Name</td>
<td><input type="text" name="hname" value=""></td>
</tr><br/>

<tr>
<td>Plot No</td>
<td><input type="text" name="hpltno" value=""></td>
</tr><br/>

<tr>
<td>Street</td>
<td><input type="text" name="hstreet" value=""></td>
</tr><br/>

<tr>
<td>City</td>
<td><input type="text" name="city" value=""></td>
</tr><br/>

<tr>
<td>State</td>
<td><input type="text" name="state" value=""></td>
</tr><br/>

<tr>
<td>Pin</td>
<td><input type="text" name="pin" value=""></td>
</tr><br/>

<tr>
<td>Start Date</td>
<td><input type="text" name="stdate" onfocus="inDate()" value=""></td>
</tr><br/>

<tr><td>Incharge Name</td><td><select name="inchrgname">

<option value="select">-Select-</option>
<% CoreHash ch2=new EmpRegistrationDAO().getGeneralManager();
Enumeration em2=ch2.elements();
EmpModel p2=null;
while(em2.hasMoreElements()){
p2=(EmpModel)em2.nextElement();
 %>
<option value="<%=p2.getEmpid()%>"><%=p2.getManagername()%></option>
<%} %>
</select>
</td></tr><br/>

<tr>
<td>Mail-ID</td>
<td><input type="text" name="mailid" onBlur="checkMailId(addhotel.mailid.value)" value=""></td>
</tr><br/>

<tr>
<td>Contact No</td>
<td><input type="text" name="contactno" onBlur="ValidatePnoneNumber()" value=""></td>
</tr><br/>

<tr><td> <input type="submit" name="submit" value="Add Hotel"/><input type="reset" name="clear"

value="Clear"/></td></tr><br/>
</form>
<script>

var frmvalidator = new Validator("addhotel");

frmvalidator.addValidation("hname","req","Please Enter Hostel Name");
frmvalidator.addValidation("hpltno","req","Please Enter Hostel Plot No");
frmvalidator.addValidation("hstreet","req","Please Enter Hostel Street");
frmvalidator.addValidation("city","req","Please Enter Hostel City");
frmvalidator.addValidation("state","req","Please Enter Hostel State");
frmvalidator.addValidation("pin","req","Please Enter Hostel Pin Number");
frmvalidator.addValidation("stdate","req","Please Enter Hostel Start Date");
frmvalidator.addValidation("inchrgname","dontselect=0");

</script>

</center>
</table>
</tbody>

</TABLE>
</DIV>
</TD>
</TR>
<TR>
<TD colspan="2" style="vertical-align: bottom" align="center">
<DIV id="footerBorder">&nbsp;<DIV id="footer">«»<SPAN
id="copyright">©2007-2009 AnswerNet</SPAN> «» <A href="#">Contact Us</A> <BR></BR>
Visit AnswerNet <A href="#" title="Call Centers">Call Centers</A>
for Customized <A href="#" title="Call Center Services">Call Center Services</A> and <A href="#"
title="Answering Services">Answering Services</A></DIV>
</DIV>

</TD>
</TR>
</TBODY></TABLE>
</BODY></HTML>

HOTEL ACTION:

package com.dts.project.action;

import java.io.IOException;

import java.io.PrintWriter;

import javax.servlet.RequestDispatcher;

import javax.servlet.ServletException;

import javax.servlet.http.HttpServlet;

import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import com.dts.project.dao.HotelDAO;

import com.dts.project.model.HotelModel;

public class AddHotelAction extends HttpServlet {

/**

* The doGet method of the servlet. <br>

* This method is called when a form has its tag value method equals to get.

* @param request the request send by the client to the server

* @param response the response send by the server to the client

* @throws ServletException if an error occurred

* @throws IOException if an error occurred

*/

public void doGet(HttpServletRequest request, HttpServletResponse response)

throws ServletException, IOException {

doPost(request,response);

/**

* The doPost method of the servlet. <br>

*
 * This method is called when a form has its tag value method equals to post.

* @param request the request send by the client to the server

* @param response the response send by the server to the client

* @throws ServletException if an error occurred

* @throws IOException if an error occurred

*/

public void doPost(HttpServletRequest request, HttpServletResponse response)

throws ServletException, IOException {

String status=request.getParameter("submit");

HotelModel htlmodel=null;

if(status.equalsIgnoreCase("Add Hotel")){

String target="AddHotel.jsp?status=Invalid Add Hotel Details";

try{

htlmodel=new HotelModel();

htlmodel.setHotelname(request.getParameter("hname"));

htlmodel.setHotelpltno(request.getParameter("hpltno"));

htlmodel.setHtlstreet(request.getParameter("hstreet"));

htlmodel.setHotelcity(request.getParameter("city"));

htlmodel.setHotelstate(request.getParameter("state"));

htlmodel.setHotelpin(request.getParameter("pin"));
 htlmodel.setHotelstdate(request.getParameter("stdate"));

htlmodel.setInchrgid(Integer.parseInt(request.getParameter("inchrgname")));

htlmodel.setHotelmailid(request.getParameter("mailid"));

htlmodel.setContactno(request.getParameter("contactno"));

boolean flag=new HotelDAO().addHotel(htlmodel);

if(flag)

target="AddHotel.jsp?status=Add Hotel Is Successful";

else

target="AddHotel.jsp?status=Add Hotel Is Fail";

catch(Exception e){e.printStackTrace();}

RequestDispatcher rd = request.getRequestDispatcher(target);

rd.forward(request,response);

if(status.equalsIgnoreCase("Update Hotel Details")){

String target="ViewAllHotels.jsp?status=Invalid Update Hotel Details";

try{

htlmodel=new HotelModel();
 htlmodel.setHotelid(Integer.parseInt(request.getParameter("hhid")));

htlmodel.setHotelpltno(request.getParameter("hpltno"));

htlmodel.setHtlstreet(request.getParameter("street"));

htlmodel.setHotelcity(request.getParameter("city"));

htlmodel.setHotelstate(request.getParameter("state"));

htlmodel.setHotelpin(request.getParameter("pin"));

htlmodel.setHotelstdate(request.getParameter("stdate"));

htlmodel.setInchrgid(Integer.parseInt(request.getParameter("inchrgid")));

htlmodel.setHotelmailid(request.getParameter("mailid"));

htlmodel.setContactno(request.getParameter("contactno"));

boolean flag=new HotelDAO().UpdateHotelDetails(htlmodel);

if(flag)

target="ViewAllHotels.jsp?status=Update Hotels Is Successful";

else

target="ViewAllHotels.jsp?status=Update Hotels Is Fail";

catch(Exception e){e.printStackTrace();}

RequestDispatcher rd = request.getRequestDispatcher(target);

rd.forward(request,response);

}
 }

MODEL AND DAO

package com.dts.project.dao;

import java.io.File;

import java.io.FileInputStream;

import java.sql.CallableStatement;

import java.sql.Connection;

import java.sql.ResultSet;

import java.sql.SQLException;

import java.sql.Statement;

import com.dts.core.dao.AbstractDataAccessObject;

import com.dts.core.util.CoreHash;

import com.dts.core.util.DateWrapper;
 import com.dts.core.util.LoggerManager;

import com.dts.project.model.EmpModel;

import com.dts.project.model.HotelModel;

public class HotelDAO extends AbstractDataAccessObject {

public HotelDAO() {

// TODO Auto-generated constructor stub

public boolean flag=false;

public Connection con=null;

public boolean addHotel(HotelModel addhotel){

CallableStatement cstmt=null;

try

con=getConnection();

cstmt=con.prepareCall("{ call ADD_HOTEL(?,?,?,?,?,?,?,?,?,?) }");

cstmt.setString(1, addhotel.getHotelname());

cstmt.setString(2, addhotel.getHotelpltno());
 cstmt.setString(3, addhotel.getHtlstreet());

cstmt.setString(4, addhotel.getHotelcity());

cstmt.setString(5, addhotel.getHotelstate());

cstmt.setString(6, addhotel.getHotelpin());

cstmt.setString(7, DateWrapper.parseDate(addhotel.getHotelstdate()));

cstmt.setDouble(8, addhotel.getInchrgid());

cstmt.setString(9, addhotel.getHotelmailid());

cstmt.setString(10, addhotel.getContactno());

int i= cstmt.executeUpdate();

if(i==1)

flag=true;

con.commit();

else

flag=false;

con.rollback();

catch (Exception e)
 {

e.printStackTrace();

flag=false;

try

con.rollback();

catch (SQLException se)

se.printStackTrace();

finally

try{

if(con!=null)

con.close();

catch(Exception e){}

return flag;
 }

public boolean UpdateHotelDetails(HotelModel addhotel){

CallableStatement cstmt=null;

try

con=getConnection();

cstmt=con.prepareCall("{ call UPDATE_HOTEL(?,?,?,?,?,?,?,?,?,?) }");

cstmt.setInt(1, addhotel.getHotelid());

cstmt.setString(2, addhotel.getHotelpltno());

cstmt.setString(3, addhotel.getHtlstreet());

cstmt.setString(4, addhotel.getHotelcity());

cstmt.setString(5, addhotel.getHotelstate());

cstmt.setString(6, addhotel.getHotelpin());

cstmt.setString(7, DateWrapper.parseDate(addhotel.getHotelstdate()));

cstmt.setInt(8, addhotel.getInchrgid());

cstmt.setString(9, addhotel.getHotelmailid());

cstmt.setString(10, addhotel.getContactno());

int i= cstmt.executeUpdate();
 if(i==1)

flag=true;

con.commit();

else

flag=false;

con.rollback();

catch (Exception e)

e.printStackTrace();

flag=false;

try

con.rollback();

catch (SQLException se)

se.printStackTrace();
 }

finally

try{

if(con!=null)

con.close();

catch(Exception e){}

return flag;

}
 public CoreHash getHotelNames(){

CoreHash aCoreHash=new CoreHash();

aCoreHash.clear();

System.out.println("aCoreHash--"+aCoreHash.isEmpty());

int sno=1;

Statement cstmt;

HotelModel hmodel=null;

try {

con = getConnection();

cstmt=con.createStatement();

ResultSet rs=cstmt.executeQuery("select hotelid,hotelNAME from HotelMaster");

while(rs.next())

hmodel=new HotelModel();

System.out.println("In Hotel DAo"+rs.getInt(1)+rs.getString(2));

hmodel.setHotelid(rs.getInt(1));

hmodel.setHotelname(rs.getString(2));
 aCoreHash.put(new Integer(sno),hmodel);

sno++;

catch(Exception e)

{e.printStackTrace();

LoggerManager.writeLogWarning(e);

finally

try{

if(con!=null)

con.close();

catch(Exception e){}

return aCoreHash;

public CoreHash getAllHotelDetails(){

 CoreHash aCoreHash=new CoreHash();

aCoreHash.clear();

System.out.println("aCoreHash--"+aCoreHash.isEmpty());

int sno=1;

Statement cstmt;

HotelModel hmodel=null;

try {

con = getConnection();

cstmt=con.createStatement();

ResultSet rs=cstmt.executeQuery("SELECT HM.HOTELID, HM.HOTELNAME,

HM.HPLOTNO, HM.HSTREET, HM.HCITY, HM.HSTATE, HM.HPIN, TO_CHAR(HM.HSTDATE,'DD-
MM-YY'), HM.HINCHRGID, EM.EMPFSTNAME ,hm.HOTELMAILID,hm.HOTELCONTACTNO
FROM HOTELMASTER HM,EMPLOYEESMASTER EM WHERE(HM.HINCHRGID=EM.EMPID)");

while(rs.next())

hmodel=new HotelModel();

System.out.println("In Hotel DAo"+rs.getInt(1)+rs.getString(2));

hmodel.setHotelid(rs.getInt(1));

hmodel.setHotelname(rs.getString(2));

hmodel.setHotelpltno(rs.getString(3));

hmodel.setHtlstreet(rs.getString(4));

hmodel.setHotelcity(rs.getString(5));

hmodel.setHotelstate(rs.getString(6));
hmodel.setHotelpin(rs.getString(7));

hmodel.setHotelstdate(rs.getString(8));

hmodel.setInchrgid(rs.getInt(9));

hmodel.setInchrgname(rs.getString(10));

hmodel.setHotelmailid(rs.getString(11));

hmodel.setContactno(rs.getString(12));

aCoreHash.put(new Integer(sno),hmodel);

sno++;

catch(Exception e)

{e.printStackTrace();

LoggerManager.writeLogWarning(e);

finally

try{

if(con!=null)

con.close();

catch(Exception e){}
 }

return aCoreHash;

public HotelModel getEachHotelDetails(int hid){

//CoreHash aCoreHash=new CoreHash();

//aCoreHash.clear();

//System.out.println("aCoreHash--"+aCoreHash.isEmpty());

int sno=1;

Statement cstmt;

HotelModel hmodel=null;

try {

con = getConnection();

cstmt=con.createStatement();

String sql="SELECT HM.HOTELID, HM.HOTELNAME, HM.HPLOTNO,

HM.HSTREET, HM.HCITY, HM.HSTATE, HM.HPIN, TO_CHAR(HM.HSTDATE,'DD-MM-YYYY'),
HM.HINCHRGID, EM.EMPFSTNAME,hm.HOTELMAILID,hm.HOTELCONTACTNO FROM
HOTELMASTER HM,EMPLOYEESMASTER EM WHERE(HM.HINCHRGID=EM.EMPID) AND
HM.HOTELID="+hid;

ResultSet rs=cstmt.executeQuery(sql);

while(rs.next())
 {

hmodel=new HotelModel();

System.out.println("In Hotel DAo"+rs.getInt(1)+rs.getString(2));

hmodel.setHotelid(rs.getInt(1));

hmodel.setHotelname(rs.getString(2));

hmodel.setHotelpltno(rs.getString(3));

hmodel.setHtlstreet(rs.getString(4));

hmodel.setHotelcity(rs.getString(5));

hmodel.setHotelstate(rs.getString(6));

hmodel.setHotelpin(rs.getString(7));

hmodel.setHotelstdate(rs.getString(8));

hmodel.setInchrgid(rs.getInt(9));

hmodel.setInchrgname(rs.getString(10));

hmodel.setHotelmailid(rs.getString(11));

hmodel.setContactno(rs.getString(12));

// aCoreHash.put(new Integer(sno),hmodel);

// sno++;

catch(Exception e)

{e.printStackTrace();
 LoggerManager.writeLogWarning(e);

finally

try{

if(con!=null)

con.close();

catch(Exception e){}

return hmodel;

public CoreHash getSuppliersNames(){

CoreHash aCoreHash=new CoreHash();

aCoreHash.clear();

System.out.println("aCoreHash--"+aCoreHash.isEmpty());

int sno=1;

Statement cstmt;

SupplierModel hmodel=null;

try {

con = getConnection();
 cstmt=con.createStatement();

ResultSet rs=cstmt.executeQuery("select supplierid,sfstname from SupplierMaster");

while(rs.next())

hmodel=new SupplierModel();

System.out.println("In Hotel DAo"+rs.getInt(1)+rs.getString(2));

hmodel.setSplid(rs.getInt(1));

hmodel.setSfstname(rs.getString(2));

aCoreHash.put(new Integer(sno),hmodel);

sno++;

catch(Exception e)

{e.printStackTrace();

LoggerManager.writeLogWarning(e);

finally

{
 try{

if(con!=null)

con.close();

catch(Exception e){}

return aCoreHash;

public CoreHash getTendersNames(){

CoreHash aCoreHash=new CoreHash();

aCoreHash.clear();

System.out.println("aCoreHash--"+aCoreHash.isEmpty());

int sno=1;

Statement cstmt;

HotelModel hmodel=null;

try {

con = getConnection();

cstmt=con.createStatement();
ResultSet rs=cstmt.executeQuery("select tenderid,tenderto from tender");

while(rs.next())

hmodel=new HotelModel();

System.out.println("In Tender DAo"+rs.getInt(1)+rs.getString(2));

hmodel.setTenderid(rs.getInt(1));

hmodel.setTenderto(rs.getString(2));

aCoreHash.put(new Integer(sno),hmodel);

sno++;

catch(Exception e)

{e.printStackTrace();

LoggerManager.writeLogWarning(e);

finally

try{

if(con!=null)

con.close();
 }

catch(Exception e){}

return aCoreHash;

TESTING &

DEBUGGING TECHNIQUES
Testing Concepts

 Testing

 Testing Methodologies

 Black box Testing:

 White box Testing.
 Gray Box Testing.

 Levels of Testing

 Unit Testing.
 Module Testing.
 Integration Testing.
 System Testing.
 User Acceptance Testing.

 Types Of Testing

 Smoke Testing.
 Sanitary Testing.
 Regression Testing.
 Re-Testing.
 Static Testing.
  Dynamic Testing.
 Alpha-Testing.
 Beta-Testing.
 Monkey Testing.
 Compatibility Testing.
 Installation Testing.
 Adhoc Testing.
 Ext….

TCD (Test Case Documentation)

 STLC
 Test Planning.
 Test Development.
 Test Execution.
 Result Analysis.
 Bug-Tracing.
 Reporting.

 Microsoft Windows – Standards

 Manual Testing
 Automation Testing (Tools)
 Win Runner.
 Test Director.
Testing:

 The process of executing a system with the intent of finding an error.

 Testing is defined as the process in which defects are identified, isolated, subjected for
rectification and ensured that product is defect free in order to produce the quality
product and hence customer satisfaction.
 Quality is defined as justification of the requirements
 Defect is nothing but deviation from the requirements
 Defect is nothing but bug.
 Testing --- The presence of bugs
 Testing can demonstrate the presence of bugs, but not their absence
 Debugging and Testing are not the same thing!
 Testing is a systematic attempt to break a program or the AUT
 Debugging is the art or method of uncovering why the script /program did not execute
properly.
Testing Methodologies:

 Black box Testing: is the testing process in which tester can perform testing on an
application without having any internal structural knowledge of application.
Usually Test Engineers are involved in the black box testing.

 White box Testing: is the testing process in which tester can perform testing on an
application with having internal structural knowledge.
Usually The Developers are involved in white box testing.

 Gray Box Testing: is the process in which the combination of black box and white box
tonics’ are used.
Levels of Testing:

Module1 Module2 Module3

Units Units Units

i/p Integration o/p i/p Integration o/p

System Testing: Presentation + business +Databases

 UAT: user acceptance testing

STLC (SOFTWARE TESTING LIFE CYCLE)

Test Planning:

1.Test Plan is defined as a strategic document which

describes the procedure how to perform various testing on the total application in
the most efficient way.
 2.This document involves the scope of testing,

3. Objective of testing,

4. Areas that need to be tested,

5. Areas that should not be tested,

6. Scheduling Resource Planning,

7. Areas to be automated, various testing tools

Used….

Test Development:

1. Test case Development (check list)

2. Test Procedure preparation. (Description of the Test cases).

1. Implementation of test
cases. Observing the result.

Result Analysis: 1. Expected value: is nothing but expected behavior

Of application.

2. Actual value: is nothing but actual behavior of

application

Bug Tracing: Collect all the failed cases, prepare documents.

Reporting: Prepare document (status of the application)

Types Of Testing:

> Smoke Testing: is the process of initial testing in which tester looks for the availability of
all the functionality of the application in order to perform detailed testing on them. (Main check
is for available forms)

> Sanity Testing: is a type of testing that is conducted on an application initially to check for
the proper behavior of an application that is to check all the functionality are available before the
detailed testing is conducted by on them.

> Regression Testing: is one of the best and important testing. Regression testing is the
process in which the functionality, which is already tested before, is once again tested whenever
some new change is added in order to check whether the existing functionality remains same.

>Re-Testing: is the process in which testing is performed on some functionality which is

already tested before to make sure that the defects are reproducible and to rule out the
environments issues if at all any defects are there.

Static Testing: is the testing, which is performed on an application when it is not been
executed.ex: GUI, Document Testing
Dynamic Testing: is the testing which is performed on an application when it is being
executed.ex: Functional testing.

Alpha Testing: it is a type of user acceptance testing, which is conducted on an application

when it is just before released to the customer.

 Beta-Testing: it is a type of UAT that is conducted on an application when it is released to

the customer, when deployed in to the real time environment and being accessed by the real time
users.

 Monkey Testing: is the process in which abnormal operations, beyond capacity operations
are done on the application to check the stability of it in spite of the users abnormal behavior.

Compatibility testing: it is the testing process in which usually the products are tested on the
environments with different combinations of databases (application servers, browsers…etc) In
order to check how far the product is compatible with all these environments platform
combination.

Installation Testing: it is the process of testing in which the tester try to install or try to
deploy the module into the corresponding environment by following the guidelines produced in
the deployment document and check whether the installation is successful or not.
Adhoc Testing: Adhoc Testing is the process of testing in which unlike the formal testing
where in test case document is used, with out that test case document testing can be done of an
application, to cover that testing of the future which are not covered in that test case document.
Also it is intended to perform GUI testing which may involve the cosmotic issues.

TCD (Test Case Document):

Test Case Document Contains

 Test Scope (or) Test objective

 Test Scenario
 Test Procedure
 Test case
This is the sample test case document for the add hotels,Facility,Items customer
ordersshippings and Employees registration

Test scope:

 Test coverage is provided for the screen “ Login check” form of a Administration
module of Hungry Hyderabad.com application
 Areas of the application to be tested

Test Scenario:
 When the office personals use this screen for the data entry, making the transactions on
items,Bookings and saving the information on s basis and quit the form.

Test Procedure:

 The procedure for testing this screen is planned in such a way that the data entry, status
calculation functionality, saving and quitting operations are tested in terms of GUI
testing, Positive testing, Negative testing using the corresponding GUI test cases, Positive
test cases, Negative test cases respectively

Test Cases:

 Template for Test Case

T.C.No Description Exp Act Result

Guidelines for Test Cases:

1. GUI Test Cases:

 Total no of features that need to be check

 Look & Feel
 Look for Default values if at all any (date & Time, if at all any require)
 Look for spell check

Example for Gui Test cases:

T.C.No Description Expected Actual value Result

value

Check for all the The screen

features in the screen must
1
contain all
the features
 Check for the The
alignment of the alignment
2
objects as per the should be in
validations proper way

2. Positive Test Cases:

 The positive flow of the functionality must be considered

 Valid inputs must be used for testing
 Must have the positive perception to verify whether the requirements are justified.

Example for Positive Test cases:

T.C.No Description Expected value Actual value Result

1 Input UserName Redirect to Redirect to Redirect to

and Password HomePage Home Page Home Page

3. Negative Test Cases:

 Must have negative perception.
 Invalid inputs must be used for test.

Example for Negative Test cases:

T.C.No Description Expected value Actual value Result

1 Input username Login Page Login Page Login Page

and password

2
OUTPUT SCREENS:
Home
Login Page
Registration Page
View All Hotels
View All Bookings
View All Items
About Organization
Contact Organization
View Services
Admin
Admin Home
View Profile
Add Employee
View All Employees
Add Hotel
View All Hotels
Add Room Types
View Room Types
Add Faculty
View All Facility Details
Update Food details
Delete Facility
Add Booking Types
View Booking Types
Add Item Details
View All Item Details
Employee
Employee Home
View Profile
Edit Profile
View All Hotels
View All Room Types
View All Facilities
View Bookings
View Customer Bookings
View All Items
Edit Item Details
View All Customer Orders
Customer
Customer Home
View Customer Profile
View All Hotels
View Room Types
View All Facilities
View Bookings Room Types
View All Booking Types
Item Details
Search Items
Order Item
FUTURE ENHANCEMENTS

It is not possible to develop a system that makes all the requirements of the user. User

requirements keep changing as the system is being used. Some of the future enhancements that

can be done to this system are:

 As the technology emerges, it is possible to upgrade the system and can be adaptable to

desired environment.

 Because it is based on object-oriented design, any further changes can be easily

adaptable.

 Based on the future security issues, security can be improved using emerging

technologies.

 Ordfer,Item,Booking module can be enhanced

 Customer ,employee role can be implemented

BIBLIOGRAPHY
(1) Java Complete Reference By Herbert Shield

(2) Database Programming with JDBC and Java By George Reese

(3) Java and XML By Brett McLaughlin

(4) Wikipedia, URL: http://www.wikipedia.org.

(5) Answers.com, Online Dictionary, Encyclopedia and much more, URL:

http://www.answers.com

(6) Google, URL: http://www.google.co.in

(7)Project Management URL: http://www.startwright.com/project.htm