三、jdk+mysql+jar打包整合成exe文件,Windows下一键安装

本文介绍如何使用InnoSetup打包工具,将JDK、MySQL和应用程序整合成一个EXE安装包,实现一键安装。包括软件和脚本准备、配置文件修改及打包脚本示例。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

一、软件准备

1、下载免安装的mysql、jdk(我用的是:官网下载的mysql-5.7.15、jdk1.8,都是64位的);

2、下载Inno Setup 打包工具(我用的是:Inno Setup 5版);

3、下载exe启动jar包工具javalauncher和更换exe图标工具rh_chinese_gb

二、脚本准备

注意:所有的脚本都保存为ANSI格式,否则在执行脚本时,会出现乱码,导致安装失败!!!

1、安装JDK

(1)准备好jdk文件(直接将安装好的复制过来即可)

(2)jdk安装脚本(.bat)

备注:rem是注释

@echo off

echo  ------begin----

rem 返回上一级目录,即jdk根目录
cd ..

echo "%~dp0"
echo "%cd%"
set jdkpath=%cd%
echo %jdkpath%

rem 设置JAVA_HOME环境变量
setx JAVA_HOME "%jdkpath%" -m

rem 设置CLASSPATH环境变量
setx CLASSPATH ".;%%JAVA_HOME%%\lib\tools.jar;%%JAVA_HOME%%\lib\dt.jar" -m

echo %Path%
echo %Path%|find /i "%java_home%" && set IsNull=true || set IsNull=false
echo %IsNull%

if not %IsNull%==true (
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /v Path /t REG_SZ /d "%Path%;%%JAVA_HOME%%\bin;%%JAVA_HOME%%\jre\bin" /f

rem 追加path变量
setx Path "%%JAVA_HOME%%\bin;%Path%"

)
exit

  在准备好脚本后,放至jdk1.8.0_131bin目录下。

2、安装MYSQL脚本

(1)准备mysql配置文件
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
# Installation Instructions
# ----------------------------------------------------------------------
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
# On Windows you should keep this file in the installation directory 
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file". 
#
# To run run the server from the command line, execute this in a 
# command line shell, e.g.
# mysqld --defaults-file="D:\test\mysql-5.7.24-winx64\my.ini"
#
# To install the server as a Windows service manually, execute this in a 
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="D:\test\mysql-5.7.24-winx64\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]
port=3306
[mysql]
default-character-set=utf8
# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this 
# file.
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
#这里是配置mysql的安装目录,当然,在Inno Setup中会将其替换成最终安装路径
basedir="C:/mysql-5.7.15-winx64"
#这里是配置mysql的数据库存放目录,当然,在Inno Setup中会将其替换成最终存放路径
datadir="C:/mysql-5.7.15-winx64/data/"
# The default character set that will be used when a new schema or table is
# created and no character set is defined
character-set-server=utf8
# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=32M
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_open_cache=256
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=35M
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before.  This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method.  This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=69M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=50M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb
# Additional memory pool that is used by InnoDB to store metadata
# information.  If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS.  As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
#innodb_additional_mem_pool_size=14M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system.  Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=96M
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=20M
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=18

放至mysql的根目录

(2)准备mysql安装脚本
cd /d %~dp0

"%cd%\mysqld.exe" --initialize-insecure --user=mysql --console

echo -----mysql init succee-----

cd ..

set "MYSQL_HOME=%cd%"

cd bin

mysqld install mysql --defaults-file="%MYSQL_HOME%\my.ini"

echo -----mysql service install succee-----


net start mysql

sc config mysql start= auto

net stop mysql


net start mysql
echo 安装完毕

cd ..

"%cd%\bin\mysqladmin" -u root password root
echo 修改密码完毕

"%cd%\bin\mysql.exe" -uroot -proot < "%cd%\sql\class.sql"
echo 建表完毕

echo 建立新用户完毕

该bat文件放至mysql的bin目录

注意:在mysql和jdk的批处理文件准备好后,先在虚拟机测试下是否能够正常安装,确认无误后,再进行打包测试!!!

3、启动服务脚本

start.bat
java -jar ****.jar
启动服务.bat
echo

sc create bms binPath= "%~dp0%start.bat"

echo

sc config bms start= auto

sc start bms

wmic service where name="bms" changestartmode "automatic"

wmic service where name="bms" startservice

pause;

exit

4、Inno Setup 打包脚本

; 脚本由 Inno Setup 脚本向导 生成!
; 有关创建 Inno Setup 脚本文件的详细资料请查阅帮助文档!

#define MyAppName "lesson"
#define MyAppVersion "1.0"
#define MyAppPublisher "pc"
#define MyAppURL "http://localhost:8082/index.html"
#define MyAppExeName "MyProg.exe"

[Setup]
; 注: AppId的值为单独标识该应用程序。
; 不要为其他安装程序使用相同的AppId值。
; (生成新的GUID,点击 工具|在IDE中生成GUID。)
AppId={{6CEE70A6-5DBD-43FF-9449-466A524C65E1}
AppName={#MyAppName}
AppVersion={#MyAppVersion}
;AppVerName={#MyAppName} {#MyAppVersion}
AppPublisher={#MyAppPublisher}
AppPublisherURL={#MyAppURL}
AppSupportURL={#MyAppURL}
AppUpdatesURL={#MyAppURL}
DefaultDirName={pf}\{#MyAppName}
DefaultGroupName={#MyAppName}
OutputDir=C:\Users\Administrator\Desktop\Output
OutputBaseFilename=setup
SetupIconFile=C:\Users\Administrator\Desktop\Icon_1.ico
Compression=lzma
SolidCompression=yes

[Languages]
Name: "chinesesimp"; MessagesFile: "compiler:Default.isl"

[Tasks]
Name: "desktopicon"; Description: "{cm:CreateDesktopIcon}"; GroupDescription: "{cm:AdditionalIcons}"; Flags: unchecked; OnlyBelowVersion: 0,6.1

[Files]
Source: "D:\test\jdk1.8.0_131\*"; DestDir: "{app}\jdk1.8.0_131"; Flags: ignoreversion recursesubdirs createallsubdirs
Source: "D:\test\mysql-5.7.15-winx64\*"; DestDir: "{app}\mysql-5.7.15-winx64"; Flags: ignoreversion recursesubdirs createallsubdirs
Source: "D:\test\web\*"; DestDir: "{app}\web"; Flags: ignoreversion recursesubdirs createallsubdirs
; 注意: 不要在任何共享系统文件上使用“Flags: ignoreversion”

[Icons]
Name: "{group}\{#MyAppName}"; Filename: "{app}\{#MyAppExeName}"
Name: "{commondesktop}\{#MyAppName}"; Filename: "{app}\{#MyAppExeName}"; Tasks: desktopicon

[INI]

;修改数据库配置文件

Filename:"{app}\mysql-5.7.15-winx64\my.ini";Section:"mysqld";Key:"basedir"; String:"{app}\mysql-5.7.15-winx64"

Filename:"{app}\mysql-5.7.15-winx64\my.ini";Section:"mysqld";Key:"datadir"; String:"{app}\mysql-5.7.15-winx64\data"

Filename:"{app}\mysql-5.7.15-winx64\my.ini";Section:"mysqld";Key:"port"; String:"3306"

Filename:"{app}\mysql-5.7.15-winx64\my.ini";Section:"client";Key:"port"; String:"3306"

[Run]
Filename: "{app}\jdk1.8.0_131\bin\autoInstallJDK.bat";

Filename: "{app}\mysql-5.7.15-winx64\bin\mysql_init.bat";

Filename: "{app}\web\启动服务.bat";

[UninstallDelete]

Type:filesandordirs;Name:"{app}\jdk1.8.0_131"

Type:filesandordirs;Name:"{app}\mysql-5.7.15-winx64"

注意:当脚本运行错误时,需要回看错误情况,可以在发生错误的地方加上 pause; 来查看,防止控制台一闪而过!
详细请参见jdk+tomcat+mysql+war打包整合成exe文件,Windows下一键安装

<think>我们正在讨论的是如何将Vue前端、SpringBoot后端和MySQL数据库的项目打包JAR文件并部署。根据用户的问题,我们需要提供从打包到部署的完整流程。下面将结合引用内容,分步骤说明。步骤1:后端SpringBoot打包JAR-在SpringBoot项目的pom.xml文件中,需要配置打包插件和最终生JAR文件名(引用[2]):```xml<build><finalName>web-master</finalName><!--设置生jar包名称--><plugins><plugin><groupId>org.springframework.boot</groupId><artifactId>spring-boot-maven-plugin</artifactId><version>2.2.2.RELEASE</version></plugin></plugins></build>```-使用Maven的package命令进行打包(在IDE中双击package或命令行执行`mvnpackage`),打包后会在target目录下生一个可执行的JAR文件(如web-master.jar)。步骤2:前端Vue项目打包-在Vue项目目录下,运行`npmrunbuild`命令,生dist目录(包含静态文件)。步骤3:将前端静态文件整合到SpringBoot项目中(可选,但常见部署方式)-将Vue打包的dist目录下的所有文件复制到SpringBoot项目的src/main/resources/static目录下。-重新打包SpringBoot项目(这样JAR包中就包含了前端静态资源,可以独立运行)。步骤4:配置生产环境文件-在SpringBoot项目中,需要配置生产环境的配置文件(如application-prod.yml),设置数据库连接、Redis等(引用[3]):```yamlspring:mvc:pathmatch:matching-strategy:ant_path_matcherapplication:name:your-app-namedatasource:driver-class-name:com.mysql.cj.jdbc.Driverurl:jdbc:mysql://服务器IP地址:3306/数据库名?characterEncoding=UTF-8username:数据库用户名password:数据库密码#其他配置如Redis等server:port:8080servlet:context-path:/api```-注意:数据库的访问权限需要设置为允许远程连接(在MySQL中创建用户并授权),并且数据库名不要使用root、test等(引用[4])。步骤5:部署到服务器-将生JAR文件(如web-master.jar)上传到服务器(可以使用WinSCP等工具,引用[2])。-在服务器上运行JAR文件:```bashjava-jarweb-master.jar```或者使用后台运行并记录日志的脚本(引用[2]):```bash#!/bin/shjava-jarweb-master.jar2>&1>>app.log&```将上述命令保存为start.sh,并赋予执行权限:`chmod+xstart.sh`,然后运行`./start.sh`。步骤6:配置MySQL数据库-在服务器上安装MySQL(如果使用宝塔面板,可以在软件商店中安装MySQL,引用[3])。-创建数据库,并设置访问权限(选择“所有人”或指定IP,确保SpringBoot应用可以连接,引用[4])。-导入数据库脚本(如果需要)。步骤7:配置反向代理(可选,但推荐)-如果使用宝塔面板,可以添加一个站点(域名或IP),然后配置反向代理到SpringBoot应用(比如运行在8080端口)。-在宝塔面板的网站设置中,添加反向代理,目标URL为`http://localhost:8080`(或实际端口)。注意:如果前端静态资源已经整合JAR包中,那么直接访问JAR运行的端口(如8080)就可以看到前端页面。如果前端是独立部署,则需要将前端部署到Web服务器(如Nginx),并通过代理访问后端API。以上步骤是基于将前端打包到后端JAR中的方式,这样部署只需要一个JAR文件。另一种方式是前后端分离部署,前端使用Nginx部署,后端独立运行JAR,并通过代理解决跨域问题(在Nginx中配置代理后端API)。根据引用[1][3][4],使用宝塔面板可以更方便地完这些部署步骤。现在,根据用户需求,我们提供了打包和部署的基本步骤。下面生相关问题:</think>### Vue + Spring Boot + MySQL 项目打包部署教程 以下是将 Vue 前端 + Spring Boot 后端 + MySQL 数据库打包JAR 文件并部署的完整流程: --- #### **一、前期准备** 1. **环境配置** - 云服务器:推荐 Linux 系统(如 CentOS 7+ 或 Ubuntu) - 本地开发环境: - JDK 17+(与 Spring Boot 3 兼容) - Node.js 16+(Vue 构建) - MySQL 8.0(与生产环境一致) - 工具: - WinSCP/Xftp(文件传输) - Xshell/PuTTY(服务器操作) - 宝塔面板(可选,简化部署)[^1] 2. **数据库准备** - 在服务器安装 MySQL,创建生产环境数据库: ```bash # 登录 MySQL mysql -u root -p # 创建数据库和用户(权限设置为所有人) CREATE DATABASE app_db CHARACTER SET utf8mb4; CREATE USER 'app_user'@'%' IDENTIFIED BY 'your_password'; GRANT ALL PRIVILEGES ON app_db.* TO 'app_user'@'%'; FLUSH PRIVILEGES; ``` - 导入本地数据库脚本: ```bash mysql -u app_user -p app_db < dump.sql ``` --- #### **二、项目打包** 1. **Vue 前端打包** - 修改 `vue.config.js` 设置生产环境 API 地址: ```javascript module.exports = { devServer: { proxy: 'http://服务器IP:后端端口' // 后端API地址 }, publicPath: process.env.NODE_ENV === 'production' ? '/' : '/' } ``` - 执行构建命令: ```bash npm run build # 生 dist 目录 ``` 2. **Spring Boot 后端配置** - 创建 `application-prod.yml` 生产配置文件: ```yaml spring: datasource: url: jdbc:mysql://服务器IP:3306/app_db?useSSL=false&characterEncoding=UTF-8 username: app_user password: your_password servlet: context-path: /api server: port: 8080 # 后端运行端口 ``` - **关键步骤**:将 Vue 的 `dist` 目录复制到 `src/main/resources/static`,使 JAR 包包含前端资源[^3] 3. **Maven 打包** - 在 `pom.xml` 中添加打包插件: ```xml <build> <finalName>app-backend</finalName> <!-- 生JAR名称 --> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <version>3.0.6</version> </plugin> </plugins> </build> ``` - 执行打包命令: ```bash mvn clean package -DskipTests # 生 app-backend.jar ``` --- #### **、服务器部署** 1. **上传文件** - 使用 WinSCP 将 `app-backend.jar` 上传到服务器 `/root` 目录 2. **创建启动脚本** - 新建 `start.sh` 启动脚本: ```bash #!/bin/bash nohup java -jar /root/app-backend.jar --spring.profiles.active=prod > app.log 2>&1 & ``` - 赋予执行权限: ```bash chmod +x start.sh ``` 3. **运行项目** ```bash ./start.sh # 后端启动,日志输出到 app.log ``` 4. **验证运行** - 检查进程: ```bash ps aux | grep java ``` - 测试访问: - 前端页面:`http://服务器IP:8080` - API接口:`http://服务器IP:8080/api/health` --- #### **四、优化与安全** 1. **反向代理配置(Nginx)** - 通过宝塔面板添加站点,配置反向代理[^1]: ```nginx server { listen 80; server_name your-domain.com; location / { root /path/to/vue/dist; # 分离部署时使用 try_files $uri $uri/ /index.html; } location /api { proxy_pass http://127.0.0.1:8080; proxy_set_header Host $host; } } ``` 2. **防火墙设置** ```bash firewall-cmd --permanent --add-port=8080/tcp # 开放后端端口 firewall-cmd --permanent --add-port=80/tcp # 开放HTTP firewall-cmd --reload ``` 3. **进程守护** - 使用 `systemd` 创建服务(示例路径:`/etc/systemd/system/app.service`): ```ini [Unit] Description=Spring Boot App After=syslog.target [Service] ExecStart=/usr/bin/java -jar /root/app-backend.jar User=root [Install] WantedBy=multi-user.target ``` - 启动服务: ```bash systemctl daemon-reload systemctl start app systemctl enable app ``` --- #### **常见问题解决** 1. **数据库连接失败** - 检查 MySQL 用户远程权限:`SELECT host FROM mysql.user WHERE user='app_user';` - 确认防火墙开放 3306 端口 2. **前端路由 404** - 在 Nginx 配置中添加: ```nginx location / { try_files $uri $uri/ /index.html; } ``` 3. **JAR 包内存不足** - 启动时指定内存: ```bash java -Xms512m -Xmx1024m -jar app-backend.jar ``` > **注意**:生产环境务必配置 HTTPS 证书,可使用宝塔面板一键申请 Let's Encrypt 证书[^1]。
评论 8
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值