Efficient Algorithms for Mining High Utility Itemsets from Transactional

Databases

Objective:The main Objective of this paper is to reducing itemsets overestimated utilities and
proposes several strategies. By applying the proposed strategies, the number of generated
candidates can be highly reduced.
Abstract:
Mining high utility itemsets from a transactional database refers to the discovery of
itemsets with high utility like profits. Although a number of relevant algorithms have
been proposed in recent years, they incur the problem of producing a large number of
Candidate itemsets for high utility itemsets. Such a large number of candidate itemsets
degrades the mining performance in terms of execution time and space requirement. The
situation may become worse when the database contains lots of long transactions or long
high utility itemsets. In this paper, we propose two algorithms, namely utility pattern
growth (UP-Growth) and UP-Growth+, for mining high utility itemsets with a set of
effective strategies for pruning candidate itemsets. The information of high utility
itemsets is maintained in a tree-based data structure named utility pattern tree (UP-Tree)
such that candidate itemsets can be generated efficiently with only two scans of database.
The performance of UP-Growth and UP-Growth+ is compared with the state-of-the-art
algorithms on many types of both real and synthetic data sets. Experimental results show
that the proposed algorithms, especially UPGrowth+, not only reduce the number of
candidates effectively but also outperform other algorithms substantially in terms of
runtime, especially when databases contain lots of long transactions.
Problem Definition:
Existing System:
In the framework of frequent itemset mining, the importance of items to users is
not considered. Thus, the topic called weighted association rule mining was brought to
attention and the concept of weighted items and weighted association rules. However,
since the framework of weighted association rules does not have downward closure
property, mining performance cannot be improved.
Disadvantages:

 Although weighted association rule mining considers the importance of items, in

some applications, such as transaction databases, items quantities in transactions
are not taken into considerations yet.
It cannot satisfy the requirements of users who are interested in discovering the
itemsets with high sales profits, since the profits are composed of unit profits, i.e.,
weights, and purchased quantities.
Proposed System:
We propose two novel algorithms as well as a compact data structure for
efficiently discovering high utility itemsets from transactional databases. Two algorithms,
named utility pattern growth (UPGrowth) and UP-Growth+, and a compact tree structure,
called utility pattern tree (UP-Tree), for discovering high utility itemsets and maintaining
important information related to utility patterns within databases are proposed. Highutility itemsets can be generated from UP-Tree efficiently with only two scans of original
databases. Several strategies are proposed for facilitating the mining processes of UPGrowth and UP-Growth+ by maintaining only essential information in UP-Tree. By these
strategies, overestimated utilities of candidates can be well reduced by discarding utilities
of the items that cannot be high utility or are not involved in the search space. The
proposed strategies can not only decrease the overestimated utilities of PHUIs but also
greatly reduce the number of candidates. Different types of both real and synthetic data
sets are used in a series of experiments to compare the performance of the proposed
algorithms with the state-of-the-art utility mining algorithms. Experimental results show
that UP-Growth and UP-Growth+ outperform other algorithms substantially in terms of
execution time, especially when databases contain lots of long transactions or low
minimum utility thresholds are set.
Advantages:
Scan the database twice to construct a global UPTree with the first two strategies

recursively generate PHUIs from global UP-Tree and local UP-Trees by UPGrowth with the third and fourth strategies or by UP-Growth+ with the last two
strategies

Identify actual high utility itemsets from the set of PHUIs

Scope of the project:

The main scope of this project is to facilitate the mining performance and avoid
scanning original database repeatedly; we use a compact tree structure, named UP-Tree,
to maintain the information of transactions and high utility itemsets.
Software Requirements :
Operating System

: Windows XP/2007 or Linux

User Interface

: HTML, CSS

Client-side Scripting

: JavaScript

Programming Language

: Java

Web Applications

: JDBC, Servlets, JSP

IDE/Workbench

: Netbeans 7.3

Database

: MySql 5.1

Server Deployment

: Tomcat 7

Hardware Requirements:
Processor

: Pentium IV

Hard Disk

: 40GB

RAM

: 512MB or more

Users Of the System:

Admin
Provider

Customer

Functional Requirements

Number Of Modules:

The system after careful analysis has been identified to be presented with the following
modules:
1. Product
2. UP-Tree
3. UP-Growth
4. UP-Growth+
5. Efficiently Identify High Utility Itemsets
6. Finding Frequent Itemsets

Module Description:

1. Product:
In this module multiple providers can add their item details with their item profit
in database and they can update and delete their item details after add the item.Admin can
view all the item details as well as Customers details. Customer can view all providers
item details and they can purchase using their OTP (one time password) which has been
sent their mail id.
2. UP-Tree:
To facilitate the mining performance and avoid scanning original database
repeatedly, we use a compact tree structure, named UP-Tree, to maintain the information
of transactions and high utility itemsets. Two strategies are applied to minimize the
overestimated utilities stored in the nodes of global UP-Tree.
3. UP-Growth:
After constructing a global UP-Tree, a basic method for generating PHUIs is
to mine UP-Tree by FP-Growth. However too many candidates will be generated. Thus,

we propose an algorithm UP-Growth by pushing two more strategies into the framework
of FP-Growth. By the strategies, overestimated utilities of itemsets can be decreased and
thus the number of PHUIs can be further reduced.
4. UP-Growth+:
UP-Growth achieves better performance than FP-Growth by using DLU
and DLN to decrease overestimated utilities of itemsets. However, the overestimated
utilities can be closer to their actual utilities by eliminating the estimated utilities that are
closer to actual utilities of unpromising items and descendant nodes. In UP-Growth,
minimum item utility table is used to reduce the overestimated utilities. In UP-Growth+,
minimal node utilities in each path are used to make the estimated pruning values closer
to real utility values of the pruned items in database
5. Efficiently Identify High Utility Itemsets:
After finding all PHUIs, the third step is to identify high utility itemsets
and their utilities from the set of PHUIs by scanning original database once. This step is
called phase II. However, in existing system, two problems in this phase occur: 1)
number of HTWUIs is too large; and (2) scanning original database is very time
consuming. In our framework, overestimated utilities of PHUIs are smaller than or equal
to TWUs of HTWUIs since they are reduced by the proposed strategies. Thus, the
number of PHUIs is much smaller than that of HTWUIs. Therefore, in phase II, our
method is much efficient than the Previous methods. Moreover, although our methods
generate fewer candidates in phase I, scanning original database is still time consuming
since the original database is large and it contains lots of unpromising items. In view of
this, in our framework, high utility itemsets can be identified by scanning reorganized
transactions.
6. Finding Frequent Itemsets:
In this module multiple providers can view their frequent itemsets using their customer
purchased details. The frequent item is finding by UP-Growth+ algorithm for each
Providers items. Providers can find frequent itemsets in either monthly or daily basis.

System Design
DESIGN ENGINEERING
GENERAL

Design Engineering deals with the various UML [Unified Modeling language] diagrams
for the implementation of project. Design is a meaningful engineering representation of a
thing that is to be built. Software design is a process through which the requirements are
translated into representation of the software. Design is the place where quality is
rendered in software engineering. Design is the means to accurately translate customer
requirements into finished product.

Architecture:

User

Register

Registration
Details

Product

Product
Details

Purchase

Purchase
Details

Admin

Provider

Find Frequent Items

It

View
Frequent
Itemsets

Up-Growth
and UpGrowth+

Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the flow of data through an
information system. It differs from the flowchart as it shows the data flow instead of the
control flow of the program. A data flow diagram can also be used for the visualization of

data processing. The DFD is designed to show how a system is divided into smaller
portions and to highlight the flow of data between those parts.

Data Flow Diagram (DFD) is an important technique for modeling a systems high-level
detail by showing how input data is transformed to output results through a sequence of
functional transformations. DFDs reveal relationships among and between the various
components in a program or system. DFD consists of four major components: entities,
processes, data stores and data flow.
DFD LEVEL 0:

Login Details

Providers

Access
Login

Providers
Options

DFD LEVEL 1:

Add Item
Select Option

store

Select Option

Providers

Database

View item
Details
Find
Frequent

DFD LEVEL 2:

Add Item
Select Option
Select Option

Providers

Select Option

Admin

store

Find
Frequent

View Item
Details

Database

Overall DFD:

Add Item
Select Option
Select Option

Providers

Select Option

store

Find
Frequent

Database

View Item
Details

Admin

Customer

Purchase

Use Case Diagram

A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases. The
main purpose of a use case diagram is to show what system functions are performed for
which actor. Roles of the actors in the system can be depicted. Use case diagrams are

formally included in two modeling languages defined by the OMG: the Unified Modeling
Language

(UML) and

the Systems

Modeling

Language

(SysML).

Use

case

diagrams are behavior diagrams used to describe a set of actions (use cases) that some
system or systems (subject) should or can perform in collaboration with one or
more external users of the system (actors). Each use case should provide some observable
and valuable result to the actors or other stakeholders of the system.

Class Diagram

A class diagram in the UML is a type of static structure diagram that describes the
structure of a system by showing the systems classes, their attributes, and the
relationships between the classes. Private visibility hides information from anything
outside the class partition. Public visibility allows all other classes to view the marked
information. Protected visibility allows child classes to access information they inherited
from a parent class. In software engineering, a class diagram in the Unified Modeling
Language (UML) is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, operations (or methods), and the
relationships among the classes. A class diagram is an illustration of the relationships
and source code dependencies among classes in the Unified Modeling Language (UML).
In a class diagram, the classes are arranged in groups that share common characteristics.
A class diagram resembles a flowchart in which classes are portrayed as boxes, each box
having three rectangles inside. The top rectangle contains the name of the class; the
middle rectangle contains the attributes of the class; the lower rectangle contains the
methods, also called operations, of the class. Lines, which may have arrows at one or
both ends, connect the boxes. These lines define the relationships, also called
associations, between the classes.

Sequence Diagram
A sequence diagram in UML is a kind of interaction diagram that shows how processes
operate with one another and in what order.
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. A sequence diagram shows object interactions
arranged in time sequence. It depicts the objects and classes involved in the scenario and
the sequence of messages exchanged between the objects needed to carry out the
functionality of the scenario. Sequence diagrams typically are associated with use case

realizations in the Logical View of the system under development. Sequence diagrams are
sometimes called event diagrams, event scenarios, and timing diagrams.

Collaboration Diagram
A collaboration diagram show the objects and relationships involved in an
interaction, and the sequence of messages exchanged among the objects during the
interaction. The collaboration diagram can be a decomposition of a class, class diagram,
or part of a class diagram. it can be the decomposition of a use case, use case diagram, or
part of a use case diagram. The collaboration diagram shows messages being sent
between classes and object (instances). A diagram is created for each system operation
that relates to the current development cycle (iteration).A collaboration diagram, also
called a communication diagram or interaction diagram, is an illustration of the
relationships and interactions among software objects in the Unified Modeling
Language (UML). The concept is more than a decade old although it has been
refined as modeling paradigms have evolved. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects as well
as the overall operation of the system in real time. Objects are shown as rectangles with
naming labels inside. These labels are preceded by colons and may be underlined. The
relationships between the objects are shown as lines connecting the rectangles. The
messages between objects are shown as arrows connecting the relevant rectangles along
with labels that define the message sequencing.

ACTIVITY DIAGRAM
Activity diagram are a loosely defined diagram to show workflows of stepwise
activities and actions, with support for choice, iteration and concurrency. UML, activity
diagrams can be used to describe the business and operational step-by-step workflows of
components in a system. UML activity diagrams could potentially model the internal
logic of a complex operation. In many ways UML activity diagrams are the objectoriented equivalent of flow charts and data flow diagrams (DFDs) from structural
development.
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-bystep workflows of components in a system. An activity diagram shows the overall flow of
control.

Providers

Login

Valid
ate

No

Yes
Option
Selection

Add
Items

User

View

Purchase

Find Frequent
Items

Admin

E-R Diagram

In software engineering, an entity-relationship model (ERM) is an abstract and

conceptual

representation

of data.

Entity-relationship

modeling

is

database

modeling method, used to produce a type of conceptual schema or semantic data

model of a system, often a relational database, and its requirements in a topdown fashion. Diagrams created by this process are called entity-relationship
diagrams, ER diagrams, or ERDs.
An entity-relationship (ER) diagram is a specialized graphic that illustrates
the relationships between entities in a database. ER diagrams often use symbols to
represent three different types of information. Boxes are commonly used to represent
entities. Diamonds are normally used to represent relationships and ovals are used to
represent attributes.

Component Diagram
In the Unified Modeling Language, a component diagram depicts how components are
wired together to form larger components and or software systems. They are used to
illustrate the structure of arbitrarily complex systems.
The Component Diagram helps to model the physical aspect of an Object-Oriented
software system. It illustrates the architectures of the software components and the
dependencies between them. Those software components including run-time components,
executable components also the source code components. A component diagram has a
higher level of abstraction than a Class Diagram - usually a component is implemented
by one or more classes (or objects) at runtime. They are building blocks so a component
can eventually encompass a large portion of a system.

Software Environment
1.Java Technology

Java technology is both a programming language and a platform.

1. The Java Programming Language

2. The Java programming language is a high-level language that can be
characterized by all of the following buzzwords:

Simple

Architecture neutral

Object oriented

Portable

Distributed

High performance

Interpreted

Multithreaded

Robust

Dynamic

Secure

With most programming languages, you either compile or interpret a program so

that you can run it on your computer. The Java programming language is unusual in that a
program is both compiled and interpreted. With the compiler, first you translate a
program into an intermediate language called Java byte codes the platformindependent codes interpreted by the interpreter on the Java platform. The interpreter
parses and runs each Java byte code instruction on the computer. Compilation happens
just once; interpretation occurs each time the program is executed. The following figure
illustrates how this works.

You can think of Java byte codes as the machine code instructions for the Java Virtual
Machine (Java VM). Every Java interpreter, whether its a development tool or a Web
browser that can run applets, is an implementation of the Java VM. Java byte codes help
make write once, run anywhere possible. You can compile your program into byte
codes on any platform that has a Java compiler. The byte codes can then be run on any
implementation of the Java VM. That means that as long as a computer has a Java VM,
the same program written in the Java programming language can run on Windows 2000,
a Solaris workstation, or on an iMac.

3.
4. The Java Platform
A platform is the hardware or software environment in which a program
runs. Weve already mentioned some of the most popular platforms like Windows
2000, Linux, Solaris, and MacOS. Most platforms can be described as a
combination of the operating system and hardware. The Java platform differs from
most other platforms in that its a software-only platform that runs on top of other
hardware-based platforms.
The Java platform has two components:

The Java Virtual Machine (Java VM)

The Java Application Programming Interface (Java API)

Youve already been introduced to the Java VM. Its the base for the Java
platform and is ported onto various hardware-based platforms.
The Java API is a large collection of ready-made software components that
provide many useful capabilities, such as graphical user interface (GUI) widgets.
The Java API is grouped into libraries of related classes and interfaces; these

libraries are known as packages. The next section, What Can Java Technology
Do? Highlights what functionality some of the packages in the Java API provide.
The following figure depicts a program thats running on the Java platform. As
the figure shows, the Java API and the virtual machine insulate the program from
the hardware.
Native code is code that after you compile it, the compiled code runs on a
specific hardware platform. As a platform-independent environment, the Java
platform can be a bit slower than native code. However, smart compilers, welltuned interpreters, and just-in-time byte code compilers can bring performance
close to that of native code without threatening portability.
2. What Can Java Technology Do?
The most common types of programs written in the Java programming language
are applets and applications. If youve surfed the Web, youre probably already
familiar with applets. An applet is a program that adheres to certain conventions
that allow it to run within a Java-enabled browser.
However, the Java programming language is not just for writing cute, entertaining
applets for the Web. The general-purpose, high-level Java programming language
is also a powerful software platform. Using the generous API, you can write many
types of programs.
An application is a standalone program that runs directly on the Java platform. A
special kind of application known as a server serves and supports clients on a
network. Examples of servers are Web servers, proxy servers, mail servers, and
print servers. Another specialized program is a servlet. A servlet can almost be
thought of as an applet that runs on the server side. Java Servlets are a popular
choice for building interactive web applications, replacing the use of CGI scripts.

Servlets are similar to applets in that they are runtime extensions of applications.
Instead of working in browsers, though, servlets run within Java Web servers,
configuring or tailoring the server.
How does the API support all these kinds of programs? It does so with packages of
software components that provides a wide range of functionality. Every full
implementation of the Java platform gives you the following features:

The essentials: Objects, strings, threads, numbers, input and output, data
structures, system properties, date and time, and so on.

Applets: The set of conventions used by applets.

Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram
Protocol) sockets, and IP (Internet Protocol) addresses.

Internationalization: Help for writing programs that can be localized for users
worldwide. Programs can automatically adapt to specific locales and be displayed
in the appropriate language.

Security: Both low level and high level, including electronic signatures, public
and private key management, access control, and certificates.

Software components: Known as JavaBeansTM, can plug into existing component

architectures.

Object serialization: Allows lightweight persistence and communication via

Remote Method Invocation (RMI).

Java Database Connectivity (JDBCTM): Provides uniform access to a wide range

of relational databases.

The Java platform also has APIs for 2D and 3D graphics, accessibility, servers,
collaboration, telephony, speech, animation, and more. The following figure
depicts what is included in the Java 2 SDK.

3.
4. How Will Java Technology Change My Life?
We cant promise you fame, fortune, or even a job if you learn the Java
programming language. Still, it is likely to make your programs better and requires
less effort than other languages. We believe that Java technology will help you do
the following:

Get started quickly: Although the Java programming language is a powerful

object-oriented language, its easy to learn, especially for programmers already
familiar with C or C++.

Write less code: Comparisons of program metrics (class counts, method counts,
and so on) suggest that a program written in the Java programming language can
be four times smaller than the same program in C++.

Write better code: The Java programming language encourages good coding
practices, and its garbage collection helps you avoid memory leaks. Its object
orientation, its JavaBeans component architecture, and its wide-ranging, easily
extendible API let you reuse other peoples tested code and introduce fewer bugs.

Develop programs more quickly: Your development time may be as much as

twice as fast versus writing the same program in C++. Why? You write fewer lines
of code and it is a simpler programming language than C++.

Avoid platform dependencies with 100% Pure Java: You can keep your
program portable by avoiding the use of libraries written in other languages. The

100% Pure JavaTM Product Certification Program has a repository of historical

process manuals, white papers, brochures, and similar materials online.

Write once, run anywhere: Because 100% Pure Java programs are compiled into
machine-independent byte codes, they run consistently on any Java platform.

Distribute software more easily: You can upgrade applets easily from a central
server. Applets take advantage of the feature of allowing new classes to be loaded
on the fly, without recompiling the entire program.
1. ODBC
Microsoft Open Database Connectivity (ODBC) is a standard programming

interface for application developers and database systems providers. Before ODBC
became a de facto standard for Windows programs to interface with database systems,
programmers had to use proprietary languages for each database they wanted to connect
to. Now, ODBC has made the choice of the database system almost irrelevant from a
coding perspective, which is as it should be. Application developers have much more
important things to worry about than the syntax that is needed to port their program from
one database to another when business needs suddenly change.
Through the ODBC Administrator in Control Panel, you can specify the particular
database that is associated with a data source that an ODBC application program is
written to use. Think of an ODBC data source as a door with a name on it. Each door will
lead you to a particular database. For example, the data source named Sales Figures
might be a SQL Server database, whereas the Accounts Payable data source could refer to
an Access database. The physical database referred to by a data source can reside
anywhere on the LAN.
The ODBC system files are not installed on your system by Windows 95. Rather,
they are installed when you setup a separate database application, such as SQL Server

Client or Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a
file called ODBCINST.DLL. It is also possible to administer your ODBC data sources
through a stand-alone program called ODBCADM.EXE. There is a 16-bit and a 32-bit
version of this program and each maintains a separate list of ODBC data sources.
From a programming perspective, the beauty of ODBC is that the application can
be written to use the same set of function calls to interface with any data source,
regardless of the database vendor. The source code of the application doesnt change
whether it talks to Oracle or SQL Server. We only mention these two as an example.
There are ODBC drivers available for several dozen popular database systems. Even
Excel spreadsheets and plain text files can be turned into data sources. The operating
system uses the Registry information written by ODBC Administrator to determine which
low-level ODBC drivers are needed to talk to the data source (such as the interface to
Oracle or SQL Server). The loading of the ODBC drivers is transparent to the ODBC
application program. In a client/server environment, the ODBC API even handles many
of the network issues for the application programmer.
The advantages of this scheme are so numerous that you are probably thinking
there must be some catch. The only disadvantage of ODBC is that it isnt as efficient as
talking directly to the native database interface. ODBC has had many detractors make the
charge that it is too slow. Microsoft has always claimed that the critical factor in
performance is the quality of the driver software that is used. In our humble opinion, this
is true. The availability of good ODBC drivers has improved a great deal recently. And
anyway, the criticism about performance is somewhat analogous to those who said that
compilers would never match the speed of pure assembly language. Maybe not, but the
compiler (or ODBC) gives you the opportunity to write cleaner programs, which means
you finish sooner. Meanwhile, computers get faster every year.

JDBC
In an effort to set an independent database standard API for Java; Sun
Microsystems developed Java Database Connectivity, or JDBC. JDBC offers a generic
SQL database access mechanism that provides a consistent interface to a variety of
RDBMSs. This consistent interface is achieved through the use of plug-in database
connectivity modules, or drivers. If a database vendor wishes to have JDBC support, he
or she must provide the driver for each platform that the database and Java run on.
To gain a wider acceptance of JDBC, Sun based JDBCs framework on ODBC. As
you discovered earlier in this chapter, ODBC has widespread support on a variety of
platforms. Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market
much faster than developing a completely new connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public
review that ended June 8, 1996. Because of user input, the final JDBC v1.0 specification
was released soon after.
The remainder of this section will cover enough information about JDBC for you to know
what it is about and how to use it effectively. This is by no means a complete overview of
JDBC. That would fill an entire book.

2. JDBC Goals
Few software packages are designed without goals in mind. JDBC is one that, because of
its many goals, drove the development of the API. These goals, in conjunction with early
reviewer feedback, have finalized the JDBC class library into a solid framework for
building database applications in Java.

The goals that were set for JDBC are important. They will give you some insight as to
why certain classes and functionalities behave the way they do. The eight design goals for
JDBC are as follows:

1. SQL Level API

The designers felt that their main goal was to define a SQL interface for Java. Although
not the lowest database interface level possible, it is at a low enough level for higherlevel tools and APIs to be created. Conversely, it is at a high enough level for application
programmers to use it confidently. Attaining this goal allows for future tool vendors to
generate JDBC code and to hide many of JDBCs complexities from the end user.
2. SQL Conformance
SQL syntax varies as you move from database vendor to database vendor. In an effort to
support a wide variety of vendors, JDBC will allow any query statement to be passed
through it to the underlying database driver. This allows the connectivity module to
handle non-standard functionality in a manner that is suitable for its users.
3. JDBC must be implemental on top of common database interfaces
The JDBC SQL API must sit on top of other common SQL level APIs. This goal
allows JDBC to use existing ODBC level drivers by the use of a software
interface. This interface would translate JDBC calls to ODBC and vice versa.
4. Provide a Java interface that is consistent with the rest of the Java system
Because of Javas acceptance in the user community thus far, the designers feel that they
should not stray from the current design of the core Java system.
5. Keep it simple

This goal probably appears in all software design goal listings. JDBC is no exception.
Sun felt that the design of JDBC should be very simple, allowing for only one method of
completing a task per mechanism. Allowing duplicate functionality only serves to
confuse the users of the API.
6. Use strong, static typing wherever possible
Strong typing allows for more error checking to be done at compile time; also, less error
appear at runtime.
7. Keep the common cases simple
Because more often than not, the usual SQL calls used by the programmer are simple
SELECTs, INSERTs, DELETEs and UPDATEs, these queries should be simple to
perform with JDBC. However, more complex SQL statements should also be possible.
5.
Finally we decided to proceed the implementation using Java Networking.
And for dynamically updating the cache table we go for MS Access database.
Java ha two things: a programming language and a platform.
Java is a high-level programming language that is all of the following

Simple Architecture-neutral
Object-oriented Portable
Distributed High-performance
Interpreted multithreaded
Robust Dynamic
Secure

Java is also unusual in that each Java program is both compiled and interpreted.
With a compile you translate a Java program into an intermediate language called
Java byte codes the platform-independent code instruction is passed and run on
the computer.

Compilation happens just once; interpretation occurs each time the program is
executed. The figure illustrates how this works.

You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether its a Java
development tool or a Web browser that can run Java applets, is an
implementation of the Java VM. The Java VM can also be implemented in
hardware.
Java byte codes help make write once, run anywhere possible. You can
compile your Java program into byte codes on my platform that has a Java
compiler. The byte codes can then be run any implementation of the Java VM.
For example, the same Java program can run Windows NT, Solaris, and
Macintosh.
6. Networking:7. TCP/IP stack
1. TCP/IP stack is shorter than the OSI one:
TCP is a connection-oriented protocol; UDP (User Datagram Protocol) is a
connectionless protocol.

2. IP datagrams
The IP layer provides a connectionless and unreliable delivery system. It considers each
datagram independently of the others. Any association between datagram must be
supplied by the higher layers. The IP layer supplies a checksum that includes its own
header. The header includes the source and destination addresses. The IP layer handles
routing through an Internet. It is also responsible for breaking up large datagram into
smaller ones for transmission and reassembling them at the other end.

3.UDP
UDP is also connectionless and unreliable. What it adds to IP is a checksum for the
contents of the datagram and port numbers. These are used to give a client/server model see later.
5. TCP
TCP supplies logic to give a reliable connection-oriented protocol above IP. It provides a
virtual circuit that two processes can use to communicate.
6. Internet addresses
In order to use a service, you must be able to find it. The Internet uses an address scheme
for machines so that they can be located. The address is a 32 bit integer which gives the
IP address. This encodes a network ID and more addressing. The network ID falls into
various classes according to the size of the network address.

7. Network address
Class A uses 8 bits for the network address with 24 bits left over for other addressing.
Class B uses 16 bit network addressing. Class C uses 24 bit network addressing and class
D uses all 32.
8. Subnet address
Internally, the UNIX network is divided into sub networks. Building 11 is currently on
one sub network and uses 10-bit addressing, allowing 1024 different hosts.
9. Host address
8 bits are finally used for host addresses within our subnet. This places a limit of 256
machines that can be on the subnet.

10. Total address

The 32 bit address is usually written as 4 integers separated by dots.

11. Port addresses
A service exists on a host, and is identified by its port. This is a 16 bit number. To send a
message to a server, you send it to the port for that service of the host that it is running
on. This is not location transparency! Certain of these ports are "well known".
Sockets:-

A socket is a data structure maintained by the system to handle network connections. A

socket is created using the call socket. It returns an integer that is like a file descriptor. In
fact, under Windows, this handle can be used with Read File and Write File functions.
#include <sys/types.h>
#include <sys/socket.h>
int socket(int family, int type, int protocol);
Here "family" will be AF_INET for IP communications, protocol will be zero, and type
will depend on whether TCP or UDP is used. Two processes wishing to communicate
over a network create a socket each. These are similar to two ends of a pipe - but the
actual pipe does not yet exist.
JFree Chart
JFreeChart is a free 100% Java chart library that makes it easy for developers to display
professional quality charts in their applications. JFreeChart's extensive feature set
includes:A consistent and well-documented API, supporting a wide range of chart types;
A flexible design that is easy to extend, and targets both server-side and client-side
applications; Support for many output types, including Swing components, image files
(including PNG and JPEG), and vector graphics file formats (including PDF, EPS and
SVG); JFreeChart is "open source" or, more specifically, free software. It is distributed
under the terms of the GNU Lesser General Public Licence (LGPL), which permits use in
proprietary applications.
Map Visualizations
Charts showing values that relate to geographical areas. Some examples include: (a)
population density in each state of the United States, (b) income per capita for each
country in Europe, (c) life expectancy in each country of the world. The tasks in this

project include:Sourcing freely redistributable vector outlines for the countries of the
world, states/provinces in particular countries (USA in particular, but also other areas);
Creating an appropriate dataset interface (plus default implementation), a rendered, and
integrating this with the existing XYPlot class in JFreeChart; Testing, documenting,
testing some more, documenting some more.
Time Series Chart Interactivity
Implement a new (to JFreeChart) feature for interactive time series charts --- to display a
separate control that shows a small version of ALL the time seriesdata, with a sliding
"view" rectangle that allows you to select the subset of the time series data to display in
the main chart.
Dashboards

There is currently a lot of interest in dashboard displays. Create a flexible dashboard

mechanism that supports a subset of JFreeChart chart types (dials, pies, thermometers,
bars, and lines/time series) that can be delivered easily via both Java Web Start and an
applet.
Property Editors
The property editor mechanism in JFreeChart only handles a small subsetof the properties
that can be set for charts. Extend (or reimplement) this mechanism to provide greater
end-user control over the appearance of the charts.

What is Database?
A database is a separate application that stores a collection of data. Each database has one
or more distinct APIs for creating, accessing, managing, searching, and replicating the
data it holds.
Other kinds of data stores can be used, such as files on the file system or large hash tables
in memory but data fetching and writing would not be so fast and easy with those type of
systems.
So now a days we use relational database management systems (RDBMS) to store and
manager huge volume of data. This is called relational database because all the data is
stored into different tables and relations are established using primary keys or other keys
known as foreign keys.
A Relational DataBase Management System (RDBMS) is a software that:

Enables you to implement a database with tables, columns, and indexes.

Guarantees the Referential Integrity between rows of various tables.

Updates the indexes automatically.

Interprets an SQL query and combines information from various tables.

RDBMS Terminology:
Before we proceed to explain MySQL database system, lets revise few definitions related
to database.

Database: A database is a collection of tables, with related data.

Table: A table is a matrix with data. A table in a database looks like a simple
spreadsheet.

Column: One column (data element) contains data of one and the same kind, for
example the column postcode.

Row: A row (= tuple, entry or record) is a group of related data, for example the
data of one subscription.

Redundancy: Storing data twice, redundantly to make the system faster.

Primary Key: A primary key is unique. A key value can not occur twice in one
table. With a key you can find at most one row.

Foreign Key: A foreign key is the linking pin between two tables.

Compound Key: A compound key (composite key) is a key that consists of

multiple columns, because one column is not sufficiently unique.

Index: An index in a database resembles an index at the back of a book.

Referential Integrity: Referential Integrity makes sure that a foreign key value
always points to an existing row.

MySQL Database:
MySQL is a fast, easy-to-use RDBMS used being used for many small and big
businesses. MySQL is developed, marketed, and supported by MySQL AB, which is a
Swedish company. MySQL is becoming so popular because of many good reasons.

MySQL is released under an open-source license. So you have nothing to pay to

use it.
MySQL is a very powerful program in its own right. It handles a large subset of
the functionality of the most expensive and powerful database packages.

MySQL uses a standard form of the well-known SQL data language.

MySQL works on many operating systems and with many languages including
PHP, PERL, C, C++, JAVA etc.

MySQL works very quickly and works well even with large data sets.

MySQL is very friendly to PHP, the most appreciated language for web
development.

MySQL supports large databases, up to 50 million rows or more in a table. The

default file size limit for a table is 4GB, but you can increase this (if your
operating system can handle it) to a theoretical limit of 8 million terabytes (TB).

MySQL is customizable. The open source GPL license allows programmers to

modify the MySQL software to fit their own specific environments

SYSTEM STUDY

FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system
analysis the feasibility study of the proposed system is to be carried out. This is to ensure
that the proposed system is not a burden to the company. For feasibility analysis, some
understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

ECONOMICAL FEASIBILITY

TECHNICAL FEASIBILITY

SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have
on the organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the
developed system as well within the budget and this was achieved because most of the
technologies used are freely available. Only the customized products had to be purchased.
TECHNICAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed
system must have a modest requirement, as only minimal or null changes are required for
implementing this system.

SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not
feel threatened by the system, instead must accept it as a necessity. The level of
acceptance by the users solely depends on the methods that are employed to educate the

user about the system and to make him familiar with it. His level of confidence must be
raised so that he is also able to make some constructive criticism, which is welcomed, as
he is the final user of the system.
Algorithm:
UP-Growth:

Pseudo Code:
private void go() throws Exception {
//start timer

long start = System.currentTimeMillis();

// first we generate the candidates of size 1
createItemsetsOfSize1();
int itemsetNumber=1; //the current itemset being looked at
int nbFrequentSets=0;
while (itemsets.size()>0)
{
calculateFrequentItemsets();
if(itemsets.size()!=0)
{
nbFrequentSets+=itemsets.size();
log("Found "+itemsets.size()+" frequent itemsets of size " + itemsetNumber + "
(with support "+(minSup*100)+"%)");;
createNewItemsetsFromPreviousOnes();
}
itemsetNumber++;
}
//display the execution time
long end = System.currentTimeMillis();
log("Execution time is: "+((double)(end-start)/1000) + " seconds.");
log("Found "+nbFrequentSets+ " frequents sets for support "+(minSup*100)+"%
(absolute "+Math.round(numTransactions*minSup)+")");
log("Done");
}

SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub-assemblies, assemblies and/or a finished product It is
the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

TYPES OF TESTS

Unit testing
Unit testing involves the design of test cases that validate that the internal program logic
is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual
software units of the application .it is done after the completion of an individual unit
before integration. This is a structural testing, that relies on knowledge of its construction
and is invasive. Unit tests perform basic tests at component level and test a specific
business process, application, and/or system configuration. Unit tests ensure that each
unique path of a business process performs accurately to the documented specifications
and contains clearly defined inputs and expected results.

Integration testing

Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components
were individually satisfaction, as shown by successfully unit testing, the combination of
components is correct and consistent. Integration testing is specifically aimed at exposing
the problems that arise from the combination of components.
Functional test

Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes must
be considered for testing. Before functional testing is complete, additional tests are
identified and the effective value of current tests is determined.
System Test
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system
testing is the configuration oriented system integration test. System testing is based on
process descriptions and flows, emphasizing pre-driven process links and integration
points.
White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of
tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot see into it. The test
provides inputs and responds to outputs without considering how the software works.

6.1 Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be
conducted as two distinct phases.
Test strategy and approach
Field testing will be performed manually and functional tests will be written in detail.

Test objectives

All field entries must work properly.

Pages must be activated from the identified link.

The entry screen, messages and responses must not be delayed.

Features to be tested

Verify that the entries are of the correct format

No duplicate entries should be allowed

All links should take the user to the correct page.

Integration Testing

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by
interface defects.
The task of the integration test is to check that components or software applications, e.g.
components in a software system or one step up software applications at the company
level interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

Table Design:
admin:

prodetails:

deduplicate:

userdetails:

adminmsgs:

customermsgs:

purchase:

frequent:

Screen Shots:
Home:

Provider Signup:

Provider Login:

Provider Menu:

Available Items:

Add Item:

Admin Login:

Admin Menu:

Available Items:

Registered Users:

Customer Signup:

Customer Login:

Customer Menu:

Purchase:

Frequent Item:

Sample Coding:Home.jsp:

<%-Document : Home
Created on : Sep 17, 2013, 6:40:57 PM
Author

: selvarani

--%>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<style type="text/css">

.id1{font-size:40px; color:black}
.id2{font-size:20px; color:white}
.id3{font-size:15px; color:black}
.id4{font-size:20px; color:black}
.id5{font-size:25px; color:blue}

</style>
<script type="text/javascript">
function val()
{
alert("Please sign in if u are a REGISTERED user and SIGN UP if u are a NEW USER
");
}

function fun1()
{

var uid = document.f1.cuser;

var pass= document.f1.cpass ;
if(Email_validation(uid))
{
if(userpass_validation(pass))
{

return true;
}
}

return false;
}

function Email_validation(uid)
{
var uid_len = uid.value.length;
var reg = /^([A-Za-z0-9_\-\.])+@+[gmail]+\.([A-Za-z]{2,3})$/;
if (uid_len == 0)
{
alert('Mail Id Should Not be Empty');
uid.focus();
return false;
}
else if (reg.test(uid.value) == false)
{
alert('Invalid Mail Id.Gmail Address only
Acceptable.Example:Alice@gmail.com');
return false;
}

return true;
}

function userpass_validation(uid)
{
var uid_len = uid.value.length;
if (uid_len === 0 )
{
alert("Password should not be empty ");
uid.focus();
return false;
}
else
{

return true;
}
}

function fun2()
{
var c = document.f2.auser.value;
var d = document.f2.apass.value;

if(c=="")
{
alert("Enter your username");
document.f2.auser.focus();
return false;
}
if(d=="")
{
alert("Enter your password");
document.f2.apass.focus();
return false;
}
}

</script>
<title>HOME</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="white">
<table align="center" border="0" width="100%" height="100">
<tr>
<td>
<table align="center" bgcolor="maroon" width="100%" height="100">
<tr>
<td class="id1"><center><font size="8" color="white"><b>Efficient Algorithms for
Mining High Utility Itemsets from Transactional Databases</b></font></center></td>
</tr>
</table>
<table align="center" bgcolor="#cccccc" width="100%" height="30">
<tr>
<td align="center" class="id4"> <a href="Home.jsp"><font
color="#666600">Home</font></a></td>
<td align="center" class="id4"><a href="About.html"><font
color="#666600">About
us</font></a></td>
<td align="center" class="id4"><a href="Contact.html"><font
color="#666600">Contact</font></a></td>
</tr>

</table>
</td>
</tr>
</table>
<p>&nbsp;</p>

<%
String Servlet_Msg = (String) session.getAttribute("msg");
String color = (String) session.getAttribute("color");
if (Servlet_Msg != null && color != null) {
%>
<left>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<blink> <font
size="3" color="<%=color%>"><%=Servlet_Msg%></font></blink></left><br><br><
%
session.removeAttribute("msg");
session.removeAttribute("color");
}%>
<table align="left" bgcolor="cccccc" border="2" bordercolor="maroon" width="30%"
height="70%">
<tr valign="top">
<td height="337">

<form name="f1" action="Logincheck1" method="post" onSubmit="return fun1()">

<table align="center" bgcolor="white" width="100%" height="135">
<tr><p align="center" class="id4">CUSTOMER LOGIN</p></tr>
<tr>
<td class="id3">Mail Id :</td>
<td><input type="text" name="cuser"></td>
</tr>
<tr>
<td class="id3">Password :</td>
<td><input type="password" name="cpass"></td>
</tr>
<tr><td></td><td class="id3"><a href="forgot.jsp"></a></td></tr>
<tr><td height="61" class="id3"><a href="CustomerReg.jsp">Sign Up</a></td>
<td><input type="submit" name="sub" value="Login">&nbsp;&nbsp; <input
type="reset" name="reset" value="Clear"></td></tr>
</table>
</form>
<p>&nbsp;</p>
<form action="Logincheck" name="f2" onSubmit="return fun2()" method="post">
<table align="center" bgcolor="white" width="100%" height="143">
<tr><p align="center" class="id4">PROVIDER LOGIN</p></tr>

<tr>

<td class="id3">Username :</td>

<td><input type="text" name="auser"></td>
</tr>
<tr>
<td class="id3">Password :</td>
<td><input type="password" name="apass"></td>
</tr>

<tr><td height="61" class="id3"><a href="ProviderReg.jsp">Sign Up</a></td>

<td><input type="submit" name="sub" value="Login">&nbsp;&nbsp; <input
type="reset" name="reset" value="Clear"></td></tr>

</table>
</form>
</td>
</tr>

</table>
<form action="#" onSubmit="return val()">
<table align="center" bgcolor="#cccccc" border="3" bordercolor="maroon"
width="61%" height="448" >

<tr valign="top"><td height="394"><p

class="id5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n

bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;<font color="#000099">&nbsp;</font>
<input class="id2" style="background-color: maroon" type="submit" name="sub"
value="ONLINE">
<font color="#000099">SHOPPING FROM YOUR HOME</font> </p> <p
class="id2">&nbsp;&nbsp;<font color="#660000">We provide electronic goods
and Computer products right in your home. </font></p>
<table align="left" width="45%" height="300">
<tr>
<td align="center" class="id4"><b>COMPUTER PRODUCTS</b></td>
</tr>
<tr><td align="center" class="id4">* Monitors<font
color="#999999">........</font></td></tr>
<tr><td align="center" class="id4">* Mouses<font
color="#999999">..........</font></td></tr>
<tr><td align="center" class="id4">* CPU<font
color="#999999">...............</font></td></tr>
<tr><td align="center" class="id4">* Key Board<font
color="#999999">.....</font></td></tr>
<tr><td align="center" class="id4">* Web cameras</td></tr>

</table>
<table align="right" width="45%" height="300">
<tr><td align="center" class="id4"><b>ELECTRONIC GOODS</b></td></tr>
<tr><td align="center" class="id4">* Televisions<font
color="#999999">..........</font></td></tr>

<tr><td align="center" class="id4">* Home Appliances</td></tr>

<tr><td align="center" class="id4">* DVD players<font
color="#999999">.......</font></td></tr>
<tr><td align="center" class="id4">* Fans<font
color="#999999">...................</font></td></tr>
<tr><td align="center" class="id4">* Glasses<font
color="#999999">.............</font></td></tr>
</table>
<p>&nbsp;</p>
<table align="center" width="90%" height="40" bgcolor="maroon" ><tr><td
class="id2">&nbsp;&nbsp;&nbsp;Phone Orders : 044749638964&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Free Home
delivery</td></tr></table>
</td></tr>

</table>
</form>
</body>
</html>
ProviderMenu.jsp:

<%-Document : ProviderMenu
Created on : Sep 17, 2013, 6:58:45 PM
Author

: selvarani

--%>

<%@ page import="java.sql.*" %>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<style type="text/css">
.id1{font-size:40px; color:black}
.id2{font-size:20px; color:black}
.id3{font-size:15px; color:black}
.id4{font-size:20px; color:black}
</style>

<title>PROVIDER MENU</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="white">
<table align="center" border="0" width="100%" height="100">
<tr>
<td>
<table align="center" bgcolor="maroon" width="100%" height="100">
<tr>

<td class="id1"><center><font size="8" color="white"><b>Efficient Algorithms for

Mining High Utility Itemsets from Transactional Databases</b></font></center></td>
</tr>
</table>
<table align="center" bgcolor="#cccccc" width="100%" height="30">
<tr>
<td align="center"> <a href="Logout.jsp"><font
color="#666600">Home</font></a></td>
<td align="center"><a href="Logout.jsp"><font
color="#666600">SignOut</font></a></td>
</tr>

</table>
</td>
</tr>
</table>

<p>&nbsp;</p>

<table align="left" bgcolor="white" width="20%" height="135" border="2"

bordercolor="#cccccc">

<tr>
<td align="center" class="id4">Welcome <%=session.getValue("name")%></td>
</tr>

</table>

<table align="center" bgcolor="white" width="40%" height="300" border="2"

bordercolor="#cccccc">

<tr>
<td align="center" class="id2"><a href="Itemlist.jsp">Available Items</a></td>
</tr>
<tr>
<td align="center" class="id2"><a href="Additem.jsp">Add Item(s)</a></td>
</tr>
<tr>
<td align="center" class="id2"><a href="Frequent.jsp">Finding Frequent
Items</a></td>
</tr>
</table>

</body>
</html>
UserMenu.jsp:

<%-Document : UserMenu
Created on : Sep 17, 2013, 7:57:46 PM
Author

: selvarani

--%>

<%@page import="Connection.DB"%>
<%@page import="java.io.File"%>
<%@page import="java.io.FileInputStream"%>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@ page import="java.sql.*" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>

<style type="text/css">
.id1{font-size:40px; color:black}
.id2{font-size:20px; color:black}
.id3{font-size:15px; color:black}
.id4{font-size:20px; color:black}
</style>
<%
if (session.getValue("name") == null) {
session.invalidate();
session=request.getSession(true);
session.setAttribute("msg", "Sorry!!! Your Login Time Out.Please Login Again ");
session.setAttribute("color", "red ");
response.sendRedirect("Home.jsp");

%>
<title>USER MENU</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="white">
<table align="center" border="0" width="100%" height="119">

<tr>
<td>
<table align="center" bgcolor="maroon" width="100%" height="100">
<tr>
<td class="id1"><center><font size="8" color="white"><b>Efficient Algorithms for
Mining High Utility Itemsets from Transactional Databases</b></font></center></td>
</tr>
</table>
<table align="center" bgcolor="#cccccc" width="100%" height="30">
<tr>
<td align="center"> <a href="Logout.jsp"><font
color="#666600">Home</font></a></td>
<td align="center"> <a href="Logout.jsp"><font color="#666600">Sign
out</font></a></td>
</tr>

</table>
</td>
</tr>
</table>
<p>&nbsp;</p>

<table align="left" bgcolor="white" width="26%" height="185">

<tr>

<td align="center" class="id2">Welcome <%=session.getValue("name")

%>&nbsp;</td>
</tr>
<tr>
<td align="center" class="id2"><a href="UpdateAcc.jsp">My Account Details</a></td>
<td></td>
</tr>

<tr>
<td align="center" class="id2"><a href="SendMsg.jsp">Message to
Admin</a></td></tr>
<tr>
<td align="center" class="id2"><a href="ViewOriginal.jsp">View Original
Product</a></td></tr>
<tr><td align="center" class="id2"><a href="UserMsgbox.jsp">Message
box</a></td></tr>
<tr>
<td align="center" class="id2"><a href="Logout.jsp">Sign out</a></td></tr>
</table>
<form action="" name="f1" method="post" onSubmit="return val()">
<table width="73%" height="382" border="1" align="right" cellpadding="0"
cellspacing="0" bgcolor="white">
<tr>
<td height="56" colspan="12" align="center" background="Images/bg_thead.gif"
class="id2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

ITEMS LIST</td>
</tr>
<tr> <th width="69" height="62" align="left" class="id2">ProductID </th>

<th width="263" height="62" align="left" class="id2"> Name </th>

<th width="124" class="id2" align="left">Rate

</th>
<th width="263" height="62" align="left" class="id2">Description </th>
<th width="237" class="id2" align="left">AvailableCount</th>
<th width="237" class="id2" align="left">Purchase</th>
</tr>
<%

ResultSet rs=null;
String pro = null,pid = null,des=null;
int rate = 0,count=0;
try
{

DB Db=new DB();

rs = Db.Select("select * from prodetails");

int i=1;
while(rs.next())
{
pid = rs.getString(1);
pro =rs.getString(2);
rate =rs.getInt(3);
des =rs.getString(4);
count=rs.getInt(5);

%>
<tr>
<td class="id2"> <%=pid%> </td>
<td class="id2"> <%=pro%> </td>
<td class="id2"><%=rate%> </td>
<td class="id2"><%=des%> </td>
<td class="id2"><%=count%> </td>

<td><a href="mail?pid=<%=pid%>&mail=<%=session.getValue("mail")%>">
Go to Purchase</a> </td>
</tr>
<%
i++;
}
rs.close();

}
catch(Exception e)
{
out.println(e.getMessage());
}

%>
<tr>
<td></td>
<td></td>
<td valign="top"> </p>
<td valign="top">&nbsp; </td>
</td></tr>
</table>

</form>
<!-<script type="text/javascript">
function val()
{
if(document.f1.p1.checked==true)
{
if(document.f1.q1.value=="")
{
alert("Select quantity1");
document.f1.q1.focus();
return false;
}
}

if(document.f1.p2.checked==true)
{
if(document.f1.q2.value=="")

{
alert("Select quantity2");

document.f1.q2.focus();
return false;
}
}

if(document.f1.p3.checked==true)
{
if(document.f1.q3.value=="")

{
alert("Select quantity3");
document.f1.q3.focus();
return false;
}
}

if(document.f1.p1.checked==false&&document.f1.p2.checked==false&&document.f1.p3
.checked==false)
{
alert("Select Product");
return false;
}
}

</script>
-->
</body>

</html>

AdminMenu.java:

<%-Document : AdminMenu
Created on : Sep 17, 2013, 6:58:11 PM
Author

: selvarani

--%>

<%@ page import="java.sql.*" %>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<style type="text/css">
.id1{font-size:40px; color:black}
.id2{font-size:20px; color:black}

.id3{font-size:15px; color:black}
.id4{font-size:20px; color:black}
</style>
<%
if (session.getValue("name") == null) {
session.invalidate();
session=request.getSession(true);
session.setAttribute("msg", "Sorry!!! Your Login Time Out.Please Login Again ");
session.setAttribute("color", "red ");
response.sendRedirect("Home.jsp");

%>
<title>ADMIN MENU</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="white">
<table align="center" border="0" width="100%" height="100">
<tr>
<td>
<table align="center" bgcolor="maroon" width="100%" height="100">

<tr>
<td class="id1"><center><font size="8" color="white"><b>Efficient Algorithms for
Mining High Utility Itemsets from Transactional Databases</b></font></center></td>
</tr>
</table>
<table align="center" bgcolor="#cccccc" width="100%" height="30">
<tr>
<td align="center"><a href="Logout.jsp"><font
color="#666600">Home</font></a></td>
<td align="center"><a href="Logout.jsp"><font color="#666600">Sign
out</font></a></td>
</tr>

</table>
</td>
</tr>
</table>

<p>&nbsp;</p>

<table align="left" bgcolor="white" width="20%" height="135" border="2"

bordercolor="#cccccc">
<tr>
<td align="center" class="id4">Welcome <%=session.getValue("name")%></td>
</tr>
<tr>
<td align="center"><a href="Msgbox.jsp">View Message box</a></td>
</tr>

</table>

<table align="center" bgcolor="white" width="40%" height="300" border="2"

bordercolor="#cccccc">
<tr>
<td align="center" class="id2"><a href="Regcus.jsp">Registered Customers</a></td>
</tr>
<tr>
<td align="center" class="id2"><a href="AvailItemlist.jsp">Available Items</a></td>
</tr>
<tr>
<td align="center" class="id2"><a href="GA.jsp">Apply GA</a></td>
</tr>
<tr>

<td align="center" class="id2"><a href="Viewdeduplicate.jsp">View

DeDuplication</a></td>
</tr>
</table>

</body>
</html>
LoginCheck.java:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/

import Connection.DB;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.ResultSet;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

/**
*
* @author selvarani
*/
@WebServlet(urlPatterns = {"/Logincheck"})
public class Logincheck extends HttpServlet {

/**
* Processes requests for both HTTP
* <code>GET</code> and
* <code>POST</code> methods.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {

response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
HttpSession session=request.getSession(true);
try
{
DB Db=new DB();

String mail = request.getParameter("auser");

String pass = request.getParameter("apass");
if(mail.compareToIgnoreCase("admin")==0 &&
pass.compareToIgnoreCase("data")==0)
{
session.putValue("name",mail);

response.sendRedirect("AdminMenu.jsp");

}
else{
String s = "select * from admin ";

ResultSet rs = Db.Select(s);
boolean st=false;
while(rs.next())

{
if(mail.compareTo(rs.getString("name"))==0 &&
pass.compareTo(rs.getString("pass"))==0)
{
st=true;
break;
}
else
st=false;
}
rs.close();
if(st==true)
{
session.putValue("name",mail);
response.sendRedirect("ProviderMenu.jsp");
}
else
{
session.setAttribute("msg", "InCorrect Details");
session.setAttribute("color", "red");
response.sendRedirect("Home.jsp");
System.out.print("xxxxxxxxxx");
}

catch(Exception x)
{
out.println(x);
}
}

// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +

sign on the left to edit the code.">
/**
* Handles the HTTP
* <code>GET</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)

throws ServletException, IOException {

processRequest(request, response);
}

/**
* Handles the HTTP
* <code>POST</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Returns a short description of the servlet.
*

* @return a String containing servlet description

*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>
}
Logincheck1.java:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/

import Connection.DB;
import java.io.File;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.ResultSet;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

/**
*
* @author selvarani
*/
@WebServlet(urlPatterns = {"/Logincheck1"})
public class Logincheck1 extends HttpServlet {

/**
* Processes requests for both HTTP
* <code>GET</code> and
* <code>POST</code> methods.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {

response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
HttpSession session=request.getSession(true);
try
{
DB Db=new DB();
String name ="";
String mail = request.getParameter("cuser");
String pass = request.getParameter("cpass");

String s = "select * from userdetails";

ResultSet rs = Db.Select(s);
boolean st=false;
while(rs.next())
{
if(mail.compareTo(rs.getString("nmail"))==0 &&
pass.compareTo(rs.getString("npass"))==0)
{
name=rs.getString(1);
st=true;
break;
}

else
st=false;
}
rs.close();
if(st==true)
{

session.putValue("name",name);
session.putValue("mail",mail);
response.sendRedirect("UserMenu.jsp");
}
else
{
session.setAttribute("msg", "InCorrect Details");
session.setAttribute("color", "red");
response.sendRedirect("Home.jsp");
System.out.print("xxxxxxxxxx");
}

catch(Exception x)

{
out.println(x);
}
}

// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +

sign on the left to edit the code.">
/**
* Handles the HTTP
* <code>GET</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**

* Handles the HTTP

* <code>POST</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Returns a short description of the servlet.
*
* @return a String containing servlet description
*/
@Override
public String getServletInfo() {
return "Short description";

}// </editor-fold>
}
Update.java:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/

import Connection.DB;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

/**
*
* @author selvarani
*/

@WebServlet(urlPatterns = {"/Update"})
public class Update extends HttpServlet {

/**
* Processes requests for both HTTP
* <code>GET</code> and
* <code>POST</code> methods.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
HttpSession session=request.getSession(true);
try
{
String pid = request.getParameter("name");
String pro = request.getParameter("pro");

String rate = request.getParameter("rate");

String des = request.getParameter("des");
String profit = request.getParameter("profit");
int r=Integer.parseInt(rate);
String count = request.getParameter("count");
int c=Integer.parseInt(count);

DB Db=new DB();
String s = "update prodetails set pro='"+pro+"',rate='"+rate+"'
,des='"+des+"',Profit='"+profit+"',count="+c+" where
Provider='"+session.getValue("name")+"' and pid='"+pid+"'";
int x=Db.Insert(s);

if(x!=0)
{
session.setAttribute("msg", "Succesfully Updated");
session.setAttribute("color", "green");
response.sendRedirect("Itemlist.jsp");
}
else
{
session.setAttribute("msg", "Updation Failed");
session.setAttribute("color", "red");

response.sendRedirect("Itemlist.jsp");
System.out.print("Failed");
}
}
catch(Exception e)
{
System.out.print(e);
}
}

// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +

sign on the left to edit the code.">
/**
* Handles the HTTP
* <code>GET</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)

throws ServletException, IOException {

processRequest(request, response);
}

/**
* Handles the HTTP
* <code>POST</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Returns a short description of the servlet.
*

* @return a String containing servlet description

*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>
}
Delete.java:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/

import Connection.DB;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.ResultSet;
import java.sql.SQLException;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;

/**
*
* @author selvarani
*/
@WebServlet(urlPatterns = {"/Delete"})
public class Delete extends HttpServlet {

/**
* Processes requests for both HTTP
* <code>GET</code> and
* <code>POST</code> methods.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException {

response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
ResultSet rs=null;
HttpSession session=request.getSession(true);

int name=(Integer.parseInt(request.getParameter("name")));

out.print(name);

try
{
DB Db=new DB();
String sql="delete from prodetails where pid="+name+" and
Provider='"+session.getValue("name")+"'";
int x=Db.Insert(sql);

if(x!=0)
{
session.setAttribute("msg", "Succesfully Deleted");
session.setAttribute("color", "green");
response.sendRedirect("Itemlist.jsp");
}
else

{
session.setAttribute("msg", "Deletion Failed");
session.setAttribute("color", "red");
response.sendRedirect("Itemlist.jsp");
out.println("error in server.. try after some time... <a
href=\"tlmailview.jsp\">Back</a>");
}

}
catch(Exception e1) { System.out.println("Database error"+e1.getMessage()); }

// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +

sign on the left to edit the code.">
/**
* Handles the HTTP
* <code>GET</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs

* @throws IOException if an I/O error occurs

*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Handles the HTTP
* <code>POST</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Returns a short description of the servlet.
*
* @return a String containing servlet description
*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>
}
ProviderReg.java:
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/

import Connection.DB;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;

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

/**
*
* @author selvarani
*/
@WebServlet(urlPatterns = {"/ProviderReg"})
public class ProviderReg extends HttpServlet {

/**
* Processes requests for both HTTP
* <code>GET</code> and
* <code>POST</code> methods.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/

protected void processRequest(HttpServletRequest request, HttpServletResponse

response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
HttpSession session=request.getSession(true);
try
{

String nname = request.getParameter("nname");

String npass = request.getParameter("npass");

DB Db=new DB();
String sql = "insert into admin values('"+nname+"','"+npass+"')";

int x= Db.Insert(sql);

if(x!=0)
{
session.setAttribute("msg", "Successfully Registered");
session.setAttribute("color", "green");

out.println("Successfully registered");
response.sendRedirect("Home.jsp");
}
else
{
out.print("Failed");
}

catch(Exception e)
{
out.println(e);
}
}

// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the +

sign on the left to edit the code.">

/**
* Handles the HTTP
* <code>GET</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Handles the HTTP
* <code>POST</code> method.
*
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs

* @throws IOException if an I/O error occurs

*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Returns a short description of the servlet.
*
* @return a String containing servlet description
*/
@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>
}
Conclusion:In this project, we have proposed two efficient algorithms named UP-Growth and UPGrowth+ for mining high utility itemsets from transaction databases. A data structure
named UP-Tree was proposed for maintaining the information of high utility itemsets.
PHUIs can be efficiently generated from UP-Tree with only two database scans.
Moreover, we developed several strategies to decrease overestimated utility and enhance
the performance of utility mining. In the experiments, both real and synthetic data sets

were used to perform a thorough performance evaluation. Results show that the strategies
considerably improved performance by reducing both the search space and the number of
candidates. Moreover, the proposed algorithms, especially UP-Growth+, outperform the
state of- the-art algorithms substantially especially when databases contain lots of long
transactions or a low minimum utility threshold is used.
Future Enhancement:We will test the project to find the frequent itemsets for large data sets. And in this
we used UP-Growth+ algorithm for online shopping Later we can implement this same
algorithm efficiently for different application to find the frequent itemsets.
References:1. R. Agrawal and R. Srikant, Mining Sequential Patterns, Proc. 11th Intl Conf.
Data Eng., pp. 3-14, Mar. 1995.
2. C.F. Ahmed, S.K. Tanbeer, B.-S. Jeong, and Y.-K. Lee, Efficient Tree Structures
for High Utility Pattern Mining in Incremental Databases, IEEE Trans.
Knowledge and Data Eng., vol. 21, no. 12, pp. 1708-1721, Dec. 2009.
3. C.H. Cai, A.W.C. Fu, C.H. Cheng, and W.W. Kwong, Mining Association Rules
with Weighted Items, Proc. Intl Database Eng. and Applications Symp.
(IDEAS 98), pp. 68-77, 1998.
4. R. Chan, Q. Yang, and Y. Shen, Mining High Utility Itemsets, Proc. IEEE Third
Intl Conf. Data Mining, pp. 19-26, Nov. 2003.
5. J.H. Chang, Mining Weighted Sequential Patterns in a Sequence Database with a
Time-Interval Weight, Knowledge-Based Systems, vol. 24, no. 1, pp. 1-9, 2011.
6. M.-S. Chen, J.-S. Park, and P.S. Yu, Efficient Data Mining for Path Traversal
Patterns, IEEE Trans. Knowledge and Data Eng., vol. 10, no. 2, pp. 209-221,
Mar. 1998.
7. C. Creighton and S. Hanash, Mining Gene Expression Databases for Association
Rules, Bioinformatics, vol. 19, no. 1, pp. 79-86, 2003.
8. M.Y. Eltabakh, M. Ouzzani, M.A. Khalil, W.G. Aref, and A.K. Elmagarmid,
Incremental Mining for Frequent Patterns in Evolving Time Series Databases,
Technical Report CSD TR#08- 02, Purdue Univ., 2008.

9. A. Erwin, R.P. Gopalan, and N.R. Achuthan, Efficient Mining of High Utility
Itemsets from Large Data Sets, Proc. 12th Pacific-Asia Conf. Advances in
Knowledge Discovery and Data Mining (PAKDD), pp. 554-561, 2008.
10. E. Georgii, L. Richter, U. Ru ckert, and S. Kramer, Analyzing Microarray Data
Using Quantitative Association Rules, Bioinformatics, vol. 21, pp. 123-129,
2005.