Documentation of Activity Management System II in J2EE

ACTIVITY MANAGEMENT SYSTEM

Abstract:

This is a project of ACTIVITY MANAGEMENT SYSTEM for a

PRUDENTIAL bank. The client is the person who comes for the sake of

getting premium from the agent of a prudential bank. (Here agent is

the one who gets the premium from the client. The duty of the agent is

not only to get the premium from the client but agent sees how the

client can be convinced to pay the premium.)

The system is to automate agent’s reports. This can be used for

maintaining and evaluation of sales activities. It allows the life advisor

to set goals and accomplish them. It is very useful to motivate the

advisor to do better, with reference of his previous progress.

Use of the project:

This project has been developed as per the general requirements

of an Insurance Advisor. But it is going to be at most customized for

the Prudential Insurance Advisor. This software can also be used or

modified as per the exact requirements of any particular Insurance

company’s Insurance Advisor.

In this project JSP is used instead of applets because the agent

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.

1. INTRODUCTION

1.1 OBJECTIVES

Internetworking is the livewire of today’s world, it has ushered in

a whole new era of evolution, that has brought about a sea of change

to this New World. With the advent of new concepts and technologies,

the whole world has been linked into one single cobweb of information.

Key to this evolution is the developments of Networking and

Information Sharing.

This project is classified into four main modules namely Zonal

Manager, Manager, Agent and Customer. And all these modules have

their own sub-modules with respect to their functionalities.

Before getting into the module first we have to know about the

login details. Here each module is having its own user name and

password. For example in the Zonal Manager module there will be a

number of Zonal Managers working in the organization. For each Zonal

Manager one unique user name and password will be provided. With

this user name and password only that particular person can enter into

the module. Before doing this we should know the validation rules

which are used in this project.

Validation Rules

The Login name and password should not be empty.

The Login name should contain only alphabets. No numerals and

special characters are allowed here.

The password should contain only alphabets and numbers. No

special characters are allowed here.

The length of the password should be between 5 and 10 only.

2. PROBLEM DEFINITION AND METHODOLOGY

2.1 DEFINITION

This project “Activity Management System” is designed to

give a complete solution for any type of Insurance Company. This

project is classified into four modules. They are :-

Zonal Manager Module

Manager Module

Agent Module

Customer Module

Zonal Manager Module

This module will describe about the various functionalities of the

Zonal Manager. Each zonal manager will be given with one user name

and password. With this the zonal manager has to enter into his

module. If a zonal manager login to his page then he will be given his

home page called the zonal manager task page. This page will also

display the name of the particular Zonal Manager with his manager id.

In this page the functionalities and controls of the user will be given.

These are the sub-modules of this Zonal Manager module. They are,

Zonal Manger List

Manager List

Branch List

Add New Branch

Agent List

Replace Manager

Incentive Details

Policy Details

Logout

Zonal Manager List

This sub-module is used to retrieve the list of Zonal Mangers who

have registered in the particular organization. Here the details of all

the zonal mangers will be given. These details comprise zonal manger

id, first name, last name and the user name. These details will be

available only in the Zonal Manager module. From other modules we

can’t retrieve these data. So the data is secured here.

Manager List

This sub-module is used to retrieve the list of managers with

their details who were working under the particular Zonal Manager. In

an organization there will be several zones and each zone will have

several managers. These managers’ details can be retrieved here by

zone wise. This will be helpful for the zonal managers to check the

managers are working for that particular zone.

Branch List

This module is used to retrieve the list of branches that comes

under a particular zone. Here the Zonal manager number is given to

identify the particular zone in which the branches were selected. Here

the details like the Branch No, Branch Name, Address of that Branch

and the Manger Name for that particular branch are given. This will be

useful for the Zonal Manager to check the branch details in less time.

A snapshot of this sub-module is shown here.

Add New Branch

This module helps the Zonal Manager to add a new branch in his

zone. This facility is only authorized to the Zonal Manager. Other

managers cannot have this functionality. Here the Zonal Manager has

to give a new manager for that branch. That details of the manager

name, login name, password, e-mail id, address and phone number

should be given.

Agent List

This module is used to retrieve the whole details of the agents

belonging to that particular zone. Here the agent details like agent

number, name, login name, policy type, branch number and policies

sold so far were given. With these details the Zonal Manager can

check the performance of the agents and he can assign incentives for

the agents based on their performances.

Replace Manager

This module helps the Zonal Manager to change or replace a

branch manager from one branch to another. If a particular branch

manager is getting retired or transferred to another branch then a new

manager has to be appointed for that branch. The Zonal Manager can

use this facility to replace the managers by selecting the branch

number in which they were working.

Here the Zonal Manager has to select the branch number in

which the manager has to be changed. If a branch is selected then it

moves to the next page where has to give the new manager’s details.

Once these details were entered then the particular branch manager

details will be changed automatically in the database.

Incentive Details

In this module the Zonal Manager can fix the incentives for the

agents based on the targets they achieved. Every agent will be given

a target day and task. Based on the task completed by the agent at

the end of the target day he will receive an Incentive amount. This

amount will be fixed only the zonal manager. Every month the zonal

manager can allot the incentive or he can set the incentive amount as

per the target achieved.

Policy Details

This module is used to view the details of what are all the

policies that particular organization has. In that each policy will be

explained in a detailed manner. Some of the details are: General

Policy Conditions, Requirements, Benefits, Premium amount, Premium

period and so on. Like this all the policies will have its own document

details.

Logout

This is used to close the session of the Zonal Manager Login. If

the user has logged out it will take the user to home page of the

Activity Management System.

Manager Module


Manager. Each manager will be given with one user name and

password. With this the manager has to enter into his module. If a

manager login to his page then he will be given his home page called

the manager task page. This page will also display the name of the

particular Manager with his manager id. In this page the functionalities

and controls of the user will be given. These are the sub-modules of

this Manager module. They are,

Manger List

Agent List

Add New Agent

Set Target

Performance Report

Policy Details

Logout

Agent Module


agent. Each agent will be given with one user name and password.

With this the agent has to enter into his module. If an agent login to

his page then he will be given his home page called the agent task

page. This page will also display the name of the particular agent with

his agent id. In this page the functionalities and controls of the user

will be given. These are the sub-modules of this agent module. They

are,

Enquiry Details

Customer Entry

Appointment Details

Policy Details

Agent List

Incentive Report

Activity Report

Logout

Client Module


client. Each client will be given with one user name and password.

With this the client has to enter into his module. If a client login to his

page then he will be given his home page called the client task page.

This page will also display the name of the particular client with his

client id. In this page the functionalities and controls of the user will be

given. These are the sub-modules of this client module. They are,

My Account

Change Password

Policy Details

My Policy

Payment Details

LOGOUT

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 : SQL-Server

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

Constrai

nts

Description

ZMGNO Number 15 Primary

key

This is primary key

which is uniquely

identify a client

FirstName Varchar

2

20 Not Null First Name of the

Zonal Manager

LastName Varchar

2

20 Not Null Last Name of the

Zonal Manager

LoginName Varchar

2

20 Not Null Manager login

name

LoginPwd Varchar

2

10 Not Null Manager Password

MGNO Number 15 Primary

key

This is primary key

which is uniquely

identify a client

FirstName Varchar

2

20 Not Null First Name of

Manager

LastName Varchar

2

20 Not Null Last Name of

Manager

LoginName Varchar

2

20 Not Null Manager login

name

LoginPwd Varchar

2

10 Not Null Manager Password

EmailId Varchar2 25 Null E_Mail Address of

the manager

Address Varchar2 100 Not Null Address of the

manager

Phoneno Varchar2 10 Null Phone no of the

manager

Brno Varchar2 10 NotNull Branch No of

manager

Username Varchar

2

20 Not Null Name of the user

password Varchar

2

20 Not Null Password for the

user

AGNO Number 15 Primary

key

This is primary key

which is uniquely

identify a client

FirstName Varchar

2

20 Not Null First Name of Agent

LastName Varchar

2

20 Not Null Last Name of Agent

LoginName Varchar

2

20 Not Null Agent login name

LoginPwd Varchar

2

10 Not Null Agent Password

EmailId Varchar2 25 Null E_Mail Id of the

Agent


agent


agent

Brno Varchar2 10 NotNull Branch No of the

agent

PType Varchar2 10 NotNull Policy Type

Target Varchar2 10 NotNull Target to be

achieved

PoliciesSol

d

Varchar2 10 NotNull No. of policies sold

CSNO Number 15 Primary

key

This is primary key

which is uniquely

identify a client

FirstName Varchar

2

20 Not Null First Name of

customer

LastName Varchar

2

20 Not Null Last Name of

customer

LoginName Varchar

2

20 Not Null Customer login

name

LoginPwd Varchar

2

10 Not Null Customer Password

EmailId Varchar2 25 Null E_Mail Id of

Customer


customer


customer

AGNO Number 15 NotNull Customer’s agent

number

3.1.4 DATA FLOW DIAGRAM

ZONAL MANAGER

MANAGER

AGENT LIST

ACCOUNT

AGENT

POLICY DETAILS

CUSTOMER ENTRY

ENQUIRYACTIVITYREPORT

INCENTIVE REPORT

PERFORMANCE REPORT

CUSTOMER

AGENT

APPOINTMENT

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.

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.

ZONAL MANAGER MODULE

MANAGER MODULE

AGENT MODULE

CUSTOMER MODULE

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.

Example:

ADD NEW AGENT

AGENT NAME :

LOGIN NAME :

PASSWORD :

POLICY TYPE :

SAVE CANCEL

3.2.3 OUTPUT DESIGN

The output design used to generate a report. The reports are

Performance Report

Activity Report

Incentive Report

Performance Report

This performance report is used to display the performance of

each and every agent who is all connected to a particular manager.

These reports include the number of policies sold by an agent, target

achieved and the incentive amount.

Activity Report

This report is used to display the activities performed by an

agent over a particular period of time. Here the agent has to select

the period in which his activity has to be checked.

Incentive Report

This report is used to generate the amount of incentive to be

received by an agent for his target period. In this report the agent can

see his target starting date, target ending date, target achieved during

this period and the incentive amount.

3.3 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.

3.4 TESTING

Software testing is a critical element 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;

avg=avg+Double.parseDoubl

e

(rs1.getFloat(9)))

Variable avg may

not have been

initialized.

Missing Term

float avg=0;

Give the missed

Term

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.

3.5 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

4. CONCLUSION

The “ACTIVITY 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.

5. BIBLIOGRAPHY

Java Server Pages

-James Goodwill, BPB Publications, I Edition.

Software Engineering

- Roger’s Pressman, Mc Graw Hill Publications

Java2 complete reference

-Herbert Schildt

Oracle SQL * Plus

- Jonathan Gennick (O’Reilly)

The Programming Language of ORACLE

- Ivan Bay Ross, II Edition.

JavaScript

- David Flanagan (O’Reilly)

6. 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.

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

as security 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 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

JAVA CODE

JAVA BYTE CODE

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

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.

Java Server Pages:

There are two ways to achieving dynamic content generation.

They are,

Programmatic content generation.

Template-based content generation

WIN32 HP-VX Solaris

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 Language called “Scriplets”.

Unlike a plain HTML page, which contains static content that

always remain the same, a JSPs 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:

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.

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

Database used:

Database is a major concern in a customer support tool

application. Hence, made a detailed study to find the most suitable

databases for this project. The result was Oracle which is the most

powerful database with reliable features.

Oracle:

Oracle is a trademark of Oracle Corporation and in

common usage refers to the database engine (which actually looks for

the data) and the range of front-end products. Oracle 8i is the largest

selling SQL-based RDBMS and a most commercially useful product.

Advantage of Oracle 8i:

Portability

Oracle is ported for more platforms than any of its

competitors running on more than 100 hardware platforms and 20

Networking protocols. This makes writing an Oracle application fairly

safe from changes of direction in hardware and operating system and

therefore a safe bet. You can develop a fairly full-featured application

with little knowledge of the underlying operating system. Oracle 8i

provides support for online backup and recovery and good software

fault tolerance to disk failure. You can also do point-in-time recovery.

Performance

Speed of Oracle 8i database is quite well managed. Even with

large database oracle 8i refers to more than 100GB databases and the

performance is only “raw”. But includes consideration of performance

with locking and transaction control.

Server Specification

Introduction

This is the top-level entry point of the documentation bundle for the Tomcat 4 Servlet/JSP container. Tomcat 4 implements the Servlet 2.3 and JavaServer Pages 1.2 specifications from Java Software, and includes many additional features that make it a useful platform for developing and deploying web applications and web services.

Select one of the links from the navigation menu (to the left) to drill down to the more detailed documenation that is available. Each available manual is described in more detail below.

Application DevelopersThe following documents are aimed at Application Developers who are

http://java.sun.com/products/servlet/

http://java.sun.com/products/jsp/

constructing web applications or web services that will run on Tomcat.

Application Developer's Guide - An introduction to the concepts of a web application as defined in the Servlet 2.3 Specification. Covers basic organization of your web application source tree, the structure of a web application archive, and an introduction to the web application deployment descriptor (/WEB-INF/web.xml).

Servlet/JSP Javadocs - The Servlet 2.3 and JSP 1.2 API Javadocs.

Catalina DevelopersThe following documents are for Java developers who wish to contribute to the development of the Catalina servlet container portion of Tomcat itself, or to better understand its internal architecture and operation.

Functional Specifications - Requirements specifications for features of the Catalina servlet container portion of Tomcat 4.

Javadocs - Javadoc API documentation for the Catalina servlet container portion of Tomcat 4.

Configuring TomcatThis 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

http://localhost:8080/tomcat-docs/catalina/docs/api/index.html

http://localhost:8080/tomcat-docs/catalina/funcspecs/index.html

http://localhost:8080/tomcat-docs/servletapi/index.html

http://java.sun.com/products/servlet/download.html

http://java.sun.com/products/servlet/download.html

http://localhost:8080/tomcat-docs/appdev/index.html

6.3 TABLE STRUCTURE

Table Name: AGT

Primary Key: AGNO

FIELDNAME DATATYPE KEY TYPE

AGNO NUMBER(15) PRIMARY KEY

FIRSTNAME VARCHAR(20) NOT NULL

LASTNAME VARCHAR(20) NOT NULL

LOGINNAME VARCHAR(20) NOT NULL

LOGINPWD VARCHAR(10) NOT NULL

EMAILID VARCHAR(20) NULL

ADDRESS VARCHAR(100) NOT NULL

PHONENO VARCHAR(20) NULL

BRNO VARCHAR(20) NOT NULL

PTYPE VARCHAR(20) NOT NULL

TARGET VARCHAR(20) NOT NULL

POLICIESSOLD NUMBER(15) NOT NULL

Table Name: BR

Primary Key: BRNO


BRNO NUMBER(15) PRIMARY KEY

BRNAME VARCHAR(20) NOT NULL


ZMGNO NUMBER(15) FOREIGN KEY

Table Name: CST

Primary Key: CSTNO


CSTNO NUMBER(15) PRIMARY KEY








AGNO NUMBER(15) FOREIGN KEY

Table Name: CUSTPOLICY

Primary Key: POLICYNO


POLICYNO NUMBER(15) PRIMARY KEY

CSNO VARCHAR(20) NOT NULL

PDATE VARCHAR(20) NOT NULL

YEARS NUMBER(15) NOT NULL

PAMT NUMBER(15) NOT NULL

MODE VARCHAR(20) NOT NULL

PREMIUM NUMBER(15) FOREIGN KEY

Table Name: ENQDETAILS

Primary Key: ENO


ENO NUMBER(15) PRIMARY KEY

ENQFNAME VARCHAR(20) NOT NULL

ENQLNAME VARCHAR(20) NOT NULL

ENQTYPE VARCHAR(20) NOT NULL

ENQDATE VARCHAR(10) NOT NULL




AGNO NUMBER(15) FOREIGN KEY

STATUS VARCHAR(10) NOT NULL

Table Name: MGR

Primary Key: MGNO


MGNO NUMBER(15) PRIMARY KEY








BRNO VARCHAR(20) NOT NULL

Table Name: PAYMENT

Primary Key: POLICYID


POLICYID NUMBER(15) PRIMARY KEY

DUEDATE DATE NOT NULL

PAYDATE DATE NOT NULL

PAYMENT VARCHAR(20) NULL

Table Name: ZMGR

Primary Key: ZMGNO


ZMGNO NUMBER(15) PRIMARY KEY





6.4 SCREEN LAYOUT

LOGIN FORM FOR ZONAL MANAGER

ZONAL MANAGER TASK PAGE

LIST OF ZONAL MANAGERS

MANAGER LIST FOR ZONAL MANAGER

BRANCH LIST FOR ZONAL MANAGER

ADD NEW BRANCH

AGENT LIST

REPLACE MANAGER

INCENTIVE DETAILS

POLICY DETAILS

MANAGER LIST

AGENT LIST

ADD NEW AGENT

SET TARGET FOR AGENT

PERFORMANCE REPORT

ADD NEW ENQUIRY

CUSTOMER DETAILS

AGENT LIST

INCENTIVE REPORT

CUSTOMER ACCOUNT DETAILS

CUSTOMER POLICY DETAILS

PAYMENT DETAILS

Documents

Documentation of Activity Management System II in J2EE