2.3 Development Environment
The development environment of digital
management information system of university
documents and archives is introduced in two parts,
one is the construction of hadoop big data cluster,
the other is the application environment of Javaweb
technology. According to the required amount of
data, this paper builds a hadoop cluster composed of
four nodes. The node is named as the master node
namenode, and three slave nodes datanode01,
datanode02 and datanode03. These clusters are
stored based on HDFS distributed storage pairs, and
are built with other hadoop ecosystem components,
such as flume, hbase and hive. The hadoop server
cluster is developed on four clients installed with
Linux system. This paper selects Centos7.8 Server
release version of Linux operating system.
The Java development tool used in the JavaWeb
application of this system is my eclipse, the
development environment is JDK 1.8, the
development language is Java, and Apache Tomcat
9.0 is selected for server construction. This system is
implemented in B/S mode. The browser side uses
the dynamic web page technology of
HTML+CSS+JaVaScript, and uses AJAX
technology to communicate with the server side. The
development of the system is based on MVC pattern.
The SSH framework of struct2+spring+hibernate is
used as the framework, and sqlsever database is used
to help manage data. Through the introduction of the
above key technical theories, the overall
environment, the configuration of related software
and tools for the development of digital management
information system of university documents and
archives are determined, and the technical feasibility
of the overall project is also clarified. (Liao, 2022)
3 DEMAND ANALYSIS
3.1 Functional Requirements
The user end of the digital management information
system of documents and archives in colleges and
universities is provided with the common user end
and the administrator user end. Ordinary users
include teachers and students, and ordinary user end
functions mainly include borrowing, returning,
booking and file retrieval. The administrator end
mainly includes two main functional modules:
application processing, file management and user
management. (Yu, 2018) At the same time, the
system has the function of electronic archives. With
the increasing content and types of archives,
electronic archives will become the main work of
future archives management. The electronic archives
in this paper need to be consulted by users in a
targeted way, so as to improve the user experience
and the management efficiency of archivists.
The performance requirements of the system
require that when the system processes the operation
request of the foreground interactive interface, it
should ensure that all functions of the business logic
layer are processed within 5 seconds in the normal
communication network environment, and the
processing results of the operation instructions are
returned in time. At the same time, considering the
scale of archives management business in colleges
and universities, the system should support the
instruction processing of concurrent operation access
of at least 100 users. (Li, 2020)
3.2 Overall Design
The overall design of digital management
information system of documents and archives in
colleges and universities is divided into two parts:
application design and data processing. This paper
divides the data processing of the system into six
layers. The first layer is the data source layer. The
data comes from the local database server and the
audit data in the information management system, as
well as other data entered inside the organization,
which can be divided into structured data and
unstructured data. In the data transmission layer,
sqoop transmits the data from the storage layer and
the source layer, and flume collects the unstructured
log data from the server. The data storage layer of
the system consists of HDFS file storage, MySQL
database and hbase database. The resources built on
hadoop cluster are managed by yarn. The interaction
of data query function is completed by Hive
component, and the scheduling of distributed cluster
needs to be completed by Oozie.
The application part of this system is divided into
three layers, namely presentation layer, business
layer and data layer. The whole system adopts B/S
mode combined with MVC thought and uses SSH
architecture of struct2+spring+hibernate for
development. The web layer is the middle part
between the view layer and the control layer, which
is handled by struct2, in which action is used to
handle all kinds of access requests and access
feedback instructions, such as HttpRequest and
HttpResponse from the network. In this process, the
request parameters need to be repackaged and
various functions of page navigation are needed. The