Conference oa system project deployment process

Table of contents

1. Project deployment environment

2. Initialize the database

2.1 Get the database script

2.2 Create a database

1. Create a database connection

2. Create a database and name it

3. Run the sql file

4. View imported data

​edit

​edit

3 Project Environment Deployment

3.1 Import project resources

3.2 Loading the framework

load success sign

Server configuration (used to save the seats and sign pictures to the local path)

4. Import the project file (officially start the project)

4.1 Import project java class

4.2 Import js, css, jsp files in WebContent

4.2.1 Create a public package (common) for public class applications

4.2.2 Create package (jsp) for jsp page storage

4.2.3 Create a package (static) project resource storage

4.2.4 Import basic jsp

5. Start the front-end interface

5.1 Register Meeting User Interface

5.2 Conference login interface

5.3 Main interface

5.4 Release meeting

5.5 My meeting (seat arrangement, review)

5.6 My approval

5.7 Pending meetings

5.8 Historical Sessions

5.9 All sessions


1. Project deployment environment

name Version
jdk 1.8
Mysql 8.0
eclipse 2017
Goodle Chrome 2023
nivacat 2017
Tom act 8.0
jQuery 3.3.1
html2canvas (seating plug-in) 2023
signature 2023
layui 2.7.6
formSelects (drop-down box plugin) 2022

2. Initialize the database

2.1 Get the database script

Find our sql in the project documentation

2.2 Create a database

1. Create a database connection

2. Create a database and name it

The general database naming needs to correspond to the database script, so that the sql script can run normally

3. Run the sql file

Click the blank area on the right, run the sql file, and then select the sql file to import

4. View imported data

 

3 Project Environment Deployment

3.1 Import project resources

Import the jar and tid (custom label) required by the project into the lib under web-inf, select one of the jars and click build path, and add to build path.

3.2 Loading the framework

Import utils into the package under src, create a new same-level directory conf, put mvc.xml (frame configuration mapping file), resource.properties (signature, seat configuration file) into it, and modify the server image mapping path That's it.

load success sign

Server configuration (used to save the seats and sign pictures to the local path)

4. Import the project file (officially start the project)

4.1 Import project java class

Put it in the package under src and utils in the same package level, and pay attention to the naming of the package name

4.2 Import js, css, jsp files in WebContent

4.2.1 Create a public package (common) for public class applications

Create a jsp file inside it to import, layui.css, layui.js, formSelects-v4.css, formSelects-v4.js, config.js (layui extension file)

4.2.2 Create package (jsp) for jsp page storage

In it is divided into two packages for storage (jsp for conference interface) and another for storage of jsp for system interface

4.2.3 Create a package (static) project resource storage

Store project css files in the css package, store project images in image, and store layui css and font js files in the js package in the build layui package; build a package named meeting (js for storing meeting jsp); build a package named system package (js of the storage system jsp); finally import jQuery, main.js, login.js, register.js

4.2.4 Import basic jsp

In the created package, import the jsp files (login, main, register) of the same level directory

5. Start the front-end interface

5.1 Register Meeting User Interface

5.2 Conference login interface

5.3 Main interface

5.4 Release meeting

5.5 My meeting (seat arrangement, review)

5.6 My approval

5.7 Pending meetings

5.8 Historical Sessions

5.9 All sessions

Guess you like

Origin blog.csdn.net/lz17267861157/article/details/132037342