Chapter 35

J2EE-Based General Document Transceiver System

Dajin Gao, Wei Zhang, Xinyan Liu, Zhenkai Xie and Tingting Jiang

Abstract Along with the development of computer network technology, network technology is integrate into management and has become important symbol and method of modern office. Sending and receiving of documents are essential contents in the daily office work. The existing electronic office and e-government affairs systems include a subsystem of Sending and receiving document and are very similar in the basic functions. However, in each system development process, all kinds of development will be repeated. Thus, the authors separate this subsystem and analyses it in details, and also use the Struts 2 spring Hibernate model to design a general document transceiver system.

Keywords J2EE bull; Document management bull; MVC model

35.1 Demand Analysis

In the system, the document sending and receiving functions can be configured flexibly; the common document send-receive flow can be easily deployed in the OA system, to meet the need of OA system. The system in this paper mainly involves these features: (1) system user management to maintain basic information, authorization and roles of users; (2) the setting and configuration of document send-receive flow to implement the configurable functions of the whole flow from dispatch to verification; (3) document dispatch management to implement the document submission of users and track the real-time process; (4) document send-receive management to verify or actually operate the documents sent by users of the previous step and transfer the processed documents to users needing to process the documents [1, 2].

35.2 Design Principles

The principles to guide the design include six aspects. (1) Module independence principle requires all modules in the system are mutually independent with clear data interfaces and a good loose coupling and can be combined into a system. (2) Cutting principle means that some functions or modules of the system can be deployed and hence the existing functions can be used [3]. (3) Code reusability principle means that the codes can be used repeatedly, which can reduce the workload of system development and also help the system modification and maintenance [4, 5]. As a general platform, keeping codes reused helps reduce the system modification range and speed up its updating when connecting to other
electronic office systems [6]. (4) Scalability principle requires new tools and functions can be added into the system flexibly and the system functions can be extended. Also, the integration can be done based on needs, and hence different levels of value-added services can be offered [7, 8]. (5) Ease-to-use principle means common users can easily use the system when there are no computer specialized technical personnel. (6) Universality principle means users can obtain the platform system easily and work with others [9]. This requires the platform should be deployed in Internet, making system expanded smoothly and serving for different users.

35.3 Overall Architecture Design

The general document transceiver system in this paper is designed and developed based J2EE platform [10]. The architecture is composed of presentation layer, business logic layer and persistent database layer as shown in Fig. 35.1.

Fig. 35.1 The system overallarchitecture design

Presentation layer is used to get data from business logic layer and display it with a certain form, and also process the data in the forms of client and submit it to business logic layer. Business logic layer can call related methods to process business logics after receiving usersrsquo; forms and other data submitted by presentation layer, and also get and process the initial data from database and saves related results, and finally needs to return the processing results to presentation layer to remind users. Business logic layer is included in service package and is the core of the systemrsquo;s business logics, is a MVC model and is realized with spring [11]. Persistence layer and database layer are responsible for the physical connection between application and database. The persistence layer in this system is implemented with Hibernate and is composed of Bean and DAO packages. The entity classes of all forms of database are in Bean; DAO is Date Access Object and is a general interface for
upper-layer business logic to access database [12]. Generally each database form is corresponding to a DAO.

35.4 Selection of Development Environments

JDK1.6 is selected for JDK tool. JDK is composed of some standard class libraries and a group of Java utility programs testing and establishing documents and its core Java API is some predefined class libraries. Eclipse is selected for development tool. Eclipse is an open source and Java-based extensible development platform and can easily establish a SSH2 framework application. Tomcat 6 selected for application server. It is a Tomcat version corresponding to JDK 6. Open-source MySQL relational database is selected for database, which can greatly reduce the overall cost.

35.5 System Functional Modules Design

Through the above demand analyses, the system can be mainly divided into incoming dispatch management, system management and user management. Its overall functional modules are as shown in Fig. 35.2. Dispatch management, system management and user management modules are shown in Figs. 35.3, 35.4 and 35.5 respectively.

Fig. 35.1 The system overall architecture design

Fig. 35.3 The incomin

剩余内容已隐藏，支付完成后下载完整资料

基于J2EE的文档传输系统

Dajin Gao · Wei Zhang · Xinyan Liu · Zhenkai Xie · Tingting Jiang

摘要：随着计算机网络技术的发展，网络技术已经融入到管理中，并且成为现代办公的重要标志和方法。文档收发是日常办公的重要内容。现有电子办公与电子政务事务系统包括发送和接收文档的子系统，并且它们的基本功能非常相似。然而，在每个系统的开发过程，各种开发步骤都在重复。因此，作者分离这个子系统，做出详细分析，并使用Struts 2 Spring Hibernate开发模式来设计一个通用文档收发系统。

关键字：J2EE；文档管理；MVC模型

35.1需求分析

在本系统中，可以灵活配置文件发送和接收功能；常见的文件发送接收流程，可以方便地部署在OA系统，满足OA系统的需要。本系统主要是包含这些特点：（1）系统用户管理维护用户的基本信息、权限和角色；（2）通过文档收发流的设置和配置实现整个流程的可配置功能完成验证；（3）文件收发管理实现用户提交文档并跟踪实时进程；（4）文档收发管理首先验证或操作用户发送的文档，并将处理后的文档传递给需要处理文档的用户[1,2]。

35.2设计原则

指导设计的原则包括六个方面。（1）模块独立性原则要求系统中的所有模块相互独立、清晰。数据接口定义良好的松耦合，模块之间可以组合成一个系统。（2）切割原理意味着系统的某些功能或模块可以被独立部署，因此已存在的功能模块可以被使用[3]。（3）代码重用性原理意味着代码可以反复使用，这样可以减少系统开发工作量，并帮助系统修改和维护[4,5]。作为一个通用平台，保持代码重用有助于减少系统修改范围，并且当系统需要连接到其他电子办公系统时，加快系统更新[6]。（4）可扩展性原则需要新的工具和功能可以灵活添加到系统中，系统功能可以扩展。此外，集成可以根据需要进行，因此不同级别的增值服务可被提供[7,8]。（5）易用原则意味着普通用户在没有电脑专业知识的情况下轻松使用系统。（6）普遍性原则是指使用者可以很轻易地获得平台系统并与他人合作[9]。这些需求要求平台应该被部署在互联网上，使系统顺利扩展并服务不同的用户。

35.3整体架构设计

本文中的文档收发系统使用J2EE平台设计和开发。体系结构由表示层，业务逻辑层和持久数据库层构成，如图35.1所示。表示层用于从业务逻辑层获取数据并使用某种形式显示数据，当然表示层也处理客户端提交的数据并提交给业务逻辑层。

图35.1 系统整体架构设计

业务逻辑层在接收到用户表单和表示层提交的其他数据后，可以调用相关的方法来处理业务逻辑，同时从数据库中得到和处理初始数据并保存相关结果，最后需要将处理结果返回到表示层以提醒用户。业务逻辑层包含在服务包中，是系统业务逻辑的核心，是一个MVC模式，并由Spring实现[11]。持久层数据库层负责应用程序和数据库之间的物理连接。该系统的持久层是用Hibernate实现的并且它包含Bean和DAO两个包。所有形式数据库的实体类都在bean中；DAO是数据访问对象，是面向上层业务逻辑访问数据库的通用接口[12]。一般每个数据库表对应一个DAO。

35.4开发环境的选择

JDK工具选择JDK1.6。JDK是由一些标准类库和一组Java工具程序的测试和创建文档，其核心java API是一些预定义类库。开发工具选择的是Eclipse。Eclipse是一个开源的，基于Java的可扩展的开发平台，可以方便地建立一个SSH框架的应用。应用服务器选择Tomcat 6。它是对应于JDK 6的Tomcat版本。数据库选择开源的MySQL关系型数据库，可以大大降低总体成本。

35.5系统功能模块设计

通过上面的需求分析，系统主要分为接收转发管理、系统管理和用户管理。其整体功能模块如图35.2所示。收发管理如图35.3所示，转发管理和用户管理模块分别为35.4和35.5。

图35.2 整体功能模块图

图35.3 收发管理

图35.4 转发管理

图35.5 用户管理

当用户收到需要处理的文档时，它将首先出现在待定的文档列表中，其中所有文档可能需要由一组用户处理。如果用户不需要处理读取文件或文档内容与用户无关，则文件可以通过转发方式传递给其他用户或用户组。当用户选择查看或读取文档时，它会被查看过的用户锁定并处理，然后只会出现在已读或待定的用户文档列表中。用户可以查看内容来选择一个文件处理，或直接从请求列表中选择。文档的相关工作完成后，这个文件可以通过处理转移到下一个流程。用户的所有文档进展都可以在已完成的文档列表中进行搜索。因此，可以跟踪此模块中的所有处理流程。

当一个文档需要进行报送时，首先要起草。在文件的起草进程中，文档可以保存为草稿。保存的草稿可以修改、删除等。文件中的所有内容全部输入后，可以报送然后进入处理流程。在处理流程中未被完全处理的文档可以存放在收发管理模块中的待定文档列表中。当整个文档处理流程完成后，将出现在该模块中已处理的文档列表中，并最终被保存。

当添加新用户时，首先需要确定用户的用户组。然后输入登录名、中文名、密码、联系信息等基本信息，然后在系统中添加用户。任何用户在系统注册后都可以更改密码。管理员在系统注册后在自己修改密码时可以进行密码重置操作，也可以删除无效用户。

35.6数据库设计

在本系统中，MySql数据库用来存放主要的数据，下面显示所有的数据表结构。

1.文档表是整个数据库的主要数据表，并保存每个文档的相关内容并命名为document，其主要字段如图35.1所示。

图35.1 文档表

2.文件处理流程表：它是记录文件处理的相关信息，包括处理时间。表名是docprocess。其主要字段如图35.2所示。

图35.2 文件处理流程表

3.附件记录表：每个文档可以包含一个或多个附件，每个附件的一些基本信息需要记录在数据库中。其主要字段如图35.3所示。

图35.3 附件记录表

4.文档和附件关系表：每个文档可能包含一个或多个附件，每个附件的一些基本信息需要记录在数据库中。该表被命名为Docfile。其主要字段如图35.4所示。

图35.4 文档和附件关系表

5.用户基本信息表：记录系统中的用户基本信息。该表被命名为user。其主要字段如图35.5所示。

图35.5 用户基本信息表

6.用户分组表：记录系统中的用户分组信息。该表被命名为usergroup。其主要字段如图35.6所示。

图35.6 用户分组表

7.用户组对应关系表：记录用户组的对应关系。该表被命名为userug。其主要字段如图35.7所示。

图35.7 用户组对应关系表

35.7结论

本文首先进行了需求分析识别系统的整体需求，并分析了系统的数据需求，导出了功能模块。然后，进行了总体设计、功能模块设计和数据库表设计。然而，该系统仍然存在不足之处，并进一步优化和分析其数据库性能是必要的。

参考文献

1. Eckel B (2005) Thinking in java, English version 3, vol 55. China Machine Press, Beijing,

pp 23–29

2. Yang SB (2008) Practices of J2EE projects—struts framework technology, vol 43. Tsinghua

University Press, Beijing, pp 35–97

3. Zhou Y, Jiang H (2008) Study on dynamic-workflow oriented web service composition

model. Comput Technol Devel 18(1):63–65

4. Liu L, Liu HQ (2008) Design and implementation of OA system based on workflow and B/S

mode. Microcomput Inf 24(2):233–235

5. Sun X (2006) Detailed interpretation on java web development, vol 37. Electronic Industry

Press, Beijing, pp 1–341

6. Turner J, Bedell K (2004) Struts kick start, vol 54. Electronic Industry Press, Beijing, pp 19–58

7. Crane D et al. (2008) Ajax in Practice (tran: He SJ et al.), vol 56. The Peoplersquo;s Posts and

Telecommunications Press, Beijing, pp 128–144

8. Ren ZF, Zhang H (2004) Overview of the research in model-view-controller pattern. Comput

Appl Res 10:1–8

9. Boranbayev AS (2007) Optimal methods for java web services. News Natl Acad Sci Repub

Kaz 5:38–43

10. Hritonenko N, Yatsenko Y (2006) Creative destruction of computing systems: analysis and

modeling. J Supercomputing 38:143–154

11. Zhang HX (2005) Study on the workflow key technology and the construction of the

lightweight engine structure. Comput Appl 2(13):35–45

12. Boranbayev SA (2009) Defining methodologies for developing J2EE web-based information

systems. Nonlinear Anal: Theory Methods Appl 71(12):1633–1637