documentation of catalog mgmt. in j2ee
TRANSCRIPT
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 1/48
CATALOG MANAGEMENT SYSTEM
Abstract:
The aim of this project is to build a system that helps any type of M.L.M(Multi Level Marketing) agency to do all their process in a systematic way. Here
all the activities are automated by using this system. Here the clients and the
administrator will transfer their views and queries by this system. Hence it will
save a large amount of time for the clients as well as the administrator.
Now, as of today, the company would require a lot of manual work to be
done regarding generation of enquiries, receipt of quotation, generation of
purchase order, confirmation etc…. All this can be done in a simplified way by
our online facility, allowing an administrator, appointed by the company to access
the company data base, interact with clients and suppliers, deal with them and
transact accordingly. This enables the company to function in a much smoother
way, obtain orders faster and clear off work in a more appropriate manner.
The system is to automate client’s reports. This can be used for
maintaining and evaluation of sales activities. It allows the clients to set goals
and accomplish them. It is very useful to motivate the client to do better, with
reference of his previous progress.
Use of the project:
This project has been developed as per the general requirements of a
MLM company. But it is going to be at most customized for the administrator and
also the client. This software can also be used or modified as per the exact
requirements of any particular organization..
In this project JSP is used instead of applets because the client has to
send the information to the server and it process it and sends the information to
the client. And since this is a online project JSP is better than using applets.
JSP is a server side scripting.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 2/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 3/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 4/48
This sort of huge information database traversing national and
international boundaries can be of significant importance especially due to the
newly liberalized policy of our country.
The key to intelligent decision-making, which is an engrained processin business, is having the right information at the right point of time
precipitating in higher profits and better bottom lines.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 5/48
OBJECTIVES OF PROJECT
In today’s world, technology plays an important role in enhancing the work
culture that’s prevalent in various companies. It can be implemented for various
purposes resulting in major improvements in the company’s way of life. The
following are ways in witch technology can be implemented in today’s corporate
façade: -
Easy accessibility of data to client:
The client is capable of accessing data from the central database at any
time from any place using the online transaction facility.
Fast paced dealing with the parent company:
Using online transaction facility, the client any time make clarifications
regarding any transaction that was previously made with the parent
company.
Ease of online communication using website:
It greatly helps to save valuable time involved for the purpose of
transacting business between the supplier and the client.
Broader access to the world and hence a world wide output:
From the company’s point of view, by putting uo anon lien transaction
facility, it can appeal to a wide range of clients world wide, thus helping to
increase the profitability of the company.
Helps save lot of time for both client and the company:
With online transaction facility made available, the client is able to transact
business with the company in a faster and more efficient way, thus
keeping up pace with the competitive business world.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 6/48
FEASIBILITY STUDY
An important outcome of the initial investigation of the system is that
the system is found to be feasible. Three key considerations are in the
feasibility analysis viz. economic, technical and operational.
Economical Feasibility:
Economic analysis is the most frequently used for evaluating the
effectiveness of the system. It is used to determine the benefits and saving
that are expected from the system and then compare them with the cost.
Operational feasibility:
The proposed system is user friendly and to operate. The system provides
the following advantages: -
Completely menu driven.
With appropriate error message for every screen, the user
can easily operate the system.
The system provides proper validation checks on the fields used in
the system.
The system is capable of producing clean and understandable
reports for the company.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 7/48
EXISTING SYSTEM
The company currently uses registers, which has some limitations like
from designing, use of graphics etc. It is not user friendly, which is one
drawback, and most of the transaction is also done manually. The transactions
involved in purchase of goods or products, which includes enquiry, quotations,
purchase, which includes enquiry, quotations, purchase order, invoice, excise
etc all has to be maintained manually. In this system, it is very difficult to locate
particular information at any given time, thus a lot of time is wasted.
NEED FOR THE SYSTEM
In order to overcome the problems faced by keeping a manual track of
data and information, the company has decided to computerize their
transactions over the web-using JAVA. The existing manual system has
drawbacks, such as the time required to locate particular information is more.
Generating various types of reports is time consuming as well as difficult.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 8/48
3. DEVELOPMENT PROCESS AND DOCUMENTATION
3.1 REQUIREMENT ANALYSIS AND SPECIFICATIONS
3.1.1 HARDWARE REQUIREMENTS
Processor : Pentium III 800 MHz
Memory size : 128 MB RAM
Storage : 20 GB Hard Disk
1.44 MB - 3.5” Floppy Disk
Display : EGA/VGA Color Monitor
600 x 800 Pixels Resolution
High Color (16 Bit)
Key Board : Any with minimum required keys
Mouse : Any
3.1.2 SOFTWARE REQUIREMENTS
Operating System : Windows 2k family.
Front-End Tool : HTML, Java Script, J2EE (Servlets, JSP , JDBC
and Java Bean)
Web Server : Apache Tomcat 5.0.
Back-End Tool : Ms-Access
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 9/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 10/48
3.1.3 DATA DICTIONARY
Data dictionary is a repository that contains all the description of all data
produced by the software. It is an organized listing of all data elements that are
pertinent to the system.
Field Name Field
Type
Field
Length
Constraint
s
Description
Referencemember id
Number 15 Primary key This is primary key
which is uniquePassword Varchar2 20 Not Null Password of the user Retypepassword
Varchar2 20 Not Null Confirmation
passwordMiddle name Varchar2 20 Not Null Middle name of the
user First name Varchar2 10 Not Null First name of the user Last name Number 15 Not Null Last name of the
user Date of birth Date Not Null Date of birth of user Address Varchar2 100 Not Null Address of the user Email id Varchar2 25 Null e-mail of the user Phone number Number 10 Not Null Phone number Credit cardnumber
Varchar2 10 Null Credit card number
MEMBER ID Varchar2 10 NotNull Member identityPASSWORD Varchar2 20 Not Null Member passwordDATE OFBIRTH
Varchar2 20 Not Null Member date of birth
REFERENCEMEMBER ID
Number 15 Primary key Reference member id
PRODUCT ID Varchar2 20 Not Null Product number PRODUCTNAME
Varchar2 20 Not Null Product name
QUANTITY Number 20 Not Null Total quantityAMOUNT Number 10 Not Null Net amount
CREDIT CARDNUMBER Number 25 Null Credit card number
QUOTATIONID
Varchar2 10 Not Null Quotation lnumber
ENQUIRY ID Number 10 Null Enquiry number CUSTOMERID
Number 10 NotNull Customer number
PRODUCT ID Number 10 NotNull Product number
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 11/48
MEMBERSHIPDETAILS
Varchar2 15 Not Null Membership deails
DATE Date Not Null Date of purchaseREMARKS Varchar2 20 Not Null Remarks if anyENQUIRY ID Number 20 Not Null Enquiry number
MEMBER ID Number 10 Not Null Member identityDATE Date Null Date of enquiryPRODUCTENQUIREDFOR
Varchar2 100 Not Null Product details
DESCRIPTION Varchar2 10 Null DescriptionYOUR E-MAIL-ID
Varchar2 15 NotNull Mail id
REFERENCEMEMBER ID
Number 15 NotNull Reference member
REFERENCE
MEMBERNAME
Varchar2 15 NotNull Reference member
name
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 12/48
3.1.4 DATA FLOW DIAGRAM
Level 0:
N
ANO
C
O S MA TIC
C LIENT
S U PPLI ER
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 13/48
Level 1:
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 14/48
3.2 SYSTEM DESIGN
3.2.1 DATABASE DESIGN
Database design takes a pivotal role in the development of any application
software. A database is a collection of tables is used to store the related
information it minimum redundancy to serve many users quickly and
efficiently. In this project the tables are designed efficiently(Not duplicate or
orphan records) by applying First, Second Normal form to reduce the
redundancy and not store the orphan records.
Normalization
Normalization is a step-By-step procedure of putting the relation in a form
that is free from all sorts of anomalies. The normalization theory is built
around the concept of the normal forms. The relation is said to be in a
particular form. If it is satisfies certain specified.
In this project, normalization is carried out for the reason given bellow
To reduce the redundancy
To structure the data
Unnormalized Form:
The unnormalized table is that which does not satisfy any constraints. The
table is in unnormalized form if it has multiply entries for a single
corresponding entry.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 15/48
3.2.2 INPUT DESIGN
The following inputs are required in the proposed system for database as
well as for data manipulation. The input for following modules.
Registration
Quotation
Enquiry
Purchase Order
Invoice
All the above modules are used in the following controls. They are
Buttons:
The most widely used control is the push button. A push button is a
component that contains a label and that generates an event when it is pressed.
Text Area:
Sometimes a single line of text input is not enough for a given task. To
handle these situation, the AWT includes a simple multi line editor called Text
Area.
Text Field:
Text field class implements a single line text entry area, usually called an
edit control. Text field allows the user to enter strings and to edit the text using
the arrow keys, cut and paste keys and mouse selection.
Radio Button:
It is possible to create a set of mutually exclusive check boxes in which
one and only one check box in the group can be checked at any one time.Drop_ Down Box:
The drop_ down box class provides a compact, multiple- choice, scrolling
selection list. Unlike the choice object, which shows only the single selected item
in this menu.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 16/48
Example:
ADD NEW USER
USER NAME:
LOGIN NAME :
PASSWORD:
DOB :
E-MAIL :
SAVECANCE
L
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 17/48
IMPLEMENTATION
The implementation is the process of converting the design into actual
code. The implementation process is done after completing the designing task.
The goal is to provide the logical order for a creation of the modules and
creation of the system.
The implementation of any software requires perfect satisfaction of the
user. The proposed system takes into account the various difficult faced by the
users in operating system and provides user friendly operations.
The system is implemented in the server and checked for its performance
and accuracy. Successful implementation of the software is accomplished. This
project is to be done using J2EE as front end and Ms-Access as back end. This
project use JSP, HTML controls and events, connected through JDBC ODBC
source.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 18/48
TESTING
Software testing is a critical elements of software quality assurance and
represents the ultimate review of specification, design, coding. The engineer
creates a serious of test cases that are intended to “demolish” the software that
has been built. In fact, testing is the one step in this software engineering
process, that could be viewed as destructive rather than constructive. The testing
process is divided into Three major components as follows
• Unit Testing
• Integration Testing
• Validation Testing
UNIT TESTING
The software is tested using the unit test method. Unit testing focuses
verification effort on the smallest unit of software design module. Using the
procedural design description as a guide, important control parts are tested to
uncover errors with in the boundary of the module.
Every module in the project is checked for verification.
Example:
Error Description Correction
float avg; Variable avg may not float avg=0;
have been initialized.
avg=avg+Double.parseDouble Missing Term Give the missed
(rs1.getFloat(9))) Term
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 19/48
INTEGRATION TESTING
This testing is the systematic technique for constructing the program structure
by performing the test in each module and later combining the entire individual module
to form a very large program.
Example:
Error:
The requested resource (http://localhost:8080/dhana/html/resource.html) is not
available.
Correction:
The requested resource should be specified for calling the correct page.
VALIDATION TESTING
Validation testing is the process of testing the input. Whether the given
inputs are valid or invalid.
Example:
The error message will be displayed whenever the wrong data entered
into the textbox. If (Prj_Id=”XXX”) then error message will be displayed. Because
it accept only number.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 20/48
MAINTENANCE ISSUES
The term “software maintenance” is used to describe the software
engineering activities that occur following delivery of a software product to the
customer. The maintenance phase of the software life cycle is the time period in
which a software product performs useful work.
In this project deals adaptive maintenance. Adaptive of software to a new
environment may involve moving the software to a different machine. Problem
correction involves modification and revalidation of software to correct errors.
The enhancement of this project can be accomplished easily. That is, any
new functional capabilities can be added to the project by simply including the
new module in the homepage and giving a hyperlink to that module. Adaptation
of this project to a new environment is also performed easily.
Adaptive Maintenance:
Adaptive maintenance results in the modification to the software to
accommodate changes to its external environment. In this project, dynamically
we can add new components when ever necessary. Such as it designed to
accommodate the new change in further.Adaptation of this software to a new environment may involve moving the
software to a different machine. Such as Windows 2000, Windows NT, Windows
98, Windows 95.
Re-Engineering:
Re-Engineering is entirely modifying the existing one. This project deals
with
re-engineering concept because entirely modify the software in this project.
Benefits of software:
More security
Easy to access
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 21/48
CONCLUSION
The “CATALOG MANAGEMENT SYSTEM” has been developed to
overcome the problem faced in the present system. The developed package was
found to work out the operation effectively. The objectives of the system have
been achieved.The goals that have been achieved are:
Ensure process time and increase throughput.
Simplifies the operation.
Avoid some manual work in the existing system.
Reduce data redundancy and inconsistency.
User friendly input screens to enter data.
A consistent and efficient system has been successfully developed,
implemented and tested. The system has been developed using J2EE and
Oracle8i under Windows 2000. The system is very flexible and user friendly. So
further changes can be incorporated into the system easily. Adequate
documentation provides for maintenance and future enhancement.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 22/48
BIBLIOGRAPHY
Java Server Pages
-James Goodwill, BPB Publications, I Edition.
Software Engineering
- Roger’s Pressman, Mc Graw Hill Publications
Java2 complete reference
-Herbert Schildt
JavaScript
- David Flanagan (O’Reilly)
http://www.javascript.com
http://www.w3schools.com
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 23/48
APPENDIX
6.1 SOFTWARE PROFILE
Windows 2000:
The computing world was presented with the first release of the
totally new and revolutionary operating system. Microsoft windows performance
and features that previously has been accessible only on $20,000 annotations
became instantly available to anyone with a high-end personal computer.
Windows is now Microsoft Corporation’s premier operating system. Designed
around powerful and well thought software architecture, the primary features that
allow Windows to use the full power of today’s processors are:
Scalability:
The ability to run on a single pc chip with a single user up to a multi-
user, microprocessor and network installation.
The Windows GUI:
The familiar graphical user interfaces it presents to the world.
Technologies used:
J2EE:
J2EE is introduced in 1998 defines a multi-tier architecture for
Enterprise Information Systems (EIS).By defining the way in which the multi-tier
application should be developed; J2EE reduces the costs, in both time and
money, of developing large scale enterprise systems. The J2EE platform
specifies the logical application components within a system and defines the
roles played in the development process.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 24/48
While developing a project, it is significant that the technologies using for
development must be reliable, flexible and robust. In case of a customer support
tool application like this, the matter is more important because it details with a
large number of clients and handles confidential data. After comprehensive
analysis, found that java and related technologies are more suitable for customer
support tool applications since java has many features set that allow it to be an
effective platform for customer support tool.
In addition, Sun has a strong understanding of the critical business
issues necessary to consider for customer tool. Another reason that java in
variety of application servers. Java 2 Enterprise Edition (J2EE) makes the java
language an even better in the customer arena because of some key features
like:
J2EE makes java a fully-fledged server-side development
platform.
J2EE has a solid infrastructure that provides a well-tested
implementation of much common applications needs such assecurity and messaging.
J2EE standardizes development making it easier for
companies to commit to J2EE.
Java2 Enterprise Edition or J2EE is a package of specifier
aligned to enable the development of multiplier enterprise
applications.
The specifications outline the various components needed
within J2EE enterprise systems the technologies for accessing and
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 25/48
providing services and even the roles played during the
development, deployment and runtime lifecycle.
J2EE handles many critical tasks of customer support tool
such as login maintenance and database maintenance and access.
J2EE Architecture:
Intermediate compilation
Runtime VM interpretation
Application Components
Four application components are defined in J2EE Platform .They are
Application Components(Stand alone java clients)
Applets(java code which executes within a browser)
Web Components(JSPs, Servlets)
Server Components(EJBs, J2EE, API implementations)
Web Components
JAVA CODE
JAVA BYTE
CODE
WIN32 HP-VX Solaris
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 26/48
They are server side components generally used to provide the
presentation layer to be returned to a client. 2 types of web components existing
are Java Server Pages (JSPs) and Java, Servlets.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 27/48
Java Server Pages:
There are two ways to achieving dynamic content generation. They are,
Programmatic content generation.
Template-based content generation
Java Servlets fall into the first category, while Java server pages belong to
typically comprise of
Static HTML/XML components
Special JSP Tags
Optionally, snippet of code written in Java Programming Languagecalled “Scriplets”.
Unlike a plain HTML page, which contains static content that always
remain the same, a Jsp page can change its content based on any number of
variable items, including the identify of the user, the users browser type,
information provided by the user, and selections made by the user.
A Jsp page contains standard markup language element such as HTML
tags, just like a regular web page. A jsp element that allow the server to insert
dynamic content in the page. Jsp elements can be used for a wide variety of
purposes, such as retrieving user preferences. Jsp pages share the “Write Once,
Run anywhere” characteristics of Java technology. Jsp technology is a key
component in the java 2 platform, enterprise edition, and Sun’s highly scalable
architecture for enterprise applications.
Jsp can use the full capability of Java components such as JDBC, RMI,
CORBA, JMS and JNDI. Java Server Pages are built on top of Java servlets and
are designed to increase the efficiency in which programmers and even non-
programmers can create web content. The main advantages of using JSP are:
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 28/48
JSP pages can be used in the combination with servlets that
handle the business logic, the modal supported by Java servlet
template engines.
Java Server Page Process:
JSP pages are interpreted only once; to java byte-code and
reinterpreted only when the file is modified.
JSP supports both scripting based and element based dynamic
content, and allows programmers to develop custom tag libraries to
satisfy application-specific needs.
JSP pages are pre-compiled for efficient server processing.
JSP run on all the main web servers.
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 29/48
It is true that both servlets and JSP pages have many features in common
and can be used for serving up dynamic web content. Naturally, this may cause
some confusion as to when to opt for one of the technologies over the other.
Java Server Pages provide a much cleaner separation of presentation from logic,
and are simpler to write. Together, JSP technology and servlets provide an
attractive alternative to other types of dynamic web scripting/programming that
offers platform independence, enhanced performance, and separation of logic
from display, ease of administration, extensibility into the enterprise and most
importantly, ease of use.
Server Components
Server components can be in form of EJBs (Enterprise Java beans).
EJB’s executes within a container that manages the runtime behavior of EJBs.
Working with the Model View Controller
Typically entity beans are used to provide the model logic, while a mix of
entity beans and session beans are used to provide the control logic and web
components are used to Implement both control and presentation logic.
The Java Beans specification allows software components to be written in
java, which encapsulates the logic behind the web application and remove the
bulk of the script let code that would otherwise clutter up the jsp. The result Jsp
code that is simpler, easier to maintain, and which is more readily accessible to
non-programmers.
Java uses the beans specification to allow the creation of software
components that can be used by other developers and designers to build
specialist applications. Java’s cross platform nature means that the same Java
bean should be reusable across any machine. This really frees us from
dependence on any particular platform
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 30/48
Server Specification
Introduction
This is the top-level entry point of the documentation bundle for the Tomcat 4Servlet/JSP container. Tomcat 4 implements the Servlet 2.3 and JavaServer Pages 1.2 specifications from Java Software, and includes many additionalfeatures that make it a useful platform for developing and deploying webapplications and web services.
Select one of the links from the navigation menu (to the left) to drill down to themore detailed documenation that is available. Each available manual isdescribed in more detail below.
Application Developers
The following documents are aimed at Application Developers who areconstructing web applications or web services that will run on Tomcat.
• Application Developer's Guide - An introduction to theconcepts of a web application as defined in the Servlet 2.3
Specification. Covers basic organization of your web applicationsource tree, the structure of a web application archive, and anintroduction to the web application deployment descriptor (/WEB-
INF/web.xml).
• Servlet/JSP Javadocs - The Servlet 2.3 and JSP 1.2 APIJavadocs.
Catalina Developers
The following documents are for Java developers who wish to contribute to thedevelopment of the Catalina servlet container portion of Tomcat itself, or tobetter understand its internal architecture and operation.
• Functional Specifications - Requirements specificationsfor features of the Catalina servlet container portion of Tomcat 4.
• Javadocs - Javadoc API documentation for the Catalina
servlet container portion of Tomcat 4.
Configuring Tomcat
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 31/48
This section will acquaint you with the basic information used during the
configuration of the container.
All of the information in the configuration files is read at startup, meaning that
any change to the files necessitates a restart of the container
6.3 TABLE STRUCTURE
REGISTRATION FORM
FIELDNAME DATATYPE KEY TYPE
REFERENCE MEMBER ID NUMBER(15) PRIMARY KEYPASSWORD VARCHAR(20) NOT NULLRETYPE PASSWORD VARCHAR(20) NOT NULLMIDDLE NAME VARCHAR(20) NULLFIRST NAME VARCHAR(20) NOT NULLLAST NAME VARCHAR(20) NOT NULLDATE OF BIRTH DATE NOT NULLAGE NUMBER(3) NULLSEX VARCHAR(6) NOT NULLADDRESS VARCHAR(20) NOT NULLEMAIL ID VARCHAR(20) NOT NULL
PHONE NUMBER NUMBER(15) NOT NULLCREDIT CARD NUMBER NUMBER(15) NOT NULL
PURCHASE ORDER
FIELDNAME DATATYPE KEY TYPE
MEMBER ID NUMBER(15) PRIMARY KEYPASSWORD VARCHAR(20) NOT NULLDATE OF BIRTH DATE NOT NULLREFERENCE MEMBER ID NUMBER(15) FOREIGN KEY
PRODUCT ID NUMBER(15) NOT NULLPRODUCT NAME VARCHAR(20) NOT NULLQUANTITY NUMBER(15) NOT NULLAMOUNT NUMBER(15) NOT NULLCREDIT CARD NUMBER NUMBER(15) NOT NULL
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 32/48
QUATATION
FIELDNAME DATATYPE KEY TYPE
QUOTATION ID NUMBER(15) PRIMARY KEY
ENQUIRY ID VARCHAR(20) NOT NULLCUSTOMER ID VARCHAR(20) NOT NULLPRODUCT ID NUMBER(15) FOREIGN KEYQUANTITY NUMBER(15) NOT NULLAMOUNT NUMBER(15) NOT NULLMEMBERSHIP DETAILS VARCHAR(100) NOT NULLDATE DATE NOT NULLREMARKS VARCHAR(20) NULL
ADDRESS DETAILS
FIELDNAME DATATYPE KEY TYPE
FIRST NAME VARCHAR(20) NOT NULLLAST NAME VARCHAR(20) NOT NULLADDRESS VARCHAR(50) NOT NULLCITY VARCHAR(20) NOT NULLSTATE VARCHAR(20) NOT NULLCOUNTRY VARCHAR(20) NOT NULLOTHER COUNTRY VARCHAR(20) NOT NULL
PIN CODE NUMBER(10) NULLPHONE NUMBER NUMBER(15) NOT NULLCREDIT CARD NO. NUMBER(15) NOT NULL
REGISTERED CUSTOMER
FIELDNAME DATATYPE KEY TYPE
MEMBER ID NUMBER(15) PRIMARY KEYPASSWORD VARCHAR(20) NOT NULL
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 33/48
ADMINISTRATOR
FIELDNAME DATATYPE KEY TYPE
ADMINISTRATOR NAME VARCHAR(20) PRIMARY KEYPASSWORD VARCHAR(20) NOT NULL
ENQUIRY DETAILS
FIELDNAME DATATYPE KEY TYPE
ENQUIRY ID NUMBER(15) PRIMARY KEYMEMBER ID NUMBER(15) FOREIGN KEYDATE DATE NOT NULLPRODUCT ENQUIREDFOR
VARCHAR(20) NOT NULL
DESCRIPTION VARCHAR(50) NULLYOUR E-MAIL-ID VARCHAR(20) NOT NULLREFERENCE MEMBERID
NUMBER(15) FOREIGN KEY
REFERENCE MEMBERNAME
VARCHAR(20) NOT NULL
INVOICE FORM
FIELDNAME DATATYPE KEY TYPE
INVOICE ID NUMBER(15) PRIMARY KEYORDER ID NUMBER(15) FOREIGN KEYDATE OF BIRTH DATE NOT NULL
MEMBER ID NUMBER(15) FOREIGN KEYREFERENCE MEMBER ID NUMBER(15) FOREIGN KEYTOTAL AMOUNT NUMBER(10) NOT NULLAMOUNT PAID NUMBER(15) NOT NULLBALANCE AMOUNT NUMBER(15) NOT NULL
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 34/48
6.4 SCREEN LAYOUT
HOME PAGE
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 35/48
RULES & REGULATIONS
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 36/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 37/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 38/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 39/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 40/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 41/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 42/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 43/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 44/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 45/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 46/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 47/48
8/7/2019 Documentation of Catalog Mgmt. in J2EE
http://slidepdf.com/reader/full/documentation-of-catalog-mgmt-in-j2ee 48/48