Objective

This project is aimed at developing an online data entry system that will enable
image assisted data entry for the shipment for the courier logistics. The scanned image if
available will be displayed on the left side of the screen when the Airway Bill Number
(AWB) is entered on the right side. This is a POC (Proof Of Concept) assignment, which
can be showcased to any organization where chunk of the work is paper-based.

A shipment in the application represents one lot of an ordered item that has a
unique event and cost history. Shipments can be created when the product departs from
the factory, when the product arrives at the consolidator or freight forwarder, or when the
product is actually received by the consolidator or freight forwarder. The physical
measure, packing list, and commercial invoice should be available at this time.

2. SYSTEM ANALYSIS

System design is a solution to the creation of a new system. It provides the

understanding and procedural details necessary for implementing the system. The
emphasis is on translating the performance requirements into design specification. Design
goes through logical and physical stages of the development.
Logical design, reviews the present physical stages, makes edit security and
control output specifications. The physical design maps out the physical system, plans the
system implementation, devices a test and implementation plan and specifies any new
hardware and software
2.1 EXISTING SYSTEM
Today one cannot afford to rely on the fallible human beings of be really wants to
stand against today’s merciless competition where not to wise saying “to err is human”
no longer valid, it’s outdated to rationalize your mistake. So, to keep pace with time, to
bring about the best result without malfunctioning and greater efficiency so to replace the
unending heaps of flies with a much sophisticated hard disk of the computer. One has to
use the data management software.
Software has been an ascent in atomization various organizations. Many software
products working are now in markets, which have helped in making the organizations
work easier and efficiently.

Data management initially had to maintain a lot of ledgers and a lot of paper work
has to be done but now software product on this organization has made their work faster
and easier. Now only this software has to be loaded on the computer and work can be
done. This prevents a lot of time and money.

The work becomes fully automated and any information regarding the
organization can be obtained by clicking the button. Moreover, now it’s an age of
computers of and automating such an organization gives the better look.
2.1.1 Drawbacks of the Existing System:
► Manual Work
► Packet Tracking Problem
► Slow Service
► Pickup request facility
► Packet lost rate high
► Branch Location problem
► Report Problem
► It take long time to work
► Limited Services
2.2 Proposed System
In shipment data entry there is no chance to occur problem.Beacause every thing
is going on by online. There is some facilities available. We can be known about detail of
products by online immediately when we need.
Features of Proposed System:
We calculate everything by online.
Report is ready within second
Transaction going immediately
Saving time while process going on
2.3 FEASIBILITY STUDY
The feasibility analysis is designed to determine whether or not, given the project
environment, a project will be successful (in virtually any interpretation of that word). A
feasibility analysis may be conducted for a project with an emphasis on financial
viability, environmental integrity, cultural acceptability, or political practicability. It is a
determination as to the likelihood of success and a description of how that determination
was achieved.

2.3.1 Economic Feasibility

Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system. More commonly known as cost/benefit analysis, the
procedure is to determine the benefits and savings that are expected from a candidate
system and compare them with costs. If benefits outweigh costs, then the decision is
made to design and implement the system. An entrepreneur must accurately weigh the
cost versus benefits before taking an action. Time Based: Contrast to the manual system
management can generate any report just by single click.

Cost Based: No special investment is needed to manage the tool. No specific

training is required for employees to use the tool. Investment requires only once at the
time of installation. The software used in this project is freeware so the cost of
developing the tool is minimal

2.3.2 Operational Feasibility

Is a measure of how well a proposed system solves the problems, and takes
advantages of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development.

2.3.3 Technical Feasibility

The assessment is based on an outline design of system requirements in terms of Input,

Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of
volumes of data, trends, frequency of updating, etc. in order to estimate whether the new
system will perform adequately or not this means that feasibility is the study of the based
in outline.

3. System Specification

3.1 Hardware Requirements

Machine : IBM Compatible machine (pc)

Processor : Pentium IV
Clock Speed : 2.5 GHz (or) more
Chipset : Intel 915G (AGP & Sounds)
RAM : 1GB
Hard Disk : 40GB
Monitor : SVGA COLOR
Keyboard : 104 Keys
Mouse : ScrollMouse-3Buttons

3.2 So ftware Requirements

Operating System : Windows XP Professional

Language : Java, DB2
Environment : RAD, Database

4. Software Description
4.1 Front End

IBM Rational Application Developer for WebSphere Software v7.5 is an

integrated development environment and platform for building Java Platform
Standard Edition (Java SE) and Java Platform Enterprise Edition (Java EE)
applications with a focus on applications to be deployed to IBM WebSphere
Application Server and IBM WebSphere Portal.
This chapter contains an introduction to the concepts, packaging, and features of
IBM Rational Application Developer v7.5 product

The Rational product suite helps businesses and organizations manage the
entire software development process. Software modelers, architects, developers,
and testers can use the same team-unifying Rational Software Delivery Platform
tooling to be more efficient in exchanging assets, following common processes,
managing change and requirements, maintaining status, and improving quality.
IBM Rational Software Delivery Platform.
The IBM Rational Software Delivery Platform offers an array of products,
services, and best practices. It is an open, modular, and proven solution that
spans the entire software and systems delivery life cycle. Its products are
comprised in five life cycle categories. Figure 1-1 shows each of the five life cycle
categories with a selection of the embedded Rational tooling.
The Rational product suite helps businesses and organizations manage the
entire software development process. Software modelers, architects, developers,
and testers can use the same team-unifying Rational Software Delivery Platform
tooling to be more efficient in exchanging assets, following common processes,
managing change and requirements, maintaining status, and improving quality.
IBM Rational Software Delivery Platform

The IBM Rational Software Delivery Platform offers an array of products,

services, and best practices. It is an open, modular, and proven solution that
spans the entire software and systems delivery life cycle. Its products are
comprised in five life cycle categories. Figure 1-1 shows each of the five life cycle
categories with a selection of the embedded Rational tooling.
to manage their requirements, write good use cases, improve traceability,
strengthen collaboration, reduce project risks, and increase quality.
Rational ClearQuest®
ClearQuest is a software change management tooling. It provides defect, task
and change request tracking, process automation, reporting and lifecycle
traceability for better visibility and control of the software development
lifecycle.
Rational Clear Case
ClearCase is a complete software configuration management tooling. It
provides a sophisticated version control, workspace management, parallel
development support and build auditing to improve productivity.
WebSphere Business Modeler
The WebSphere Business Modeler belongs to the WebSphere brand, but is
an important product of the Rational Software Delivery Platform. WebSphere
Business Modeler targets the business analyst who models business
processes. WebSphere Business Modeler can be used to generate Business
Process Execution Language (BPEL) definitions to be imported into
WebSphere Integration Developer to create applications for WebSphere
Process Server. BPEL from WebSphere Business Modeler provides a more
seamless move to implementation and eliminates the need to create paper
diagrams for the developer.
IBM WebSphere Application Server, Version 6.0 (included)
(optionally with Feature Pack for Web 2.0)
IBM WebSphere Application Server, Version 6.1 (included)
(optionally with Feature Packs for Web 2.0, EJB 3.0, and Web Services)
IBM WebSphere Application Server, Version 7.0 (included)
(optionally with Feature Pack for Web 2.0)
IBM WebSphere Portal, Version 6.0
IBM WebSphere Portal, Version 6.1 (included)
IBM HTTP Servers
Introduction
Draft Document for Review May 9, 2009 12:19 am 7672-intro-1-intro.fm
The following list of server adapters from the Web Tools Platform 3.0 based on
Eclipse technology are included in Application Developer V7.5:
• HTTP Preview
• Java EE Preview
• Apache Tomcat, Versions 3.2, 4.0, 4.1, 5.0, 5.5, and 6.0
• JBoss, Versions 3.2.3, 4.0, 4.2, and 5.0
• Object Web Java Open Application Server (JOnAS), Version 4
• Oracle® Containers for J2EE (OC4J) Standalone Server, V10.1.3 and
• 10.1.3.n
Supported databases
The following databases are compatible with the Application Developer v7.5
workbench:
• IBM Cloudscape®, Version 5.1
• Apache Derby, Versions 10.0, 10.1, and 10.2
• IBM DB2® Database for Linux, UNIX® and Windows,
Versions 7.2, 8.1, 8.2, 9.1, and 9.5
• IBM DB2 for i5/OS®, Versions 5R2, 5R3, and 5R4
• IBM DB2 for z/OS® Versions 7, 8, 9 (compatibility mode)
and Versons 8, 9 (new function mode)
• IBM Informix® Dynamic Server, Versions 9.2, 9.3, 9.4, 10.0, and 11.0
• HSQLDB, Version 1.8
• Microsoft SQL Server® Enterprise, Versions 7, 2000, and 2005
• MySQL™, Versions 4.0, 4.1, 5.0, and 5.1
• Oracle, Versions 8, 9, 10, and 11
• SAP MaxDB, Versions 7.6 and 7.7
• Sybase Adaptive Server Enterprise, Versions 12.x, and 15.0
• Generic JDBC™ Version 1.0
IBM Rational Deployment Toolkit for WebLogic Server provides a
seamless integration of BEA WebLogic Server, Versions 6.1, 7.0, and 8.1
within Application Developer. More information can be found here:
http://www.ibm.com/developerworks/rational/downloads/08/toolkit_weblogicv7
Note: Additional to the compatibility mode, the new function mode includes
the generated data model that has all the new catalog features of DB2 for
z/OS v8 and v9. Use the new function mode if you plan to work with the
generated data models available in IBM Rational Software Delivery
Platform products.
7672-intro-1-intro for Review May 9, 2009 12:19 am
12 Rational Application Developer V7.5 Programming Guide
Application Developer v7.5 eAssembly
IBM Rational Application Developer for WebSphere Software v7.5 is comprised of the
following two eAssemblies:
IBM Rational Application Developer for WebSphere V7.5 Multilingual
Multiplatform eAssembly (Core)
• Quick Start Guide
• License Activation Kit
• Application Developer v7.5 Core (6 parts)
• WebSphere Application Server Test Environment V6.0 (2 parts)
• WebSphere Application Server Test Environment V6.1 (4 parts)
• WebSphere Application Server Test Environment V7.0 (4 parts)
• Java Runtime Environment V1.6 SR2
• IBM Rational Application Developer for WebSphere V7.5 Multilingual
• Multiplatform eAssembly (Optional)
• Application Developer Build Utility V7.5 (5 parts)
• Rational Enterprise Deployment V7.5 for Windows / Linux (each 1 part)
• (includes License Server, Installation Manager and Packaging Utility)
• IBM WebSphere Portal V6.1 for Windows / Linux (each 9 parts)
• Crystal Reports Server XI Release 2 Windows / Linux (each 2 parts)
• IBM WebSphere Application Server for Developers V7.0 for Windows /
• Linux (each 1 part)
 • IBM CICS Transaction Gateway V7.1.0.2 Windows / Linux (each 1 part)
• Rational Debug Extension for IBM Rational Team Concert Server
• Rational Agent Controller V8.0

TOOLS
Application Developer v7.5 includes a wide array of tooling to simplify or
eliminate tedious and error-prone tasks, and provide the ability for Rapid Web
Development. We have listed the key areas of tooling included with Application
Developer:
• Java development tools (JDT)
• Relational database tools
• XML tools
• Web development tools
• Web 2.0 development tools
• Struts tools
• JSF development tools
• SDO development tools
• Enterprise Generation Language tools
• EJB tools
• JPA tools
• Portal tools
• Web services tools
• Team collaboration tools
• Debugging tools
• Performance profiling and analysis tools
• Server configuration tools
• Testing tools
• Crystal Report tools
• Deployment tools
 • Plug-in development tools
WebService
• Template based to provide prefilled attribute values based on the
annotation’s java context
• Indicates where annotation attribute values may be overridden
• Hovering on indicator provides the value from the deployment
descriptor file
– Annotation View
• Editing for annotations without definitions
• Annotation attributes of type annotations and array of annotations
supported
• Integrated JPA editing
• EJB deployment descriptor override indicators
• Integrated with EJB Visualizer
– Tracing and Logging
• Java Annotation Index

Compatibility with previous versions

Application Developer v7.5 includes a compatibility option to facilitate sharing
projects with Application Developer v7.0.x.
_ Projects can be shared with Application Developer v7.0.x developers through
a SCM (Rational Team Concert or CVS) or using project interchange zip files.
_ Metadata and project structure are not updated to the new Application
Developer format. A .compatibility file is added to projects and is used to
track the timestamps of resources.
_ Compatibility The compatibility feature can be accessed by selecting Windows →
Preferences → Backward Compatibility (Figure 1-3).
This chapter describes a number of example application development scenarios,
based on a simple banking application. Throughout these examples, we will
review the Java and supporting technologies, as well as highlight the tooling
provided by Application Developer v7.5, which can be used to facilitate
implementing the programming technologies.
This chapter is organized into the following sections:
• Desktop applications
• Static Web sites
• Dynamic Web applications
• Enterprise JavaBeans and Java Persistence API (JPA)
• Java EE Application Clients
• Web services

Desktop applications
By desktop applications we mean applications in which the application runs on
asingle machine and the user interacts directly with the application using a user
interface on the same machine.
When this idea is extended to include database access, some work might be
performed by another process, possibly on another machine. Although this
begins to move us into the client-server environment, the application is often only
using the database as a service—the user interface, business logic, and control
of flow are still contained within the desktop application. This contrasts with full
client-server applications in which these elements are clearly separated and
might be provided by different technologies running on different machines.
This type of application is the simplest type we will consider. Many of the
technologies and tools involved in developing desktop applications, such as the
Java editor and the XML tooling, are used widely throughout all aspects of
Application Developer.
The first scenario deals with a situation in which a bank requires an application
toallow workers in a bank call center to be able to view and update customeraccount
information. We will call this the Call Center Desktop.
Simple desktop applications
A starting point for the Call Center Desktop might be a simple stand-alone
application designed to run on desktop computers.Java Platform, Standard Edition (Java
SE) provides all the elements necessaryto develop such applications. It includes, among
other elements, a completeobject-oriented programming language specification, a wide
range of usefulclasses to speed development, and a runtime environment in which
programscan be executed.
Java is a general purpose, object-oriented language. The basic language syntax
is similar to C and C++, although there are significant differences. Java is a
higher-level language than C or C++, in that the developer is presented with a
more abstracted view of the underlying computer hardware and is not expected
to take direct control of issues such as memory management
Java IDL is the Java implementation of the Interface Definition Language
(IDL) for the Common Object Request Broker Architecture (CORBA), allowing
Java programs to access objects hosted on CORBA servers.
We focus on the Java DataBase Connectivity (JDBC) technology in this section.
JDBC.
Java SE 6.0 includes JDBC 4.0. The specification can be downloaded here:
http://jcp.org/aboutJava/communityprocess/final/jsr221/index.html
Although JDBC supports a wide range of data store types, it is most commonly
used for accessing relational databases using SQL. Classes and interfaces are
provided to simplify database programming, such as:
7672-intro-2-prog.fm Draft Document for Review May 9, 2009 12:19 am
30 Rational Application Developer V7.5 Programming Guide
• java.sql.DriverManager and javax.sql.DataSource can be used to obtain a
connection to a database system.
• java.sql.Connection represents the connection that an application has to a
database system.
• java.sql.Statement, PreparedStatement, and CallableStatement represent
executable statements that can be used to update or query the database.
• java.sql.ResultSet represents the values returned from a statement that has
queried the database.
• Various types such as java.sql.Date and java.sql.Blob are Java
• representations of SQL data types that do not have a directly equivalent
primitive type in Java.
 • Requirements for the development environment
• The development environment should provide access to all the facilities of
JDBC4.0. However, because JDBC 4.0 is an integral part of Java SE 6.0, this
requirement has already been covered in “Simple desktop applications” on
page 26. In addition, the development environment should provide:
• A way of viewing information about the structure of an external database.
• A mechanism for viewing sample contents of tables.
• Facilities for importing structural information from a database server so that it
can be used as part of the development process.
• Wizards and editors allowing databases, tables, columns, relationships, and
constraints to be created or modified.
• A feature to allow databases created or modified in this way to be exported to
an external database server.
• A wizard to help create and test SQL statements.
These features allow developers to develop test databases and work with
production databases as part of the overall development process. They can also
be used by database administrators to manage database systems, although they
might prefer to use dedicated tools provided by the vendor of their database
systems.
IBM Rational Application Developer v7.5 includes these features.
Graphical user interfaces
A further enhancement of the Call Center Desktop is to make the application
easier to use by providing a graphical user interface (GUI).
Abstract Window Toolkit (AWT)
The Abstract Window Toolkit (AWT) is the original GUI toolkit for Java. It has
been enhanced since it was originally introduced, but the basic structure remains
the same. The AWT includes the following items:
 A wide range of user interface components, represented by Java classes
such as [java.awt.] Frame, Button, Label, Menu, and TextArea.
 An event-handling model to deal with events such as button clicks, menu
choices, and mouse operations.
Classes to deal with graphics and image processing.
Layout manager classes to help with positioning components in a GUI.
Support for drag-and-drop functionality in GUI applications.
The AWT is implemented natively for each platform’s JVM. AWT interfaces
typically perform relatively quickly and have the same look-and-feel as the
operating system, but the range of GUI components that can be used is limited to
the lowest common denominator of operating system components, and the
look-and-feel cannot be changed.
Swing
Swing is a newer GUI component framework for Java. It provides Java
implementations of the components in the AWT and adds a number of more
sophisticated GUI components, such as tree views and list boxes. For the basic
components, Swing implementations have the same name as the AWT
component with a J prefix and a different package structure, for example,
java.awt.Button becomes javax.swing.JButton in Swing.
Swing GUIs do not normally perform as quickly as AWT GUIs, but have a richer
set of controls and have a pluggable look-and-feel.
Standard Widget Toolkit
The Standard Widget1 Toolkit (SWT) is the GUI toolkit provided as part of
theEclipse Project and used to build the Eclipse GUI itself. The SWT is written
entirely in Java and uses the Java Native Interface (JNI™) to pass the calls
1 In the context of windowing systems, a widget is a reusable interface component, such
as a menu,scroll bar, button, text box, or label.
• It has a rich, portable component model, like Swing.
• It has the same look-and-feel as the native operating system, like the AWT.
• GUIs built using the SWT perform well, like the AWT, because most of the
components simply pass through to operating system components.
A disadvantage of the SWT is that, unlike the AWT and Swing, it is not a
standard part of Java SE V6.0. Consequently, any application that uses the SWT
has to be installed along with the SWT class libraries. However, the SWT, like the
rest of the components that make up Eclipse, is open source and freely
distributable under the terms of the Common Public License.
Another popular technology based on SWT and Eclipse is the Eclipse Rich
ClientPlatform (RCP). The architecture of Eclipse allows that its components can be
used to create any kind of client applications.
Java components providing a GUI
There are two types of Java components that might provide a GUI:
• Stand-alone Java applications: Launched in their own process (JVM). This
category would include Java EE Application Clients, which we will come to
later.
• Java applets: Normally run in a JVM provided by a Web browser or a Web
browser plug-in.
An applet normally runs in a JVM with a very strict security model, by
default.The applet is not allowed to access the file system of the machine on which it
isrunning and can only make network connections back to the machine from which
it was originally loaded. Consequently, applets are not normally suitable for
applications that require access to databases, since this would require the
database to reside on the same machine as the Web server. If the security
restrictions are relaxed, as might be possible if the applet was being used only on
a company intranet, this problem is not encountered.
An applet is downloaded on demand from the Web site that is hosting it. This
gives an advantage in that the latest version is automatically downloaded each
time it is requested, so distributing new versions is trivial. On the other hand, it
also introduces disadvantages in that the applet will often be downloaded several
times even if it has not changed, pointlessly using bandwidth, and the developer
has little control over the environment in which the applet will run.
Requirements for the development environment
The development environment should provide a specialized editor that allows
adeveloper to design GUIs using a variety of component frameworks (such as
AWT, Swing, or SWT). The developer should be able to focus mainly on the
visual aspects of the layout of the GUI, rather than the coding that lies behind it.
Where necessary, the developer should be able to edit the generated code to
add event-handling code and business logic calls. The editor should be dynamic,
reflecting changes in the visual layout immediately in the generated code and
changes in the code immediately in the visual display. The development
environment should also provide facilities for testing visual components that
make up a GUI, as well the entire GUI.
Extensible Markup Language (XML)
Communication between computer systems is often difficult because different
systems use different data formats for storing data. XML has become a common
way of resolving this problem.
It can be desirable for the Call Center Desktop application to be able to
exchangedata with other applications. For example, we might want to be able to
exporttabular data so that it can be read into a spreadsheet application to produce a
chart, or we might want to be able to read information about a group of
transactions that can then be carried out as part of an overnight batch operation.
A convenient technology for exchanging information between applications is
XML, which is a standard, simple, flexible way of exchanging data. The structure
of the data is described in the XML document itself, and there are mechanisms
for ensuring that the structure conforms to an agreed format—these are known
as document type definitions (DTDs) and XML schemas (XSDs).

XML is increasingly also being used to store configuration information for

applications. For example, many aspects of Java EE 5 use XML for configuration
files called deployment descriptors, and WebSphere Application Server V7.0
uses XML files for storing its configuration settings.
several elements:
• A parser interface based on the Document Object Model (DOM) from the
W3C, which builds a complete internal representation of the XML document
• The Simple API for XML Parsing (SAX), which allows the document to be
parsed dynamically using an event-driven approach
 • XSL Transformations (XSLT), which uses Extensible Stylesheet Language
(XSL) to describe how to transform XML documents from one form into
another
Since JAXP is a standard part of Java SE V6.0, all these features are available
inany Java code running in a JVM.
Requirements for the development environment
In addition to allowing developers to write code to create and parse XML
documents, the development environment should provide features that allow
developers to create and edit XML documents and related resources. In
particular:
• An XML editor that checks the XML document for well-formedness
(conformance with the structural requirements of XML) and for consistency
with a DTD or XML Schema.
A static Web site is one in which the content viewed by users accessing the
siteusing a Web browser is determined only by the contents of the file system on the
Web server machine. Because the user’s experience is determined only by the
content of these files and not by any action of the user or any business logic
running on the server machine, the site is described as static.
In most cases, the communication protocol used for interacting with static
Websites is the Hypertext Transfer Protocol (HTTP).
In the context of our sample scenario, the bank might want to publish a static
Web site in order to inform customers of bank services, such as branch locations
and opening hours, and to inform potential customers of services provided by the
bank, such as account interest rates. This kind of information can safely be
provided statically, since it is the same for all visitors to the site and it changes
infrequently.
Hypertext Transfer Protocol (HTTP)
HTTP follows a request/response model. A client sends an HTTP request to
theserver providing information about the request method being used, the requested
Uniform Resource Identifier (URI), the protocol version being used, various other
header information and often other details, such as details from a form
completed on the Web browser. The server responds by returning an HTTP
response consisting of a status line, including a success or error code, and other
header information followed by a the HyperText Markup Language (HTML) code
for the static page requested by the client.
Web applications:
GET requests are normally used in situations where the user has entered an
address into the address or location field of a Web browser, used a bookmark
or favorite stored by the browser, or followed a hyperlink within an HTML
document.
POST requests are normally used when the user has completed an HTML
form displayed by the browser and has submitted the form for processing.
This request type is most often used with dynamic Web applications, which
include business logic for processing the values entered into the form.
Status codes
The status code returned by the server as the first line of the HTTP response
indicates the outcome of the request. In the event of an error, this information can
be used by the client to inform the user of the problem. In some situations, such
as redirection to another URI, the browser will act on the response without any
interaction from the user. The classes of status code are:
1xx: Information—The request has been received and processing is
continuing.
2xx: Success—The request has been correctly received and processed; an
HTML page accompanies a 2xx status code as the body of the response.
3xx: Redirection—The request did not contain all the information required or
the browser needs to take the user to another URI.
4xx: Client error—The request was incorrectly formed or could not be fulfilled.
5xx: Server error—Although the request was valid, the server failed to fulfill it.
The most common status code is 200 (OK), although 404 (Not Found) is very
commonly encountered. A complete list of status codes can be found at the W3C
site mentioned above.
Cookies
 Cookies are a general mechanism that server-side connections can use to both
store and retrieve information on the client side of the connection. Cookies can
contain any piece of textual information, within an overall size limit per cookie of 4
kilobytes. Cookies have the following attributes:
_ Name: The name of the cookie.
_ Value: The data that the server wants passed back to it when a browser
requests another page.
Domain: The address of the server that sent the cookie and that receives a
copy of this cookie when the browser requests a file from that server. The
domain can be set to equal the subdomain that contains the server so that
multiple servers in the same subdomain receive the cookie from the browser.
Path: Used to specify the subset of URLs in a domain for which the cookie is
valid.
Expires: Specifies a date string that defines the valid lifetime of that cookie.
Draft Document for Review May 9, 2009 12:19 am 7672-intro-2-prog.fm
Secure: Specifies that the cookie is only sent if HTTP communication is taking
place over a secure channel (known as HTTPS).
A cookie's life cycle proceeds as follows:
• The user gets connected to a server that wants to record a cookie.
• The server sends the name and the value of the cookie in the HTTP
response.
• The browser receives the cookie and stores it.
• Every time the user sends a request for a URL at the designated domain, the
• browser sends any cookies for that domain that have not expired with the
HTTP request.
Once the expiration date has been passed, the cookie crumbles.
Non-persistent cookies are created without an expiry date—they will only last for
the duration of the user’s browser session. Persistent cookies are set once and
remain on the user’s hard drive until the expiration date of the cookie.
 5.Project Description

5.1 Problem Definition

This project is aimed at developing an online data entry system that will enable
image assisted data entry for the shipment for the courier logistics.
The scanned image if available will be displayed on the left side of the screen when the
Airway Bill Number (AWB) is entered on the right side.
This is a POC (Proof Of Concept) assignment, which can be showcased to any
organization where chunk of the work is paper-based.

5.2 Overview of the Project

The General Description.

This section describes the general factors that affect the product and its
requirements. This section consists of five subsections that follow. This section does not
state specific requirements. Each of the subsections makes those requirements easier to
understand, it does not specify design or express specific requirements.

A shipment in the application represents one lot of an ordered item that has a
unique event and cost history. Shipments can be created when the product departs from
the factory, when the product arrives at the consolidator or freight forwarder, or when the
product is actually received by the consolidator or freight forwarder. The physical
measure, packing list, and commercial invoice should be available at this time.

Functions of System Components:

Database:
• Stores data
• Creates reports
• Provides access to data
• Updates information
 Server:
• Provides access to the database
• Authenticates users
• Processes reservations
• Performs backups
• Produces reports

5.3 Module Description

BOOKING
IMPORT
EXPORT
DELIVERY

The Booking invoice should contain names and addresses of consignor and
consignee, accurate description of goods and components (trademarks, name of the
vessel ) and the date of sailing, port of loading and port of discharge, net and gross
weight, quantity, unit price and extended price of each type of goods, total value of the
shipment, contents of each package and container, currency, number of L/C (if
applicable) and freight and insurance.

A shipment in the application represents one lot of an ordered item that has a unique
event and cost history. Shipments can be created when the product departs from the
factory, when the product arrives at the consolidator or freight forwarder, or when the
product is actually received by the consolidator or freight forwarder. The physical
measure, packing list, and commercial invoice should be available at this time.

DATA ENTRY FOR SHIPPING BILLS

1 Exporters / CHAs are required to register their IE Codes, CHAs Licence Nos., and the
Bank A/C No. (for credit of Drawback amount) in the Customs Computer Systems before
an EDI Shipping Bill is filed.
2 Exporters/CHAs would be required to submit at the Service Centre the following
documents:
A declaration in the specified format
SDF declaration
Quota / Inspection certificate
Drawback/DEEC/DFRC/DEPB Declarations etc., as applicable

3 The formats should be duly completed in all respects and should be signed by the
exporter or his authorised CHA. Forms, which are incomplete or unsigned, will not be
accepted for data entry.
4 Initially, data entry for Shipping Bills will be allowed to be made only at the Service
Centre. After the exporters/CHAs become conversant with the EDI procedures, the
option of Remote EDI System would also be made available. In the Remote EDI System
(RES) Exporters/CHAs can electronically file their shipping bills from their offices.

.5 The schedule of charges to be levied for data entry at the Service Centre is as follows: -

Charges for Shipping Bills having up to Rs.60

five items

Charges for additional block of five items Rs.10

Amendment fees (for a block of five items) Rs.10

Printing of a Shipping Bill for Remote EDI Rs.20

System

6 The Service Centre operators shall carefully enter the data on the basis of declarations
made by the CHAs/exporters. After completion of data entry, the checklist will be printed
by the Data Entry Operator and shall be handed over to the exporters/CHAs for
confirmation of the correctness. Thereafter, the CHA/Exporter will make corrections, if
any, in the checklist and return the same to the operator duly signed. The operator shall
make the corresponding corrections in the data and shall submit the Shipping Bill. The
operator shall not make any amendment after generation of the checklist and before
submission in the system unless the corrections made by the CHAs/exporters are clearly
indicated on the checklist against the respective fields and duly authenticated by
CHA/Exporter's signatures.

7 The system automatically generates the Shipping Bill number. The operator shall
endorse the same on the checklist in clear and bold figures. It should be noted that no
copy of the Shipping Bill would be available at this stage.

8 The Declarations would be accepted at the Service Centre from 10.00 hrs to 16.30 hrs.
Declarations received up to 16.30 hrs will be entered in the computer system on the same
day.

9 The validity of the shipping bill in EDI System is fifteen days only. After expiry of
fifteen days from the date of filing of shipping bill, the exporter has to file the declaration
afresh.

PROCEDURE FOR GR-1

3.1 Under the revised EDI procedure, there would be no GR-1 Procedure.
Exporters (including CHAs) would be required to file a declaration in the form SDF . It
would be filed at the stage of "goods arrival". One copy of the declaration would be
attached to the original copy of the S/B generated by the system and retained by the
Customs. The second copy would be attached to the duplicate S/B (the exchange control
copy) and surrendered by the exporter to the authorised dealer for collection/
negotiations.

3.2 The exporters are required to obtain a certificate from the bank through which they
would be realising the export proceeds. If the exporter wishes to operate through different
banks for the purpose, a certificate would have to be obtained from each of the banks.
The certificate(s) would be submitted to Customs and registered in the system. These
would have to be submitted once a year for confirmation or whenever the bank is
changed.

3.3 In the declaration form to be filed by the exporters for the electronic processing of
export documents, the exporters would need to mention the name of the bank and the
branch code as mentioned in the certificate from the bank. The Customs will verify the
details in the declaration with the information captured in the system through the
certificates registered earlier.

3.4 In the case of S/Bs processed manually, the existing arrangement of filing GR 1
forms would continue.

4 OCTROI PROCEDURES, QUOTA ALLOCATION AND OTHER

CERTIFICATION
4.1 The processing of S/Bs involving allocation of ready-made garments quota by the
Apparel Export Promotion Council (AEPC) will change with the introduction of the
system. The quota allocation label will be pasted on the export invoice instead of S/B.
Allocation number of AEPC would be entered in the system at the time of S/B data entry.
The quota certification on export invoice should be submitted to Customs along with
other original documents at the time of examination of export cargo.

4.2 As a transitional measure, AEPC certification even on S/B form would be accepted.
However, in these cases, S/B number should be indicated on the invoice when goods are
presented for examination. This transitional facilitation measure will be available for a
period of two months i.e. up to 30th November, 2004.

4.3 For determining the validity date of the quota, the relevant date would be the date on
which the full consignment is presented for examination and the date is recorded in the
system.

4.4 The certification of other agencies, such as, the Cotton Textiles Export Promotion
Council; the Wildlife Inspection Agency under CITES; the Engineering Export
Promotion Council; the Agricultural Produce Export Development Agency (APEDA), the
Central Silk Board and the All India Handicraft Board should also be obtained on the
invoice. Similarly, the no objection of the Asst. Drug Controller and of the
Archaeological of Survey India would be obtained on the invoice.

The transitional arrangements would be the same as in the case of AEPC certification.
4.5 The exporters would have to make use of export invoice or such other documents as
required by the Octroi Authorities for the purpose of octroi exemption.

5 ARRIVAL OF GOODS AT EXPORT EXAMINATION SHEDS IN CFS.

5.1 The existing procedure of permitting entry of goods, brought for the purpose of
examination (and subsequent "Let export" order), in the CFS on the strength of S/B shall
be discontinued. The CONCOR will permit entry of the goods on the strength of the
checklist, the data entry form and the declaration. The CONCOR would endorse the
quantity of goods entering the CFS on the reverse of the checklist.

5.2 The goods should be brought for examination within 15 days of filing of declaration
in the Centre. In case of delay, a fresh declaration would need to be filed.

5.3 If at any stage subsequent to the entry of goods in CFS, it is noticed that the
declaration has not been registered in the system, the exporters and CHAs will be
responsible for the delay in shipment of goods and any damage, deterioration or
pilferage, without prejudice to any other action that may be taken.

6 PROCESSING OF SHIPPING BILLS

6.1 The S/B shall be processed by the system on the basis of declaration made by the
exporter. However, the following S/B shall require clearance of the Assistant
Commissioner/ Deputy Commissioner (AC/DC Exports): -
Duty free S/B for FOB value above Rs. 10 lakh
Free Trade Sample S/B for FOB value above Rs. 25,000
Drawback S/B where the drawback exceeds Rs. one lakh
6.2 Subject to the provisions of para 20.3 of this PN, the following categories of Shipping
Bills shall be processed by the Appraiser (Export Assessment) first and then by the
Asstt/Deputy Commissioner:

6.3 Apart from verifying the value and other particulars for assessment, the AO/ AC/ DC
may call for the samples for confirming the declared value or for checking classification
under the Drawback
Schedule / DEEC / DEPB / DFRC / EOU etc,. He may also give special instruction for
examination of goods.
6.4 If the S/B falls in the categories indicted in para 6.1 above, the exporter should check
up with the query counter at the Centre whether the S/B has been cleared by Assistant
Commissioner/ Deputy Commissioner, before the goods are taken for examination. In
case AC/DC raises any query, it should be replied through the Service Centre or, in case
of EDI connectivity, through terminals of the exporter/CHA. After all the queries have
been satisfactorily replied to, AC/DC will pass the S/B.

Booking Order Key, Order, Orig ID, Vendor Booking, Booking Number, Item,
Dest ID, User-defined order set identifier, [Sub-Item Detail Scheme,
Scheme Level, sub-item detail optional fields]
User-defined
order set
identifier1 User-defined order set identifier, Order Key, Item, Order
 Import

The term "import" is derived from the conceptual meaning as to bring in the
goods and services into the port of a country. The buyer of such goods and services is
referred to an "importer" who is based in the country of import whereas the overseas
based seller is referred to as an "exporter".Thus an import is any good (e.g. a
commodity) or service brought in from one country to another country in a legitimate
fashion, typically for use in trade. It is a good that is brought in from another country
for sale.Import goods or services are provided to domestic consumers by foreign
producers. An import in the receiving country is an export to the sending country.
Imports, along with exports, form the basis of international trade. Import of
goods normally requires involvement of thecustoms authorities in both the country of
import and the country of export and are often subject to import quotas, tariffsand trade
agreements. When the "imports" are the set of goods and services imported, "Imports"
also means theeconomic valuofall goods and services that are ported. The
macroeconomic variable I usually stands for the value of these imports over a given
period of time, usually one year.

Types of import
There are two basic types of import:
1. Industrial and consumer goods
2. Intermediate goods and servicesCompanies import goods and services to supply to
the domestic market at a cheaper price and better quality than competing goods
manufactured in the domestic market. Companies import products that are not available
in the local market.
There are three broad types of importers:
1. Looking for any product around the world to import and sell.
2. Looking for foreign sourcing to get their products at the cheapest
price.
3. Using foreign sourcing as part of their global supply chain.
 Direct-import refers to a type of business importation involving a major retailer
(e.g. Wal-Mart) and an overseasmanufacturer. A retailer typically purchases products
designed by local companies that can be manufactured overseas. In a direct-import
program, the retailer bypasses the local supplier (colloquialmiddle - ma n) and buys the
final product directly from the manufacturer, possibly saving in added costs. This type
of business is fairly recent and follows the trends of theglobal economy.

1. Power of Attorney - By the Importer signing this form they are hereby authorizing
Gallagher Transport Int'l and all it's employees to sign all Customs & Border Protection
forms on their behalf.
2. Commerical Invoice - This is something the importer must provide to GTI.
Normally the importer has this form in their possesion and is not something GTI
provides. Although, if the importer does not have a commerical invoice than GTI can
provide upon request. C.B.P. does allow importers to simply write an invoice for their
imported items, if they know what exactly is in the shipment and know the correct piece
count and value.

3. Packing List - This is a form that is not a requirement from C.B.P. but may or may
not get your customs entry rejected and cause C.B.P. to ask more questions about your
entry. Therefore taking more time to clear your good from C.B.P. By clicking on the link
you can get a form that has been created if you feel you would rather have a packing list.

4. House Bill of Lading (if any) - This is not a requirment from C.B.P. but is required if
a House Bill of Lading has been issued by your shipper. Your shipper would be able to
tell you how to obtain a copy of the House Bill of Lading, if one has been issued. If you
need to track your shipment please click on the link to your left for your ocean or air
shipment tracking page. Or you can contact Gallagher Transport Intl and have one of our
employees track it for you.

5. Master Bill of Lading - This is a required form for C.B.P. Your shipper would be able
to tell you how to obtain a copy of the Master Bill of Lading.If you have an ocean import
shipiment, an original copy of the Master Bill of Lading will need to be provided to your
shippers U.S. contact with your endorsement anywhere on the back of the original Master
Bill of lading. If you need to track your shipment please click on the link to your left for
your ocean or air shipment tracking page. Or you can contact Gallagher Transport Intl
and have one of our employees track it for you.

6. Arrival Notice - This is not a requirment from C.B.P. but is VITAL to GTI in tracking
your shipment and knowing if any charges or other forms are required in order to get
your freight delivered to you (the importer). Your shipper would be able to tell you how
to obtain a copy of the arrival notice, if one has been issued. If you need to track your
shipment please click on the link to your left for your ocean or air shipment tracking
page. Or you can contact Gallagher Transport Intl and have one of our employees track it
for you.

Product : Wood dowel pins,plain,conifero indian wooden and brass handicrafts items.
Carrier : ALPJ
Vessel Name : Emirates Freedom Mango International Engg. Works
B-19 Shanker Tekri, Udyog Nagar , Jamnagar-361 004 ,Gujarat State, India
Same as Consignee Pen-Union Corp
229 Waterford Street,Edinboro, Pa 16412 U.S.A
Tel No: 235-684-3432

Date : 14/08/2006
Weight : 5014 K.G
Manifest units : PKG
US Port : NEW YORK NY
Indian Port : JNPT
Bol Number : IGOQNSINYC607136

Product : Brass electrical apparatus/components. 14350 pcs of clamp 988 pcs of lug
connector 10920 pcs of connector 620 pcs of tap assy 3000 pcs of base clamp 4250 pcs of
c connector 4400 pcs of ground clamp 600 pcs of lsn025necpctnsstlh 5000 pcs of jc-2aa-
bs 500.
Carrier : IGOQ
Vessel Name : Lahore Express Asiaan Handicrafts

Export
The development of a successful export strategy must encompass a thorough
knowledge of shipping procedures, documents required, and methods. The mechanics of
shipping include:
(1) Attention to packaging, including banding of bundles, grade stamping,
labeling, and color coding;
(2) Proper documentation;
(3) Scheduling the best shipping routes and carriers.

The details of export shipping are often handled by a ‘freight forwarder,’ who acts
as an exporter’s agent when shipping goods overseas. Freight forwarders are licensed by
the Federal Maritime Administration to facilitate the movement of goods from ports.
They may advise the exporter regarding freight costs, port charges, consular fees,
documentation fees, insurance, and handling costs. In addition to assuring that the goods
arrive overseas in good condition, they review the letter of credit and other necessary
documentation and may prepare the ocean bill of lading. After shipment, the forwarder
will send all documents to the paying bank to confirm the export of the commodity.
Three types of ocean carriers ship products overseas. The first are conference lines which
consist of an association of ocean carriers providing common rates and services.

Individual conference carriers may take independent action and offer shippers lower
rates. Also, shippers may form associations to negotiate lower rates with conferences.
The second type of carriers are the independents. Independent rates may be higher than
other carriers, but they may also be lower when in direct competition with conference
carriers. Both conference and independent carriers operate on regular schedules and trade
routes. Independent proprietary carriers include major forest products companies with
their own transportation operations. These lines specialize in forest products and other
bulk commodity shipping.
The third type of carrier is the tramp vessel. These carriers generally handle only bulk
cargo and are not on regular schedules or trade routes. According to the Western Wood
Products Association, tramps' economical rates make these carriers a common means of
shipping wood products.

A booking contract is mandatory to reserve space for the cargo on a specified vessel. You
may not need to know this because most of the time a freight forwarder can help with
these details. In any case, the contract is binding insofar as the carrier has the right to
charge for reserved space that is not used or to charge for canceled reservations without
adequate notice.

Transporting lumber and other forest products through general cargo terminals can be
very expensive. Transportation costs can be significantly reduced by using specialized
forest products handling facilities at the ports of export and destination, which will result
in lower freight rates and landed costs. .

The Exporters can get the export goods examined by Central Excise / Customs
Officer at the factory even prior to filling of Shipping Bill. Self sealing Facility is also
available. He shall obtain the Examination report in the form to this Public Notice duly
signed and stamped by the Examining Officer and Supervising Officer at the factory. The
export invoice shall also be signed and stamped by both the officers at the factory.
Thereafter the goods shall be brought to the concerned Customs Warehouse for the
purpose of clearance and subsequent "Let Export". The Exporters / CHA shall present the
goods for registration along with Examination Report, ARE-1, Export Invoice duly
signed by the Examining Officer and Supervising Officer at the factory, check list,
declaration in form and other documents such as document of transportation, ARE-1, etc.
to the Examiner in the concerned shed. After registration of goods, the shipping bill will
be marked to an Examiner for verification of documents and seal. If seal is found intact
the Shipping Bill will be recommended for LEO, which will be given by the Shed
Appraiser. However if seal is not found intact, the goods will be marked for examination
and LEO will be given if the goods are found in order.

Bill of Lading

A contract between the owner of the goods and the carrier (as with domestic shipments).
For vessels, there are two types: a straight bill of lading, which is non-negotiable, and a
negotiable or shipper's order bill of lading. The latter can be bought, sold, or traded while
the goods are in transit. The customer usually needs an original as proof of ownership to
take possession of the goods .

Commercial Invoice

A bill for the goods from the seller to the buyer. These invoices are often used by
governments to determine the true value of goods when assessing customs duties.
Governments that use the commercial invoice to control imports will often specify its
form, content, number of copies, language to be used, and other characteristics .

Export Packing List

Considerably more detailed and informative than a standard domestic packing list, it lists
seller, buyer, shipper, invoice number, date of shipment, mode of transport, carrier, and
itemizes quantity, description, the type of package, such as a box, crate, drum, or carton,
the quantity of packages, total net and gross weight (in kilograms), package marks, and
dimensions, if appropriate. Both commercial stationers and freight forwarders carry
things.

The proper packaging of products is vitally important, particularly when

shipments are bound for ports with inadequate handling and storage facilities. Lumber,
plywood, and veneer bundles must be securely strapped and protected from such
hardships as rough handling, moisture, or weathering. In many foreign ports, bundles
may be stored uncovered while awaiting pickup or delivery, making proper protection
essential. Bundles should be clearly marked according to foreign specifications and
include the company logo or color coding.
Wood products are shipped by a variety of methods including break bulk,
containers, flat racks, and lash barge. The most common methods are break bulk for
lumber and plywood shipments and containers for higher valued shipments such as kiln-
dried dimension stock, lumber clears, and veneer.
Freight containers are capable of holding approximately 4,000 board feet of logs or
10,000-14,000 board feet of lumber, depending on the product and moisture content.
Maximum cargo weights are, however, limited by carriers to comply with laws
established to protect roads and bridges. A 40-foot container, therefore, can only be
loaded with about 46,000 pounds of forest products when traveling over U.S. highways.
Containers loaded at the port may have higher cargo weights.

Delivery
Receipt (RCV
Select if the product has arrived at the purchasers designated facility and has
transferred ownership. The product has cleared export customs, and all document
requirements of the purchase agreement and letter of credit have been completed. A
forwarders cargo receipt should be available
Vendor Delivery (VDL)

Select if the product has arrived at the purchasers designated facility but has not
transferred ownership. The product has not cleared export customs, or not all document
requirements of the purchase agreement or letter of credit have been completed.

Factory Departure (FTY

Select if the product has left the factory but has not yet arrived at the purchasers
designated facility. The physical measure, packing list, and commercial invoice should
be available at this time.

Delivery Event Est Sail* Rcv City ID Load ID Est Disch Facility Type
Rcv Date ETA Dest Facility ID Est Load Site ID Disch ID

Data base
These database will be created with Oracle8i (Client/Server) version 8.1.6.0.0
Release 2. The following are the requirements for these databases that are to be
developed as part of the product. They include:
Operations.
The normal operations required by the user can be viewed as the following:

User-initiated Operations:
These operations include the login operation, which is initiated by the users. Also,
the process of becoming a new user is in this category. Building, changing, and viewing
itineraries, as well as paying for the itinerary are all initiated by the users. The user
initiates the report generation activity, as well as changing train schedules.
Interactive Operations and Unattended Operations:
The users initiate all the operations mentioned above, and almost all of them are
somehow interactive. Displaying the train schedule is non-interactive. The report display
is a non-interactive operation, although selecting the desired reports will require user
input.
Data Processing Support Functions:
The user account data is used to create new accounts, as well as to validate user
id's during login functions. For building itineraries, user input, user account data, and
train schedule data are used, and processed. User data along with final results of user
interaction (whether the user purchased a trip, number of tickets bought, etc.) are
collected, and used for report generation purposes. Administrative users' inputs are
collected in order to modify and present schedules.
Backup and Recovery Operations:
Both databases used (passenger account database and reservations database) are
production databases. The main operation used for the backup and recovery is Oracle's
built-in cold backup, which is also known as the "archive mode". Depending on the
customer's needs and budget, additional redundancy can be added using systems like
RAID 5 and tape backup.

9. Appendix
9.1 Source Code:
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

/**
* Servlet implementation class LoginServlet
*/
public class LOG extends HttpServlet {
private static final long serialVersionUID = 1L;

/**
* @see HttpServlet#HttpServlet()
*/
public LOG ()
 {
super();
// TODO Auto-generated constructor stub
}

/**
* @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse
response)
*/
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
// TODO Auto-generated method stub
}

/**
* @see HttpServlet#doPost(HttpServletRequest request, HttpServletResponse
response)
*/
protected void doPost(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
// TODO Auto-generated method stub
DBconnection db=new DBconnection();
Connection con=db.getConnection();
String user= request.getParameter("username");
String pass= request.getParameter("password");
String user1=null;
String pass1=null;
System.out.println("ok");
PreparedStatement ps;
ResultSet rs=null;
if(user!=null && pass!=null)
{
try
{
ps=con.prepareStatement("select * from LEAVESYS.LOG where
USERNAME=?");
ps.setString(1,user);
rs=ps.executeQuery();

while(rs.next())
{

user1=rs.getString(1);
pass1=rs.getString(2);
}
if(user.equals(user1)&&pass.equals(pass1))
 {
System.out.println("Success");
String url= "/eli.jsp";
RequestDispatcher dispatcher =
getServletContext().getRequestDispatcher(url);
if (dispatcher!=null)
{
dispatcher.forward(request, response);
}
}

else
System.out.println("Unsuccess");
}
catch(Exception e)
{

e.printStackTrace();
}
}
else
{
System.out.println("the user name or password fields cannot be empty");
}

package com.ibm.servlet;

import java.io.IOException;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
//import java.sql.Statement;

import javax.servlet.RequestDispatcher;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
//import javax.servlet.http.HttpSession;
/**
* Servlet implementation class LoginServlet
*/
public class Controler extends HttpServlet {
private static final long serialVersionUID = 1L;

/**
* @see HttpServlet#HttpServlet()
*/
public Controler() {
super();
// TODO Auto-generated constructor stub
}

/**
* @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse
response)
*/
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
// TODO Auto-generated method stub
}

/**
* @see HttpServlet#doPost(HttpServletRequest request, HttpServletResponse
response)
*/
protected void doPost(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
// TODO Auto-generated method stub
DBConnection db=new DBConnection();
Connection con=db.getConnection();
String user= request.getParameter("username");
String pass= request.getParameter("password");
String user1=null;
String pass1=null;
//String name=null;
System.out.println("ok");
//Statement st=null;
ResultSet rs=null;
PreparedStatement ps;
try
{
//ps=con.prepareStatement("select * from LOGSCHEMA.LOGIN
where USERNAME=?");
 ps=con.prepareStatement("select * from LOGSCHEMA.LOGIN
where USERNAME=?");
ps.setString(1,user);
//st=con.createStatement();
rs=ps.executeQuery();
while(rs.next())
{

user1=rs.getString(1);
pass1=rs.getString(2);
//name=rs.getString(3);
}
if(user.equals(user1)&&pass.equals(pass1))
{
/*System.out.println(name);
HttpSession session=request.getSession();
session.setAttribute(name,"name");*/
String url= "/master.jsp";
RequestDispatcher dispatcher =
getServletContext().getRequestDispatcher(url);
if (dispatcher!=null)
{
dispatcher.forward(request, response);
}
}

else
System.out.println("Unsuccess");
}
catch(Exception e)
{

e.printStackTrace();
}
}

}
package com.ibm.servlet;
import java.sql.Connection;
import java.sql.DriverManager;

public class DBConnection {

public Connection getConnection()

 {
Connection con = null;
try{

Class.forName("com.ibm.db2.jcc.DB2Driver");
// -- Type 2 syntax:
String url = "jdbc:db2:LOG";
String username = "Administrator";
String password = "admin";
con =
DriverManager.getConnection(url,username,password);
System.out.println("Connection successful");
}
catch ( Exception e)
{
System.out.println("Drive Issue");
e.printStackTrace();
}
return con;
}
}

5.7 Input Design

Input design is the process of converting user-oriented input to computer-based
format. The goal of input data design is to make data entry as easy, logical and free from
errors as possible. Inputs are raw data that are acceptable by the system and processed it
to produce the output. It also includes determining media, method of input, speed of
capture and entry into the system. Errors entered are controlled by the input design.
Four objectives guiding the design of input focus on:

• Controlling the amount of input required.

• Avoid delay.
• Controlling errors.
• Keeping the steps simple.
 Main screen is designed with Menu bar, Tool box, Property window, Design
frame and Code window. The skeleton structure of the form design required by the user is
given as the input. Components can be added to the design frame from the Toolbox
window and the user required form design can be designed.

5.8 Output Design

The output design was done so that results of processing could be communicated
to the users. The various outputs have been designed in such a way that they represent the
same format that the office and management used to.
Computer output is the most important and direct source of information to the
user. Efficient, intelligible output design should improve the systems relationships with
the user and help in decision making. A major form of output is hardcopy from the
printer.

6. System Testing
This document is a high-level overview defining our testing strategy for the Sorted
Binary Tree application. Its objective is to communicate project-wide quality standards
and procedures. It portrays a snapshot of the project as of the end of the planning phase.
This document will address the different standards that will apply to the unit, integration
and system testing of the specified application. We will utilize testing criteria under the
white box, black box, and system-testing paradigm. This paradigm will include, but is
not limited to, the testing criteria, methods, and test cases of the overall design.
Throughout the testing process we will be applying the test documentation specifications
described in the IEEE Standard 829-1983 for Software Test Documentation.

Testing Process

b. Design System
Test

a. Organize c. Design/Build e. Design/Build

Project Test Proc. Test Proc. f. Signoff

d. Organize
Project
The testing of a conventional software system involves some of the following phases.
They are

 Unit Testing
 Acceptance Testing
 Test Cases

6.1 Unit Testing

A software module can be created by building up of many small parts into a
single module. This small part is called as a unit. A unit is a piece of code that will
perform a specific task. At the end of this testing all units will be tested so that we can
get the correct result. By using unit testing we can easily identify the errors.

6.2 Acceptance Testing

User acceptance of the system is a key factor for the success of any system.
The system under the consideration is tested for user acceptance by constantly keeping
touch with prospective system and user at the time of developing and making changes
whenever required. This is done regarding to the following points.
• Input Screen design
• Output screen design
White Box Testing

In white box testing, the UI is bypassed. Inputs and outputs are tested directly at the code
level and the results are compared against specifications. This form of testing ignores the
function of the program under test and will focus only on its code and the structure of that
code. Test case designers shall generate cases that not only cause each condition to take
on all possible values at least once, but that cause each such condition to be executed at
least once. To ensure this happens, we will be applying Branch Testing. Because the
functionality of the program is relatively simple, this method will be feasible to apply.

Each function of the binary tree repository is executed independently; therefore, a

program flow for each function has been derived from the code.
Black Box Testing

Black box testing typically involves running through every possible input to verify that it
results in the right outputs using the software as an end-user would. We have decided to
perform Equivalence Partitioning and Boundary Value Analysis testing on our
application.

Equivalence Partitioning

In considering the inputs for our equivalence testing, the following types will be used:

Legal input values – Test values within boundaries of the specification equivalence
classes. This shall be input data the program expects and is programmed to transform
into usable values.
Illegal input values – Test equivalence classes outside the boundaries of the specification.
This shall be input data the program may be presented, but that will not produce any
meaningful output.

The equivalence partitioning technique is a test case selection technique in which the test
designer examines the input space defined for the unit under test and seeks to find sets of
input that are, or should be, processed identically. The following table represents our
equivalence classes, both valid and invalid.

Incremental Testing
There are two primary modules that will need to be integrated: the Graphic User Interface
module and the Tree Repository module (back-end). The two components, once
integrated, will form the complete Binary Search Tree Application. The following
describes these modules as well as the steps that will need to be taken to achieve
complete integration. We will be employing an incremental testing strategy to complete
the integration.

Module 1 - Graphic User Interface (GUI) Module

This module provides a simple GUI where the user can perform the different actions
(functions). This module will be tested separate from the backend to check if each
interface (e.g. insert button) is functioning properly, and in general, to test if the mouse-
event actions are working properly. The testing will be performed by writing a stub for
each element in the interface.

Future enhancement

► Removes the restriction and/or warning against processing Orders in Shipping

Entry when a Customer is on Credit Hold or has exceeded his or her Credit Limit.
Prevents freight recalculation when a specified Order Header UDF is set to a
particular value. Issues audible alerts any time the user over ships a line or selects
an item that is not on the order Default all lines to the color of red, and then to
change to black as they are shipped.
Conclusion

When you need to plug a drain in your budget and become more self-reliant, your
first step is to contact DCS for a free assessment. With our help you can calculate the
ROI and then activate EDI for high volume, key customers or move to a modern
version supporting XML that is already adapted to your ERP system. The next step is
easy, call or e-mail DCS for more information

Booking Database

Login Import Delivery

Export

Report

5/30/2011 Dept of MCA / KCT Model Review 1

 http://www.ibm.com/developerworks/data/products/db2/index.html?
S_TACT=105AGX11&S_CMP=FP
 Rational Application Developer for WebSphere Software-
http://www.ibm.com/developerworks/rational/products/rad/
 IBM RedBooks- http://www.redbooks.ibm.com