Report Samplesssssss

SANTOSH M
CONTENTS 1: INTRODUCTION
Introduction to the project Goal Objective Scope of the project General Description about the existing system Project Function Overview
2:
HARDWARE REQUIREMENTS
2.1 Machine Configuration 2.2 Peripheral Specification 2.3 Software for Development & Deployment
3:
SOFTWARE REQUIREMENTS
3.1 Front End 3.2 Why JAVA 3.3 Back End
4:
SYSTEM DEFINITION
4.1 4.2 4.3 4.4 4.5 Analysis Data Flow Diagrams SCREEN SHOTS Tables Source Code
5 : IMPLEMETATION 6 : TESTING & RESULTS 7 : CONCLUSION 8 : FUTURE ENHANCEMENT 9: BIBILOGAPHY
National College / BCA 6 Sem
Page 1
SANTOSH M
1. INTRODUCTION 1.1 Introduction of The Project:

.
1.2 Goal:
1.3
Objective:
1.4 Scope Of The Project: 1.5 General Description Of the Existing System
1.6 Project Function Overview
2. HARDWARE REQUIREMENTS 2.1

Machine Configuration:
Pentium processor RAM Capacity Hard Disk Floppy disk CD-ROM Drive KEYBOARD ------------------------------------------Pentium 4 or above 1GB 80GB 1.44 MB 32 HZ 108 Standard
2.2
Peripheral Specifications:
Page 2
SANTOSH M
Pentium processor RAM Capacity Hard Disk Floppy disk CD-ROM Drive Monitor KeyBoard
---------------------------------------------------
Pentium 4 or above 1GB 20GB 1.44 MB 32 HZ 14 inch Monitor 108 Standard
2.3

Software for development and deployment:

Operating System Browser Web/Application Server Database Server Programming Language Database Connectivity Web Technologies -------------------------------------------------Windows 95/98/NT/2000 Internet Explorer Tomcat server 5.5 Sql Server 2000 Java 1.4 and above (JDK) JDBC-ODBC Driver JSP,HTML, FlashMx, SwisHmax, Dream Weaver, Web style-4.
Page 3
SANTOSH M
Deployment:
The Java 2 Platform, Enterprise Edition Deployment Specification defines a contract between deployment tools and J2EE products. The J2EE products provide plug-in components that run in the deployment tool and allow the deployment tool to deploy applications into the J2EE product. The deployment tool provides services used by these plug-in components.
3. SOFTWARE REQUIREMENTS :
One of the most difficult tasks is that, the selection of the software, once system requirement is known is determining whether a particular software package fits the requirements. After initial selection further security is needed to determine the desirability of particular software compared with other candidates. This section first summarizes the application requirement question and then suggests more detailed comparisons. SRS (software requirement specification) is the official statement of what is required of the system developers; it includes both user requirements for the system and detailed specification of the system requirements. This document is used while designing the proposed system and can also be used in the future if the system is to be enhanced.
3.1 Front End : J2EE (Servlets,JSP,HTML)

An Overview of J2EE The J2EE platform uses a multitiered distributed application model. This means application logic
Page 4
SANTOSH M is divided into components according to function, and the various application components that make up a J2EE application are installed on different machines depending on which tier in the multitiered J2EE environment the application component belongs. Figure 1 shows two multitiered J2EE applications divided into the following tiers. The J2EE application parts shown in the figure are presented in J2EE Apllication Components.

Client tier components run on the client machine Web tier components run on the J2EE server Business tier components run on the J2EE server Enterprise information system (EIS) tier software runs on the EIS server
While a J2EE application can consist of the three or four tiers shown in Figure 1, J2EE multitiered applications are generally considered to be three-tiered applications because they are distributed over three different locations: client machines, J2EE server machine, and the database or legacy machines at the back-end. Three-tiered applications that run in this way extend the standard two-tiered client and server model by placing a multithreaded application server between the client application and back-end storage.
Figure 1 Multitiered Applications
Page 5
SANTOSH M
J2EE Application Components:

J2EE applications are made up of components. A J2EE component is a self-contained functional software unit that is assembled into a J2EE application with its related classes and files and communicates with other components. The J2EE specification defines the following J2EE components:

Application clients and applets are client components. Java Servlet and JavaServer PagesTM (JSPTM) technology components are web components. Enterprise JavaBeansTM (EJBTM) components (enterprise beans) are business components. J2EE components are written in the Java programming language and compiled in the same way as any Java programming language program. The difference when you work with the J2EE platform, is J2EE components are assembled into a J2EE application, verified that they are well-formed and in compliance with the J2EE specification, and deployed to production where they are run and managed by the J2EE server. Client Components: A J2EE application can be web-based or non-web-based. An application client executes on the client machine for a non-web-based J2EE application, and a web browser downloads web pages and applets to the client machine for a web-based J2EE application.
Application Clients:
An application client runs on a client machine and provides a way for users to handle tasks such as J2EE system or application administration. It typically has a graphical user interface created from Project Swing or Abstract Window Toolkit (AWT) APIs, but a command-line interface is certainly possible. Application clients directly access enterprise beans running in the business tier. However, if the J2EE application client requirements warrant it, an application client can open an
Page 6
SANTOSH M HTTP connection to establish communication with a servlet running in the web tier.
Web Browsers:
The user's web browser downloads static or dynamic Hypertext Markup Language (HTML), Wireless Markup Language (WML), or Extensible Markup Language (XML) web pages from the web tier. Dynamic web pages are generated by servlets or JSP pages running in the web tier.
Applets:
A web page downloaded from the web tier can include an embedded applet. An applet is a small client application written in the Java programming language that executes in the Java VM installed in the web browser. However, client systems will likely need Java Plug-in and possibly a security policy file so the applet can successfully execute in the web browser. JSP pages are the preferred API for creating a web-based client program because no plug-ins or security policy files are needed on the client systems. Also, JSP pages enable cleaner and more modular application design because they provide a way to separate applications programming from web page design. This means personnel involved in web page design do not need to understand Java programming language syntax to do their jobs. Applets that run in other network-based systems such as handheld devices or car phones can render Wireless Markup Language (WML) pages generated by a JSP page or servlet running on the J2EE server. The WML page is delivered over Wireless Application Protocol (WAP) and the network configuration requires a gateway to translate WAP to HTTP and back again. The gateway translates the WAP request coming from the handheld device to an HTTP request for the J2EE server, and then translates the HTTP server response and WML page to a WAP server response and WML page for display on the handheld device.
JavaBeansTM Component Architecture:

The client tier might also include a component based on the JavaBeansTM component architecture (JavaBeans
Page 7
SANTOSH M component) to manage the data flow between an application client or applet and components running on the J2EE server. JavaBeans components are not considered components by the J2EE specification. JavaBeans components written for the J2EE platform have instance variables and get and set methods for accessing the data in the instance variables. JavaBeans components used in this way are typically simple in design and implementation, but should conform to the naming and design conventions outlined in the JavaBeans component architecture.
J2EE Server Communications:

Figure 2 shows the various elements that can make up a thin client. The thin client communicates with the business tier running on the J2EE server either directly, or as in the case of a thin client running in a browser, by going through JSP pages or servlets running in the web tier.
Figure 2 Thin Client and J2EE Application
Thin Clients:
J2EE applications use a thin client. A thin client is a lightweight interface to the application that does not do things like query databases, execute complex business rules, or connect to legacy applications. Heavyweight operations like these are off-loaded to web or enterprise beans executing on the J2EE server where they can leverage the security, speed, services, and reliability of J2EE server-side technologies.
Page 8
SANTOSH M
Web Components:
J2EE web components can be either JSP pages or servlets. Servlets are Java programming language classes that dynamically process requests and construct responses. JSP pages are text-based documents that execute as servlets, but allow a more natural approach to creating static content. Static HTML pages and applets are bundled with web components during application assembly, but are not considered web components by the J2EE specification. Server-side utility classes can also be bundled with web components, and like HTML pages, are not considered web components. Like the client tier and as shown in Figure 3, the web tier might include a JavaBeans class to manage the user input and send that input to enterprise beans running in the business tier for processing.
Figure 3 Web Tier and J2EE Application
Business Components:
Business code, which is logic that solves or meets the needs of a particular business domain such as banking, retail, or finance, is handled by enterprise beans running in the business tier. Figure 4 shows how an enterprise bean receives data from client programs, processes it (if necessary), and sends it to the enterprise information system tier for storage. An enterprise bean also retrieves data from storage, processes it (if necessary), and sends it back to the client program.
Page 9
SANTOSH M There are two kinds of enterprise beans: session beans and entity beans. A session bean represents a transient conversation with a client. When the client finishes executing, the session bean and its data are gone. In contrast, an entity bean represents persistent data stored in one row of a database table. If the client terminates or if the server shuts down, the underlying services ensure the entity bean data is saved.
Figure 4 Business and EIS Tiers
Enterprise Information System Tier:

The enterprise information system tier handles enterprise information system software, and includes enterprise infrastructure systems such as enterprise resource planning (ERP), mainframe transaction processing, database systems, and other legacy information systems. J2EE application components might need access to enterprise information systems for database connectivity, for example.
J2EE Architecture:
Normally, thin-client multitiered applications are hard to write because they involve many lines of intricate code to handle transaction and state management, multithreading, resource pooling, and other complex low-level details. The component-based and platform-independent J2EE architecture makes J2EE applications easy to write because business logic is organized into reusable components and the J2EE server provides underlying services in the form of a container for every component type. Because you do not
Page 10
SANTOSH M have to develop these services yourself, you are free to concentrate on solving the business problem at hand. Containers and Services: Components are installed in their containers during deployment and are the interface between a component and the low-level platform-specific functionality that supports the component. Before a web, enterprise bean, or application client component can be executed, it must be assembled into a J2EE application and deployed into its container. The assembly process involves specifying container settings for each component in the J2EE application and for the J2EE application itself. Container settings customize the underlying support provided by the J2EE Server, which include services such as security, transaction management, Java Naming and Directory InterfaceTM (JNDI) lookups, and remote connectivity. Here are some of the highlights:
The J2EE security model lets you configure a web component or enterprise bean so system resources are accessed only by authorized users. The J2EE transaction model lets you specify relationships among methods that make up a single transaction so all methods in one transaction are treated as a single unit. JNDI lookup services provide a unified interface to multiple naming and directory services in the enterprise so application components can access naming and directory services. The J2EE remote connectivity model manages lowlevel communications between clients and enterprise beans. After an enterprise bean is created, a client invokes methods on it as if it were in the same virtual machine.
The fact that the J2EE architecture provides configurable services means that application components within the same J2EE application can behave differently based on where they are deployed. For example, an enterprise bean can have security settings that allow it a certain level of access to database data in one production environment
Page 11
SANTOSH M and another level of database access in another production environment. The container also manages non-configurable services such as enterprise bean and servlet life cycles, database connection resource pooling, data persistence, and access to the J2EE platform APIs described in J2EE APIs. Although data persistence is a non-configurable service, the J2EE architecture lets you override container-managed persistence by including the appropriate code in your enterprise bean implementation when you want more control than the default container-managed persistence provides. For example, you might use bean-managed persistence to implement your own finder (search) methods or to create a customized database cache. Container Types: The deployment process installs J2EE application components in the following types of J2EE containers. The J2EE components and container addressed in this tutorial are shown in Figure 5.
An Enterprise JavaBeans (EJB) container manages the execution of all enterprise beans for one J2EE application. Enterprise beans and their container run on the J2EE server. A web container manages the execution of all JSP page and servlet components for one J2EE application. Web components and their container run on the J2EE server. An application client container manages the execution of all application client components for one J2EE application. Application clients and their container run on the client machine. An applet container is the web browser and Java Plug-in combination running on the client machine.
Page 12
SANTOSH M
Figure 5 J2EE Server and Containers
Packaging:
J2EE components are packaged separately and bundled into a J2EE application for deployment. Each component, its related files such as GIF and HTML files or server-side utility classes, and a deployment descriptor (DD), are assembled into a module and added to the J2EE application. A J2EE application is composed of one or more enterprise bean, web, or application client component modules. The J2EE application and each of its modules has its own deployment descriptor. A deployment descriptor is an Extensible Markup Language (XML) text-based file with an .xml extension that describes a component's deployment settings. An enterprise bean module deployment descriptor, for example, declares transaction attributes and security authorizations for an enterprise bean. Because deployment descriptor information is declarative, it can be changed without modifying the bean source code. At run time, the J2EE server reads the deployment descriptor and acts upon the component accordingly. The first step in assembling a J2EE application is to create an Enterprise ARchive (EAR) file. A J2EE application with all of its modules is delivered in an EAR file. An EAR file is a standard Java Archive (JAR) file with an .ear extension. Next, the J2EE modules are assembled into EJB JAR, application client JAR, or Web ARchive (WAR) files.
Page 13
SANTOSH M
Each EJB JAR file contains its deployment descriptor, related files, and the .class files for the enterprise bean. Each application client JAR file contains its deployment descriptor, related files, and the .class files for the application client. Each WAR file contains its deployment descriptor, related files, and the .class files for the servlet or .jsp files for a JSP page.
Using modules and EAR files makes it possible to assemble a number of different J2EE applications using some of the same components. No extra coding is needed; it is just a matter of assembling various J2EE modules into J2EE EAR files.
Development Roles:
Reusable modules make it possible to divide the application development and deployment process into distinct roles so different people or companies can perform different parts of the process. The first two roles involve purchasing and installing the J2EE product and tools. Once software is purchased and installed, J2EE components can be developed by application component providers, assembled by application assemblers, and deployed by application deployers. In a large organization, each of these roles might be executed by different individuals or teams. This division of labor works because each of the earlier roles output a portable file that is the input for a subsequent role. For example, in the application component development phase, an enterprise bean software developer delivers EJB JAR files. In the application assembly role, another developer combines these EJB JAR files into a J2EE application and saves it in an .ear file. In the application deployment role, a system administrator at the customer site uses the EAR file to install the J2EE application into a J2EE server. The different roles are not always executed by different people. If you work for a small company, for example, or if you are prototyping a sample application, you might perform the tasks in every phase.
Page 14
SANTOSH M
J2EE Product Provider:

The company that designs and makes available for purchase the J2EE platform, APIs, and other features defined in the J2EE specification. Product providers are typically operating system, database system, application server, or web server vendors who implement the J2EE platform according to the Java 2 Platform, Enterprise Edition Specification.
Tool Provider:
The person or company who makes development, assembly, and packaging tools used by component providers, assemblers, and deployers. See Tools for information on the tools available with J2EE SDK version 1.3.
Application Component Provider

The company or person who creates web components, enterprise beans, applets, or application clients for use in J2EE applications.
Enterprise Bean Creation

A software developer performs the following tasks to deliver an EJB JAR file that contains the enterprise bean:

Writes and compiles the source code Specifies the deployment descriptor Bundles the .class files and deployment descriptor into an EJB JAR file
Web Component Creation

A web designer (JSP pages) or software developer (servlets) performs the following tasks to deliver a WAR file containing the web component.

Writes and compiles servlet source code Writes JSP and HTML files Specifies the deployment descriptor for the web component Bundles the .class, .jsp, .html, and deployment descriptor files in the WAR file
Page 15
SANTOSH M
J2EE Application Client Creation

A software developer performs the following tasks to deliver a JAR file containing the J2EE application client.

Writes and compiles the source code Specifies the deployment descriptor for the client Bundles the .class files and deployment descriptor into the JAR file
Application Assembler The company or person who gets application component JAR files from component providers and assembles them into a J2EE application EAR file. The assembler or deployer can edit the deployment descriptor directly or use tools that correctly add XML tags according to interactive selections. A software developer performs the following tasks to deliver an EAR file containing the J2EE application.
Assembles EJB JAR and web components (WAR) files created in the previous phases into a J2EE application (EAR) file. Specifies the deployment descriptor for the J2EE application. Verifies that the contents of the EAR file are well-formed and comply with the J2EE specification.
Application Deployer and Administrator

The company or person who configures and deploys the J2EE application, administers the computing and networking infrastructure where J2EE applications run, and oversees the runtime environment. Duties include such things as setting transaction controls, security attributes, and specifying connections to databases. During configuration, the deployer follows instructions supplied by the application component provider to resolve external dependencies, specify security settings, and assign transaction attributes. During installation, the deployer moves the application components to the server, and generates the container-specific classes and interfaces.
Page 16
SANTOSH M A deployer/system administrator performs the following tasks to install and configure a J2EE application.

Adds the J2EE application (.ear) file created in the preceding phase to the J2EE server. Configures the J2EE application for the operational environment by modifying the deployment descriptor of the J2EE application. Verifies that the contents of the EAR file are wellformed and comply with the J2EE specification. Deploys (installs) the J2EE application (.ear) into the J2EE server
Reference Implementation Software

The J2EE SDK is a non-commercial operational definition of the J2EE platform and specification made freely available by Sun Microsystems for demonstrations, prototyping, and educational uses. It comes with the J2EE application server, web server, relational database, J2EE APIs, and complete set of development and deployment tools. You can download the J2EE SDK from the web: http://java.sun.com/j2ee/download.html
Product providers use the J2EE SDK to determine what their implementations must do under a given set of application conditions, and to run the J2EE Compatibility Test Suite to test that their J2EE products fully comply with the specification. Application component developers run their J2EE applications on the J2EE SDK to verify the applications are fully portable across all J2EE products and tools.
Web Server
The web server provides services to one or more web containers. For example, a web container typically relies on a web server to provide HTTP message handling. A J2EE implementation is not required to support a particular type of web server, which means the web server supported by different J2EE products can vary.
Page 17
SANTOSH M
Database Access
The relational database provides persistent storage for application data. A J2EE implementation is not required to support a particular type of database which means the database supported by different J2EE products can vary. See the Release Notes included with the J2EE SDK download for a list of the databases currently supported by the reference implementation.
J2EE APIs
The Java 2 Platform, Standard Edition (J2SETM) SDK is required to run the J2EE SDK, and provides core APIs for writing J2EE components, core development tools, and the Java virtual machine. The J2EE SDK provides the following APIs to be used in J2EE applications.
JDBCTM 2.0 API

The JDBC API lets you invoke SQL commands from Java programing language methods. The only time you would use the JDBC API in an enterprise bean is when you are overriding the default container-managed persistence. With container-managed persistence, database access operations are handled by the container and your enterprise bean implementation contains no JDBC code or SQL commands. You could also use the JDBC API from a servlet or JSP page to access the database directly without going through an enterprise bean. The JDBC API has two parts: an application-level interface used by the application components to access a database, and a service provider interface to attach a JDBC driver to the J2EE platform.
Java Servlet Technology 2.3

Java Servlet technology lets you define HTTP-specific servlet classes. A servlet class extends the capabilities of servers that host applications accessed by way of a request-response programming model. Although servlets can respond to any type of request, they are commonly used to extend the applications hosted by web servers.
Page 18
SANTOSH M
JavaServer Pages (JSP) Technology 1.2

JSP pages technology lets you put snippets of servlet code directly into a text-based document. A JSP page is a textbased document that contains two types of text: static template data which can be expressed in any text-based format such as HTML, WML, and XML, and JSP elements that determine how the page constructs dynamic content.
Java Message Service (JMS) 1.0

The JMS API is a messaging standard that allows J2EE application components to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous.
Java Transaction API (JTA) 1.0

The JTA API provides a standard demarcation interface for demarcating transactions. The J2EE architecture provides a default auto commit to handle transaction commits and roll backs. An auto commit means any other applications viewing data will see the updated data after each database read or write operation. However, if your application performs two separate database access operations that depend on each other, you will want to use the JTA API to demarcate where the entire transaction including both operations begins, rolls back, and commits.
JavaMailTM Technology 1.2

Many Internet applications need to send email notifications so the J2EE platform includes the JavaMail API with a JavaMail service provider that application components can use to send Internet mail. The JavaMail API has two parts: an application-level interface used by the application components to send mail, and a service provider interface.
JavaBeans Activation Framework 1.0

The JavaBeans Activation Framework is included because JavaMail uses it. It provides standard services to determine the type of an arbitrary piece of data, encapsulate access to it, discover the operations available
Page 19
SANTOSH M on it, and create the appropriate JavaBean component to perform those operations.
Java API for XML (JAXP) 1.1

XML is a language for representing and describing textbased data so the data can be read and handled by any program or tool that uses XML APIs. Programs and tools can generate XML files that other programs and tools can read and handle. For example, a company might use XML to produce reports so different parties who receive the reports can handle the data in a way that best suits their needs. One party might put the XML data through a program to translate the XML to HTML so it can post the reports to the web, another party might put the XML data through a tool to create a marketing presentation. Same data, different needs, and an array of platform-independent programs and tools to use the same data in any number of different ways. These highly flexible and cost-effective capabilities are available by using standard XML tags, Document Type Definitions (DTDs) also known as XML schemas, and the Java API for XML.
J2EE Connector API 1.0

The Connector API is used by J2EE tools vendors and system integrators create resource adapters that support access to enterprise information systems that can be plugged into any J2EE product. A resource adapter is a software component that allows J2EE application components to access and interact with the underlying resource manager. Because a resource adapter is specific to its resource manager, there is typically a different resource adapter for each type of database or EIS.
Java Authentication and Authorization Service (JAAS) 1.0

The Java Authentication and Authorization Service (JAAS) provides a way for a J2EE application to authenticate and authorize a specific user or group of users to run it. JAAS is a Java programing language version of the standard Pluggable Authentication Module (PAM)
Page 20
SANTOSH M framework that extends the Java 2 platform security architecture to support user-based authorization.
Tools
The J2EE reference implementation provides an application deployment tool and an array of scripts for assembling, verifying, and deploying J2EE applications and managing your development and production environments. See J2EETM SDK Tools for a discussion of the tools.
Application Deployment Tool

The J2EE reference implementation provides an application deployment tool for assembling, verifying, and deploying J2EE applications. It comes in two versions: command-line and GUI. The GUI tool includes wizards for

Packaging, configuring, applications Packaging and configuring Packaging and configuring Packaging and configuring Packaging and configuring
and
deploying
J2EE
enterprise beans web components application clients resource adaptors
Page 21
SANTOSH M
J2EE Architecture
Introduction to Servlets:
Servlets provide a Java(TM)-based solution used to address the problems currently associated with doing serverside 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 serverside 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-
Page 22
SANTOSH M loadable, pluggable helper byte code objects on the server side that can be used to dynamically extend server-side functionality.
What is a Servlet?
Servlets are modules that extend
request/response-oriented servers, such as Java-enabled web servers. For example, a servlet might be responsible for taking data in an HTML order-entry form and applying the business logic used to update a company's orderdatabase.
Servlets are to servers what applets are to browsers. Unlike applets, however, servlets have no graphical user interface. Servlets can be embedded in many different servers because the servlet API, which you use to write servlets, assumes nothing about the server's environment or protocol. Servlets have become most widely used within HTTP servers; many web servers support the Servlet API.
Page 23
SANTOSH M
The Life cycle of a Servlet:

Three methods are central to the life cycle of a servlet. These are: Init ( ) Service ( ) Destroy ( ) First, assume that a user enters a Uniform
Resource locator (URL) to a Web browser. The browser then generates an HTTP request for this URL. This request is then sent to the appropriate server. Second, the Web server receives this HTTP request. The server maps this request to a particular servlet. The servlet is dynamically retrieved and loaded into the address space of the server. Third, the server invokes the init ( ) method of the servlet. This method is invoked only when the servlet is first loaded into memory. It is possible to pass initialization parameters to the servlet so it may configure itself. Fourth, the server invokes the service ( ) method of the servlet. This method is called to process the HTTP request. you will see that it is possible for the servlet to read data that has been provided in the HTTP request. It may also formulate an HTTP response for the client. The server remains in the servers address space and is available to process any other HTTP requests received from clients. The service ( ) method is called for each HTTP request. Finally, the server may decide to unload the servlet from its memory. The server calls the destroy ( ) method to relinquish
Page 24
SANTOSH M any resources such as file handles then garbage collected. at are allocated for the
servlet. The memory allocated for the servlet and its objects can
The Servlet API:

Two packages contain the classes and interfaces that are required to build Servlets. These are javax.servlet javax.servlet.http They constitute the Servlet API. These are
standard extensions. Therefore, they are not included in the Java Software Development Kit.
Javax.servlet Package:
The javax.servlet package contains a number of interfaces and classes. The most significant of these is Servlet .All Servlets must implements this interfaces or extend a class that implements the interface. The ServletRequest and ServletResponse interfaces are also very important. Some of the interfaces provided by this package are: Servlet, SevletConfig, ServletContext,, ServletRequest,ServletResponse, Some of the classes provided by this package are:GenericServlet,ServletInputStream,ServletOutputStream, ServletException, UnavailableException
Page 25
SANTOSH M
Introduction to JDBC:
Databases constitute the primary data resource in enterprise application. The JDBC API facilitates access to relational data from Java. This connectivity and data access API provides cross-vendor database across relational
from different vendors. A database vendor such as oracle, Sybase typically provides a set of proprietary API for accessing the data managed by the database server. Client applications written in C/C++ can make use of these API calls for database access directly. The JDBC provides specific native a Java for language database alternative access, the to API vendorof these
API.JDBC API does not eliminate the access to APIs implementation
JDBC API still make these native calls for data access. The JDBC driver is middle layer that translates the JDBC calls to the vendor specific APIs. The JVM uses the JDBC driver to translate the generalized JDBC calls into vendor specific database calls. The following are four different approaches for connection from client application to a database server via a database driver.
Type1 JDBC-ODBC Bridge:

Open Data Base Connectivity(ODBC) is Microsofts API for database driver and is popular on windows platform. The first category of JDBC drivers provides a bridge between the JDBC API and the ODBC API. This bridge translates JDBC calls to corresponding ODBC calls.
Page 26
SANTOSH M
Type2 Part Java, Part Native Driver:

Type2 driver uses the mixture of Java implementation and vendor specific API for data access. This is much faster than Type-1.when a database call is made using JDBC, the driver translates the request into vendor specific API calls. In this client must have some binary code to be loaded into machine.
Type3 Intermediate Database Access Server:

Type3 servers are based on intermediate database server. In this the Java Client application sends a JDBC call through JDBC driver to intermediate server Which handles request using another driver to complete the request. This type of solution makes it possible to implement a pure java client.
Type4 Pure Java Driver:

This is pure Java driver that communicates directly with data source. This simplifies and most efficient method of accessing database, both in performance and development time. The JDBC Core API is specified in the
java.sql.package. JDBC defines eight interfaces that must be implemented by a driver in order to be JDBC complaint. java.sql.Driver java.sql.CallableStatement java.sql.Connection java.sql.ResultSet
Page 27
SANTOSH M java.sql.Statement java.sql.DatabaseMetadata java.sql.PreparedStatement java.sql.ResultSetMetaData
About Html:
HTML (hyper text markup language) is a language used to create hyper text documents that have hyper links embedded in them . It consists of tags embedded in the text of a document with HTML. We can build web pages or web document s. it is basically a formatting language and not a programming language. The browser reading the document interprets mark up tags to help format the document for subsequent display to a reader. HTML is a language for describing structured documents. HTML is a platform independent. WWW (World Wide Web) pages are written using HTML. HTML tags control in part the representation of the WWW page when view with web browser. The browser interprets HTML tags in the web document and displays it. Different browsers show data differently. Examples of browsers used to be web pages include: Netscape Internet Explorer
Page 28
SANTOSH M
Java Server Pages (JSP): What is a JSP Page?

A JSP page is a text-based document that describes how to process a request to create a response. The description intermixes template data with some dynamic actions and leverages on the Java 2 Platform. The features in the JSP technology support a number of different paradigms for authoring of dynamic content; the document Using the JavaServer Pages(tm) Technology expands on this topic.
Tomcat Server:
Apache Tomcat is the Servlets container that is used in the official Reference Implementation for the Java Servlets and Java Server Pages technologies. Apache Tomcat is developed in an open and participatory environment and released under the Apache Software License. Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.
3.2 Why JAVA?

Coding standards for Java are important because they lead to greater consistency within your code and the code of your teammates. Greater consistency leads to code that is easier to understand, which in turn means it is easier to develop and to maintain. This reduces the overall cost of the applications
Page 29
SANTOSH M that you create. You have to remember that your Java code will exist for a long time, long after you have moved on to other projects. An important goal during development is to ensure that you can transition your work to another developer, or to another team of developers, so that they can continue to maintain and enhance your work without having to invest an unreasonable effort to understand your code. Code that is difficult to understand runs the risk of being scrapped and rewritten I wouldnt be proud of the fact that my code needed to be rewritten, would you? If everyone is doing their own thing then it makes it very difficult to share code between developers, raising the cost of development and maintenance. Inexperienced developers, and cowboys who do not know any better, will often fight having to follow standards. They claim they can code faster if they do it their own way. Pure hogwash. They might be able to get code out the door faster, but I doubt it. Cowboy programmers get hung up during testing when several difficultto-find bugs crop up, and when their code needs to be enhanced it often leads to a major rewrite by them because theyre the only ones who understand their code. Is this the way that you want to operate? I certainly do not.
3.3 BACK END: SQL SERVER 2000 SQL Server Architecture Overview
Microsoft SQL Server 2000 is a set of components that work together to meet the data storage and analysis needs of the largest Web sites and enterprise data processing systems. The topics in SQL Server Architecture describe how the various components work together to manage data effectively.
Page 30
SANTOSH M
Structured Query Language

To work with data in a database, you have to use a set of commands and statements (language) defined by the DBMS software. Several different languages can be used with relational databases; the most common is SQL. The American National Standards Institute (ANSI) and the International Standards Organization (ISO) define software standards, including standards for the SQL language. SQL Server 2000 supports the Entry Level of SQL-92, the SQL standard published by ANSI and ISO in 1992. The dialect of SQL supported by Microsoft SQL Server is called Transact-SQL (T-SQL). T-SQL is the primary language used by Microsoft SQL Server applications.
Features of SQL Server 2000

Internet Integration.
The SQL Server 2000 database engine includes integrated XML support. It also has the scalability, availability, and security features required to operate as the data storage component of the largest Web sites. The SQL Server 2000 programming model is integrated with the Windows DNA architecture for developing Web applications, and SQL Server 2000 supports features such as English Query and the Microsoft Search Service to incorporate user-friendly queries and powerful search capabilities in Web applications.
Scalability and Availability.
The same database engine can be used across platforms ranging from laptop computers running Microsoft Windows 98 through large, multiprocessor servers running Microsoft Windows 2000 Data Center Edition. SQL Server 2000 Enterprise Edition supports features such as federated servers, indexed views, and large memory support that allow it to scale to the performance levels required by the largest Web sites.
Enterprise-Level Database Features.
The SQL Server 2000 relational database engine supports the features required to support demanding data processing environments. The database engine protects data integrity while minimizing the overhead of managing thousands of users
Page 31
SANTOSH M concurrently modifying the database. SQL Server 2000 distributed queries allow you to reference data from multiple sources as if it were a part of a SQL Server 2000 database, while at the same time, the distributed transaction support protects the integrity of any updates of the distributed data. Replication allows you to also maintain multiple copies of data, while ensuring that the separate copies remain synchronized. You can replicate a set of data to multiple, mobile, disconnected users, have them work autonomously, and then merge their modifications back to the publisher.
Ease of installation, deployment, and use.
SQL Server 2000 includes a set of administrative and development tools that improve upon the process of installing, deploying, managing, and using SQL Server across several sites. SQL Server 2000 also supports a standards-based programming model integrated with the Windows DNA, making the use of SQL Server databases and data warehouses a seamless part of building powerful and scalable systems. These features allow you to rapidly deliver SQL Server applications that customers can implement with a minimum of installation and administrative overhead.
Data warehousing.
SQL Server 2000 includes tools for extracting and analyzing summary data for online analytical processing. SQL Server also includes tools for visually designing databases and analyzing data using English-based questions
SQL Server Enterprise Manager

You can set the interval at which SQL Server Enterprise Manager checks the status of SQL Server, SQL Server Agent, the Full-Text Search feature (which runs as the Microsoft Search service), SQL Mail, Replication Monitor, and Microsoft Distributed Transaction Coordinator (MS DTC) to determine whether they are running, paused, or stopped. The status of each service is displayed through its icon in the console tree of Microsoft Management Console (MMC).
SQL Server Service Manager

You can set the interval at which SQL Server Service Manager checks the status of SQL Server, SQL Server Agent, the Full-Text
Page 32
SANTOSH M Search feature, and MS DTC to determine whether they are running, paused, or stopped. View the status by clicking the SQL Server Service Manager icon in the Windows taskbar.
Importing and Exporting Data

Importing data is the process of retrieving data from sources external to Microsoft SQL Server (for example, an ASCII text file) and inserting it into SQL Server tables. Exporting data is the process of extracting data from an instance of SQL Server into some user-specified format (for example, copying the contents of a SQL Server table to a Microsoft Access database). Importing data from an external data source into an instance of SQL Server is likely to be the first step you perform after setting up your database. After data has been imported into your SQL Server database, you can start to work with the database. Importing data into an instance of SQL Server can be a one-time occurrence (for example, migrating data from another database system to an instance of SQL Server). After the initial migration is complete, the SQL Server database is used directly for all data-related tasks, rather than the original system. No further data imports are required. Importing data can also be an ongoing task. For example, a new SQL Server database is created for executive reporting purposes, but the data resides in legacy systems updated from a large number of business applications. In this case, you can copy new or updated data from the legacy system to an instance of SQL Server on a daily or weekly basis. Usually, exporting data is a less frequent occurrence. SQL Server provides tools and features that allow applications, such as Access or Microsoft Excel, to connect and manipulate data directly, rather than having to copy all the data from an instance of SQL Server to the tool before manipulating it. However, data may need to be exported from an instance of SQL Server regularly. In this case, the data can be exported to a text file and then read by the application. Alternatively, you can copy data on an ad hoc basis. For example, you can extract data from an instance of SQL Server into an Excel spreadsheet running on a portable computer and take the computer on a business trip. SQL Server provides tools for importing and exporting data to and from data sources, including text files, ODBC data sources
Page 33
SANTOSH M (such as Oracle databases), OLE DB data sources (such as other instances of SQL Server), ASCII text files, and Excel spreadsheets. Additionally, SQL Server replication allows data to be distributed across an enterprise, copying data between locations and synchronizing changes automatically between different copies of data.
Creating and Maintaining Databases Overview

A client/server database system comprises two components: Programs that provide an interface for client-based users to access data.
The database structure that manages and stores the data on the server.
For example, if you use Microsoft SQL Server 2000 to create a checking account application, you must set up a database structure to manage the account transaction data and an application that acts as the user interface to the database, allowing users to access checking account information. Creating a database to serve your business needs requires an understanding of how to design, create, and maintain each of these components to ensure that your database performs optimally.
Databases
A database in Microsoft SQL Server 2000 consists of a collection of tables that contain data and other objects, such as views, indexes, stored procedures, and triggers, defined to support activities performed with the data. The data stored in a database is usually related to a particular subject or process, such as inventory information for a manufacturing warehouse. SQL Server can support many databases. Each database can store either interrelated orunrelated data from other databases. For example, a server can have one database that stores personnel data and another that stores product-related data. Alternatively, one database can store current customer order data, and another related database can store historical customer orders used for yearly reporting.
Page 34
SANTOSH M Before you create a database, it is important to understand the parts of a database and how to design these parts to ensure that the database performs well after it is implemented. Important It is recommended that you do not create any user objects, such as tables, views, stored procedures, or triggers, in the master database. The master database contains the system tables that store the system information used by SQL Server, such as configuration option settings.
4.SYSTEM DEFINITION
4.1 Analysis Need of the system
Today the programs are developed in fast track and we need a help online. If we get struck in any of the coding, net is the best person to provide solutions. Searching for the code and prototype in net gives us plenty of code by which we will be dilemma. To provide this type of solutions by a normal programmer to a programmer we design this application. Where any person can act as programmer and any person can act as buyer.
Proposed System
Proposed system enables both coders and buyers interact each other. Cost of the project reduces to 50% to 90% less than if the project were done in there country. Small enterprises can login as a coder and they can get the projects from worl wide clients. Buyers can hire coders internationally.
Page 35
SANTOSH M Coders will work as freelance developer by that coder may be student / programmer / professor / etc. Coder can be recognized by their successful completion of projects.
Features of the proposed system:

The proposed web application serves the following range of ads. o Registration of Coders / programmers o Registration of Buyers. o Adding projects / individual codes for bidding. o Conduct online bidding. o Selecting coders through bidding o Payments for the completed work by buyers to coders.
Project Description:
By the click of Home option displays the brief description of project. Login enables Admin, Coders / programmers and Buyers to get logged in. This option is for only those who are already got registered. Guest option is for those who are new and would like to view more information about the application. Features option can be used to know the salient features of the application. By the click of Purpose option displays the main pupose of the application. Contact option displays the contact details of the apllication developer.
Page 36
SANTOSH M
MODULES:
The system has the following four modules Admin Coder / programmer Buyer Guest
Admin Module:
Admin is the supermost user of our application, who can create new programmers and buyers. If the programmer or buyers are not following the rules of website, Admin can block these users. And admin is also having the rights to unblock the programmers and buyers. Admin is the super user who can view anybodys transactions, admin can view sales information, purchase information,buyers information, programmers information and bid details. This module consists mainly of the following sub options: Add buyer Add programmer Block buyer or programmer Unblock buyer or programmer View
Buyer Module:
Buyer can view the snapshots and code samples and its ratings. If the buyer is interested to purchase those codings can bid for the same. For buyer we have provided the option purchasing of codes online. Buyer can transfer the amount using debit cards. Buyer can download the purchase code immediately. This module mainly consists of the following sub options. o o o o o o View languages View sample codes View code details Bid for code and project Request for purchase Download
Page 37
SANTOSH M
Programmer Module:
Programmer will design the projects and codes and samples of those codes and projects will be launched to the website. Programmer can decide whether to sale the code or not. Programmer is a decision maker for bid accept or reject. Programmer can upload the codes into the website for the download of buyer. Programmer can view the ratings given to his/her codes or projects on the basis of its working. This module has the following important sub options. o o o o o Languages Code details and work Add new projects View bid details View rating
Guest module:
Guest is the visitor of website. He/she can view the salient features of the site. Guest can view the different code samples from different programmers, there ratings. If the guest is satisfied he can send a request to the website admin for registration as a buyer or programmer as mentioned by the guest. This module has the following options. View sample codes and their ratings View old buyers and old programmers iformation Request for registration as a buyer or programmer
o o o
For all the users we have provided some common features nlike online feedback, mail and online chatting. These options can be used by admin, programmers and buyers to negotiate with each other. From any point or moment user can comeout to the login page by just clicking the logout. And the users can even directly come to the website homepage by clicking home.
Page 38
SANTOSH M
4.2Data Flow Diagrams (DFD):

Data Flow Diagram is central to most structured design. All data flow diagrams are graphical. It can be used to show current physical activities and for the logical model of the system. The objective of his method is the derivation of the program structure, which supports architectural design. It is a network that describes the flow of data and process that transform the data throughout a system. DFDs specify data sources, data links and data stores
transformation to be performed on the data and the flow of data between sources. The DFD is also know as a data flow graph or a bubble chart. DFDs are directed graphs in which nodes specify processing activities and arcs specify data items transformed between processing nodes. It may be partition into levels that represent increasing information flow and functional details. At level 0 DFD, fundamental system models are representing the entire software elements as a single bubble with input and output data indicated by incoming and outgoing arrows into levels that represents increasing information flow and functional details. The Symbols used in DFD such as arrow identifies the data flow in motion. It is a pipeline through which information is flown like the rectangle in the flowchart. A circle stands for process that converts data into information. An open ended box represents a data store, data at rest or a temporary repository of data. A square defines a source or destination of system data
Page 39
SANTOSH M
DFD FOR LOGIN PROCESS
Login Admin User Login Login process invalid Relogin
Buyer
Programmer
DFD for BRAIN BENCH
ADMIN
Adding, Blocking, Unblocking Programmers & Buyers View, Bid, Purchase, Download of codes & projects.
ADMIN
BUYER BRAIN BENCH
BUYER
PROGRAMMER
Adding sample codes, Projects, Selling, Uploading
PROGRAMMER
Page 40
SANTOSH M
DFD for Administrator Module
Buyerinfo
Progmrinfo
Blockinfo
Add Buyer
Add Programmer
Block Buyers & Programmers
Unblock Buyers & Programmers
ADMIN
Page 41
SANTOSH M
DFD for Buyer Module
Langs
samplecode
Bidforcode & Bidforprjt
purchase & purchaseprjt
upload codedetails
Bid for code & project View Sample codes
Request for purchase Download
View Languages
View code details
BUYER
Page 42
SANTOSH M
DFD for Programmer Module
Langs Codedetails
samplecode projectsinfo
Biddetails
upload
rating
Code details Languages Sample codes
Add projects View bid details
View rating Upload
PROGRAMMER
Page 43
SANTOSH M
4.3SCREEN SHOTHS
HOMEPAGE
SNAPSHOTS
Login page
ADMIN HOME PAGE
ADD BUYER
BLOCK PROGRAMMER UNBLOCKING
VIEW BUYER INFORMATION
Page 44
SANTOSH M
CURRENCY CONVERSION
FEEDBACK REPLY MAIL (INBOX)
CHANGE PASSWORD
ADDING NEW LANGUAGES
VIEW LANGUAGES
Page 45
SANTOSH M
VIEW BID DETAILS
VIEW SOLD INFORMATION
Page 46
SANTOSH M
UPLOADING A FILE
MAIL COMPOSE
Page 47
SANTOSH M
BID FOR CODE
REQUEST FOR PURCHASE
Page 48
SANTOSH M
FILE DOWNLOAD
REQUEST FOR REGISTRATION
Page 49
SANTOSH M
PROFILE UPDATION
Page 50
SANTOSH M
NEW USER
Page 51
SANTOSH M
Page 52
SANTOSH M
Page 53
SANTOSH M
Page 54
SANTOSH M
D a t a b a s e D e s i gn : A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. The
Page 55
SANTOSH M general objective of database design is to make the data access easy, inexpensive and flexible to the user. Table Name :Erp_login
Field Name User Name Password Emptype Empno Skill
Data Type VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2
Field Width 50 20 50 10 50
Table Name : Employee
Field Name Empno Empid PWD Fname Midname Lname DOB DOJ Deptno Jobtitle
Data Type NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2
Field Width 10 10 15 20 20 20 20 20 10 25
Page 56
SANTOSH M Basic Addr City State Country PCODE Gender Marit_st Email_id Phone Company Accno VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 NUMBER 15 50 20 20 20 20 8 10 20 20 15 10
Table name : Department
Field Name Data Type Deptno Dname Loc NUMBER VARCHAR2 VARCHAR2
Field Width 10 14 13
Table Name : Leaves
Field Name Data Type
Field
Page 57
SANTOSH M Width SL CL ML LOP NUMBER NUMBER NUMBER NUMBER 10 10 10 10
Table Name : Daily
Field Name Data Type Day Empno DATE NUMBER
Field Width
10
Table Name : Generating Reports
Field Name Name Empno Month_year Days_present SL CL ML
Data Type VARCHAR2 NUMBER VARCHAR2 NUMBER NUMBER NUMBER NUMBER
Field Width 50 20 50 10 10 10 10
Page 58
SANTOSH M LOP NUMBER 10
Table Name : Work_Days
Field Name Data Type Month_year Wdays Hols VARCHAR2 NUMBER NUMBER
Table Name : EmpLeaves
Field Name Data Type Empno Year SL CL ML LOP NUMBER VARCHAR2 NUMBER NUMBER NUMBER NUMBER
Field Width 20 10 10 10 10 10
Page 59
SANTOSH M
Table Name : Emp_Erp
Field Name Empno Fname Mname Lname DOB DOJ Chno Cstreet Ccity Ccountry Paddress Gender Marital Spouse Father Deptno JOB Basic Email Phone
Data Type NUMBER VARCHAR2 VARCHAR2 VARCHAR2 DATE DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 NUMBER VARCHAR2 NUMBER
Field Width 10 50 20 20
50 50 50 50 300 8 20 20 30 20 20 20 50 20
Page 60
SANTOSH M
Table Name : Posting Resumes
Field Name Fname Mname Lname DOB Gender Add1 Add2 Add3 City PIN Country State Email Phone Qly1 Splz1 Qadd1 Prcnt1 Qly2 Splz2 Qadd2 Prcnt2 Tech1 Prof1
Data Type VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2
8 50 50 50 50 15 20 20 20 20 30 20 20 50 30 20 20 50 50 30
Page 61
SANTOSH M Exp1 Tech2 Prof2 Exp2 Tech3 Prof3 Exp3 ResumeId View1 DOS VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 DATE 20 20 50 50 20 50 50 10 20
Page 62
SANTOSH M
6.Implementation Conversion: Conversion means changing from one system to another. The objective is to put the tested system into operation. It involves proper installation of the software package developed and training the operating staff. The software has been installed and found to be functioning properly. The users how to be trained to handle the system effectively. Sample data provide to the operating stuff and were asked to operate on the system. The operating stuffs now have a clear out look of the software and are ready for practical implementation of the package. Post Implementation Review: A post implantation review is an evaluation of system in terms of the extent to which the system accomplishes the started objectives. This starts after the system is implemented and conversation is complete.
Page 63
SANTOSH M 7. Testing And Results: Testing is the major quality measure employed during the software engineering development. Its basic function is to detect error in the software. Testing is necessary for the proper functioning of the system. Testing has to be done at four levels
Unit Testing Unit testing focuses verification effort on the smallest unit of the software ,design the module. Here ,using the detail design as a guide ,important control paths are tested to uncover errors within the boundary of the module. Unit testing is always whitebox oriented, and the step can be conducted in parallel for multiple modules. Integration Testing Integration testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors , associated with interfacing .The objective is to take the unit tested modules and build program structure that has been directed by the design. .
Validation Testing
Page 64
SANTOSH M Validation testing demonstrates the traces the requirements of the software .This can be achieved through a series of black box tests.
System Testing System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system . Although each test has a different purpose, all works should verify that all system elements have been properly integrated and perform allocated functions. The various tests include recovery testing , stress testing , perform testing.
RESULTS
Tes C.N o.
Input
Expected Behaviour
Observ ed behavi our -do-
Status P= Passed F= Failed P
1 2
Typed the http://localhost: 7001/ERPHRMS/ welcome.htm Sign in link is clicked
The application should be launched and show the initial Welcome page. This displays the login page
-do-
The login and Password for the
Displays the required employee page
-do-
Page 65
SANTOSH M employee is bean entered The login and Display password for the authentication hr is entered failure page wrongly
-do-
5 6
Clicked on the generate reports link Clicked on view resumes by date link Sign in for administrator module Clicked on workdays link
Displays the reports which are present for the hr Displays the from and to dates Gives the appropriate admin information of the application Gives the workdays setup fro the company
-do-
-do-
-do-
-do-
Clicked the submit button of the update employee Clicks on the update button of the create department module
Stores the data in the database
-do-
10
Stores the data in the database
-do-
Page 66
SANTOSH M
7.CONCLUSION
The fundamental problem in managing and maintaining the work by the administrator is hence overcome. Prior to this it was a bit cumbersome for maintaining the library and also keeping track of the users who were using it. But by developing this web-based application the administrator can enjoy the task, doing it ease and also by saving the valuable time. The amount of time consumption is reduced and also the manual calculations are omitted, the reports and bills can be obtained regularly and also whenever on demand by the user. The effective utilization of the work, by proper sharing it and by providing the accurate results. The storage facility will ease the job of the operator. Thus the system developed will be helpful to the administrator by easing his/her task.
Page 67
SANTOSH M
Glossary API CGI DHTML GUI HTML HTTP J2EE JDBC JSP SQL URL XML ------------------Application Programming Interface. ---Common Gateway Interface.
Dynamic HyperText Markup Language. ---Graphical User Interface .
HyperText Markup Language. HyperText Transfer Protocol. Java 2 Enterprise Edition. Java DataBase Connectivity.
---- Java Server Pages. ---------Structured Query Language. Uniform Resource Locator. Extensible Markup Language.
Page 68
SANTOSH M 9. Bibilography
1. Deitel ,Deitel and Nieto ,Internet and World Wide Web how to program. 2. Ian Somerville, Principles of Software Engineering ,4 Edition . 3. Roger S. Pressman ,Software Engineering A Practitioners Approach . 4. IEEE, IEEE Software Standards , IEEE Press ,1989 . 5. Patrick Naughton and Herbert Schildt , Complete Reference Java 2 , 3 Edition ,Tata McGraw Hill ,1999. 6. Er. V.K.Jain , Programming Java Server Pages & Servlets.
Page 69

Report Samplesssssss

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Report Samplesssssss

Caricato da

Copyright:

Formati disponibili

SANTOSH M

5 : IMPLEMETATION 6 : TESTING & RESULTS 7 : CONCLUSION 8 : FUTURE ENHANCEMENT 9: BIBILOGAPHY

National College / BCA 6 Sem

1. INTRODUCTION 1.1 Introduction of The Project:

1.6 Project Function Overview

2. HARDWARE REQUIREMENTS 2.1

National College / BCA 6 Sem

Pentium 4 or above 1GB 20GB 1.44 MB 32 HZ 14 inch Monitor 108 Standard

Software for development and deployment:

National College / BCA 6 Sem

3.1 Front End : J2EE (Servlets,JSP,HTML)

National College / BCA 6 Sem

Figure 1 Multitiered Applications

National College / BCA 6 Sem

J2EE Application Components:

National College / BCA 6 Sem

JavaBeansTM Component Architecture:

National College / BCA 6 Sem

J2EE Server Communications:

Figure 2 Thin Client and J2EE Application

National College / BCA 6 Sem

Figure 3 Web Tier and J2EE Application

National College / BCA 6 Sem

Figure 4 Business and EIS Tiers

Enterprise Information System Tier:

National College / BCA 6 Sem

National College / BCA 6 Sem

National College / BCA 6 Sem

Figure 5 J2EE Server and Containers

National College / BCA 6 Sem

National College / BCA 6 Sem

J2EE Product Provider:

Application Component Provider

Enterprise Bean Creation

Web Component Creation

National College / BCA 6 Sem

J2EE Application Client Creation

Application Deployer and Administrator

National College / BCA 6 Sem

Reference Implementation Software

National College / BCA 6 Sem

JDBCTM 2.0 API

Java Servlet Technology 2.3

National College / BCA 6 Sem

JavaServer Pages (JSP) Technology 1.2

Java Message Service (JMS) 1.0

Java Transaction API (JTA) 1.0

JavaMailTM Technology 1.2

JavaBeans Activation Framework 1.0

National College / BCA 6 Sem

Java API for XML (JAXP) 1.1

J2EE Connector API 1.0

Java Authentication and Authorization Service (JAAS) 1.0

National College / BCA 6 Sem

Application Deployment Tool

enterprise beans web components application clients resource adaptors

National College / BCA 6 Sem

National College / BCA 6 Sem

National College / BCA 6 Sem

The Life cycle of a Servlet:

National College / BCA 6 Sem

The Servlet API:

National College / BCA 6 Sem

API.JDBC API does not eliminate the access to APIs implementation