Vansh Internship Report

DHARAMPETH POLYTECHNIC
NAGPUR
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
INTERNSHIP REPORT
SESSION 2023-2024
IT-NetworkZ Infosystems Pvt. Ltd.

(Kavin India Pvt. Ltd.)
TECHNICAL HEAD: PRESENTED BY:

Mr. Rajiv Verma Vansh D. Boratkar
IT-NETWORKZ INFOSYSTEMS PVT.LTD 1|Page

DECLARATION
During my internship in IT-NetworkZ Infosystems Pvt. Ltd and preparation of this report I
realized that it is the joint venture guidance, assistance and co-operation. So, it would have not
been completed without and declaration and help received. It is matter of great privileges to
express my deep sense of gratitude towards my guide Mr. Rajiv Verma at IT-NetworkZ
Infosystems Pvt. Ltd Nagpur. For having this guidance, I am extremely thankful to him for
constant motivation and inspiration extended throughout during internship work which has made
me possible to complete the work in scheduled time. My sincere thanks to all the faculties.
Submitted By:
Vansh D. Boratkar

ACKNOWLEDGEMENT
I have taken efforts in the project. However, it would not have been possible
without the kind and help of support and help of many individual and organizations
would like to extend my sincere thanks to all of them.
I am highly indebted to Mr. RajivVerma for their guidance and constant

supervision as well as for providing necessary information regarding the project &also
for their support in completing the project. I would like to express my gratitude toward
my parents & members of IT-NetworkZ Infosystems Pvt. Ltd. for their kind co-
operation and encouragement which help me in completion of this project.
I would like to give my special gratitude and thanks to industry persons for
giving me such attention and time.
My thanks and appreciation also go to my colleague in developing the project

and people who have willingly helped me out with their abilities.
TECHNICAL HEAD: PRESENTED BY:

Mr. Rajiv Verma Vansh D. Boratkar

INDEX
Topics Page
Chapter 1: WHAT IS WEB APPLICATION 9
Chapter 2: INTRODUCTION TO DYNAMIC WEB APPLICATION 10
Chapter 3:HTML TAGS 13
Chapter 4: DATABASE AND MY SQL 14
Chapter 5: SERVLETS 16
Chapter 6: INTRODUCTION TO MVC ARCHITECTURE 40
Chapter 7: APPLICATION DESIGNING USING MVC 42
Chapter 8: VIEW DESIGNING USING HTML AND JSP PAGES 46
Chapter 9: CONTROLLER DESIGNING USING SERVLETS
Chapter 10: CREATION OF MODEL CLASSES
Chapter 11: CREATION OF DATAMANAGER CLASS TO HANDLE CRUD
OPERATION USING JDBC
Chapter 12: REFRENCES

COMPANY INFORMATION
Name: IT-NetworkZ Infosystems Pvt. Ltd.
INTRODUCTION
Ms IT-NetworkZ is an IT Company and part of Information Technology

industry, it was set on 22 May 2007. IT NetworkZ started its operations with
Information Technology services including IT Infrastructure Management and
Professional IT Training & Online Exam Facility, later in Dee 2009, company
established Software Development wing well On26 June 2015 Company was
incorporated as 'IT-NetworkZ Infosystems Pvt Ltd Company has its presence in
India & in South Africa, its head office is situated in Laxmi Nagar) and branch
offices are at Nandanvan-Nagpur, Cape Town & Johannesburg-South Africa.
Company is running its all operations independently as per their Geographic
area India operations are handled by a team of 20-25 professionals.
SERVICE CATEGORIES:
1) IT Training & International Assessment:
IT Network has very strong bonding with educational institutions and hence
established around 28- MoU's with esteemed Institutions which comes under
MSBTE, UGC and AICTE, these MoU are done for students & faculty
development. Technical team members GENwork have fine experience and
keen interest in teaching Company has trained around 4000+ candidates
under its banner and usually 7200+ students attend IT- NetworkZ Tech
sessions every year. IT NetworkZ is an Ex-authorized Prometric and
Pearson VUE test centre for International IT Exams. Currently, it is
authorized by "Kryterion Testing Network for reputed Sales Force and other
IT international exams; IT giant "Persistent Systems Ltd had taken an
initiative with company to start this facility for needy candidates.
2) Live Project & Internships:
Live Project Internship turns student into professionals. Being a part of IT

Industry IT Network Management started with this initiative to produce more

quality and Industry ready professionals Company is providing 6 Weeks, 6
Months & 1 Year Internship / Live projects for Final Year and Graduate
Candidates
3) Software Development:
IT-Network has a term of enthusiastic and creativity developers and

designers Company is providing stand alone, web applications and mobile
app developmentto various clients till now company has completed various
projects and working for some of the esteemed clients in Hospitality,
Education, and Government sector. As per the market demand and own
strength company has planned service-based solutions in Matrimony,
Employment, Education Listing Electronics Test System Venue Searching,
etc Company is planning to develop few solutions for health care industry as
well as professionals Company is providing 6 Weeks, 6 Months &1
Internship /Live for Final Year and Graduate Candidates.
AWARDS:
1) Awarded in TOP TEN Prometric Test Centres in the world; out of 5600+ Centre's for
theyear2013-14.
2) Microsoft Network Partner
3) 700-Tech Session Delivered to 20,000-Students
PRODUCTS:
Microsoft Dot Net
Virtualization Cloud
CCNA
Linux
Hardware
Security

List of Figures
Figure Page
1.1: Social Media Platforms 11
3.1: How to write HTML tags 13
4.1: Database and My SQL 14
5.1: Creating a Web application folder 18
5.2: Web INF folder inside web application 19
5.3: Web XML file and classes folder 19
5.4: Servlet class file 20
5.5: Servlet name using servlet <tag> 21
5.6: URL pattern using the servlet Mapping 21
5.7: Servlet Output 22
6.1: Architecture of MVC 23
6.2: MVC Diagram 24
8.1: View Designing using HTML & JSP page 30
9.1: Controller Design of Servlets 31
10.1: Creation of model classes 35
11.1: Creating data manager class 37
11.2: Connection of Data manager 38
4.4: Checkbox in Android 33
5.1: Communication Flow of Receiver Service 37
7.1: Output of Google Maps 45
Chapter 1
WHAT IS WEB APPPLICATION
What is Web Application:

A web application is an application program that is usually stored on a remote server, and users
can access it through the use of Software known as Web Browser.
A web application is software that runs in your web browser. Businesses have to exchange
information and deliver services remotely. They use web applications to connect with customers
conveniently and securely. The most common website features like shopping carts, product search
and filtering, instant messaging, and social media newsfeeds are web applications in their design.
They allow you to access complex functionality without installing or configuring software .
Benefits Of Web Application:
Web applications have several benefits, with almost all major enterprises utilizing them as part of
their user offerings. Here are some of the most common benefits associated with web apps.
Accessibility
Web apps can be accessed from all web browsers and across various personal and business
devices. Teams in different locations can access shared documents, content management systems,
and other business services through subscription-based web applications.
Efficient development
As detailed, the development process for web apps is relatively simple and cost-effective for
businesses. Small teams can achieve short development cycles, making web applications an
efficient and affordable method of building computer programs. In addition, because the same
version works across all modern browsers and devices, you won't have to create several different
iterations for multiple platforms.
User simplicity
Web apps don't require users to download them, making them easy to access
while eliminating the need for end-user maintenance and hard drive capacity. Web
applications automatically receive software and security updates, meaning they
are always up to date and less at risk of security breaches.
Scalability
Businesses using web apps can add users as and when they need, without additional infrastructure
or costly hardware. In addition, the vast majority of web application data is stored in the cloud,
meaning your business won't have to invest in additional storage capacity to run web apps.
Some Common Web Applications are:

There are numerous types of web applications. Here are some of the most well-known.
Workplace collaboration web applications

Workspace Collaboration web apps allow team members to access documents, shared calendars,
business instant messaging services, and other enterprise tools.
Ecommerce web applications

Ecommerce web apps such as Amazon.com enable users to browse, search, and pay for products
online.
Email web applications

Webmail apps are widely used by enterprises and personal users to access their emails. They often
include other communication tools such as instant messaging and video meetings.
Online banking web applications

Business and personal users widely use online banking web apps to access their accounts and other
financial products such as loans and mortgages.
Working Of Web Applications:

Web applications have a client-server architecture. Their code is divided into two components—
client-side scripts and server-side scripts.
Client-side architecture
The client-side script deals with user interface functionality like buttons and drop-down boxes.
When the end user clicks on the web app link, the web browser loads the client-side script and
renders the graphic elements and text for user interaction. For example, the user can read content,
watch videos, or fill out details on a contact form. Actions like clicking the submit button go to the
server as a client request.
Server-side architecture
The server-side script deals with data processing. The web application server processes the client
requests and sends back a response. The requests are usually for more data or to edit or save new
data. For example, if the user clicks on the Read More button, the web application server will send
content back to the user. If the user clicks the Submit button, the application server will save the
user data in the database. In some cases, the server completes the data request and sends the
complete HTML page back to the client. This is called server side rendering.
Chapter 2
INTRODUCTION TO DYNAMIC WEB APPPLICATION

Dynamic web applications are type of web applications that utilizes dynamic content and interactive
features to provide a more engaging and personalized user experience. Unlike static web pages, which
display the same information to all users, dynamic web applications generate content on the fly based on
user input, database queries, or real-time data.
The dynamic nature of these applications allows for a wide range of functionalities, such as user
registration and login systems, online shopping carts, discussion forums, content management
systems, social media platforms, and much more. They enable users to interact with the
application, submit forms, receive personalized recommendations, and access real-time
information.
Dynamic web applications are typically built using a combination of front-end and back-end
technologies. The front-end, also known as the client-side, is responsible for the user interface and
handling user interactions. This includes HTML, CSS, and JavaScript, which are used to structure
and style the web pages and implement interactive features.
On the other hand, the back end, or server-side, is responsible for processing user requests,
querying databases, performing calculations, and generating dynamic content. It involves server-
side programming languages like Python, Ruby, PHP, or Java, as well as frameworks and libraries
that streamline development tasks.
To create dynamic web applications, developers often utilize databases to store and retrieve data.
These databases can be relational (such as MySQL or PostgreSQL) or NoSQL (like MongoDB or
Redis), depending on the application's requirements.
Furthermore, dynamic web applications often employ the use of APIs (Application Programming
Interfaces) to integrate with external services, retrieve data from other applications, or expose their
own functionality to be consumed by other developers.
Overall, dynamic web applications offer a more interactive and personalized user experience by
generating content dynamically, processing user input, and utilizing databases and external
services. They have revolutionized the way we interact with websites, enabling a wide range of
functionalities and enhancing the overall usability and engagement for users.
Examples Of Dynamic Web Applications:

There are numerous examples of dynamic web applications across various industries. Here are
some common examples:
1. Social Media Platforms: Websites like Facebook, Twitter, and Instagram are dynamic web
applications that allow users to create profiles, connect with friends, post updates, share
media, and interact with other users in real time.
IT-NETWORKZ INFOSYSTEMS PVT.LTD 10 | P a g e

Fig 1.1 Social Media Platforms
1. E-commerce Websites: Online marketplaces like Amazon, eBay, and Shopify are dynamic
web applications that enable users to browse and purchase products, add items to shopping
carts, make secure payments, track orders, and receive personalized recommendations
based on their browsing and purchasing history.
2. Content Management Systems (CMS): CMS platforms like WordPress, Joomla, and Drupal
are dynamic web applications that provide a user-friendly interface for managing and
publishing content on websites. They allow users to create, edit, and organize web pages,
blog posts, images, and other media elements.
3. Online Banking Systems: Banking websites and applications provide dynamic features
such as account balance inquiries, fund transfers, bill payments, transaction histories, and
online loan applications. These applications interact with backend banking systems to
retrieve and update account information in real time.
4. Online Learning Platforms: Platforms like Udemy, Coursera, and Khan Academy are
dynamic web applications that offer online courses, quizzes, assessments, and interactive
learning materials. They track student progress, provide personalized recommendations,
and facilitate communication between students and instructors.
5. Travel and Booking Websites: Dynamic web applications like Expedia, Airbnb, and
Booking.com allow users to search and book flights, hotels, vacation rentals, and car
rentals. These applications integrate with multiple travel APIs to fetch real-time
availability, pricing, and booking information.
6. Real-Time Collaboration Tools: Applications such as Google Docs, Trello, and Slack
enable users to collaborate in real time on documents, projects, and team communication.
Multiple users can edit documents simultaneously, track changes, assign tasks, and
exchange messages in a dynamic and interactive environment.
7. Online Food Delivery Platforms: Services like Uber Eats, Grubhub, and Deliveroo are
dynamic web applications that enable users to browse restaurants, view menus, place
orders, track deliveries, and provide ratings and reviews.

Chapter 3
HTML TAGS
HTML (Hypertext Markup Language) tags are elements used to structure and define the content of
a web page. HTML tags are enclosed within angle brackets ("<" and ">") and consist of an
opening tag, content, and a closing tag.
Some Of The Basic HTML Tags Are:

1. <html>: Represents the root element of an HTML document. All other elements are
descendants of this element.
2. <head>: Contains metadata about the document, such as the title, linking to external
stylesheets or scripts, and other related information.
3. <body>: Encloses the main content of the web page, including text, images, links, and
other elements that are visible to the users.
4. <h1> to <h6>: Heading tags that represent different levels of headings. <h1> is the highest
level, used for main headings, while <h6> is the lowest level, used for subheadings.
5. <p>: Defines a paragraph of text, typically used for longer blocks of content.
6. <a>: Creates a hyperlink and is used for linking to other web pages or resources. It can be
customized with attributes like href to specify the target URL.
7. <img>: Inserts an image into the web page. It requires the src attribute to specify the image
source (URL) and can have optional attributes like alt for alternate text and width/height
for dimensions.
8. <ul> and <ol>: <ul> defines an unordered list, while <ol> defines an ordered list. List
items (<li>) are used within these tags to represent individual list elements.
9. <div>: Defines a division or container for grouping and styling content. It is a versatile tag
used for layout purposes and CSS styling.
10. <span>: Defines an inline container for styling or manipulating specific portions of text. It
is often used for applying CSS styles or targeting specific text elements.
11. <table>: Represents tabular data and contains rows (<tr>), table headers (<th>), and table
cells (<td>). It is used to create structured data tables.
12. <form>: Creates a form for user input, such as text fields, checkboxes, radio buttons,
dropdown menus, and submit buttons.
13. <input>: Defines an input field within a form, allowing users to enter data. It can have
various types (text, password, email, etc.) specified by the type attribute.
14. <button>: Creates a clickable button, typically used to trigger an action or submit a form.

Fig 3.1 How to write Html tags
Chapter 4
DATABASE AND MY SQL
DATABASE:
A database is a structured collection of data that is organized and managed to facilitate efficient
storage, retrieval, and manipulation of information. Databases are widely used in web applications
to store and manage large amounts of data, such as user information, product details, or any other
data relevant to the application. Databases are used in various domains, including web
applications, business systems, scientific research, and more. They provide a way to store and
organize data in a structured manner, ensuring data integrity and consistency.
Key Features Of Database:

1. Data Organization: Databases organize data into tables, which consist of rows (records) and
columns (fields). This tabular structure allows for efficient storage and retrieval of data.
2. Data Retrieval: Databases provide powerful query languages, such as SQL (Structured
Query Language), to retrieve specific data based on defined conditions and criteria.
3. Data Integrity: Databases enforce data integrity rules, such as unique constraints, primary
keys, and referential integrity, to maintain the accuracy and consistency of the data.
4. Scalability: Databases can handle large volumes of data and support concurrent access from
multiple users or applications. They can scale vertically (increasing hardware resources) or
horizontally (distributed across multiple machines) to accommodate growing data needs.
5. Security: Databases offer security measures to protect data from unauthorized access and
ensure data privacy. These include user authentication, access control, and encryption.
6. Transactions: Databases provide transactional capabilities to ensure data consistency.
Transactions allow multiple operations to be executed as a single logical unit, ensuring that

either all operations succeed or none of them take effect (the ACID properties: Atomicity,
Consistency, Isolation, Durability).
7. Indexing: Databases use indexes to speed up data retrieval by creating optimized data
structures that allow quick look up and searching based on specific columns.
My SQL:
MySQL is one of the most popular relational database management systems (RDBMS) used for
web applications. It provides a robust and scalable solution for storing and retrieving data. SQL
(Structured Query Language) is a programming language used to communicate with and
manipulate databases.
Fig 4.1 Database and My SQL
Key Concepts Related To Databases And My SQL:

1. Tables: Databases consist of one or more tables, which are structured entities that organize
data into rows and columns. Each table represents a specific type of data, and each row in
the table represents a unique record, while each column represents a specific attribute of
that record.
2. Fields and Datatypes: Each column in a table is known as a field, and each field has a
specific datatype, such as text, number, date, etc. The datatype defines the type of data that
can be stored in that field.
3. Primary Key: A primary key is a unique identifier for each record in a table. It ensures that
each record is uniquely identified and can be used to establish relationships between tables.
4. SQL Queries: SQL is used to perform various operations on databases, including creating
tables, inserting data, retrieving data, updating records, and deleting records. Common SQL
commands include SELECT, INSERT, UPDATE, DELETE, and JOIN.
5. Relationships: Relationships can be established between tables using keys (such as primary
keys and foreign keys) to define how data is related. The most common types of
relationships are one-to-one, one-to-many, and many-to-many.
6. Indexes: Indexes improve the performance of database queries by creating an ordered
structure for faster data retrieval. They are created on specific columns to speed up search
operations.

7. Normalization: Normalization is the process of organizing data in a database to minimize
redundancy and improve data integrity. It involves breaking down tables into smaller, more
manageable pieces and establishing relationships between them.
MySQL offers a wide range of features and functionalities to manage databases effectively. It has
extensive community support and is compatible with various programming languages and web
frameworks, making it a popular choice for web applications that require data storage and retrieval.
Understanding databases and SQL is essential for building dynamic web applications that interact
with data, perform complex queries, and ensure data integrity and efficiency.
Chapter 5
SERVLETS
Servlets are Java-based components that run on a web server and dynamically generate web
content. They are an integral part of Java Enterprise Edition (Java EE) and provide a powerful way
to handle HTTP requests, process data, and generate responses.
Some Key Points About Servlets:

1. Servlet Lifecycle: Servlets follow a lifecycle consisting of several phases, including
initialization, request handling, and destruction. Servlet containers, such as Apache Tomcat
or Jetty, manage the lifecycle of servlets.
2. HTTP Handling: Servlets are primarily used to handle HTTP requests and generate
responses. They can handle different HTTP methods (GET, POST, PUT, DELETE) and
retrieve information from request parameters, headers, and cookies.
3. Server-side Processing: Servlets run on the server-side and can perform various tasks such
as accessing databases, interacting with external APIs, processing form data, and
implementing business logic.
4. Dynamic Content Generation: Servlets dynamically generate web content by using Java to
generate HTML, XML, JSON, or any other desired format. They can combine static
templates with dynamic data to create dynamic web pages.
5. Session Management: Servlets provide session management capabilities, allowing for the
tracking and maintenance of user-specific information across multiple requests. Sessions
can store user state, such as login credentials or shopping cart contents.
6. Multithreading: Servlets are designed to handle multiple requests concurrently. The servlet
container manages the thread pool and assigns threads to handle incoming requests,
ensuring efficient utilization of resources.
7. Deployment: Servlets are packaged as WAR (Web Application Archive) files and deployed
on a web server or servlet container. The container handles the instantiation, management,
and execution of servlets.

Brief Summary About Servlets:
1. Functionality: Servlets are server-side programs that receive HTTP requests and generate
responses dynamically. They can handle various HTTP methods (GET, POST, PUT,
DELETE) and interact with databases, perform calculations, or integrate with external
systems.
2. Java EE Platform: Servlets are part of the Java Enterprise Edition (Java EE) platform and
are commonly used for web application development. They are portable and can be
deployed on different web servers or servlet containers.
3. Lifecycle: Servlets follow a lifecycle with phases like initialization, request handling, and
destruction. During initialization, resources can be set up, while the request handling phase
executes the main logic based on incoming requests. The destruction phase releases any
held resources.
4. Request and Response Handling: Servlets receive HTTP requests from clients and generate
HTTP responses. They can read request parameters, headers, and cookies, and construct
dynamic responses by generating HTML, XML, JSON, or other formats.
5. Session Management: Servlets provide session management to maintain state information
across multiple requests from the same client. Session objects allow storing and retrieving
user-specific data throughout the session.
6. Multithreading: Servlet containers handle the multithreading aspect of servlets, allowing
them to handle multiple requests concurrently. The container manages a pool of threads and
assigns them to handle incoming requests efficiently.
7. Deployment: Servlets are typically packaged as WAR (Web Application Archive) files and
deployed on a web server or servlet container. The container manages the servlets'
lifecycle, handles incoming requests, and dispatches them to the appropriate servlet.
Servlets form the backbone of Java-based web applications, providing a server-side solution for
handling HTTP requests and generating dynamic responses. They offer flexibility, scalability, and
portability, making them widely used in enterprise web development.
Installation, Configuration and running Servlet:

In this section, we will see as how to install a Web Server, configure it, and finally run servlets
using this server. Throughout this tutorial, we will be using Apache’s Tomcat server as the Web
Server. Tomcat is not only an open and free server, but also the most preferred Web Server across
the world. A few reasons we can attribute for its popularity is Easy to install and configure, very
less memory footprint, fast, powerful, and portable. It is the ideal server for learning purpose.
1. Installation of Tomcat Server And JDK

As mentioned earlier, Apache’s Tomcat Server is free software available for download
@ www.apache.org. The current version of Tomcat Server is 6.0 (as of November 2007). This
Server supports Java Servlets 2.5 and Java Server Pages (JSPs) 2.1 specifications. In case of
doubt or confusion, you can refer to the abundant documentation repository available on this
site.

Important software required for running this server is Sun’s JDK (Java Development Kit) and
JRE (Java Runtime Environment). The current version of JDK is 6.0. Like Tomcat, JDK is also
free and is available for download at www.java.sun.com.
2. Configuring Tomcat Server

1. Set JAVA_HOME variable - You must have to set this variable which points to the
base installation directory of JDK installation. (e.g. c:\program file\java\jdk1.6.0).
You can either set this from the command prompt or from My Computer ->
Properties -> Advanced -> Environment Variables.
2. Specify the Server Port. You can change the server port from 8080 to 80 (if you
wish to) by editing the server.xml file in the conf folder. The path would be
something like this. c\program files\Apache software foundation\tomcat 6\conf\
server.xml.
3. Run Tomcat Server:

Once the above pre-requisites are taken care, you can test as whether the server is
successfully installed as follows:
Step 1:
Go to C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin and double click
on tomcat6
OR
Go to Start->Programs->Apache Tomcat 6.0 -> Monitor Tomcat. You will notice an

icon appear on the right side of your Status Bar. Right click on this icon and click on
Start service.
Step 2:
Open your Browser (e.g. MS Internet Explorer) and type the following URL:
http://localhost/ (If you have changed to port # to 80)
OR
Open your Browser (e.g. MS Internet Explorer) and type the following URL:
http://localhost:8080/ (If you have NOT changed the default port #)
In either case, you should get a page similar to the one in Figure-8 which signifies that
the Tomcat Server is successfully running on your machine.

4. Compile And Execute Your Servlet
This section through a step by step (and illustration) approach explains as how to
compile and then run a servlet using Tomcat Server. Though this explanation is specific
to Tomcat, the procedure explained holds true for other Web servers too (e.g. JRun,
Caucho’s Resin).
Step 1: Compile Your Servlet Program

The first step is to compile your servlet program. The procedure is no different from
that of writing and compiling a java program. But, the point to be noted is that neither
the javax.servlet.* nor the javax.servlet.http.* is part of the standard JDK. It has to be
exclusively added in the CLASSPATH. The set of classes required for writing servlets
is available in a jar file called servlet-api.jar. This jar file can be downloaded from
several sources. However, the easiest one is to use this jar file available with the
Tomcat server (C:\Program Files\Apache Software Foundation\Tomcat 6.0\lib\servlet-
api.jar). You need to include this path in CLASSPATH. Once you have done this, you
will be able to successfully compile your servlet program. Ensure that the class file is
created successfully.
Step 2: Create Your Web Application Folder

The next step is to create your web application folder. The name of the folder can be
any valid and logical name that represents your application (e.g. bank _apps, airline
_tickets _booking, shopping _cart,etc). But the most important criterion is that this
folder should be created under webapps folder. The path would be similar or close to
this - C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps. For demo
purpose, let us create a folder called demo-examples under the webapps folder.
Fig 5.1 Creating a Web Application Folder

Step 3: Create the Web-INF Folder
The third step is to create the WEB-INF folder. This folder should be created under your
web application folder that you created in the previous step. Figure-10 shows the WEB-INF folder
being placed under the demo-examples folder.
Fig 5.2 WEB-INF folder inside web application folder
Step 4: Create the Web.XML File And the Classes Folder

The fourth step is to create the web.xml file and the classes folder. Ensure that
the web.xml and classes folder are created under the WEB-INF folder. Figure 5.2 shows this file
and folder being placed under the WEB-INF folder.

Fig 5.3 Web.XML File and the Classes Folder
Note: Instead of creating the web.xml file an easy way would be to copy an existing web.xml file
(e.g., C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\examples\WEB-INF)
and paste it into this folder. You can later edit this file and add relevant information to your web
application.
Step 5: Copy the Servlets Class to the Folder

We need to copy the servlet class file to the classes folder to run the servlet that we
created. All you need to do is copy the servlet class file (the file we obtained from Step 1) to this
folder. Figure 5.4 shows the servlet _lifecycle class being placed in the classes folder.
Fig 5.4 Servlet class file placed under classes Folder.
Step 6: Edit Web.XML to include Servlet’s name and URL pattern

This step involves two actions viz. including the servlet’s name and then
mentioning the URL pattern. Let us first see as how to include the servlet’s name in the web.xml
file. Open the web.xml file and include the servlet’s name as shown in Figure 5.5.

Fig 5.5 Include servlet’s name using the <servlet> </servlet> tag.
Note : The servlet-name need not be the same as that of the class name. You can give a different
name (or alias) to the actual servlet. This is one of the main reasons as why this tag is used for.
Next, include the URL pattern using the <servlet-mapping> </servlet-mapping> tag. The URL
pattern defines as how a user can access the servlet from the browser. Figure 5.6 shows the URL
pattern entry for our current servlet.
Fig 5.6 Include URL-pattern using the <servlet-mapping> </servlet-mapping> tag.

Note : Please remember that the path given in the URL-pattern is a relative path. This means that
this path is w.r.t your web applications folder (demo-examples in this case).
Step 7: Run Tomcat Server and then Execute your Servlet.

This step again involves two actions viz. running the Web Server and then
executing the servlet. To run the server, follow the steps explained in Section 1.3.3.
After ensuring that the web server is running successfully, you can run your servlet. To do this,
open your web browser and enter the url as specified in the web.xml file. The complete url that
needs to be entered in the browser is:
http://localhost/demo-examples/servlet_lifecycle
Fig 5.7 Servlet Output

Chapter 6
INTRODUCTION TO MVC ARCHITECTURE
MVC:
A software design pattern called Model-View-Controller (MVC) divides an application into three
interdependent parts: the model, the view, and the controller.
Each of these parts oversees a particular aspect of the functionality of the application. The model is
a representation of the application's data.
It is in charge of validating and transforming data, as well as storing and retrieving it. The view
oversees showing the user the data.
It uses the controller to deliver data to it rather than directly interacting with the model. The
controller oversees gathering user input and adjusting the model as necessary.
Additionally, it updates the view by passing data from the model to the view. The MVC design has
several benefits.
This makes it simpler to comprehend, create, and maintain the program. Testability: The MVC
architecture makes it simple to test each individual component of the application separately.
This is so because each component has a distinct job to accomplish and doesn't directly
communicate with the others. Scalability: Increasing the number of controllers or views in the
MVC architecture is a simple way to scale it.
This is so that they are not directly dependent on one another and are loosely coupled in the MVC
design. MVC is a well-liked software design pattern that is applied to numerous applications,
including desktop, mobile, and web-based ones. It is a tried-and-true pattern that has been
successful in several situations.
Fig 6.1 MVC Architecture

Fig 6.2 MVC Diagram
The Model-View-Controller (MVC) architecture is a software design pattern commonly used in

the development of user interfaces. It provides a structured approach to organizing code and
separating different aspects of an application's logic. MVC promotes modularity, reusability, and
maintainability by dividing the application into three main components: the model, the view, and
the controller.
1. Model: The model represents the data and business logic of the application. It encapsulates
the data and provides methods to access and manipulate it. This component is responsible
for managing the application's state, performing data validation, and interacting with
databases or other data sources. In essence, the model represents the core functionality and
underlying structure of the application.
2. View: The view is responsible for presenting the data to the user and receiving input from
them. It represents the user interface (UI) of the application, including the layout, visual
elements, and user interactions. The view retrieves data from the model and formats it for
display. It can also send user actions and input back to the controller for further processing.
3. Controller: The controller acts as the intermediary between the model and the view. It
receives user input from the view, processes it, and interacts with the model accordingly.
The controller is responsible for updating the model's state based on user actions and
updating the view to reflect any changes in the model. It essentially controls the flow of
data and coordinates the communication between the model and the view.
The key idea behind MVC is the separation of concerns. Each component has a specific
responsibility, which helps in maintaining code organization, reducing dependencies, and
facilitating code reuse. This separation also enables parallel development, as different developers
can work on different components simultaneously.

By using the MVC architecture, developers can achieve better code maintainability, extensibility,
and testability. It also allows for easier modifications and enhancements to different parts of the
application without impacting the entire system.
The MVC model is a popular design pattern for web development because it
provides several benefits, including:
i. Separation of concerns: The MVC model separates the different aspects of an
application into different components. This makes the application easier to
understand, maintain, and test.
ii. ii. Flexibility: The MVC model is flexible and can be adapted to different types
of applications.
iii. iii. Scalability: The MVC model is scalable and can be easily extended to handle
larger applications.
Chapter 7
APPLICATION DESIGNING USING MVC
Process of Web Application using MVC:
• Create the necessary data entities (model classes) to represent the data in your application's
database schema (if applicable).
• Create the model classes and methods for interacting with the database or other data sources.
• To define the user interface, create the view components (JSP files or templates).
• Implement the controller components (servlets or managed beans) to handle user requests and
conduct actions like as updating the model and retrieving data for the view.
• Define the routing or mapping rules that will be used to route URLs to the relevant controller
components.
• Connect the components by connecting the view and controller to the model, typically via
method invocations or data bindings.
• Check your web application to confirm that the model, view, and controller are all functioning
properly.

The Model-View-Controller (MVC) is a software architectural pattern
commonly used in web application development. It divides an application into
three interconnected components: the model, the view, and the controller.
Here's a high-level description of the process of building a web application
using MVC:
1. Model:
 The model represents the data and business logic of the application. It encapsulates
the application's data structures, database interactions, and validation rules.
 The model is responsible for retrieving and manipulating data, as well as enforcing
the business rules and logic.
 It provides an interface to access and modify the data, and it notifies the view and
controller of any changes in the data.
2. View:
 The view is responsible for presenting the data to the user. It defines the user
interface (UI) and how the application's data is displayed.
 It typically consists of HTML, CSS, and sometimes JavaScript. The view is focused
on the presentation layer and does not contain business logic.
 The view receives data from the model and renders it in a format that is easily
understandable and usable by the user.
3. Controller:
 The controller acts as an intermediary between the model and the view. It handles
user input and manages the flow of data between the model and the view.
 It receives input from the user through the UI and translates it into commands for
the model or the view.
 The controller updates the model based on user actions and also updates the view to
reflect any changes in the data.
 It performs tasks such as data validation, authentication, and authorization.
4. Request Processing:
 When a user interacts with the web application, their actions are typically captured
through HTTP requests.
 The web server receives the request and routes it to the appropriate controller based
on the requested URL and HTTP method.
 The controller receives the request, processes the input, and interacts with the model
as necessary.
 The controller may perform operations such as retrieving data from the model,
updating the model, or invoking specific model methods.
 After processing the request, the controller prepares the necessary data and chooses
an appropriate view to render the response.

5. Response Rendering:
 The view is responsible for rendering the response based on the data received from
the controller.
 The view uses the provided data to generate the appropriate HTML, CSS, or
JavaScript code.
 The rendered response is then sent back to the user's browser for display.
6. Interaction Flow:
 The MVC pattern facilitates a clear separation of concerns, allowing developers to
work on different components independently.
 The user interacts with the UI, triggering actions that are handled by the controller.
 The controller updates the model and determines which view should be used to
present the data.
 The view receives the updated data from the model and renders it to the user.
 The process continues as the user interacts with the UI, and the cycle of updating
the model, processing requests, and rendering responses continues.
Simple explanation of MVC Logic:
1. Model = Here, “getters” and “setters” are designed in this class, so that value from
html input can be interchanged between all the scripted pages.
2. View = JSP (Java Servlet Pages) are created which are same as web pages which
are used to access (and sometimes perform CRUD processes on them)
3. Controller = Servlets contain objects of Model and View class and also objects of
some other packages too which help finalize the web application’s working process.

Chapter 8
VIEW DESIGNING USING HTML AND JSP PAGES
Process of Designing View Using HTML and JSP pages:
a. Create a html page with file name as the action that you want to do using it. In our case we are
going to name it as ‘Delete.jsp’.
b. Into the body tag, add input in form of text and name the object that is going to take the entered
value. In our case we named it as ‘name=”fname”’.
c. Add a button so that it will trigger the input action and pass the value from html to its
‘Controller’ class.
In Java web development, the View class is an integral part of the Model-View-Controller (MVC)
architectural pattern. It represents the user interface components and is responsible for presenting
data to the user and capturing user input.
The View class primarily focuses on the presentation layer, providing a visual representation of the
underlying data. It communicates with the Model to retrieve data and update it when necessary.
The View class is typically implemented using technologies such as JavaServer Pages (JSP),
JavaServer Faces (JSF), or Thymeleaf.
When designing views using HTML and JSP (JavaServer Pages) pages, you can
follow the following guidelines to create dynamic and interactive user
interfaces:
1. HTML Structure:
 Begin by defining the basic HTML structure of your page using the <html>,
<head>, and <body> tags.
 Include necessary CSS and JavaScript files by using the <link> and <script> tags
within the <head> section.
2. Static Content:
 Use HTML markup to create the static content of your view, such as headings,
paragraphs, lists, images, and buttons.
 Structure your content using appropriate HTML elements like <div>, <section>,
and <ul>.
3. Dynamic Content with JSP:

 Embed JSP code within HTML using <% %> tags to include dynamic content
from your server-side code.
 Use JSP expressions (<%= %>) to display the values of variables or expressions
within your HTML.
4. Looping and Conditionals:
 Utilize JSP control structures like <% if(condition) { } %>, <% for(...){ } %>, and
<% while(condition){ } %> to incorporate looping and conditionals in your view.
 Generate dynamic HTML content based on the data retrieved from the server or the
logic implemented in your Java code.
5. Form Handling:
 Use HTML <form> tags to create input forms for user interaction.
 Specify the action attribute to point to a JSP or servlet that will handle form
submission.
 Access form data in the server-side code using the request parameters.
6. Displaying Dynamic Data:
 Retrieve data from the server-side using Java code or by calling methods of your
Java classes.
 Use JSP tags like <jsp:useBean>, <jsp:getProperty>, or <jsp:setProperty> to
interact with Java objects and access their properties.
7. Styling:
 Apply CSS styles to enhance the visual appearance of your view.
 Use CSS selectors, classes, and IDs to target specific HTML elements and apply
styling rules.
8. Maintain Separation of Concerns:
 Keep your JSP pages focused on presentation logic and avoid including extensive
Java code within them.
 Consider utilizing servlets or other server-side components to handle complex
processing and keep JSP pages clean.
9. Testing and Iteration:
 Test your HTML and JSP pages on different browsers and devices to ensure
compatibility and responsiveness.
 Iterate on your design based on user feedback and make necessary improvements.

Fig 8.1 View designing using HTML and JSP pages.
Chapter 9
CONTROLLER DESIGNING USING SERVLETS
Process Of Controller Designing using Servlets:
Go to your IDE and open the folder of this project.
Add “Servlet” file in it and name it as per project topic.
In ‘doGet()’ method there, add a String variable for the value that above created JSP will return.
Using method ‘request.getParameter()’, assign the JSP returning value to the crested variable.
Now, using the ‘setter’ method, set the variable value to respective variable of model class.

Fig 9.1 Controller Designing Using Servlets
When designing the controller layer using Servlets, you can follow these steps to
handle user requests, perform business logic, and coordinate the flow of data
between the model and the view:
1. Identify the Controller Responsibilities:
 Determine the responsibilities of the controller, such as handling incoming requests,
processing data, invoking business logic, and directing the flow of control.
 Define the actions or operations that the controller needs to perform based on user
interactions.
2. Map URLs to Servlets:
 Configure the servlet mapping in the deployment descriptor (web.xml) or using
annotations.
 Associate specific URLs or URL patterns with corresponding servlet classes.
3. Extend HttpServlet:
 Create a Java class for each servlet by extending the HttpServlet class.
 Override the appropriate methods, such as doGet(), doPost(), or doPut(), to handle
specific HTTP requests.
4. Handle Request Parameters:
 Extract data submitted by the user from the request object.
 Retrieve request parameters using methods like getParameter(),
getParameterValues(), or getInputStream() depending on the request type.

5. Validate and Sanitize Inputs:
 Validate the received inputs to ensure they meet the required criteria.
 Sanitize the inputs to prevent any security vulnerabilities, such as cross-site
scripting (XSS) attacks or SQL injections.
6. Interact with the Model:
 Access the model layer, which represents the data and business logic of the
application.
 Retrieve, update, or delete data from the model as required.
 Invoke appropriate methods or services in the model layer to perform business
operations.
7. Set Attributes for the View:
 Store data or objects in the request or session attributes to make them available to
the view layer.
 Use methods like setAttribute() or getSession().setAttribute() to set attributes.
8. Forward or Redirect to the View:
 Choose the appropriate approach to communicate the result to the client and display
the response.
 Use methods like getRequestDispatcher().forward() to forward the request and
response objects to a JSP page or another servlet.
 Alternatively, use response.sendRedirect() to redirect the client to a different
URL.
9. Implement Error Handling:
 Handle exceptions that may occur during request processing.
 Create appropriate error pages to handle common HTTP error codes or specific
exceptions.
10. Test and Debug:
 Test the servlets by sending different types of requests and verifying the expected behavior.
 Debug any issues that arise during the development process.
11. Refactor and Improve:
 Review the servlets for code duplication or complex logic and consider refactoring to
improve maintainability.
 Look for opportunities to enhance the performance and efficiency of your servlets.

In Java web development, the controller class is responsible for handling
incoming requests from the client, coordinating the business logic, and
determining the appropriate response to be sent back. It acts as the
intermediary between the user interface (view) and the backend components
(model).
Here's a brief description of the controller class in Java web development:
1. Request Handling:
 The controller receives requests from the client, typically through HTTP methods
like GET or POST.
 It captures the incoming request parameters, headers, and other relevant
information.
 It validates and sanitizes the input to ensure data integrity and security.
2. Business Logic:
 The controller coordinates the execution of business logic or rules associated with
the request.
 It may interact with various backend components, such as service classes, DAOs
(Data Access Objects), or other external systems.
 The controller can invoke methods in these components to retrieve or manipulate
data, perform calculations, or orchestrate complex operations.
3. Data Processing:
 The controller processes the data received from the client or retrieved from the
backend components.
 It applies any necessary transformations, formatting, or calculations to prepare the
data for presentation or storage.
 It may validate the data against predefined rules or perform additional processing
based on the application requirements.
4. Decision Making:
 Based on the request, data, and business logic outcomes, the controller makes
decisions about the appropriate response.
 It determines the view or resource to be rendered, the data to be passed to the view,
or any further actions to be taken.
 The controller can also handle exceptions, errors, or edge cases and provide
appropriate error messages or redirects.
5. Response Generation:
 The controller prepares the response to be sent back to the client.
 It sets response headers, status codes, and content type.

 It may forward the request and response objects to a view component (such as a JSP
page or a templating engine) for rendering, or it may directly generate the response
content.
6. Integration with View and Model:
 The controller communicates with the view layer to ensure the appropriate display
of data to the user.
 It sets attributes or parameters in the request or session scope to make data available
to the view components.
 It may also interact with the model layer to retrieve or modify data, perform
database operations, or invoke external APIs.
7. Maintain Separation of Concerns:
 The controller class ensures separation of concerns by focusing on request handling
and coordinating the flow of data and logic.
 It delegates complex operations to other components, such as service classes or
utility classes, to maintain code modularity and reusability.
 It keeps the business logic decoupled from the presentation layer, promoting
maintainability and scalability.
By effectively designing and implementing the controller class, you can manage the flow of data,
logic, and responses in your Java web application, creating a robust and maintainable system.

Chapter 10
CREATION OF MODEL CLASSES
Process of Creation of Model Classes:
Go to your IDE and open the folder of this project.

• Create a class with name ending as “Model’.
• Apply encapsulation by creating ‘private’ variable. In our case we write as: “private String
name”.
• Now create ‘getter’ and ‘setter’ methods as mentioned in the code below.
• After this we have to create Object of this class to use ‘setName()’ method in servlet.
• As mentioned in code of previous chapter, the object that we created object as ‘mfes’.
Fig 10.1 Creation of model classes

When creating model classes in Java, you are defining the structure and behavior of the data
entities that your application will work with. These classes represent the data and business logic of
your application, encapsulating the state and operations related to the entities you're modeling.
Here's a brief description of the steps involved in creating model classes:
1. Identify Entities: Determine the entities or objects that your application needs to represent.
Examples include users, products, orders, customers, or any other concept relevant to your
application's domain.
2. Define Class Structure: Create a Java class for each entity. Define the class name, access
modifiers, and any necessary inheritance or interface implementations. Declare private
instance variables to represent the entity's state (properties). Implement public getter and
setter methods (accessors and mutators) for accessing and modifying the properties.
3. Add Behavior (Business Logic): Implement methods in the model class to encapsulate the
business logic associated with the entity. These methods can perform operations such as
validation, calculations, data manipulation, or any other logic relevant to the entity.
4. Consider Data Validation: Implement validation checks for the entity's properties to ensure
the data is consistent and valid. Validate input parameters, enforce constraints, and handle
any exceptional conditions. Use conditional statements, assertions, or validation
frameworks to perform the validation.
5. Implement Relationships: If your entities have relationships with each other (e.g., one-to-
one, one-to-many, or many-to-many), define the appropriate instance variables and
methods to handle those relationships. Use associations, references, or collections to
represent these relationships. Implement methods to navigate and manage the relationships
between entities.
6. Consider Persistence: If you need to persist the data represented by the model classes in a
database or any other storage mechanism, consider integrating a persistence framework like
JPA or an ORM library. Define annotations or configuration files to map the model classes
to the corresponding database tables or collections.
7. Test and Iterate: Write unit tests for the model classes to verify their behavior and
functionality. Test various scenarios, including positive and negative cases, to ensure the
model classes work as expected. Iterate on your design based on testing results and
feedback.
8. Consider Separation of Concerns: Ensure that your model classes primarily focus on
representing the data and behavior of the entities. Avoid including presentation or UI-
related code in the model classes to maintain separation of concerns. Keep the model
classes independent of the user interface and the controller components.

Chapter 11
CREATION OF DATAMANAGER CLASS TO HANDLE CRUD
OPERATIONS USING JDBC
Use Of Data manager Class

Data manager classes are typically used to handle the management and manipulation of data within
the application. These classes provide a structured approach to perform common data operations
such as retrieval, storage, updating, and deletion.
Process of Creating a Data Manager Class:
• Open your Dynamic Web Project in IDE.

• Create a new class there with classname ending with ‘DAO’.
• Now, import “java.sql.Connection” and “java.sql.DriverManager” package (NOTE: save the
DAO class in DataManager names user defined package).
• Write following code to register your SQL drivers with Class.
Fig 11.1 Creating a Data manager class.

Fig 11.2 Connection of data manager.
In Java web development, a data manager class is a component that facilitates the management and
manipulation of data within a web application. It typically acts as an intermediary between the
application's business logic and the underlying data source, such as a database.
The primary responsibility of a data manager class is to handle data retrieval, storage, and
modification operations. It provides methods and functionality to interact with the data source,
allowing the application to perform CRUD (Create, Read, Update, Delete) operations on data
entities.
To handle CRUD (Create, Read, Update, Delete) operations using JDBC (Java
Database Connectivity), you can create a DataManager class that encapsulates
the database-related functionality.
Here's a brief description of the steps involved in creating a DataManager class:
1. Establish Database Connection:

 Set up a database connection using JDBC by loading the appropriate database driver
and providing the connection URL, username, and password.
 Use the DriverManager.getConnection() method to establish a connection to the
database.
2. Create Data Access Methods:
 Implement methods for CRUD operations in the DataManager class.
 The create method inserts new records into the database.
 The read method retrieves data from the database.
 The update method modifies existing records in the database.
 The delete method removes records from the database.

3. Prepare SQL Statements:
 Use SQL statements to perform database operations.
 Prepare SQL statements using either parameterized queries or plain SQL strings.
 Use prepared statements or statement objects to execute the SQL statements.
4. Execute Database Operations:
 Execute the appropriate SQL statement for each CRUD operation.
 Use methods like executeUpdate() for create, update, and delete operations that
modify the database.
 Use methods like executeQuery() to retrieve data from the database.
5. Handle Results:
 Process the results returned from the database operations.
 For read operations, retrieve the data from the result set and populate Java objects
or collections.
 For create, update, and delete operations, check the affected rows to determine the
success or failure of the operation.
6. Close Database Resources:
 Close the database connection, statement, and result set after executing the database
operations.
 Use close() or try-with-resources to ensure proper resource cleanup.
7. Exception Handling:
 Implement exception handling to catch any errors that may occur during database
operations.
 Handle and log exceptions appropriately, providing meaningful error messages.
8. Test and Refine:
 Write unit tests to verify the functionality of the DataManager class.
 Test various scenarios, including success cases and error conditions.
 Refine and improve the code based on testing results and feedback.
9. Consider Data Access Object (DAO) Pattern:
 Optionally, consider implementing the Data Access Object (DAO) pattern to further
separate data access logic from the DataManager class.
 Create separate DAO classes that handle specific entity operations and interact with
the DataManager for database connectivity.
By creating a DataManager class that handles CRUD operations using JDBC, you can effectively
interact with the database, encapsulating the database-related functionality in a modular and
reusable manner.

Some Common Features And Functions of a Datamanager Class are:
• Connection Management: The data manager class establishes and maintains a

connection to the data source, ensuring efficient and secure communication.
• Query Execution: It executes SQL queries or other appropriate methods to retrieve
and manipulate data from the database. This includes executing SELECT statements
for data retrieval, INSERT and UPDATE statements for data modification, and
DELETE statements for data deletion.
• Data Mapping: The data manager class maps the retrieved data from the database
to appropriate Java objects or data structures, making it easier for the application to
work with the data.
• Data Validation: It performs data validation and ensures the integrity of data before
storing or modifying it in the database. This helps prevent data corruption or
inconsistencies.
• Transaction Management: The data manager class handles database transactions,
ensuring atomicity, consistency, isolation, and durability (ACID properties) when
performing multiple operations on the data source.
• Error Handling: It handles exceptions and errors that may occur during data
operations, providing appropriate error messages or taking necessary recovery
actions.
• Caching and Performance Optimization: Depending on the application's
requirements, the data manager class may incorporate caching mechanisms to
improve performance by storing frequently accessed data in memory.
• Overall, the data manager class acts as a central component for managing data
operations in a Java web application, abstracting the complexity of data access and
providing a clean and organized interface for interacting with the underlying data
source

Chapter 8
REFRENCES
https://www.javatpoint.com/mvc-architecture-in-java
https://phoenixnap.com/kb/install-tomcat-windows
https://www.geeksforgeeks.org/introduction-to-jsp/
https://www.javatpoint.com/what-is-database
https://www.oracle.com/in/database/what-is-database/
https://www.geeksforgeeks.org/mvc-design-pattern/
https://www.simplilearn.com/tutorials/html-tutorial/html-tag

Vansh Internship Report

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vansh Internship Report

Uploaded by

Copyright:

Available Formats

DHARAMPETH POLYTECHNIC

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

IT-NetworkZ Infosystems Pvt. Ltd.

TECHNICAL HEAD: PRESENTED BY:

IT-NETWORKZ INFOSYSTEMS PVT.LTD 1|Page

IT-NETWORKZ INFOSYSTEMS PVT.LTD 2|Page

I am highly indebted to Mr. RajivVerma for their guidance and constant

My thanks and appreciation also go to my colleague in developing the project

TECHNICAL HEAD: PRESENTED BY:

IT-NETWORKZ INFOSYSTEMS PVT.LTD 3|Page

Chapter 1: WHAT IS WEB APPLICATION 9

Chapter 2: INTRODUCTION TO DYNAMIC WEB APPLICATION 10

Chapter 3:HTML TAGS 13

Chapter 4: DATABASE AND MY SQL 14

Chapter 6: INTRODUCTION TO MVC ARCHITECTURE 40

Chapter 7: APPLICATION DESIGNING USING MVC 42

Chapter 8: VIEW DESIGNING USING HTML AND JSP PAGES 46

Chapter 9: CONTROLLER DESIGNING USING SERVLETS

Chapter 10: CREATION OF MODEL CLASSES

Chapter 11: CREATION OF DATAMANAGER CLASS TO HANDLE CRUD

OPERATION USING JDBC

Chapter 12: REFRENCES

IT-NETWORKZ INFOSYSTEMS PVT.LTD 4|Page

Ms IT-NetworkZ is an IT Company and part of Information Technology

1) IT Training & International Assessment:

2) Live Project & Internships:

Live Project Internship turns student into professionals. Being a part of IT

IT-NETWORKZ INFOSYSTEMS PVT.LTD 5|Page

IT-Network has a term of enthusiastic and creativity developers and

Microsoft Dot Net

IT-NETWORKZ INFOSYSTEMS PVT.LTD 6|Page

3.1: How to write HTML tags 13

4.1: Database and My SQL 14

5.1: Creating a Web application folder 18

5.2: Web INF folder inside web application 19

5.3: Web XML file and classes folder 19

5.4: Servlet class file 20

5.5: Servlet name using servlet <tag> 21

5.6: URL pattern using the servlet Mapping 21

5.7: Servlet Output 22

6.1: Architecture of MVC 23

6.2: MVC Diagram 24

8.1: View Designing using HTML & JSP page 30

9.1: Controller Design of Servlets 31

10.1: Creation of model classes 35

11.1: Creating data manager class 37

11.2: Connection of Data manager 38

4.4: Checkbox in Android 33

5.1: Communication Flow of Receiver Service 37

7.1: Output of Google Maps 45

What is Web Application:

Some Common Web Applications are:

IT-NETWORKZ INFOSYSTEMS PVT.LTD 8|Page

Workplace collaboration web applications

Ecommerce web applications

Email web applications

Online banking web applications

Working Of Web Applications:

IT-NETWORKZ INFOSYSTEMS PVT.LTD 9|Page

Examples Of Dynamic Web Applications:

IT-NETWORKZ INFOSYSTEMS PVT.LTD 10 | P a g e

IT-NETWORKZ INFOSYSTEMS PVT.LTD 11 | P a g e

Some Of The Basic HTML Tags Are:

IT-NETWORKZ INFOSYSTEMS PVT.LTD 12 | P a g e