基于JAVA的圖書借閱管理系統(tǒng)

1、精選優(yōu)質(zhì)文檔傾情為你奉上精選優(yōu)質(zhì)文檔傾情為你奉上專心專注專業(yè)專心專注專業(yè)精選優(yōu)質(zhì)文檔傾情為你奉上專心專注專業(yè)摘 要當(dāng)今各個(gè)單位圖書資料需求量快速增加，過(guò)去傳統(tǒng)的圖書管理方法已無(wú)法適應(yīng)現(xiàn)在社會(huì)形勢(shì)對(duì)圖書的需求，所以現(xiàn)代科技就運(yùn)用計(jì)算機(jī)來(lái)研發(fā)了有關(guān)圖書資料的管理系統(tǒng)，因?yàn)橛凶约旱膱D書管理系統(tǒng)來(lái)管理書籍，圖書管理會(huì)方便快捷許多，也有利于工作人員快捷方便地對(duì)圖書的信息進(jìn)行查詢、修改和維護(hù)等相關(guān)信息。圖書館擁有豐富的文獻(xiàn)信息資源，是社會(huì)信息系統(tǒng)的重要組成部分，在信息社會(huì)中的作用愈來(lái)愈重要。本文介紹了在JAVA環(huán)境下連接數(shù)據(jù)庫(kù)的并提取信息的一個(gè)管理信息系統(tǒng)的過(guò)程。通過(guò)對(duì)圖書管理的調(diào)查和需求分析，創(chuàng)建了一套

2、行之有效的計(jì)算機(jī)管理圖書館的方案。文章詳細(xì)介紹了該系統(tǒng)的各個(gè)部分的功能，包括圖書管理，學(xué)生管理，借閱管理，系統(tǒng)幫助等信息，而且也闡述了系統(tǒng)的可行性分析、數(shù)據(jù)表內(nèi)容、業(yè)務(wù)流程分析、數(shù)據(jù)流程分析、數(shù)據(jù)字典等等；系統(tǒng)設(shè)計(jì)部分主要介紹了系統(tǒng)功能設(shè)計(jì)和數(shù)據(jù)庫(kù)設(shè)計(jì)；系統(tǒng)實(shí)現(xiàn)部分列出了幾個(gè)主要的程序框圖，并附帶了系統(tǒng)的一些截圖。系統(tǒng)界面友好，可操作性強(qiáng)，以高效率為讀者提供最好的圖書借閱服務(wù)。讓圖書管理更加方便快捷，本系統(tǒng)適合小型圖書館的圖書管理。關(guān)鍵詞：JAVA；圖書借閱；查詢；圖書管理ABSTRACTAs each unit is now a rapid increase in demand for bo

3、oks and materials, the traditional library management methods can not adapt to the needs of social situation on the books, so the use of computers to modern technology to develop information about the library management system, because of their library management system to manage the librarys books,

4、 many will be convenient. Also help staff quickly and easily query the information of books, modification and maintenance and other related information. Libraries have a wealth of information resources, social information system is an important part of the role in the information society more and mo

5、re important.This article describes the JAVA environment, connecting to the database and extract information, the process of a management information system. Through research and library management needs analysis, created a set of effective management of library computer program. This paper introduc

6、es the various parts of the system functions, including library management, student management, loan management, system help and other information, but also described the feasibility analysis, data table content, business process analysis, data flow analysis, data dictionaries, etc.; system design p

7、art introduces the system function design and database design; system implementation section lists the main block diagram, and the system comes with some screenshots. Friendly interface and operable to provide readers with high efficiency will be the best book lending service. Faster and more conven

8、ient for library management, the system is for managing a small library of books.Key words: JAVA; Borrowing; Query; Books Management目 錄 TOC o 1-3 h z u 第一章 引 言現(xiàn)代社會(huì)發(fā)展越來(lái)越快，信息也越來(lái)越多，人們對(duì)知識(shí)的需求也不斷增長(zhǎng)，人們想在激烈的競(jìng)爭(zhēng)中獲得勝利，就必須掌握足夠的信息，書籍是信息的載體，人們對(duì)書籍的渴求程度將會(huì)越來(lái)越高，如何科學(xué)的管理圖書信息不僅關(guān)系到讀者獲取信息的方式，更直接關(guān)系到圖書館自身的管理，因此開發(fā)出功能完善、適合客戶使

9、用、操作簡(jiǎn)單的圖書管理系統(tǒng)很有必要。管理信息系統(tǒng)是介于信息論，統(tǒng)計(jì)學(xué)與運(yùn)籌學(xué)及計(jì)算機(jī)科學(xué)之間的一門邊緣性，綜合性，系統(tǒng)性的交叉科學(xué)，它是隨著管理科學(xué)，信息技術(shù)，計(jì)算機(jī)技術(shù)等的發(fā)展而產(chǎn)生和發(fā)展起來(lái)的。圖書管理系統(tǒng)也是一門信息管理系統(tǒng)，該系統(tǒng)的設(shè)計(jì)的主要內(nèi)容是程序軟件的設(shè)計(jì)和數(shù)據(jù)庫(kù)的設(shè)計(jì)【1】，這是設(shè)計(jì)的兩個(gè)模塊，程序軟件的設(shè)計(jì)主要包括界面的設(shè)計(jì)，基本功能代碼的實(shí)現(xiàn)以及功能與界面的連貫性。數(shù)據(jù)庫(kù)設(shè)計(jì)主要是數(shù)據(jù)表的設(shè)計(jì)和相關(guān)觸發(fā)器與存儲(chǔ)過(guò)程，設(shè)計(jì)要求應(yīng)用程序功能完備，易用【2】等特點(diǎn)。第二章 需求分析在設(shè)計(jì)系統(tǒng)之前一定要充分與用戶交流,認(rèn)真了解用戶的基本要求,并進(jìn)行調(diào)查分析【3】，做好需求分析可以讓

10、用戶更好的接受程序，程序的后期開發(fā)與維護(hù)費(fèi)用就會(huì)越少。2.1 系統(tǒng)用戶圖書館管理系統(tǒng)主要的用戶分為三種類型：超級(jí)管理員、圖書管理員、出借管理員和普通用戶。針對(duì)不同的用戶，應(yīng)該擁有不同的權(quán)限和操作。(1) 超級(jí)管理員：超級(jí)管理員擁有該系統(tǒng)的一切權(quán)限，除了擁有普通用戶的權(quán)限以外，還擁有其他管理員的權(quán)限，更重要的是超級(jí)管理員可以添加、刪除、修改圖書管理員、出借管理員的信息。(2) 圖書管理員：圖書管理員擁有對(duì)圖書的完全管理，包括添加、修改、刪除和查詢圖書信息，不具有其他方面的權(quán)限。(3) 出借管理員：圖書管理員擁有對(duì)圖書借閱情況的完全管理，還包括添加、修改、刪除學(xué)生信息還可以檢索借閱情況，不再具有其

11、他方面的權(quán)限。2.2系統(tǒng)需求2.2.1功能需求各用戶主要功能：(1) 超級(jí)管理員：超級(jí)管理員擁有該系統(tǒng)的一切權(quán)限，除了擁有普通用戶的權(quán)限以外，還擁有其他管理員的權(quán)限，更重要的是超級(jí)管理員可以添加、刪除、修改圖書管理員、出借管理員的信息。(2) 圖書管理員：圖書管理員擁有對(duì)圖書的完全管理，包括添加、修改、刪除和查詢圖書信息，不具有其他方面的權(quán)限。(3) 出借管理員：圖書管理員擁有對(duì)圖書借閱情況的完全管理，還包括添加、修改、刪除學(xué)生信息還可以檢索借閱情況，不再具有其他方面的權(quán)限。系統(tǒng)主要功能：1. 系統(tǒng)的功能主要包括兩大部分：軟件部分和數(shù)據(jù)庫(kù)部分【4】。2. 實(shí)現(xiàn)對(duì)一定數(shù)量的圖書信息、讀者信息、管

12、理員信息相對(duì)應(yīng)的信息存儲(chǔ)、數(shù)據(jù)操作與管理,系統(tǒng)主要功能概括如下： (1) 對(duì)圖書信息的輸入、修改和查詢【5】。 (2) 對(duì)圖書借還信息的輸入、修改和查詢。 (3) 對(duì)讀者信息的輸入、修改和查詢。 (4) 對(duì)管理員的添加修改刪除。(5) 有圖書的借閱、歸還、續(xù)借管理功能。2.2 .2系統(tǒng)功能圖系統(tǒng)功能圖闡述系統(tǒng)的總體功能【6】，非常有利于軟件開發(fā)。系統(tǒng)總體功能圖下如圖所示。圖書借閱管理系統(tǒng)信息一覽幫助系統(tǒng)管理學(xué)生管理借閱管理書籍管理在線幫助關(guān)于所有讀者所有書籍借閱信息書籍查詢查詢學(xué)生修改學(xué)生借書還書退出刪除書籍修改書籍添加書籍用戶管理用戶登錄 圖2-1 系統(tǒng)功能圖2.2.3 數(shù)據(jù)庫(kù)安全需求1.

13、安全性系統(tǒng)安全性要求體現(xiàn)在數(shù)據(jù)庫(kù)安全性、信息安全性和系統(tǒng)平臺(tái)的安全性等方面。安全性先通過(guò)視圖機(jī)制，不同的用戶只能訪問系統(tǒng)授權(quán)的視圖，這樣可提供系統(tǒng)數(shù)據(jù)一定程度上的安全性，再通過(guò)分配權(quán)限、設(shè)置權(quán)限級(jí)別來(lái)區(qū)別對(duì)待不同操作者對(duì)數(shù)據(jù)庫(kù)的操作來(lái)提高數(shù)據(jù)庫(kù)的安全性。2. 完整性約束系統(tǒng)完整性要求系統(tǒng)中數(shù)據(jù)的正確性以及相容性?？赏ㄟ^(guò)建立主、外鍵，使用check約束，或者通過(guò)使用觸發(fā)器和級(jí)聯(lián)更新。2.3 數(shù)據(jù)流圖系統(tǒng)數(shù)據(jù)流圖如圖2-2圖書信息輸入學(xué)生信息管理學(xué)生管理員信息圖書信息管理信息輸入管理員信息輸入借閱圖書 圖2-2系統(tǒng)數(shù)據(jù)流圖2.4各功能模塊流程圖2.4 .1刪除、修改模塊由于添加和修改操作大體相同，

14、可以放在同一個(gè)流程圖中，流程圖5-1所示。是否符合進(jìn)入添加功能模塊信息添加成功填寫內(nèi)容彈出出錯(cuò)提示框確認(rèn)YN圖2-3 刪除，修改功能模塊流程圖 2.4.2添加模塊圖書添加與學(xué)生添加模塊基本相同，可以放在同一個(gè)流程圖中，如流程圖 5-2所示。內(nèi)容符合要求？進(jìn)入添加功能模塊寫入數(shù)據(jù)庫(kù)填寫添加內(nèi)容彈出出錯(cuò)提示框用戶單擊“確定”存入系統(tǒng)YN圖2-4 添加功能模塊流程圖2.4.3借閱模塊流程圖 2-5所示。是否可借？學(xué)生開始借閱借書成功出借管理員做出響應(yīng)彈出出錯(cuò)提示框?qū)W生輸入書名寫入系統(tǒng)YN圖2-5 出借功能模塊流程圖保留原來(lái)借書情況不變2.5系統(tǒng)數(shù)據(jù)字典數(shù)據(jù)字典在一個(gè)系統(tǒng)中是各類數(shù)據(jù)表現(xiàn)的集合，它是對(duì)

15、數(shù)據(jù)進(jìn)行收集和數(shù)據(jù)分析來(lái)得到的主要成果。圖書借閱管理系統(tǒng)所設(shè)計(jì)到的表，用數(shù)據(jù)字典表示如下：表2-1 系統(tǒng)數(shù)據(jù)項(xiàng)列表數(shù)據(jù)項(xiàng)編號(hào)數(shù)據(jù)項(xiàng)名數(shù)據(jù)項(xiàng)含義與其它數(shù)據(jù)項(xiàng)的關(guān)系存儲(chǔ)結(jié)構(gòu)DI-1u_id管理員自動(dòng)編號(hào)Int(4)DI-2u_name管理員用戶名Varchar(20)DI-3u_pass管理員密碼Varchar(50)DI-4u_status管理員類型Char(1)DI-5b_id圖書號(hào)Char(10)DI-6b_name圖書名Varchar(20)DI-7b_author圖書作者Varchar(20)DI-8b_max圖書最大量Int(4)DI-9b_count圖書剩余量Int(4)DI-10b

16、_publish出版社Varchar(30)DI-11b_adderss出版社地址Varchar(100)DI-12r_id讀者自動(dòng)編號(hào)Int(4)DI-13r_name讀者姓名Char(20)DI-14r_sex讀者性別Char(2)DI-15r_class讀者班級(jí)Varchar(50)DI-16r_max最大借閱量Int(4)DI-17r_readed讀者已借量Int(4)DI-18r_id借書讀者編號(hào)同讀者idInt(4)DI-19b_id借出圖書編號(hào)同圖書idChar(10)DI-20br_date1借出日期Datetime(8)DI-21br_limit最大借閱量Int(4)DI-2

17、2br_date2歸還日期Datetime(8)第三章 概念設(shè)計(jì)階段3.1系統(tǒng)主要實(shí)體及其關(guān)系(1) 系統(tǒng)主要實(shí)體：圖書、學(xué)生、管理員。(2) 各實(shí)體間有如下關(guān)系：一本圖書只能別一個(gè)學(xué)生借閱，但一個(gè)學(xué)生一次可以借多本圖書，因此二者是一對(duì)多的關(guān)系（1：n）。一個(gè)借閱管理員可以管理多個(gè)學(xué)生的借閱，一個(gè)學(xué)生的借閱情況也能被多個(gè)管理員管理，故二者是多對(duì)多的關(guān)系(m:n)。一本圖書可以被多個(gè)管理員管理，一個(gè)管理員當(dāng)然也可以管理多本圖書，所以二者是多對(duì)多的關(guān)系（m：n）。3.2 系統(tǒng)總體E-R圖根據(jù)各實(shí)體間的關(guān)系，得到系統(tǒng)總體E-R圖如圖3-1所示：圖書學(xué)生管理員管理借 閱m1mn管 理mn m書名書號(hào)最

18、大量作者總數(shù)出版社姓名性別學(xué)號(hào)班級(jí)最大量借書數(shù)管理號(hào)姓名密碼狀態(tài) 圖3-1 系統(tǒng)總體E-R圖第四章 邏輯設(shè)計(jì)階段4.1 數(shù)據(jù)庫(kù)關(guān)系模式定義數(shù)據(jù)庫(kù)模式定義如下各表所示：表1 book信息表結(jié)構(gòu)字段名數(shù)據(jù)類型可否為空說(shuō)明b_idChar(10)不可為空主鍵b_nameChar(20)不可為空b_authorChar(10)可為空b_maxInt(4)可為空b_countInt(4)可為空b_publishVarchar(30)可為空b_addressVarchar(100)可為空表2 borrow信息表結(jié)構(gòu)字段名數(shù)據(jù)類型可否為空說(shuō)明r_idInt(4)不可為空主鍵b_idChar(10)可為空br

19、_date1Datetime(8)可為空br_limitInt(4)可為空br_date2Datetime(8)可為空 表3 reader信息表結(jié)構(gòu)字段名數(shù)據(jù)類型可否為空說(shuō)明r_idInt(4)不可為空主鍵r_nameChar(20)可為空r_sexChar(2)可為空r_classVarchar(50)可為空r_maxInt(4)可為空r_readedInt(4)可為空表4 usertable信息表結(jié)構(gòu)字段名數(shù)據(jù)類型可否為空說(shuō)明u_idInt(4)不可為空主鍵u_nameVarchar(20)可為空u_passVarchar(50)可為空u_statusChar(1)可為空4.2 對(duì)所建表的

20、分析1. 數(shù)據(jù)庫(kù)表中的字段都是單一屬性的，不可再分,符合第一范式。2. 數(shù)據(jù)庫(kù)表中不存在非關(guān)鍵字段對(duì)任一候選關(guān)鍵字段的部分函數(shù)依賴，也即所有非關(guān)鍵字段都完全依賴于任意一組候選關(guān)鍵字，符合第二范式。3. 在第二范式的基礎(chǔ)上，數(shù)據(jù)表中如果不存在非關(guān)鍵字段對(duì)任一候選關(guān)鍵字段的傳遞函數(shù)依賴，因此符合第三范式。第五章 設(shè)計(jì)實(shí)施階段5.1 數(shù)據(jù)庫(kù)設(shè)計(jì)5.1.1創(chuàng)建數(shù)據(jù)庫(kù)和數(shù)據(jù)表創(chuàng)建名為bookDB的數(shù)據(jù)庫(kù)，并根據(jù)數(shù)據(jù)庫(kù)模式定義【7】，為數(shù)據(jù)庫(kù)創(chuàng)建了四個(gè)表：book表，borrow表，reader表，usertable表！5.1.2創(chuàng)建規(guī)則、觸發(fā)器和存儲(chǔ)過(guò)程1.規(guī)則【8】 (1) 學(xué)生“性別”一欄必需為“男

21、”和“女”。 (2) “借閱時(shí)間”一欄必需是時(shí)間類型。 (3) 為保證系統(tǒng)正常運(yùn)行，剩余圖書數(shù)量必須大于0。2.系統(tǒng)經(jīng)常需要查詢圖書信息和學(xué)生信息，因此建立了兩個(gè)存儲(chǔ)過(guò)程【9】：“books”存儲(chǔ)過(guò)程和“students”存儲(chǔ)過(guò)程，用于提高查詢速度。3.在圖書表里創(chuàng)建了“insert”觸發(fā)器和“update”觸發(fā)器?！癷nsert”觸發(fā)器用于管理圖書插入時(shí)更改圖書總數(shù)，“update”觸發(fā)器用于當(dāng)更改books表中圖書信息時(shí)，其他表中關(guān)于該圖書的信息也相應(yīng)更改。5.2 應(yīng)用程序設(shè)計(jì)5.2.1啟動(dòng)窗體啟動(dòng)窗體是剛打開軟件時(shí)，用戶首先看到的界面，這個(gè)要滿足用戶的使用習(xí)慣，這樣用戶才容易接受，該界面

22、要求簡(jiǎn)潔、和諧。 圖 5-1 啟動(dòng)窗體說(shuō)明：登陸窗體可以直接預(yù)覽部分信息，用戶不用登陸便可以查看相關(guān)信息。5.2.2用戶登錄模塊的實(shí)現(xiàn)點(diǎn)擊菜單中的“系統(tǒng)管理”項(xiàng)，再點(diǎn)擊“用戶登陸”便可以進(jìn)入該界面。圖5-2 用戶登錄模塊的實(shí)現(xiàn)圖說(shuō)明:管理員需要輸入正確的用戶名和密碼才能進(jìn)入主界面管理整個(gè)系統(tǒng)。各種類型的管理員都在這里登陸。5.2.3登錄超級(jí)管理員的主界面圖5-3 系統(tǒng)主界面的實(shí)現(xiàn)圖該界面是超級(jí)管理員登陸后的界面，因?yàn)槌?jí)管理員擁有全部權(quán)限，因此，所有操作超級(jí)管理員都可以執(zhí)行。5.2.4圖書管理模塊的實(shí)現(xiàn)添加圖書是圖書管理系統(tǒng)的基本功能，這個(gè)功能必須完善，通過(guò)需求分析可以完善該功能。圖5-4 圖

23、書管理模塊的實(shí)現(xiàn)圖說(shuō)明：圖書管理模塊實(shí)現(xiàn)了對(duì)圖書信息的維護(hù)和管理。它可以對(duì)圖書進(jìn)行添加、刪除、修改等，也可以輸入書號(hào)或書名來(lái)查詢圖書庫(kù)里的圖書信息。5.2.5讀者管理模塊的實(shí)現(xiàn) 學(xué)生管理與讀者管理類似，主要包括添加、刪除、修改和查詢功能。圖5-5 讀者管理模塊的實(shí)現(xiàn)圖說(shuō)明：讀者管理模塊主要是對(duì)讀者信息的維護(hù)和管理。它實(shí)現(xiàn)了對(duì)讀者信息查詢、添加、保存、修改和刪除等功能。也可以按年級(jí)、讀者證號(hào)、讀者姓名、讀者所學(xué)專業(yè)來(lái)查詢讀者的信息。5.2.6圖書借還功能模塊的實(shí)現(xiàn)圖5-6 圖書續(xù)借管理模塊的實(shí)現(xiàn)圖說(shuō)明：圖書續(xù)借管理模塊可以延長(zhǎng)圖書借閱的時(shí)間，以滿足讀者對(duì)圖書的需求。5.2.7信息一覽功能模塊的實(shí)

24、現(xiàn)圖5-7 圖書管理系統(tǒng)信息一覽模塊說(shuō)明：信息一覽可以讓任何人檢索書籍讀者信息，以及借閱信息！這樣方便查看。5.2.8系統(tǒng)幫助功能 系統(tǒng)幫助是根據(jù)需求分析，為更方便用戶使用、增加與用戶互動(dòng)而設(shè)置的模塊。 圖5-8 系統(tǒng)幫助功能說(shuō)明：系統(tǒng)幫助展現(xiàn)系統(tǒng)的相關(guān)信息包括版本號(hào)等，在線幫助可以直接進(jìn)入瀏覽器界面！5.2.9其他功能除上面介紹的主要模塊之外，還有管理員注冊(cè)管理模塊、圖書丟失管理模塊、密碼管理模塊等等，因?yàn)檫@些窗體的實(shí)現(xiàn)同上面模塊都設(shè)計(jì)實(shí)現(xiàn)的有相同之處，所以不一一列舉了。第六章 系統(tǒng)測(cè)試與感觸數(shù)據(jù)庫(kù)設(shè)計(jì)是保證系統(tǒng)質(zhì)量和可靠性的最后關(guān)口，是對(duì)整個(gè)系統(tǒng)開發(fā)過(guò)程包括系統(tǒng)分析【10】、系統(tǒng)設(shè)計(jì)和系統(tǒng)

25、實(shí)施的最終審查。為了保證每個(gè)程序頁(yè)面能夠正確實(shí)現(xiàn)系統(tǒng)設(shè)計(jì)的功能，首先在數(shù)據(jù)庫(kù)中配置一些系統(tǒng)功能運(yùn)行所需的基本數(shù)據(jù)，然后運(yùn)行每個(gè)程序模塊，檢查運(yùn)行結(jié)果是否符合要求。為了確保系統(tǒng)功能的可靠性，對(duì)系統(tǒng)所有功能反復(fù)操作，如發(fā)現(xiàn)錯(cuò)誤要及時(shí)更正。本系統(tǒng)適合于學(xué)校小型的圖書館的圖書管理，采用的是JAVA作為開發(fā)工具，數(shù)據(jù)庫(kù)采用的是SQL Server 2000開發(fā)工具，系統(tǒng)總共包括圖書管理、圖書流通管理、讀者管理、系統(tǒng)管理等幾部分功能。但是在系統(tǒng)中還存在一些不足，如各類圖書借還數(shù)量匯總和讀者類型借閱圖書數(shù)量限制，由于時(shí)間問題，這些功能未能完善。通過(guò)這次畢業(yè)設(shè)計(jì)，讓我很大程度的了解了圖書管理系統(tǒng)【11】的功能

26、，熟悉了圖書館的業(yè)務(wù)流程，而且很好的運(yùn)用了設(shè)計(jì)系統(tǒng)所用的相關(guān)軟件。參考文獻(xiàn)1 魏站線.數(shù)據(jù)庫(kù)系統(tǒng)概論(第三版)M. 北京:北京機(jī)械工業(yè)出版社,2000.2 Ralph Morelli.JAVA面向?qū)ο蟪绦蛟O(shè)計(jì)M.北京:人民郵電出版社,2003 .3 錢樂秋.軟件工程M. 北京:清華大學(xué)出版社,2009.4 蘇寶莉.SQL Server數(shù)據(jù)庫(kù)案例教程M.北京:中國(guó)電力出版社,2008.5 萬(wàn)波.JAVA語(yǔ)言程序設(shè)計(jì)M. 北京:機(jī)械工業(yè)出版社,2008.6 陳佳.信息系統(tǒng)開發(fā)方法教程M. 北京:清華大學(xué)出版社,2000.7 Bruce Eckel美.Thinking in JavaM.China

27、machine Press.2007.098 張來(lái)福.管理信息系統(tǒng)M. 北京:科學(xué)出版社,1997.9 崔群法.SQL Server 2008從入門到精通M. 北京:電子工業(yè)出版社,2001.10 付凱芳.網(wǎng)格計(jì)算在圖書文獻(xiàn)檢索應(yīng)用J.微計(jì)算機(jī)信息,2009,25(8):113-117.11 張李杰,王貴加,杜康能.管理系統(tǒng)的設(shè)計(jì)與實(shí)現(xiàn)J管理學(xué)學(xué)刊,2010,18(6):6-8.附錄J2EE OVERVIEWTHE CONCEPT OF J2EECurrently, Java 2 platform has three versions, which are suitable for small

28、 devices and smart cards in the Java 2 Platform Micro Edition (Java 2 Platform Micro Edition, J2ME), for desktop Java 2 Platform, Standard Edition (Java 2 Platform Standard Edition , J2SE), for creating server applications and services for Java 2 Platform, Enterprise Edition (Java 2 Platform Enterpr

29、ise Edition, J2EE).J2EE is an advantage of Java 2 platform enterprise solutions to simplify development, deployment and management of complex issues related to architecture. J2EE based technology is the core Java platform or Java 2 Platform Standard Edition, J2EE is not only the standard version to

30、consolidate a number of advantages, such as write once, run anywhere features, easy to access the database JDBC API, CORBA technology and the ability to Internet applications in the security model to protect data, etc., and also provides EJB (Enterprise JavaBeans), Java Servlets API, JSP (Java Serve

31、r Pages) and XML technology, full support. The ultimate goal is to become a developer can enable enterprises to dramatically reduce time to market architecture. Middle-tier J2EE architecture provides the integrated framework to meet the needs without too much cost but high-availability, high reliabi

32、lity and scalability of applications. By providing a unified development platform, J2EE multi-tier application development reduces the cost and complexity, while providing strong support for integration of existing applications and fully support the Enterprise JavaBeans, a good wizard support packag

33、e and deploy applications, add the directory support , enhanced security, improved performance.THE FORE MODELS OF J2EEJ2EE multi-tier distributed applications using the model, application logic into components according to the functions of various application components based on where they are distr

34、ibuted in layers on different machines. In fact, sun design of the original intention was to address J2EE two-tier model (client / server) the disadvantages of the traditional model, the client played a role in the bloated excess, in this mode, the first deployment Relatively easy time, but difficul

35、t to upgrade or improve, to stretch is not ideal, but often a proprietary protocol based on DD is usually some kind of database protocols. It allows reuse of business logic and interface logic is very difficult. Now J2EE multi-tier enterprise application model will be two different aspects of the mo

36、del cut into many layers. A multi-layer applications can provide a different service for each separate layer, the following is a typical four-layer structure of J2EE: Running on the client machine client tier components On the server running on the J2EE Web tier components On the server running on t

37、he J2EE business logic layer components On the server running on the EIS Enterprise Information System (Enterprise information system) software layerTHE STRUCTURE OF J2EEThis component-based, platform-independent nature of the J2EE architecture enables J2EE procedures for the preparation is very sim

38、ple, because the business logic is encapsulated into reusable components, and J2EE server container in the form of components for all types of services to provide background . because you do not own the development of this service, so you can concentrate on solving business problems at hand.CONTAINE

39、RS AND SERVICES Set customized J2EE server container provides internal support may include security, transaction management, JNDI (Java Naming and Directory Interface) addressing, remote access and other services, the following list of the most important of several services: J2EE Security (Security)

40、 model allows you to configure the web component or enterprise bean, so that only authorized users can access system resources. Every customer is a special role, and each role to allow only certain method of activation. You should describe the enterprise bean declared in the arrangement of the role

41、and methods that can be activated. Because of this declarative approach, you do not write the rules to enhance security. J2EE transaction manager (Transaction Management) model allows you to specify the formation of a transaction the relationship between all the methods, so that all the methods in a

42、 transaction are treated as a single unit. When a client activates a method in the enterprise bean, the container involved in a management affairs. Due to container-managed transaction, the enterprise bean is not necessary to encode the boundaries of the transaction. The code requires control of dis

43、tributed transactions can be very complex. You only need to file a statement described in the arrangement of the affairs of enterprise bean properties, rather than write and debug complex code. Containers will read this file and you deal with the affairs of this enterprise bean. JNDI address (JNDI L

44、ookup) services to multiple enterprise name and directory services provide a unified interface, so application components can access the name and directory services. J2EE remote connectivity (Remote Client Connectivity) model of management between the client and the enterprise bean low-level interac

45、tion. When an enterprise bean is created, a client can call its methods as it and the client on the same virtual machine on the same. Life Cycle Management (Life Cycle Management) Model Management to create and remove enterprise bean, a enterprise bean in their life cycle through several states will

46、 be. Container to create enterprise bean, and in the instance pool and the active state can move him, and eventually will be removed from the container. Even if you can call the enterprise beans methods create and remove the container will also perform these tasks in the background. Database connect

47、ion pool (Database Connection Pooling) model is a valuable resource. Get the database connection is a time-consuming work, and the number of connections is very limited. Container through the management connection pool to alleviate these problems. enterprise bean can quickly get a connection from th

48、e pool. Release in the bean can be connected to other bean to use.Container type Deployment of J2EE application components can be installed into the container to the following: J2EE EJB container to manage all enterprise bean application execution. J2EE Web container manages all application componen

49、ts JSP pages and Servlet implementation. Web components and their container run on J2EE server. Application client container manages all J2EE application client components in the application execution. The application clients and their container run on J2EE server. Applet container is running on the

50、 client machine on the web browser and Java plug-in combination. THE CORE API AND THE J2EE COMPONENTS1. J2EE platform consists of a set of services (Services), application programming interfaces (APIs) and the Agreement constitutes, its Web-based multi-tier application development that provides the

51、functional support, following the 13 on the J2EE specification in a simple description (limited space , where only a simple description):2. JDBC (Java Database Connectivity): JDBC API for accessing different databases provides a uniform way, the same as ODBC, JDBC developer shield some of the detail

52、s, the other, JDBC also have access to the database platform independence.3. JNDI (Java Name and Directory Interface): JNDI API is used to perform name and directory services. It provides a consistent model to access and operate enterprise-level resources such as DNS and LDAP, local file system, or

53、application server object.4. EJB (Enterprise JavaBean): J2EE technical reason won wide attention in a body of one of the reasons is the EJB. They provide a framework to develop and implement distributed business logic, which is significantly simplified scalable and highly complex enterprise-class ap

54、plication development. EJB specification defines the EJB component when the container how to interact with them. Container is responsible for providing public services such as directory services, transaction management, security, resource pool, and fault tolerance. But here is worth noting that, EJB

55、 is not the only way to achieve J2EE. It is because of the openness of J2EE, so some companies can and EJB in a parallel way to achieve the same purpose.5. RMI (Remote Method Invoke): As its name indicates that, RMI protocol on the remote object method call. It uses serialization on the client side

56、and server-side transfer data. RMI is a lower level for use by EJB protocol.6. Java IDL / CORBA: In the Java IDLs support, developers can integrate Java and CORBA. They can create a Java object and make it expand in the CORBA ORB, or they can also create Java classes and the other as the CORBA ORB t

57、o start with the customer object. The latter method provides another means by which Java can be used to your new applications and legacy systems integration.7. JSP (Java Server Pages): JSP page is embedded in HTML code and composition of one of the Java code. Server in the pages of the client reques

58、ts after the Java code and then will generate the HTML page returned to the client browser.Java Servlet: Servlet is a small Java program that extends the Web server functionality. As a server-side application, when the request started, This is very similar to CGI Perl scripts. Most of Servlet and JS

59、P provide similar functionality, but implemented in different ways. JSP HTML code is usually embedded in most of a small amount of Java code, servlets written in Java and generates all the HTML.8. XML (Extensible Markup Language): XML is a markup language can be used to define other languages. It is

60、 used in different business processes to share data. The development of XML and Java are independent of each other, but it has the same goal of Java is platform independence. By a combination of Java and XML, you can get a perfect solution is platform independent.9. JMS (Java Message Service): MS is