CHAPTER 1 : INTRODUCTION

1
1.1 Company Profile

SSP Technology is a leader in Software Development and empowers

IT individuals with competitive advantage. SSP Technology dedicates
itself to simplify the technology trends with its great R&D Division.
SSP Technology is an Indian Software Development Company. A
rapidly growing software company with a team of experienced
intellectuals working in various technologies. It deals with Product and
Service based applications in all major areas. We are committed to the
qualitative, efficiency, innovativeness and timeliness of our
deliverables with high focus on maximum customer satisfaction. SSP
Technology is a high end full service IT solution Company based in
India. Established in 2010, we are pioneer in providing total offshore
and onshore web based solutions for small to large corporate
companies. SSP Technology provides IT services to clients globally as
partners to conceptualize and realize technology driven business
transformation initiatives. Today we are comprised of a team of
programming technicians, designers, and marketing executives-
selectively chosen to lead our clients in their IT solutions.
SSP Technology has grown from strength to strength in both our
Business and Software Solutions arena. From our IT Consulting as
well as Custom Application Development, Web Development and E-
commerce all of which help our customers with their diverse yet
demanding needs. We are geared towards generating business value to
the companies by providing expertise personnel and software services.

2
Our Vision
"To Become a Complete Software Company with the Quality
performances and to develop success path for every industry's growth
and progress."

Our Mission
"To provide multiple solutions for each and every problem to achieve
the goal of organization."

Our Value
We at SSP Technology aim and are continuously approaching towards
customer satisfaction and create a value to customer along with
yielding knowledge for us by maintaining a motivated workforce.
Our Services
SSP technology provides various Software Development services to
the clients located worldwide in order to rationalize their business
processes and e-enabling their business. We, at SSP Technology
strongly believe that technology is a true business enhancer and you
should not implement technology for the sake of it. That's why; we
help you make best use of information technology. With the use of our
services such as application development, application migration and
application maintenance for your existing applications, you can
formulate the best possible use of technology. We are a team of
professional organization teamed by competent, committed, qualified
and experienced personnel in various field. With the help of our
commitment to professionalism and excellence. The programmers we
design are developed to meet specific organizational needs. We provide
a service that provides clients with value for each rupee invested. So

3
feel free to come forward and avail the opportunity of getting
reasonably priced consultancy services from us.

IT PROVIDES THE FOLLOWING SERVICES TO THE

CLIENTS:-
Technology Services-
Data Warehousing
Data Migration
High Availability
Internet of Things
Java Technology
Linux and Unix
Open Source
Optimized Solution
Web Development Services
Security
Server Consolidation
SEO Services
Service Oriented Architecture
Windows and Dot Net
Virtualization

Business Services-

Business Analytics
Business Process Services

4
 Customer Experience
Customer Relationship Management
Enterprise Content Management
Enterprise Management
Financial Management
Governance, Risk, and Compliance
Human Capital Management
Marketing Automation & Utilities Services
Master Data Management & Retail Services
Database and IT Infrastructure
Project Portfolio Management

Cloud Services Mobile Services and Industrial Services

Aerospace and Defence

Automotive
Chemicals
Communications
Consumer Goods
Education and Research
Engineering and Construction
Financial Services
Healthcare

1.2 Existing system & need of the system

TimeDelay
User has to access or utilize all services offered by all the service
providers. Since all the services are offered by different organizations
it takes lot of time to make recharges of each and every organization
.
Redundancy
There are different recharging coupons available for each and every

5
service provider but the problem is shop keeper has to maintain all the
things and has to be given to the customer what they are looking for.
Shop Keeper should have the knowledge of all the coupons available.
It is very difficult for any one to maintain these many numbers of
coupons.

Accuracy
Since there is much service providers and so many recharge coupons
of each and every service providers there is a problem for the shop
keeper to maintain all the coupons and the problem with the individual
user that they have to make the manual recharging facility and it
ultimately becomes a headache to all kind of users.

Conclusion:
Online Mobile Recharge project provides all the information related to
all the Service Providers and also gives the facility of making the
recharging for all the Service Providers under one application at any
time and from anywhere. It is beneficial for both individual user and
also the people who are into business like the shop keepers. It also
provides the complete information of all the recharge coupons of
different Service Providers to all users.
1.2.1 Need for System

6
To enhance the working of the organization, which was completely
handled manually, the improvements was thought on the basis of
computerizing the major activities. They are:

User friendly: This system provides user friendliness.

Because in the existing system register work was very difficult
to handle.

Data Security: The proposed will also prevent

unauthorized access to the system. At the very beginning, the
administrator enters the username and password and checks the
permission to use that software.

Data redundancy: The data is stored only once which

can be accessed at anytime and at any place. So it can be
minimized but cannot be removed completely.

Easy to access: Data can be accessed easily.

Cost Reduction: It requires less amount of cost as

compared to existing system.

Time & efforts reduction: It requires fewer amounts of

time and efforts.

7
 Security mechanism: Database can be secured by
applying password in encryption and decryption techniques.

Concurrency control: This database provides

mechanism to provide information and ensure the correctness
of the data.

Earning : For extra earning income with

referralprogram.

1.3 Scope Of Work

8
Globalsoft Technology is the website development company .It works
for all type of client's that is big,medium and small client also .Our
company has many customers for website development project and it is
the core work of the company .we have been appointed to work for
developing a new website which will be use for all type of recharges
like Mobile,DTH,Datacard according to our client request.
This site have been provide many features like authentication
and authorization for accessing pages,any user can sign up and login
with its own created id and password and can do recharge online easily.
This pay u circle website consist of following models:
I) Admin Module
II)Customer or Member Module
I)Admin Module:
Admin module is used to handle user .Admin can do many
function like he can add the services like Mobile,DTH,Datacard can
also add the customer .Admin can update and delete the records which
he may think of no use .Admin can search the particular user, can send
the messages to user ,admin is able to deactivate user account which is
not active long period of time.
If user have any problem he has to send the ticket to admin,then
admin will solve the problem.
Admin can generate many functions which are as follows:
i) All customer or user report.
ii) Total customer count report.
iii) Date to date earning report.
iv) Total user balance report.
v) Report of recent user transfer point.
vi) Recent recharge report.

9
vii) Recent user load amount report .
II) Customer or Member Module:
One's the person will become the member of the site then his
able to see his profile any time by using his id and password which is
unique for every user .customer can help other customer to transfer
point,customer can see his balance of his wallet and can recharge from
the wallet amount or by using this credit or debit ,customer can share
promotional link on various website like Facebook ,Twitter,Google+ or
share link via message,also by using whatup,email account like
bluetooth transfer or text message.
Customer have some rights given by the site like he can view
his recharge status,his able to see the transfer point report and can see
his recharge history.

1.4 Operating Environments - Hardware & Software

10
 Hardware Specifications (Client Side)
Minimum 512MB and
RAM
above
Minimum 40 GB and
Hard Disk
above
Pentium-IV and
Processor
above

Hardware Specifications (Server Side)

Minimum 2GB and
RAM
above
Minimum 80 GB and
Hard Disk
above
Pentium-IV and
Processor
above

Software Specifications (Client Side)

Operating System Windows XP/Later
Internet Explorer-
Web Browser 6/Later
Mozilla Firefox

Software Specifications (Server Side)

Operating System Windows XP/Later
Internet Explorer-6/Later
Web Browser
Mozilla Firefox
Technology Java, J2EE. Strut 2.0

11
Database MYSQL
Eclipse Indigo
Development Tool(Editor) Jasper Report
iReport
Server Tomcat 7.0

1.5 Detail Description of Technology Used

Java is a powerful, cross-platform, object-oriented programming
language suitable for writing anything from a distributed application
that runs on a corporate network to a database-driven Web site to host
your personal photo gallery.

12
Java and Open Source
In 2006 Sun started to make Java available under the GNU General
Public License (GPL). Oracle continues this project called OpenJDK.

Java virtual machine

The Java virtual machine (JVM) is a software implementation of a
computer that executes programs like a real machine.

The Java virtual machine is written specifically for a specific operating

system, e.g., for Linux a special implementation is required as well as
for Windows.

Characteristics of Java
The target of Java is to write a program once and then run this program
on multiple operating systems.

Java has the following properties:

Platform independent: Java programs use the Java virtual

machine as abstraction and do not access the operating system
directly. This makes Java programs highly portable. A Java
program (which is standard-compliant and follows certain rules)
can run unmodified on all supported platforms, e.g., Windows or
Linux.

Object-orientated programming language: Except the

primitive data types, all elements in Java are objects.

Strongly-typed programming language: Java is strongly-

typed, e.g., the types of the used variables must be pre-defined and

13
 conversion to other objects is relatively strict, e.g., must be done in
most cases by the programmer.

Interpreted and compiled language: Java source code is

transferred into the bytecode format which does not depend on the
target platform. These bytecode instructions will be interpreted by
the Java Virtual machine (JVM). The JVM contains a so called
Hotspot-Compiler which translates performance critical bytecode
instructions into native code instructions.

Automatic memory management: Java manages the memory

allocation and de-allocation for creating new objects. The program
does not have direct access to the memory. The so-called garbage
collector automatically deletes objects to which no active pointer
exists.

Garbage collector:The JVM automatically re-collects the

memory which is not referred to by other objects. The Java
garbage collector checks all object references and finds the objects
which can be automatically released.

While the garbage collector relieves the programmer from the need
to explicitly manage memory, the programmer still need to ensure
that he does not keep unneeded object references, otherwise the
garbage collector cannot release the associated memory. Keeping
unneeded object references are typically called memory leaks.

JSP(Java Server Pages):

Java Server Pages (JSP) is a technology for developing

web pages that support dynamic content which helps

14
 developers insert java code in HTML pages by making use of
special JSP tags, most of which start with <% and end with %>.

A Java Server Pages component is a type of Java servlet

that is designed to fulfil the role of a user interface for a Java
web application. Web developers write JSPs as text files that
combine HTML or XHTML code, XML elements, and
embedded JSP actions and commands.

Using JSP, you can collect input from users through

web page forms, present records from a database or another
source, and create web pages dynamically.

JSP Architecture:

The web server needs a JSP engine i.e. container to

process JSP pages. The JSP container is responsible for
intercepting requests for JSP pages. This tutorial makes use of
Apache which has built-in JSP container to support JSP pages
development.

A JSP container works with the Web server to provide

the runtime environment and other services a JSP needs. It
knows how to understand the special elements that are part of
JSPs.

15
 MVC Architecture:

Model View Controller or MVC as it is popularly called, is

a software design pattern for developing web applications. A Model
View Controller pattern is made up of the following three parts:

Model - The lowest level of the pattern which is responsible for

maintaining data.

View - This is responsible for displaying all or a portion of the

data to the user.

Controller - Software Code that controls the interactions

between the Model and View.

MVC is popular as it isolates the application logic from the

user interface layer and supports separation of concerns. Here the
Controller receives all requests for the application and then works
with the Model to prepare any data needed by the View. The View
then uses the data prepared by the Controller to generate a final

16
 presentable response. The MVC abstraction can be graphically
represented as follows.

The model

The model is responsible for managing the data of the

application. It responds to the request from the view and it also
responds to instructions from the controller to update itself.

The view

A presentation of data in a particular format, triggered

by a controller's decision to present the data. They are script
based tempting systems like JSP, ASP, PHP and very easy to
integrate with AJAX technology.

The controller

The controller is responsible for responding to user

input and perform interactions on the data model objects. The

17
 controller receives the input, it validates the input and then
performs the business operation that modifies the state of the
data model.

Struts 2.0:

Struts2 is popular and mature web application

framework based on the MVC design pattern. Struts2 is not just
the next version of Struts 1, but it is a complete rewrite of the
Struts architecture.

The Webwork framework started off with Struts

framework as the basis and its goal was to offer an enhanced
and improved framework built on Struts to make web
development easier for the developers.

After some time, the Webwork framework and the

Struts community joined hands to create the famous Struts2
framework.

Struts 2 framework features:

1) POJO forms and POJO actions - Struts2 has done away

with the Action Forms that were an integral part of the Struts
framework. With Struts2, you can use any POJO to receive the form
input. Similarly, you can now see any POJO as an Action class.

2) Tag support - Struts2 has improved the form tags and the new tags
allow the developers to write less code.

18
3)AJAX support - Struts2 has recognised the take over by Web2.0
technologies, and has integrated AJAX support into the product by
creating AJAX tags, that function very similar to the standard Struts2
tags.

4)Easy Integration - Integration with other frameworks like Spring,

Tiles and SiteMesh is now easier with a variety of integration available
with Struts2.

5) Template Support - Support for generating views using templates.

Struts 2.0 Architecture :

From a high level, Struts2 is a pull-MVC (or MVC2)

framework. The Model-View-Controller pattern in Struts2 is
realized with following five core components:

Actions

Interceptors

Value Stack / OGNL

Results / Result types

View technologies

19
 Struts 2 is slightly different from a traditional MVC
framework in that the action takes the role of the model rather
than the controller, although there is some overlap.

The above diagram depicts the Model, View and

Controller to the Struts2 high level architecture. The controller
is implemented with a Struts2 dispatch servlet filter as well as
interceptors, the model is implemented with actions, and the
view as a combination of result types and results. The value
stack and OGNL provide common thread, linking and enabling
integration between the other components.

APACHE TOMCAT

20
Apache Tomcat is an open-source web server and servlet container
developed by the Apache Software Foundation (ASF). Tomcat
implements several Java EE specifications including Java Servlet,
JavaServer Pages (JSP), Java EL, and WebSocket, and provides a "pure
Java" HTTP web server environment for Java code to run in.

Apache is developed and maintained by an open community of

developers under the auspices of the Apache Software Foundation,
released under the Apache License 2.0 license, and is open-source
software.Components:Tomcat 4.x was released with Catalina (a
servlet container), Coyote (an HTTP connector) and Jasper (a JSP
engine).

1. Catalina:
Catalina is Tomcat's servlet container. Catalina implements Sun
Microsystems' specifications for servlet and JavaServer Pages (JSP).

2. Coyote:
Coyote is a Connector component for Tomcat that supports the HTTP
1.1 protocol as a web server. This allows Catalina, nominally a Java
Servlet or JSP container, to also act as a plain web server that serves
local files as HTTP documents.

3. Jasper:
Jasper is Tomcat's JSP Engine. Jasper parses JSP files to compile them
into Java code as servlets (that can be handled by Catalina). At
runtime, Jasper detects changes to JSP files and recompiles them.

21
INTRODUCTION OF MySQL

My Structured Query Language(MySQL), is the most popular Open

Source SQL database management system. Structured Query
Language(SQL) is a computer language designed for the retrieval and
management of data in relational database management systems,
database schema creation and modification, and database object access
control management .SQL has been standardized originally designed as
a declarative query and data manipulation language.

variations of MySQL have been created by database management

system (DBMS) vendors that add procedural constructs, control-of-
flow statements, user-defined data types, and various other language
extensions.

MySQL has come under criticism for its lack of cross-platform

portability between vendors, inappropriate handling of missing data,
complex three-valued logic system, and its complex and occasionally
ambiguous language grammar and semantics.

Using MySQL one can create and maintain data manipulation objects
such as table, views, sequence etc. These data manipulation objects
will be created and stored on the server's hard disk drive, in a table
space, to which the user has been assigned.
Once these data manipulation objects are created, they are used
extensively in commercial applications.

22
 CHAPTER 2 : PROPOSED SYSTEM

23
2.1 Proposed System

Even there are website for all these things, but at the end what we see,
for everything we go for different website and these website has a
different policies such as user have to create a different credentials to
get the detail information, this is just the basic.
Hence we are going to build a website which will act as a one stop
recharge wallet. It will provide all facilities of recharge for all types of
SimCard companies on a single website itself. Characterized by unity,
users can engage in special interest sections which include the main
modules like schemes for simcard recharge and DTH recharge also.
The model also provides facility for the user such as whenever he/she
recharge from the website they will get the credits for that recharge and
also the user will refer this site to other friends while social
communication medium. Also, The website also provide a toll free no
to the registered user so that whenever there Internet is not available at
that time the registered user can perform their recharge by just sending
the message on the toll free number this is one of the big advantage of
using this websites.
2.2) Feasibility Study

The Crucial part is deciding upon user requirements and to provide

him with the best possible solution. To determine the user requirement
following point have to be considered

24
 System must meet the user needs
System must be economically feasible
System should be able to operate the system easily and
efficiently.

Feasibility Study is conducted to test:

Technical Feasibility
Economical Feasibility
Operational Feasibility

2.2.1 Technical Feasibility:

This determines whether the project work can be done with the
current equipment, existing software technology and available
personnel. For this proposed system the necessary software and
hardware are available, so there are no problems from the technical
aspect.

2.2.2 Economical Feasibility:

This refers to if there are sufficient benefits in developing the
new systems to make the cost acceptance or is the cost of not creating
the system so great that the project works must not be undertaken.
Since the cost of hardware has considerably gone and hence there is no
problem on developing this system for a particular organization having
the required hardware. The proposed system can be developed in a
short period of time and with the minimum cost. If in case there is a
need for any changes to the system, which are easily possible with the

25
low cost. Lastly, Inventory Management system does not involve any
kind of large operating or maintenance costs as well as no storage costs
as such.

2.2.3 Operational Feasibility:

The Proposed system is beneficial from the aspect only when it
is implemented and turned into a fully functional information system.
Simply stated this test of feasibility asks if the system will work when
it is developed and installed. Following are the points that system is
operational feasible. As there is direct involvement of the user with the
system, there are less chances of any resistance from them in using the
system. The training imparted to the end user and the support extended
through the user manuals make the system operationally feasible.

26
2.2 Objectives of System
Following are the important objectives of the project:

To Improved processing speed.

To Enhance capacity to process a greater amount of activity

To Faster retrieval of information with accuracy and
consistency
To Reducing paper work and Cost.
To maintain security.
To provide a GUI(graphical user interface) to update the
information
To provide an interface for feeding the suggestion
To store those suggestions in the database
To secure the data of records in very efficient way
To allow the access of data and software to only the people who
are authenticated

27
2.3) User Requirements

Functional Requirement
The functional requirements of this system are as follows:
Share Link : User Can Share Their Own Link.

Contact us data Management: Admin Can Manage Contact

us massage.
Website Management: Admin can manage all the details of
the Websites
Date wise report management: Admin As well as user can
show all type of report .
Wallet point transfer: user can transfer wallet point

Recharge Management: User can manage all there recharge

with payment gateway or wallet point on data card ,dth ,mobile.
Fund Management: Admin can upload recharge stock amount.

Non-functional requirements
The Nonfunctional requirements are as follows:

Security

Each member is required to have an individual password

Administrators have the option of increasing the level of

password security their members must use.

28
 For maximum security, each member must protect their
password.

Reliability:
System will prompt the user if any incorrect input is
made.
To handle data consistency, DBMS software is used.
Maintainability:
Proper documentation is available for further up
gradation and maintenance.
User will be trained enough to handle the minor
changes required.
Availability:
The system shall be available all the time i.e 24*7*365.
Portability:
System is independent of hardware specification.
It can run on any operating system
System is independent of browser compatibility because
web pages will be designed by JSP and Servlet.
Performance:
The performance of our product is at its best if stored
locally, as the response time will be much faster.

If the product accessed via Internet, the performance is

limited by the connection speed.
The only foreseen limitation is that of web server
response

29
 .User Friendly:
Our system is very easy to use and user friendly. Its
GUI is very attractive and understandable to the common users.

CHAPTER 3 : ANALYSIS & DESIGN

30
3.1 Architecture Over View

MVC Architecture:

Model View Controller or MVC as it is popularly called, is a software

design pattern for developing web applications. A Model View
Controller pattern is made up of the following three parts:

Model - The lowest level of the pattern which is responsible for

maintaining data.
View - This is responsible for displaying all or a portion of the
data to the user.

Controller - Software Code that controls the interactions

between the Model and View.

MVC is popular as it isolates the application logic from the

user interface layer and supports separation of concerns. Here the
Controller receives all requests for the application and then works
with the Model to prepare any data needed by the View. The View
then uses the data prepared by the Controller to generate a final

31
 presentable response. The MVC abstraction can be graphically
represented as follows.

The model

The model is responsible for managing the data of the

application. It responds to the request from the view and it also
responds to instructions from the controller to update itself.

The view

A presentation of data in a particular format, triggered by a

controller's decision to present the data. They are script based
templating systems like JSP, ASP, PHP and very easy to integrate with
AJAX technology.

The controller

The controller is responsible for responding to user input and

perform interactions on the data model objects.

32
 3.2) Use Case Diagrams

Overview:
A use case diagram is a graphic depiction of the interactions among the
elements of a system.

A use case is a methodology used in system analysis to identify, clarify,

and organize system requirements .Use case diagrams are employed
in UML (Unified Modeling Language), a standard notation for the
modeling of real-world objects and systems.

A use case diagram contains four components.

The boundary, which defines the system of interest in relation

to the world around it.
The actors, usually individuals involved with the system
defined according to their roles.
The use cases, which are the specific roles played by the actors
within and around the system.
The relationships between and among the actors and the use
cases.
Purpose:
Use case diagrams are used to gather the requirements of a system
including internal and external influences. These requirements are
mostly design requirements. So when a system is analyzed to gather
its functionalities use cases are prepared and actors are identified.

33
Global Use Case Diagram:

34
Use case diagram for Registration and login:

35
Use case diagram for Recharge process:

3) Use Case Diagram For Payment Details:

36
3.3) Activity Diagram

Overview:

37
Activity diagram is another important diagram in UML to describe
dynamic aspects of the system.

Activity diagram is basically a flow chart to represent the flow form

one activity to another activity. The activity can be described as an
operation of the system.

So the control flow is drawn from one operation to another. This flow
can be sequential, branched or concurrent. Activity diagrams deals
with all type of flow control by using different elements like fork, join
etc.

Purpose:
Activity diagrams are not only used for visualizing dynamic nature of
a system but they are also used to construct the executable system by
using forward and reverse engineering techniques.

Activity diagrams illustrate the dynamic nature of a system by

modeling the flow of control from activity to activity. An activity
represents an operation on some class in the system that results in a
change in the state of the system. Typically, activity diagrams are used
to model workflow or business processes and internal operation.

1.Activity diagram for Registration

38
Activity diagram for Login:

39
Activity Diagram For Mobile Recharge:

40
Activity Diagram For DTH Recharge:

41
Activity Diagram For DTH Recharge:

42
Activity Diagram For Data card Recharge:

43
Activity Diagram For Payment Detail:

44
Sequence diagram
Overview

45
Sequence diagram is the most common kind of interaction diagram,
which focuses on the message interchange between a number
of lifelines.

Sequence diagram describes an interaction by focusing on the

sequence of messages that are exchanged, along with their
corresponding occurrence specifications on the lifelines.

The following nodes and edges are typically drawn in a UML sequence
diagram: lifeline, execution specification, message, fragment,
interaction, state invariant, continuation, destruction occurrence.

Sequence diagram:
Sequence diagram for Login:

46
Sequence diagram for Recharge:

47
Sequence diagram for Payment:

48
Class Diagram:

49
Overview:
The class diagram is a static diagram. It represents the static view of
an application. Class diagram is not only used for visualizing,
describing and documenting different aspects of a system but also for
constructing executable code of the software application.

The class diagram describes the attributes and operations of a class

and also the constraints imposed on the system. The class diagrams
are widely used in the modeling of object oriented systems because
they are the only UML diagrams which can be mapped directly with
object oriented languages.

The class diagram shows a collection of classes, interfaces,

associations, collaborations and constraints. It is also known as
a structural diagram.

Purpose:
The purpose of the class diagram is to model the static view of an
application. The class diagrams are the only diagrams which can be
directly mapped with object oriented languages and thus widely used
at the time of construction.

The purpose of the class diagram can be summarized as:

Analysis and design of the static view of an application.

Describe responsibilities of a system.

50
 3.6 Class Diagram

51
Deployment diagram
Overview:
Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are
deployed.So deployment diagrams are used to describe the static
deployment view of a system. Deployment diagrams consist of nodes
and their relationships.

Purpose:
The name Deployment itself describes the purpose of the diagram.
Deployment diagrams are used for describing the hardware
components where software components are deployed. Component
diagrams and deployment diagrams are closely related.

Component diagrams are used to describe the components and

deployment diagrams shows how they are deployed in hardware.

UML is mainly designed to focus on software artifacts of a system.

But these two diagrams are special diagrams used to focus on
software components and hardware components.

So most of the UML diagrams are used to handle logical components

but deployment diagrams are made to focus on hardware topology of
a system. Deployment diagrams are used by the system engineers.

The purpose of deployment diagrams can be described as:

Visualize hardware topology of a system.

52
3.7.1 Deployment Diagram:

3.7.2 Component Diagram:

53
3.8 Web Site Map Diagram
Start

Open Web site

54
 Admin Customer
Cust Login
Admin Login
Recharge Process
Add
Recharge
Service
s Transfer Point
Customer
Genr
Ticket
View
View

Member Recharge
List Status
Total Transfer
Earnings Point
Report Ticket

Recharge Status
Customer

Earnings Successful
Transfer Point Pending

Logout Logout

3.6 Database Design

1)
Table Name :Member_reg
Primary Key :mem_id
Description member registration

55
 Fie Field Name Da Data Type Siz Size
C D Description
Constraints
mem_id Integer 4 Primary key Member id
mem_email Varchar 30 Not Null Member mail id
mem_pwd Double 8 Not Null Password
mem_mob Varchar 10 Not Null Mobile no
mem_refid Int 5 Not Null Member reference id
mem_status Varchar 50 Not Null status
mem_act Varchar 10 Not Null Activation
mem_datetime Date Not Null Registration date

2)
Table Name : Recharge
Primary Key :rech_id Foreign key : mem_id
Fie Field Name Da Data Type Siz SizeC Constraints De Description
rech_id Integer 4 Primary key Recharge id
rech_info Varchar 50 Not Null Recharge info

56
 rech_number Varchar 20 Not Null Mobile no
mem_id Double 4 Foreign key Member id
rech_date Date Not Null Date
Rec rech_amt Varchar 6 Not Null Amount
R rech_operator Varchar 25 Not Null Operator
Re rech_result Varchar 50 Not Null Status
rech ref_id Integer 5 Not Null P Payment gateway
reference id

3)
Table Name :Mobile
Primary Key :m_id Foreign key:mem_id
Description :Mobile Recharge Detail

Fi Field Name Da Data Type Siz SizeC Constraints De description

m_id Integer 4 Primary key Unique id

57
m_date Datetime Not Null Recharge date
m_operator Varchar 20 Not Null Mobile operator
m_no Varchar 10 Not Null Mobile number
rech_amt Varchar 6 Not Null Recharge amount
mem_id Integer 4 Foreign key Member id

4)
Table Name : dth
Primary Key : dth_id Foreign key:mem_id
Description : DTH Recharge Detail

Field_name Da Data Type Siz SizeC Constraints De Description

dth_id Integer 4 Primary Key Unique id

58
 dth_date Datetime Not Null Recharge date
dth_operator Varchar 20 Not Null Dth operator
dth_no Varchar 16 Not Null Dth number
dth_amt Varchar 6 Not Null Recharge amount
Me m_id Integer 4 Foreign Key Member id
dth_status Varchar 25 Not Null Recharge status

5)
Table Name : datacard
Primary Key : datacard_id Foreign key:mem_id
Description : Datacard Recharge Detail

Field_name Da Data Type Siz SizeC Constraints

De Description
datac_id Integer 4 Primary Key Unique id

59
 datac_date Datetime Not Null Datacard Recharge
datac_operator Varchar 10 Not Null Datacard operator
datac_no Varchar 16 Not Null Datacard number
datac_amt Varchar 6 Not Null Datacard Recharge am
Me mem_id Integer 4 Foreign Key Member id
datac_status Varchar 25 Not Null Datacard Recharge st

6)
Table Name : Bank_Detail
Primary Key :bank_id Foreign Key : member _id
Description : user bank detail

IFi Field_name Da Data Type Siz SizeCo constraints D description

Bank_id Integer 6 Primary key Bank id
Bank_accno Varchar 15 Not Null Bank account no

60
 Bank_name Varchar 15 not Null Bank name

Bank_ifsc Varchar 15 not Null Bank ifsc code

Bank_acc_type Varchar 10 not Null Account type
Bank_city Varchar 10 not Null City
Bank_state Varchar 10 not Null Bank state
mem_id Int 4 Foreign key Member id

7)
Table Name:Member details
Primary key:memberdetail_id

61
 Field Name Data type Size Constraints Description

memdetail_id Integer 4 Primary key Member id

member_fname Varchar 10 Not Null First Name
membdetail_lname Varchar 10 Not Null Last Name
membdetail_addr Varchar 25 Not Null Member Address
membdetail_city Varchar 15 Not Null City

membdetail_state Varchar 20 Not Null State

membdetail_country Varchar 15 Foreign key Country
membdetail_gender Varchar 7 Not Null Gender
mem_id Integer 4 Foreign key Member id

8)
Table Name : Transfer wallet point
Primary Key : tran_wpid Foreign key : mem_id

Fie Field Name Da Data Type Siz SizeC ConstraintsDe Description

62
 tran_wpid Integer 4 Primary key Transfer Id
tran_wpdate Date Not Null Transaction date
tran_wppoint Varchar 8 Not Null Wallet Point
mem_id Integer 4 Foreign key Member id
tran_wpmemid Integer 5 Not Null From whom account
transfer

9)
Table Name :Support_ticket
Primary Key :ticket_id Foreign key :mem_id
Description Generate support ticket
Fie Field Name
Da Data TypeSiz SizeCo Constraints
De Description

63
 ticket_id Integer 4 Primary key Ticket Id
email_id Varchar 20 Foreign key Email Id
mobile_no Varchar 16 Not Null Mobile no on which
recharge
operator Varchar 16 Not Null Operator
Integer 4 Foreign key Transaction id
trans_id
amount Varchar 8 Not Null Amount
mem_id Integer 4 Forign key Member id
Status Varchar 10 Not Null Status
Date Date Not Null Ticket date
Remark Varchar 10 Not Null Remark
Status Varchar 20 not null Dealer Status
(active/
deactivate)

10)

Table Name : User wallete

Primary Key :userwallet_id Foreign key :mem_id
Description Send requirement details
Fie Field Name D Data Type
Siz SizeCo Constraints Description
userwallet_id Integer 4 Primary key Id

64
Fie Field Name D Data Type
Siz SizeCo Constraints Description
userwallet_date Date Not Null Date
userwallet_poin Varchar 10 Not Null Point
t
mem_id Varchar 4 Foreign key Member id

11)
Table Name : Company Wallet
Primary Key :wallet_id
Description : Contact us Details
Fie Field Name Data Type Siz SizeConstraints D Description
wallet_id Integer 4 Primary key walletid
wallet_date Date Not Null Created date
wallet_point Varchar 10 Not Null Amount
mem_id Integer 4 Foreign key Member id
cmpny_id Integer 4 Foreign key Comapany reference

wallet_datetime Datetime Not null Transaction date

12)
Table Name :last seen
Primary Key :ls_id Foreign key:mem_id
Description : user list login status
Fie Field Name Da Data Type Siz Size Co Constraints De Description
ls_id Integer 4 Primary key Last Login id

65
 ls_date Date time Not Null Login date time
mem_id Integer 4 Foreign key Member id

13)
Table Name : wallet balance
Primary Key :tot_point_id Foreign key : mem_id
Description wallet balance
Fie Field Name D Data Type Siz SizeCo Constraints De Description
tot_point_id Integer 4 Primary key Total point id
wallet_amt Varchar 6 Not Null Wallet amount
tot_ date Date Not Null Modify date
M mem_id Int 4 Foreign key Member id

14)
Table Name :Contact_Us
Primary Key :contact_id Description : contact us
message
Fie Field_Name Da Data Type Siz Size Co Constraints De Description
contact_id Integer 4 Primary key Contact id
contact_name Varchar 10 Not Null Contact name

66
contact_email Varchar 20 Not Null Email id
contact_msg Varchar 20 Not Null Customer message

15)
Table Name: Ad_msg
Primary Key: ad_id
Description : Post Advertisement

67
 Fie Field_Name
Da Data TypeSiz Size
Co Constraints De Description
ad_id Int 4 Primary key Ad id
ad_date Date Not Null A advertise post date
ad_message Varchar 50 Not Null A advertise message

16)
Table Name : Admin_Recharge_Wallete
Primary Key :Recharge_id
Description : Recharge Detail
Fie Field_Name D Data Type Siz Size CC Constraints De Description
recharge_id Integer 4 Primary key Recharge_ id
recharge_Amount Varchar 8 Not Null Recharge amount
recharge_date datetime Not Null Recharge date
company_id Integer 6 Not Null C Company reference
id

17)
Table Name : loadamtstatus
Primary Key :loadstatus_id
Description: Load recharge amount by admin
Fie Field Name Data Type SiS Size Co Constraints De Description
loadstatus_id Integer 4 Primary key Load id

68
loadstatus_name Varchar 15 Not Null Status
load_amount Varchar 8 Not Null Load amount

3.9 Data Dictionary

Sr.No Field Name Data Type Constraints Description Table

Name
1 ad_date Date Not Null A advertise
post date
2 ad_id Int 4 Primary Ad id
Key
3 ad_message Varchar 45 Not Null advertise
message
4 amount Varchar 6 Not Null Amount

5 Bank_accno Varchar 15 Not Null Bank

account
no
6 Bank_id Integer 6 Primary key Bank id

7 Bank_acc_type Varchar 10 not Null Account type

69
8 Bank_city Varchar 10 not Null City

9 Bank_ifsc Varchar 15 not Null Bank ifsc

code
10 Bank_name Varchar 15 not Null Bank name

11 Bank_state Varchar 10 not Null Bank state

12 company_id Integer 6 Not Null C Company

reference
id
13 contact_email Varchar 20 Not Null Email id

14 contact_id Integer 4 Primary key Contact id

15 contact_name Varchar 10 Not Null Contact

name
16 contact_msg Varchar 20 Not Null Customer
message
17 Date Date Not Null Ticket date

18 Date Date Not Null Modify date

19 datac_amt Varchar 6 Not Null Datacard

Recharge
amount
20 datac_date Date Not Null Datacard
Recharge
date
21 datac_id Integer 4 Primary Key Unique id

22 datac_operator Varchar 10 Not Null Datacard

operator

70
23 datac_no Varchar 16 Not Null Datacard
number
24 datac_status Varchar 25 Not Null Datacard
Recharge
status
25 dth_amt Varchar 6 Not Null Recharge
amount
26 dth_date Date Not Null Recharge date

27 dth_id Integer 4 Primary Key Unique id

28 dth_operator Varchar 20 Not Null Dth operator

29 dth_no Varchar 16 Not Null Dth number

30 dth_status Varchar 25 Not Null Recharge

status
31 email_id Varchar 20 Foreign key Email Id

32 ls_date date Not Null Login date time

33 ls_id Integer 4 Primary key Last Login id

34 load_amount Varchar 8 Not Null Load amount

35 loadstatus_id Integer 4 Primary key Load id

36 loadstatus_name Varchar 15 Not Null Status

37 mem_act Varchar 10 Not Null Activation

38 mem_email Varchar 30 Not Null Member mail id

39 m_date Date Not Null Recharge date

71
40 mem_datetime datetime Not Null Registration
date
41 m_id Integer 4 Primary key Unique id

41 m_operator Varchar 20 Not Null Mobile

operator
42 m_no Varchar 10 Not Null Mobile number

43 mem_id Integer 4 Primary key Member id

44 mobile_no Varchar 12 Not Null Mobile no

recharge
done
45 membdetail_addr Varchar 25 Not Null Member
Address
46 membdetail_city Varchar 15 Not Null City

47 membdetail_countr Varchar 15 Foreign key Country

y
48 member_fname Varchar 10 Not Null First Name

49 membdetail_gender Varchar 7 Not Null Gender

50 memdetail_id Integer 4 Primary key Member id

51 Varchar 10 Not Null Last Name

membdetail_lna
me
52 Varchar 20 Not Null State
membdetail_state
53 m_date datetime Not Null Recharge date

54 m_id Integer 4 Primary key Unique id

72
55 m_operator Varchar 20 Not Null Mobile
operator
56 m_no Varchar 10 Not Null Mobile number

57 mem_pwd double 8 Not Null Password

58 mem_refid Int 5 Not Null Member

reference
id
59 mem_status varchar 50 Not Null status

60 Operator Varchar 16 Not Null Operator

61

62 recharge_Amount Varchar 8 Not Null Recharge

amount
63 rech_am Varchar 6 Not Null Amount

64 rech_amt Varchar 6 Not Null Recharge

amount
65 recharge_date Date Not Null Recharge date

66 recharge_id Integer 4 Primary key Recharge_ id

67 Remark Varchar 10 Not Null Remark

68 rech_date Date Not Null Date

69 R rech_operator Varchar 25 Not Null Operator

70 rech_id Integer 4 Primary key Recharge id

71 rech_info Varchar 50 Not Null Recharge info

73
72 rech_number Varchar 20 Not Null Mobile no

73 Re rech_result Varchar 50 Not Null Status

74 rech ref_id Integer 5 Not Null P Payment

gateway
reference
id
75 Status Varchar 10 Not Null Status

76 userwallet_date Date Not Null Date

77 userwallet_id Integer 4 Primary key Id

78 userwallet_point Varchar 10 Not Null Point

79 ticket_id Integer 4 Primary key Ticket Id

80 trans_id Integer 4 Foreign key Transaction id

81 tran_wpid Integer 4 Primary key Transfer Id

82 tran_wpdate Date Not Null Transaction

date
83 tran_wppoint Varchar 8 Not Null Wallet Point

84 tran_wpmemid Integer 5 Not Null From whom

account
transfer
85 tot_point_id Integer 4 Primary key Total point id

86 wallet_amt Varchar 6 Not Null Wallet

amount
87 wallet_date Date Not Null Created date

74
88 wallet_id Integer 4 Primary key walletid

89 Datetime Not null Transaction

wallet_datetime
date

75
 CHAPTER 4: USER MANUAL

USER MANUAL
User Manual for Administrator:
The administrator is the main user of this system. The administrator
has some extra features that are not provided to users/employee.
1) Registration:
This is provided to register for PAY U CIRCLE system.

76
 By using it you can do registration with the PAY U CIRCLE
system.

2) Login:
This is provided to do the login.
The Admin and the customer must have logged in to use the
system.
So to do the login you can use this.
Here simply by entering your login details you can logged in.

3) Add User:
This is to add new user to the Pay U Circle.
You can add the new user to the Pay U Circle using it.

4) Process :
You can check complaint status using with the help of ticket
. This is provided to manage all member details data.
You can check register friends using member id, last name etc.
You can check transfer point
It is provide check the date wise amount.

77
 You can deactivate user. They are no longer access long time.

5) Recent Activity :
This is provided load amount to the user account.
With the help of it you can check recent recharge activity.
You can use it for recent transfer point to all users.

6) Date wise Record:

This is provided to manage all your Date wise report
related data.
Using this you can view all reports date wise.
7) Recharge History:
This is provided to manage all your recharge related data.
Using this you can view all recharge records, edit recharge
complaint , delete old recharge request, search and filter
recharge type etc.

6.2 User Manual For User:

Login:
This is provided to do the login.
So to do the login you can use this.
Here simply by entering your login details you can logged in.

78
Recharge Process:
Enter your mobile number for make a recharge to Pay U Circle.
Fill all the bank details in payment options.
After completing all transactional process ,you got the message
your recharge is successfully done.

Balance:
With the help of using my balance, you can check all the
activity regarding your account i.e. check total amount, today
amount, remaining balance etc.
With the help of using my circle, you can check all the down
line of all users i.e. check total users.
Using transfer money options ,you can help to your friend
anytime and anywhere.

Help Desk:
This is provided to generate new ticket when the some issues
occur regarding recharge process related data.
Using this you can view all ticket status and search all the
fields.

Recent Activity:
This is provided to view transfer point to all user using various
member id.
Using this you can view all recharge activity.
Date wise Report:
This is provided to manage all your Date wise report related
data.

79
 Using this you can view all reports date wise.

4.2 Operations Manual

1. Index:
Index allows users to perform functionalities like login
etc.
2. Login:
User can login throw their unique username and
password and redirected to user home page.
3. User Home:
After successful login the user is redirected to his/her
home page. On the home page there are all the functionalities
available which user can perform.
4. Logout:
The logout allows the user come out of the system. User
will select the logout button and come out of the system.

80
4.2) Forms and Report

Index Page :-

About us:

81
 Sign in :-

Validation:-

82
 Sign up :-

After sign in :-

83
Recharge Process:-

84
My Circle:-

85
 My Balance:-

Help Friends:-
Transfer Money

86
Help Desk :-
Generate new ticket:

87
 Recent activity :-
View transfer point

View recharge-

88
Promo Link :-

Admin Panel :-

Index Page -

89
Process-
Ticket

Member Details List-

90
Register Friend -

91
 Transfer Point:-

92
 Datewise Amount:-

93
 Message:-

94
 Deactivate Member:-

Recent Activity:-
Load Amount-

95
Recent Recharge-

96
 Admin Recent Transfer Point-

97
4.4Test Procedures and Cases
TYPES OF TESTING:
UNIT TEST
Testing of individual software components or modules. Typically done
by the programmer and not by testers, as it requires detailed knowledge
of the internal program design and code. In our application we do the
unit testing for the login form where all the validations are being
checked properly.
INTEGRATION TESTING:
Testing of integrated modules to verify combined functionality after
integration. Modules are typically code modules, individual
applications, client and server applications on a network, etc. This type
of testing is especially relevant to client/server and distributed systems.
SYSTEM TESTING:
Entire system is tested as per the requirements. Black-box type testing
that is based on overall requirements specifications, covers all
combined parts of a system.
Our whole applications are being tested.
PERFORMANCE TESTING:

98
Term often used interchangeably with stress and load testing. To
check whether system meets performance requirements. Used different
performance and load tools to do this.

Test cases are built around specifications and requirements, i.e., what
the application is supposed to do. Test cases are generally derived from
external descriptions of the software, including specifications,
requirements and design parameters. Although the tests used are
primarily functional in nature, non-functional tests may also be used.
The test designer selects both valid and invalid inputs and determines
the correct output without any knowledge of the test object's internal
structure.

Test Design Techniques

Typical black-box test design techniques include:

Decision table testing

All-pairs testing
State transition Analysis
Equivalence partitioning
Boundary value analysis
Causeeffect graph
Error guessing

Advantages
Efficient when used on large systems.
Since the tester and developer are independent of each other,
testing is balanced and unprejudiced.
Tester can be non-technical.

99
 There is no need for the tester to have detailed functional
knowledge of system.
Tests will be done from an end user's point of view, because the
end user should accept the system. (This testing technique is
sometimes also called Acceptance testing.)
Testing helps to identify vagueness and contradictions in
functional specifications.
Test cases can be designed as soon as the functional
specifications are complete.

Disadvantages
Test cases are challenging to design without having clear
functional specifications.
It is difficult to identify tricky inputs if the test cases are not
developed based on specifications.
It is difficult to identify all possible inputs in limited testing
time. As a result, writing test cases may be slow and difficult.
There are chances of having unidentified paths during the
testing process.
There is a high probability of repeating tests already performed
by the programmer.

100
TEST CASE FOR LOGIN

Test Objective Condition Steps/Input Expected Actual Test

Cas Result Result Status
e No
1 Logged Valid Enter valid User User
into Login user name successfull account Pass
system and y logged and user
password. into the profile
Click on system and will
Login user profile display
will
display.
2 Validation Invalid Enter Error Error
check for email. invalid message message
email email. window invalid Pass
Enter valid should be email or
password. display password.
Click on with proper
login. error
message.
invalid
name.

101
3 Validation Invalid Enter valid Error Error
check for password. email id. message message
password Enter window Invalid Pass
invalid should be name or
password. displayed password
Click on with proper .
login. error
message
invalid
password

4 Validation Invalid Enter Error Error

check of email and invalid message message
both email password email. window Invalid Pass
and Enter should be email and
password invalid displayed password
password. with proper .
Click on error
login. message
invalid
name or
password

102
 2] Test case For Check Customer registration:
Test Test Case Input Expected Actual Test
Case Procedure Data Output Output Status
ID
DST- Checking the Keep all field Shows Shows Pass
CR-01 functionality blank proper proper blank
of Customer blank message
registration message
otp button
button

2)insert Shows It shows Pass

wrong mail id proper email id
blank incorrect
message
about
wrong
mail id
3)insert Shows It shows Pass
character in proper phone no is
phone no blank not
textbox message matching
about with format
wrong
phone no

103
 4)input all Otp send Otp send on
valid field on mobile mobile and pass
and shows shows otp
otp input input box
box with with submit
submit buttion
buttion

DST Checking the Input wrong Otp not Otp not Pass
-CR-02 functionality otp match match
of check message message
button display display
functionality
for otp 2) Input
correct otp Otp match Otp match pass
message message
display display and
and enable enable
submit submit
buttion buttion
DST Checking the Click on Varificatio Varification Pass
-CR-03 functionality submit n mail mail send on
of Submit buttion send on email id
Button from email id

4.5)Implementation

104
 The Struts implementation of Model 2 uses a specific type of
servlet, called on action servlet, and one or more actions and action
mappings to implement the controller. It also uses a specific type of
Java bean, called a form bean. As illustrated in Figure 3, the Web
server at run time contains both the view and controller components of
a Model 2 Web application, while a third tier (which is usually outside
of the Web server) contains the model.

Struts contribution to MVC components as shown in Table 3.

Component Contribution
Model None directly. However, the Struts actions and
configuration file provide an elegant way to control
the circumstances under which the model components
are invoked.

105
 Component Contribution
View Java class
org.apache.struts.action.ActionForm, which
you subclass to create a form bean that is used
in two ways at run time:
o When a JSP page prepares the related
HTML form for display, the JSP page
accesses the bean, which holds values
to be placed into the form. Those
values are provided from business logic
or from previous user input.
o When user input is returned from a
Web browser, the bean validates and
holds that input either for use by
business logic or (if validation failed)
for subsequent redisplay.

Numerous custom JSP tags that are simple to

use but are powerful in the sense that they hide
information. Page Designer does not need to
know much about form beans, for example,
beyond the bean names and the names of each
field in a given bean.

106
 Component Contribution
Controller The Struts action servlet handles run-time
events in accordance with a set of rules that are
provided at deployment time. Those rules are
contained in a Struts configuration file and
specify how the servlet responds to every
outcome received from the business logic.
Changes to the flow of control require changes
only to the configuration file.
Struts also provides the Java class
org.apache.struts.action.Action, which a Java
developer subclasses to create an "action
class". At run time, the action servlet is said to
"execute actions," which means that the servlet
invokes the execute method of each of the
instantiated action classes. The object returned
from the execute method directs the action
servlet as to what action or JSP file to access
next.

107
 CHAPTER 5: DRAWBACK AND
LIMITATION

108
Drawbacks and Limitations

Our project has the following limitations:-

Need internet connection

Limited storage

If the website is down, customer wont be able to recharge.

109
 CHAPTER 6:
PROPOSED ENHANCEMENT

110
 6. Proposed Enhancement
The proposed enhancements of this system are as follows:
1. This system will convert into Android version and make
available it for android devices.
2. Integration with external outlook plug-in.
3. Integration with external plug-ins to improve the
performance and functionality of system.
4. Dynamic and easy graphical report generation.
5. Integration with office plug-in.
6. Recharge using text message keyword.

111
 CHAPTER 7 : CONCLUSION

112
Conclusion:

This project has satisfied user requirement, as well as so many

department requirements. By giving user friendly system.
The application is efficient to automate the data processing and
showing all information.
When user wants bank account then he no needs to fill the
form; if his data already stored if no then user go to on net and
create his account.
This application generates different types of report with user
friendly GUI.
Since this application is very user friendly so it understands by
user in very short time.
It is time consuming and cost reducing system as compare to
existing system.

113
CHAPTER 8 : BIBLIOGRAPHY

114
8. BIBLIOGRAPHY
WEBSITES:
www.w3schools.com
www.javatpoint.com
www.javatutorial.com

REFERENCE BOOKS:
Core Java

Dr. R. Nageswara Rao

System Analysis and Design

Java Server Programming

115
CHAPTER 9: ANNEXURE

116
 USER INTERFACE SCREENS

My Circle:-

My Balance:-

117
Help Friends:-
Transfer Money

118
 Ticket status
Recent activity :-

119
 View transfer point

120
 Viewrecharge-

Admin Panel :-

Process-

121
 Ticket -

Member Details List-

122
 Register Friend-

123
 Transfer Point:-

124
 Datewise Amount:-

125
 Message:-

126
 Deactivate Member:-

Recent Activity:-

127
 Load Amount-

Recent Recharge-

128
 Admin Recent Transfer Point-

129
 ANNEXURE 3 : SAMPLE CODE

{
<%@page
import="java.sql.ResultSet"%>
<%@page import="java.sql.Connection"%>
<%@page import="com.dbUtil.DbUtil"%>
<%@ page language="java" contentType="text/html; charset=ISO-
8859-1"
pageEncoding="ISO-8859-1"%>
<%@ taglib uri="/struts-tags" prefix="s"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>

<head>
<meta charset="utf-8">

130
<meta name="viewport" content="width=device-width, initial-
scale=1">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-
8859-1">
<link rel="stylesheet"
href="<%=request.getContextPath()
%>/css/bootstrap.min.css">
<script src="<%=request.getContextPath()
%>/js/jquery.min.js"></script>
<%-- <script src="<%=request.getContextPath()
%>/js/bootstrap.min.js"></script> --%>
<%-- <script
src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"
></script> --%>
<script
src="http://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.
js"></script>

<%-- <script type="text/javascript" src="<%=request.getContextPath()

%>/js/jquery.js"></script> <!--Data table for searching -->--%>

<!--Data table for searching -->

<title>PayuCircle</title>
<link href="<%=request.getContextPath()%>/images/pay.ico"/>
<link href="<%=request.getContextPath()%>/css/payucircle.css"
rel="stylesheet" media="screen" type="text/css">

131
<script type="text/javascript">
/* $(selector).click()
$("#x").hide();
$(".close").hide(); */

function validatedata() {
/*
document.getElementById('mem_email').style.display = "none"; */
var mbno =
document.getElementById("mobileno").value;

if (mbno == null || mbno == "") {

alert("Please Enter Mobile Number");
document.getElementById("mobileno").focus();

return false;
}
if
((document.getElementById("mobileno").value.length < 10)
||
(document.getElementById("mobileno").value.length > 10)) {
alert(" Your Contact number must 10 Digits");
document.getElementById("mobileno").focus();
return false;
}

var opr = document.getElementById("operator").value;

if (opr == null || opr == "") {

132
 alert("Please Enter Operator");
document.getElementById("operator").focus();
return false;
}

var mbamt = document.getElementById("amt").value;

if (mbamt == null || mbamt == "") {
alert("Please enter amount");
document.getElementById("amt").focus();
return false;
}

$('#myModal11').modal('show');
/* $('#myModal11').modal('toggle'); */
/* $('#myModal13').modal('hide'); */

return true;

function validatedth() {
/*
document.getElementById('mem_email').style.display = "none"; */
var opr =
document.getElementById("operatordth").value;
if (opr == null || opr == "") {
alert("Please Enter Operator");

133
 document.getElementById("operatordth").focus();
return false;
}

var mbno = document.getElementById("dthno").value;

if (mbno == null || mbno == "") {

alert("Please Enter V.C Number");
document.getElementById("dthno").focus();

return false;
}
if ((document.getElementById("dthno").value.length <
16)
||
(document.getElementById("dthno").value.length > 16)) {
alert(" Your v.c number must 16 Digits");
document.getElementById("dthno").focus();
return false;
}

var mbamt =
document.getElementById("dthamt").value;
if (mbamt == null || mbamt == "") {
alert("Please enter amount");
document.getElementById("dthamt").focus();
return false;

134
 }

$('#myModal12').modal('show');
/* $('#myModal11').modal('toggle'); */
/* $('#myModal13').modal('hide'); */

return true;

function validatecard() {
var opr =
document.getElementById("cardoperator").value;
if (opr == null || opr == "") {
alert("Please Enter Operator");

document.getElementById("cardoperator").focus();
return false;
}
var mbno = document.getElementById("mobno").value;

if (mbno == null || mbno == "") {

alert("Please Enter Mobile Number");
document.getElementById("mobno").focus();

return false;
}

135
 if ((document.getElementById("mobno").value.length <
10)
||
(document.getElementById("mobno").value.length > 10)) {
alert(" Your v.c number must 10 Digits");
document.getElementById("mobno").focus();
return false;
}

var mbamt =
document.getElementById("cardamt").value;
if (mbamt == null || mbamt == "") {
alert("Please enter amount");
document.getElementById("cardamt").focus();
return false;
}

$('#myModal13').modal('show');

return true;

function checkNum(x) {

var s_len = x.value.length;

var s_charcode = 0;
for ( var s_i = 0; s_i < s_len; s_i++) {

136
 s_charcode = x.value.charCodeAt(s_i);
if (!((s_charcode >= 48 && s_charcode <= 57)))
{
alert("Only Numeric Values Allowed");
x.value = '';
x.focus();
return false;
}
}
return true;
}

function checkchar() {

if (!
document.getElementById("operator").value.match(/^[a-zA-Z ]+$/)) {
alert("Only Characters are Allowed");
document.getElementById("operator").value =
'';
return false;
}
return true;
}

function infodata() {

var mno =
document.getElementById("mobileno").value;

137
 //alert(mno);
document.getElementById("monum").value = mno;
var amount = document.getElementById("amt").value;
//alert(amount);
document.getElementById("amount").value = amount;
// alert(document.getElementById("monum").value);
var operatr =
document.getElementById("operator").value;
//alert(operatr);
document.getElementById("serviceoperator").value =
operatr;

var rtype = document.getElementById("type").value;

// alert(rtype);
document.getElementById("rechtype").value = rtype;

}
function infodth() {
var dno = document.getElementById("dthno").value;
//alert(mno);
document.getElementById("dnum").value = dno;
var amtdth =
document.getElementById("dthamt").value;
//alert(amount);
document.getElementById("amtdt").value = amtdth;
// alert(document.getElementById("monum").value);
var operatr =
document.getElementById("operatordth").value;

138
 //alert(operatr);
document.getElementById("dthoperator").value =
operatr;

var rtype = document.getElementById("typedth").value;

// alert(rtype);
document.getElementById("dthtype").value = rtype;
}

function infocard() {
var datano =
document.getElementById("mobno").value;
//alert(mno);
document.getElementById("mbnum").value = datano;
var amtdatacard =
document.getElementById("cardamt").value;
//alert(amount);
document.getElementById("cardamount").value =
amtdatacard;
// alert(document.getElementById("monum").value);
var operatrdatacard =
document.getElementById("cardoperator").value;
//alert(operatr);
document.getElementById("datacardoperator").value =
operatrdatacard;

var datacardtype =
document.getElementById("cardtype").value;

139
 // alert(rtype);
document.getElementById("typedata").value =
datacardtype;
}

function validatemsg() {
var x = document.getElementById("msgsend").value;
if (x == null || x == "") {
alert("Please Enter Massage");
return false;
}
return true;
}

function setFocusToTextBox() {
document.getElementById("mobileno").focus();
}
</script>

</head>

<body>
<div class="responsive">

<div class="col-md-12"

140
 style="background-color: #d9534f; margin-top:
-19px; position: fixed;">
&nbsp&nbsp
<div class="clearfix"></div>
<%
Connection con=null;
ResultSet rs=null;
DbUtil db = new DbUtil();
try {

con = db.getConnection();

String query = "SELECT ad_msg

FROM advertise" ;
rs = db.selectQuery(query);
while (rs.next()) {
%>

<marquee style="color: #FFF"><

%=rs.getString(1)%></marquee>

<%
}

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

141
 }
finally {
if (rs != null)
try {
rs.close();
} catch (Exception e) {
// TODO Auto-
generated catch block

e.printStackTrace();
}

db.closeConnection();

%>

</div>
<div id="center">

<!--header & logo-->

<div id="header">

<div class="col-md-2" style="margin-

top: 29px;">

142
 <img src="<
%=request.getContextPath()%>/image/payucircle logo.png"
width="90%;"
alt="payucircle">
</div>
<div class="col-md-6" style="margin-
left: 10%;">
<img src="<
%=request.getContextPath()%>/image/pu.png" width="90%;"
alt="payucircle">
</div>
<a
href="https://plus.google.com/payucircle"><img src="<
%=request.getContextPath()%>/image/icon-google-plus.png"
class="img-circle" alt="Cinque Terre" width="50" style="margin-top:
30px; float:right;"> </a>

<a href="https://www.twitter.com/payucircle2"><img src="<

%=request.getContextPath()%>/image/tw.png" class="img-circle"
alt="Cinque Terre" width="50" style="margin-top:
30px;float:right;"></a>
<a href="https://www.facebook.com/payucircle"><img src="<
%=request.getContextPath()%>/image/fb.png" class="img-circle"
alt="Cinque Terre" width="50" style="margin-top: 30px;
float:right;"></a>

<div class="clearfix"></div>
</div>

143
}

144