Purpose Of SalePOS J2EE Application .

Uploaded on:
Category: Sales / Marketing
Point Of Sale(POS) J2EE Application. (POS J2EE Application with JRun). < Master Degree Final Project >. Department : Computer Science Degree : Master Student : Woojin Choi ID : 0426367. Topics. Introduction of POS Application System requirement Application Map Database Diagram
Slide 1

Purpose Of Sale(POS) J2EE Application (POS J2EE Application with JRun) < Master Degree Final Project > Department : Computer Science Degree : Master Student : Woojin Choi ID : 0426367

Slide 2

Topics Introduction of POS Application System prerequisite Application Map Database Diagram POS Component POS Workflow utilizing J2EE Design HTML/JSP/Servlet/EJB in POS J2EE Introduction (J2EE – J2EE API) POS Application with J2EE Enterprise JavaBeans (EJB) POS Component Example POS Security Mechanism POS Scheduler Supplementary Issues

Slide 3

Introduction of POS : Point of Sale Business theme : Web based application for a client to look at the shopping effortlessly and quick Current Process : Customer comes in store - > Put the thing to shopping basket - > Wait to look at - > Clerk look at Problem : Customers need to sit tight for quite a while even the thing is basic Solution : Put the agent standardized identification examining and looking at frameworks to every shopping path and take into consideration a client to look at the trucks independent from anyone else New framework to take care of the issue : POS J2EE Application Benefits : Portable business arrangement/Integrated e-business/Save the client\'s chance/Down the store cost

Slide 4

System Requirement Server side Operating System : Win NT 4.0/Win2K Web Server : IIS 4.0/5.0 Application Server : JRun 3.0.2 Database : MS SQL Server 7.0 Client side Browser : IE4.0 or higher

Slide 5

Application Map Index.jsp (Display shoppling truck) Products.jsp Add/Edit/Delete Shopping list Authentication Servlet Login.jsp Checkout.jsp Customized Error Pages HTTP Error Jrun Application Error 403.html 404.html 405.html 500.html Loginerror.jsp Logout.jsp Scheduler

Slide 6

Database Diagram

Slide 7

POS Components Presentation Logic HTML JSP Login.jsp, customers.jsp, customer_profile.jsp, … Interface Logic (Data Modeling) Servlet EditCustomer.class, DeleteCustomer.class, AddShoppingList.class, … Business Logic EJB Customer EJB, ShoppingList EJB, …

Slide 8

POS Workflow utilizing J2EE plan Presentation : JSP Interface : Servlet Business Logic : EJB Benefits : Presentation rationale doesn\'t actualize business rationales by any stretch of the imagination. Each business information is redesigned through EJB or Servlets. Particularly Servlet is reponsible for information displaying for business rationale as interface amongst presentation and business rationale. JSP Servlet EJB Container <> DB

Slide 9

HTML/JSP/Servlet/EJB in POS JRun HTTP Server(HTML) JSP Engine JDBC <> HTTP Servlet Container DB HTTP on LAN EJB Container

Slide 10

Java 2 Enterprise Edition (J2EE) Defines a standard for creating multi-level applications Vendors team up on norms and contend on execution All the bits of the application are versatile crosswise over stages and servers Simplifies application improvement Developer concentrates on application rationale J2EE server handles multifaceted nature of lower level administrations Component JSPs/Servlets/EJBs API : Servlet/JSP/EJB/JDBC/JNDI/JavaMail/JMS/JTA

Slide 11

J2EE APIs Servlets Standard API augmenting and upgrading Web servers Java Server Pages (JSP) Standard API for making dynamic substance utilizing static formats Enterprise JavaBeans (EJB) Standard server-side segment demonstrate Java Database Connectivity (JDBC) JavaMail Java Naming and Directory Interface (JNDI) Java Message Service (JMS) Java Transaction API (JTA) *) POS framework : Servlet/JSP/EJB/JNDI/JDBC

Slide 12

POS Application with J2EE Provides finish usage of J2EE Servlets 2.2 JSP 1.1 EJB 1.1 JNDI JMS JDBC JTA/JTS JavaMail POS Application Servlet 2.2 JSP 1.1 EJB 1.1 JNDI POS Application Work Flow Presentation : JSP Interface : Servlet Business Logic : EJB

Slide 13

Enterprise JavaBeans (EJB) Server-side part display permitting designers to focus on business rationale EJB server handles many-sided quality of lower level administrations EJB API ensures segments to be compact crosswise over EJB Servers Component life cycle State administration Persistence Multi-threading Connection pooling Transaction administration Security

Slide 14

Entity Beans Used to Represent a business element (like a column in a database table) Provide standard get to and approval for business elements Persistent (live past server lifetime) Usually speak to information in a database Examples Customer, Product, Employee, ...

Slide 15

Entity Beans Bean Managed Persistence (BMP) Developer composes tirelessness code Container Managed Persistence (CMP) EJB properties are mapped to database sections Persistence code naturally produced by EJB compartment Implements javax.ejb.EntityBean

Slide 16

Session Beans Used to Manage procedures and undertakings Model the work process of Entity beans Retrieve and overhaul information that can\'t be sufficiently caught in a substance bean No industrious state Example Order an item Check out the shopping basket Reservation

Slide 17

Session Beans Stateful Session Bean Maintain a state between technique summons Store properties as occasion factors Expose strategies to control properties Stateless Session Bean Do not hold data between strategy summons Each technique is totally free Client passes required data as parameters to the technique Participate in occurrence pooling Greatest versatility Many customers share predetermined number of cases Implements javax.ejb.SessionBean

Slide 18

Home/Remote Interface Home Interface Defines techniques to make (get), find, or expel a Bean Instance for the benefit of the customer Extends javax.ejb.EJBHome Remote Interface Defines the bean\'s business techniques Extends javax.ejb.EJBObject

Slide 19

Packaging the Bean in a JAR File Includes: Bean class Remote interface Home Interface Deployment descriptor (ejb.xml) ShoppingListHome.class ShoppingList.class ShoppingListEJB.class ejb.xml

Slide 20

Deploy Tool Deploy Tool(Macromedia KAWA, J2EE deploytool) produces stub classes and question classes Deploy Tool utilizes bump document and creates essential classes for EJB server Stub classes Downloaded to a customer powerfully at run time Used by customer Object classes Implement every single relating interface Used by EJB server

Slide 21

lookup("Customer") make/find EJB Home Stub EJB Home Interface Home Interface getList( ) EJB Object Stub EJB Object EJB Class Remote Interface Remote Interface EJB Conceptual Architecture  JNDI Server ƒ ‚ InitialContext „ EJB Server † … ‡ ˆ

Slide 22

Development Process EJB Developer Home Interface Remote Interface EJB class Support classes Deployer (Deploy device) Packaging Interfaces, EJB class, and bolster classes Deploy the bundled EJB (shake record) Server Implement EJB Servers CustomerHome.class EJB Devloper Customer.class CustomerEJB.class ejb.xml

Slide 23

POS Component Example Add, evacuate, and show a client shopping list ShoppingListSession Display Index.jsp DB Add Remove AddShoppingList RemoveShoppingList ShoppingCart Table Select, redesign, erase shopping list from ShoppingCart table Display all shopping list from EJB Form activity to include/expel shopping list Implement get, include, expel shipping list strategies Capture the Shopping list id Call bean strategy to be fit with every activity

Slide 24

POS Security Mechanism Form Based JRun application security in view of J2EE User/Group/Role Protect whole application JSPs/Servlets/EJBs *) DatabaseAthentication.java to confirm client utilizing DB POS Authentication* Servlet Login.jsp HTML JSP Servlet EJB Other Resources Loginerror.jsp

Slide 25

POS Scheduler Jrun gives a Scheduler servlet to execute activities at indicated times Scheduler servlet : allaire.jrun.scheduler.CronService Defines the servlet in web.xml Application characterizes Schedule.ini for the administration Schedule.ini incorporates the govern and the solicitations to be planned * If this administration is utilized as a part of use, this application is not consumable on the grounds that JRun included this administration.

Slide 26

Web.xml test for scheduler <servlet> characterizes the administration </servlet> <servlet> <servlet-name>POSScheduler</servlet-name> <servlet-class>allaire.jrun.scheduler.CronService</servlet-class> <display-name>POSScheduler</show name> <description>Scheduler for POS System</description> <init-param> <param-name>schedfile</param-name> <param-value>C:\JRun\3.0\servers\default\pos-app\schedule.ini</param-value> </init-param> <init-param> <param-name>logfile</param-name> <param-value>C:\JRun\3.0\servers\default\pos-app\scheduler-log\pos-scheduler.log</param-value> </init-param> <load-on-startup/> </servlet> Except those striking labels, designer can give any name or record

Slide 27

Schedule.ini Example Schedule.ini is characterized in web.xml <init-param> <param-name>schedfile</param-name> <param-value>C:\JRun\3.0\servers\default\pos-app\schedule.ini</param-value> </init-param> Developer can utilize any document name on that Schedule.ini case # This is the ini petition for JRun scheduler # Scheduler checks the shopping basket table at regular intervals and redesigns the shopping basket status. # If the shopping basket things are observed to be more seasoned than 2hr, those will be erased. # Those things to be more seasoned than 2hr should be not in the truck or client left the store without checkout. 0 0,10,20,30,40,50 * http://localhost/pos/servlet/SchedulerForShoppingCart Scheduler runs this servlet at regular intervals

Slide 28

Supplementary Issues Physical Security Mechanism Barcode scanner integration(physical) Credit card handle integration(physical) Business information trade utilizing XML

View more...