STATEMENT ABOUT THE PROBLEMS:There are different types of problem faced by the Spice producing Farmers, manuf acturing

companies, and Exporters. These are Lac of Transparency in Product transaction. Unavailability Online Order Processing The Sources of collecting Spice Products. Information about the spice products. Exploitation of Farmers By Manufacturer and Dealers. Another problem is that people are not getting the proper information about the spice products produced in different regions of the country .so this project can help to overcome this problem .Another facility is that Exporters and manufactu rers can apply online. 1.2 OBJECTIVE AND SCOPE OF THE PROJECT: As the taste of people is changing very frequently and it is among a fe w regions in India which are getting the opportunities of using different flavor s of Spices .So it is highly required to develop and provide all the information regarding spices and here the spice board is wor ing day and night to maintain the gap between different parties involved in spice production . So the objective of this project is to simplify the actions and provide the transparency. The project is capable of meeting needs of the organization , though it needs some modules to be sophisticated which we plan to fulfill in future . The users of the website can use it very efficiently and easily without any others help.

System Enviroment

2. An Overview of Java 2.1 About Java Initially the language was called as oa but it was renamed as Java in 1995. The pri mary motivation of this language was the need for a platform-independent (i.e., architecture neutral) language that could be used to create software to be embed ded in various consumer electronic devices. Java is a programmer s language. Java is cohesive and consistent. Except for those constraints imposed by the Internet environment, Java g ives the programmer, full control. Finally, Java is to Internet programming where C was to system programmi ng. 2.1.1 IMPORTANCE OF JAVA TO THE INTERNET : Java has had a profound effect on the Internet. This is because; Java expands th e Universe of objects that can move about freely in Cyberspace. In a networ , tw o categories of objects are transmitted between the Server and the Personal comp uter. They are: Passive information and Dynamic active programs. The Dynamic, Se lf-executing programs cause serious problems in the areas of Security and probab ility. But, Java addresses those concerns and by doing so, has opened the door t o an exciting new form of program called the Applet. 2.1.2 THE BYTE CODE : The ey that allows the Java to solve the security and portability problems is t hat the output of Java compiler is Byte code. Byte code is a highly optimized se t of instructions designed to be executed by the Java run-time system, which is called the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter for byte code. Translating a Java program into byte code helps ma es it much easier to run a pr ogram in a wide variety of environments. The reason is, once the run-time pac ag e exists for a given system, any Java program can run on it. Although Java was designed for interpretation, there is technically nothing abou t Java that prevents on-the-fly compilation of byte code into native code. Sun h as just completed its Just In Time (JIT) compiler for byte code. When the JIT co mpiler is a part of JVM, it compiles byte code into executable code in real time

, on a piece-by-piece, demand basis. It is not possible to compile an entire Jav a program into executable code all at once, because Java performs various run-ti me chec s that can be done only at run time. The JIT compiles code, as it is nee ded, during execution. 2.1.3 JAVA VIRTUAL MACHINE (JVM) : Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embe dded within a web browser or an operating system. Once a piece of Java code is l oaded onto a machine, it is verified. As part of the loading process, a class lo ader is invo ed and does byte code verification ma es sure that the code that s ha s been generated by the compiler will not corrupt the machine that it s loaded on. Byte code verification ta es place at the end of the compilation process to ma e sure that is all accurate and correct. So byte code verification is integral t o the compiling and executing of Java code. Java programming uses to produce byte codes and executes them. The first box ind icates that the Java source code is located in a. Java file that is processed wi th a Java compiler called javac. The Java compiler produces a file called a. cla ss file, which contains the byte code. The. Class file is then loaded across the networ or loaded locally on your machine into the execution environment is the Java virtual machine, which interprets and executes the byte code.

2.2 J2EE : Open and standard based platform for developing deploying and managing n-tier,Webenabled,server-centric and component-based enterprise applic ation. J2EE provides a rich set of technologies that are useful for developin g enterprise applications. In version 1.3

2.3 JDBC JDBC is a Java API for executing SQL statements. (As a point of interest, JDBC i s a trademar ed name and is not an acronym; nevertheless, JDBC is often thought of as standing for Java Database Connectivity. It consists of a set of classes a nd interfaces written in the Java programming language. JDBC provides a standard API for tool/database developers and ma es it possible to write database applic ations using a pure Java API. Using JDBC, it is easy to send SQL statements to virtually any relational databa se. One can write a single program using the JDBC API, and the program will be a

ble to send SQL statements to the appropriate database. The combinations of Java and JDBC lets a programmer write it once and run it anywhere. Simply put, JDBC ma es it possible to do three things: Establish a connection with a database Send SQL statements Process the results.

2.3.1 JDBC VERSUS ODBC AND OTHER APIS : At this point, Microsoft's ODBC (Open Database Connectivity) API is that probabl y the most widely used programming interface for accessing relational databases. It offers the ability to connect to almost all databases on almost all platform s. So why not just use ODBC from Java? The answer is that you can use ODBC from Jav a, but this is best done with the help of JDBC in the form of the JDBC-ODBC Brid ge, which we will cover shortly. The question now becomes "Why do you need JDBC? " There are several answers to this question: 1. ODBC is not appropriate for direct use from Java because it uses a C int erface. Calls from Java to native C code have a number of drawbac s in the secur ity, implementation, robustness, and automatic portability of applications. 2. A literal translation of the ODBC C API into a Java API would not be des irable. For example, Java has no pointers, and ODBC ma es copious use of them, i ncluding the notoriously error-prone generic pointer "void *". You can thin of JDBC as ODBC translated into an object-oriented interface that is natural for Ja va programmers. 3. ODBC is hard to learn. It mixes simple and advanced features together, a nd it has complex options even for simple queries. JDBC, on the other hand, was designed to eep simple things simple while allowing more advanced capabilities where required. 4. A Java API li e JDBC is needed in order to enable a "pure Java" solution . When ODBC is used, the ODBC driver manager and drivers must be manually instal led on every client machine. When the JDBC driver is written completely in Java, however, JDBC code is automatically installable, portable, and secure on all Ja va platforms from networ computers to mainframes.

2.3.2 JDBC DRIVER TYPES : The JDBC drivers that we are aware of at this time fit into one of four categori es: JDBC-ODBC bridge plus ODBC driver Native-API partly-Java driver JDBC-Net pure Java driver Native-protocol pure Java driver

2.4 SERVLETS 2.4.1 INTRODUCTION :

The Java web server is JavaSoft's own web Server. The Java web server is just a part of a larger framewor , intended to provide you not just with a web server, but also with tools. To build customized networ servers for any Internet or Int ranet client/server system. Servlets are to a web server, how applets are to the browser. Servlets provide a Java-based solution used to address the problems currently as sociated with doing server-side programming, including inextensible scripting so lutions, platform-specific APIs, and incomplete interfaces. Servlets are objects that conform to a specific interface that c an be plugged into a Java-based server. Servlets are to the server-side what app lets are to the client-side - object byte codes that can be dynamically loaded o ff the net. They differ from applets in that they are faceless objects (without graphics or a GUI component). They serve as platform independent, dynamically lo adable, plugable helper byte code objects on the server side that can be used to dynamically extend server-side functionality. For example, an HTTP Servlets can be used to generate dynamic HTML content. When you use Servlets to do dynamic content you get the following advantages: They re faster and cleaner than CGI scripts They use a standard API (the Servlets API) They provide all the advantages of Java (run on a variety of servers wit hout needing to be rewritten). 2.4.2 INVOKING SERVLETS : A Servlet invo er is a Servlet that invo es the "service" method on a named Serv let. If the Servlet is not loaded in the server, then the invo er first loads th e Servlet (either from local dis or from the networ ) and the then invo es the "service" method. Also li e applets, local Servlets in the server can be identif ied by just the class name. In other words, if a Servlet name is not absolute, i t is treated as local. A client can invo e Servlets in the following ways: The client can as for a document that is served by the Servlet. The client (browser) can invo e the Servlet directly using a URL, once i t has been mapped using the Servlet Aliases section of the admin GUI. The Servlet can be invo ed through server side include tags. The Servlet can be invo ed by placing it in the Servlets/ directory. The Servlet can be invo ed by using it in a filter chain. 2.5 JAVA SERVER PAGES (JSP) Java server Pages is a simple, yet powerful technology for creating and maintain ing dynamic-content web pages. Based on the Java programming language, Java Serv er Pages offers proven portability, open standards, and a mature re-usable compo nent model .The Java Server Pages architecture enables the separation of content generation from content presentation. This separation not eases maintenance hea daches; it also allows web team members to focus on their areas of expertise. No w, web page designer can concentrate on layout, and web application designers on programming, with minimal concern about impacting each other s wor . 2.5.1 STEPS IN THE EXECUTION OF A JSP APPLICATION : 1. The client sends a request to the web server for a JSP file by giving th e name of the JSP file within the form tag of a HTML page.

2. This request is transferred to the JavaWebServer. At the server side Jav aWebServer receives the request and if it is a request for a jsp file server giv es this request to the JSP engine. 3. JSP engine is program which can understands the tags of the jsp and then it converts those tags into a Servlet program and it is stored at the server si de. This Servlet is loaded in the memory and then it is executed and the result is given bac to the JavaWebServer and then it is transferred bac to the result is given bac to the JavaWebServer and then it is transferred bac to the clien t.

2.6 JAVA SERVER-APACHE TOMCAT Apache Tomcat is a web container, or application server developed at the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the JavaServer Pages (JSP) specifications from Sun Microsystems, providing an envir onment for Java code to run in cooperation with a web server. It adds tools for configuration and management but can also be configured by editing configuration files that are normally XML-formatted. Tomcat includes its own internal HTTP se rver. Different versions of Apache Tomcat are available for different ver sions of the Servlet and JSP specifications. The mapping between the specificati ons and the respective Apache Tomcat verisons is:

Some of the features of tomcat are written bellow : Performance optimizations and reduced garbage collection . Refactored application deployer, with an optional standalone deployer al lowing validation and compilation of a web application before putting it in prod uction . Complete server monitoring using JMX and the manager web application Complete server monitoring using JMX and the manager web application Improved Taglibs handling, including advanced pooling and tag plugins Improved platform integration, with native Windows and Unix wrappers Embedding using JMX Enhanced Security Manager support Integrated session clustering Expanded documentation 2.7 AJAX Ajax stands for Asynchronous JavaScript And Xml . Ajax is only a name gi ven to a set of tools that were previously existing. The main part is XMLHttpRequest, a class usable in JavaScript, that was implemented into Internet Explorer since the 4.0 version. The same concept was named XMLHTTP sometimes, before the Ajax name beco mes commonly used. The use of XMLHttpRequest in 2005 by Google , in Gmail and GoogleMaps ha s contributed to the success of this format. But this is the name Ajax itself th at made the technology so popular as a) AJAX is a type of programming made popular in 2005 by Google (with Googl e Suggest). b) AJAX is not a new programming language, but a new way to use existing st andards.

c) With AJAX you can create better, faster , and more user-friendly web ap plications. d) AJAX is based on JavaScript and HTTP requests.

System Specification

3.Hardware and Software requirements (1) The system must be user friendly. (2) The system must be able to handle large volume of data. (3) Processing speed of the system should be huge. 3.1 Hardware Specification The software has been developed on computers with the fo llowing specifications. The Client Machines: Processor : Intel Pentium IV Speed : 2.66GHz RAM : 512 MB Hard Dis : 80 GB Key Board (104 eys) : Standard

Networ Card The Server Machines: Processor Speed RAM Hard Dis 3.2 Software Specification Operating System Language Tools Database

: : Intel Pentium IV : 1.4GHz : 512MB : 80 GB : Windows 2000 Professional : JAVA, SQL : JSP, HTML, XML,STRUTS :ORACLE 10g

Requirements Analysis

4.1 Problem Definition and Description Existing System

The existing system is a manual system. The main tas s of the existing system are to accept their requirements from different areas in India and verify them and process. The need for computerization of the existing system arose because of many difficulties, irregularities and inaccuracy present in the current syste m. The main causes of worry include lac some important information in records a nd reports, inaccuracies in certain transactions, and various time-consuming act ivities. For example, the staff often find it difficult to eep trac of suspens e field numbers such as different area s ddc having the same amount, They fail to show proper head combinations in different reports which result in a lac of som e vital information in the reports. For an example of inaccuracy, reports are so metimes incorrectly made. Generating some reports especially the monthly reports is a very time-consuming tas . Preparing correct report is a cumbersome process as it involves a lot of differe nt calculations basing on different rules. Also copy of same record is made many times in different format. Most of the time the staff fails to represents the c orrect calculations creating controversial and pending cases. The process is a t ime consuming process resulting in late delivery of account slips. Proposed System The proposed system is completely web based. It is an internet and intra net based application. Client need not search whole site for particular informat ion. If any information is required then he can directly clic on appropriate op tion mention on the site. The system should be user friendly so that any client can easily access this site from any place at any time.

ADVANTAGES OF THE PROPOSED SYSTEM: a) Manpower can concentrate on mainstream jobs & machines can do repetitive nature of jobs. b) Introduction of self-chec ing mechanics can reduce errors and prevent ig norant or intentional irregularities. c) Computerization in networ fashion will provide an integrated MIS to all the departments and help to formulate realistic budgets. d) Systematic storage and retrieval of large amount of data. e) Capturing information from the bills can develop allied MIS. f) Decision ma ers can decide budgetary requirements and allocations. g) Expenses can be streamlined by nowing the ways and means position. h) Internal auditing and control can be carried out.

System Analysis & Design

5.1 Introduction Analysis is the focus of system developing and is the stage when system designer s have to wor at two levels of definition regarding the study of situational is sues and possible solutions in terms of what to do and how to do . System Study DEFINITION OF THE SYSTEM: A system is an orderly grouping of independent components lin ed together acco rding to a plan to achieve a specific objective. Its main characteristics are or ganization, interaction, independent, integration and central objective a system does not necessarily mean to a computer system. It may be a manual system or an y other names. NEEDS OF THE SYSTEM Social and economic factor: a wave of social and economic changes often follows in the wa e of the new technology. New opportunities may arise to improve on a p roduction process or to do something that was not previously possible. Changes i n the ways individuals are organized into groups may then be necessary, and the new groups may complete for economic resources with established units.

Technological factor: people have never before in a time when the scope of scien tific inquiry was so broad, so when the speed of applying the new technology acc ounts for many changes in the organization. High level decisions and operating processes: in response to technological, soci o-economical factors, top level managers may decide to recognize operations and introduce new products. To deal with these needs, people commonly see new modified info rmation to support the decision. When that happens, then they obtain turn to a c omputer system for help the information users and data processing specialist the n wor together to complete a series of steps in a system study to produce outpu t results to satisfy information needs. System analysis System Analysis is a process by which we attribute process or goals to a human activity, determine how well those purpose are being achieved and specify the requirements of the various tools and techniques that are to be used within the system if the system performances are to be achieved. 1. SYSTEM PLANNING Planning for information systems has a time horizon and a focus dimension. The t ime horizon dimension specifies the time range of the plan, where as the focus d imension relates whether the primary concern is strategic, managerial, or operat ional. The system i.e. The Project that we were assigned was required to complet e within 20 wee s. What we had planned is as follows: Requirements analysis, Preliminary Investigation & Information Gathering should be covered within the 1st and 2nd wee . Since I was not aware of MYECLIPSE IDE it require 1 wee for me to adjust with that tool. 12 Wee s for the design of t he system under development. 1 wee for Testing & Implementation. And rest 2 res erve wee s. 2. PRELIMINARY INVESTIGATION The initial investigation has the objective of determining the validity of the u ser s request for a candidate system and whether a feasibility study should be con ducted. The objectives of the problem posed by the user must be understood within the f ramewor of the organization s MIS plan. I had investigated from the concerned aut hority about the project 3. INFORMATION GATHERING

A ey part of feasibility analysis is gathering information about the present system. The analyst must now what information to gather, where to find it, how to collect it, and what to ma e of it. The proper use of tools for gathe ring information is the ey to successful analysis. The tools are the traditiona l interview, questionnaires, and on-site observation. 4. STRUCTURED ANALYSIS

The traditional tools of data gathering have limitations. An English narrative d escription is often vague and difficult for the user to grasp. System flowcharts focus more on physical than on logical implementation of the candidate system. Because of these drawbac s, structured tools were introduced for analysis. Struc tured analysis is a set of techniques and graphical tools (DFD) that allow the a nalyst to develop a new ind of system specifications that are easily understand able to the user.

4.2 Data Flow Diagram

Data Flow Diagram is a diagrammatic representation of data movement through a system manual or automated - from inputs to outputs through processing. The data flow diagrams help in the analysis of the flow of data through a system and thus help in identifying the system requirements. These are of two types Logical Dat a Flow Diagrams and Physical Data Flow Diagrams. The Data Flow Diagram (DFD) cla rifies system requirements and identifies major transformations that will become programs in system design. It is the starting point of system design that decom poses the requirements specifications down to the lowest level of detail.

4.3 DATA DICTIONARY A Data Dictionary is a structured repository of data about data. It offers the p rimary advantages of documentation & improving analyst/user communication by est ablishing consistent definitions of various elements, terms, & procedures. The t hree classes to be defined are data elements (smallest unit of data), data struc tures (group of data elements handled as a unit), and data flows and data stores (Data structures in motion & rest respectively).

E-R Diagram

Conclusion

7. CONCLUSION

As we discussed earlier during project time does not permit to complete t he entire project, so as a part of the whole is being carried out and being subm itted as the project for 6th semester of M.C.A Degree. Total software along with extensive features will be submitted as Major project , here is the entire GLOBAl Share Mar et with extensive features fulfilling the requirements of any modern software organization. Although we have attempted to ma e the entire pac age full proof of erro rs, it may have some inherent bugs (beyond our nowledge) as it is yet to being tested with real time data. Lastly, we will carry our effort in developing the software fulfilling t he basic requirements of any software organization, if time permits. We do believe that the system will satisfy the basics and will prove to be user friendly and effective software whenever it s being implemented in the org anization.

8.SYSTEM TESTING System testing is the process in which the system undergoes experimental testing so as to chec that the system does not fail i.e. to chec whether the required system is running according to specification and user expectation. System testi ng also tests to find discrepancies between the system and its original objectiv e, current specification and systems documentation. Hence most useful and practi cal approach is with the understanding that testing is the process of executing a program with the explicit intention of finding errors that is ma ing the progr am fail. Testing performs a very critical role for quality assuranc e and ensuring the reliability of the software. During testing, the program to b e tested is executed with a set of test cases and output of the program for the test cases and output of the program for the test case is evaluated to determine if the program is performing as it is expected to. Hence Testing is the process of executing a program with the intention of find ing errors. A good test case is the one that has a high probability of finding as ye t undiscovered error. A successful test is one yet uncovers as yet undiscovered errors. Testing is performed according to two different strategies: 8.1 Code Testing: The code testing strategy examines the logic of program i.e. the analyst develop s test cases that results in executing every instruction in the program. Basical ly during code testing every path through the program is tested. 8.2 Specification Testing: To perform specification testing the analyst examines the specification starting what the program should do and how it should perform under various conditions. Then test cases are developed for each .In order to find which strategies to fol low, levels of testing should be followed 8.3 Levels of Testing The basic levels are unit testing, integration testing, system testing and accep tance testing. These different levels of testing attempt to Detect different types of faults. The different levels of testing are as follows :

8.3.1 Unit testing: In this testing different modules are tested against specification produced dur ing design of the modules. Unit testing is essential for verification of code pr oduced during the coding phase and hence its main goal is to test internal logic modules. 8.3.3 Integration testing: In this testing tested modules are combined into subsystems which are then test ed. The goal here is to see if the modules can be indicated properly and emphasi s is being on testing interfaces between modules. 8.3.4 System testing: In this testing the entire software system is tested. The reference document fo r this process is the requirements document and the goal is to see if the system meets its requirements. This is normally performing on realistic data of the client to demonstrate for t he software is wor ing satisfactorily. Testing here focus on external behavior o f the system. 9.System Implementation Implementation is the stage of the project when the theoretical design turned i nto a wor ing system. At this stage the main wor load, the up heal and the major impact on the existing practices shift to user department. If the implementatio n stage is not carefully planned and controlled, it can cause chaos. Thus it can be considered to be the most crucial stage in achieving a new successful system and in giving the users confidence that the users confidence that the new syste m will wor and be effective. The implementation view of software requirements presents the real worlds manifestation of processing functions and information structures. In some cases a physical representation is developed as the first step in software design. However most computer based systems are specified in a manner that dict ates accommodation of certain implementation details. Implementation involves careful planning, investigation of cur rent system and constraints on implementation, design of methods to achieve the changeover, training of staff in the changeover procedures and evaluation of cha ngeover methods. The first tas is the implementation planning i.e. deciding the methods and time scale to be adopted. Once the planning has been completed, the major effort in the computer department is to ensure that the programs in the system are wor ing pro perly. At the same time the user department must concentrate on training user st aff. What the staffs have been trained, a full system test can be carried out, i nvolving both the computer and clerical procedures. The main steps of implementation includes 1. Installing client machine. 2. Installing the software on the server. 3. Training the operational staff.