Environment Deployment:Backend No-Code Designer Jar Package Startup Method
I. Download Oinone Exclusive Starter
(Ⅰ) Mac OS Platform Startup
# Direct run
./darwin-boot java -jar ./pamirs-designer-boot-4.7.0.jar
# nohup background run
nohup ./darwin-boot java -jar ./pamirs-designer-boot-4.7.0.jar > out.log 2>&1 &
(Ⅱ) Mac OS (arm64 Architecture) Platform Startup
# Direct run
./darwin-boot-arm64 java -jar ./pamirs-designer-boot-4.7.0.jar
# nohup background run
nohup ./darwin-boot-arm64 java -jar ./pamirs-designer-boot-4.7.0.jar > out.log 2>&1 &
(Ⅲ) Linux Platform Startup
# Direct run
./linux-boot java -jar ./pamirs-designer-boot-4.7.0.jar
# nohup background run
nohup ./linux-boot java -jar ./pamirs-designer-boot-4.7.0.jar > out.log 2>&1 &
(Ⅳ) Linux (arm64 Architecture) Platform Startup
# Direct run
./linux-boot-arm64 java -jar ./pamirs-designer-boot-4.7.0.jar
# nohup background run
nohup ./linux-boot-arm64 java -jar ./pamirs-designer-boot-4.7.0.jar > out.log 2>&1 &
(Ⅴ) Windows Platform Startup
.\win-boot.exe java -jar .\pamirs-designer-boot-4.7.0.jar
II. Instructions
- The
java -jar
command used above is exactly the same as the conventional usage. - The Oinone no-code designer does not support the use of
javaagent
parameters.
III. Common Startup Scripts
#!/bin/bash
# Directory where the script is located
home=$(cd "$(dirname "$0")" && pwd)
# Startup jar path
jarPath=$home/pamirs-designer-boot-4.7.0.jar
# Configuration path
applicationPath=$home/application.yml
# License information
subject=
licensePath=
nohup $home/linux-boot java -Duser.timezone=GMT+08:00 -Dhttps.protocols=TLSv1.2 -Dfile.encoding=UTF-8 \
-jar $jarPath \
--spring.config.location=$applicationPath \
-Psubject=$subject \
-Plicense=$licensePath \
-Plifecycle=INSTALL > $home/out.log 2>&1 &
sleep 1
tail -200f $home/out.log
IV. How to Handle the "cannot execute binary file" Exception?
(Ⅰ) Problem Cause
The Oinone exclusive starter
is compiled and executed using Go language
, which requires separate compilation for different operating system architectures.
(Ⅱ) Solution
- Install the
Go language
environment on the physical machine. - Download the
boot.go
file and place it in therun
directory. (You need to askOinone customer service
for the latestboot.go
file) - Enter the
run
directory and execute the commandgo build -o "boot-starter" "boot.go"
. - Add
-v $home/run/boot-starter:/opt/pamirs/run/boot-starter \
to thestartup.sh
command to mount the file to the container. - Delete the docker container and then execute the
startup.sh
script to restart the image.
V. How to Handle the "failed to open elf at /lib64/ld-linux-x86-64.so.2" Exception?
(Ⅰ) Problem Cause
Some arm64
architecture hosts cannot be compatible with the linux-boot
starter compiled in the amd64
environment, and the starter needs to be replaced with linux-boot-arm64
.
(Ⅱ) Solution
- Download oinone-boot-starter.zip and unzip it to obtain the
linux-boot-arm64
starter. - Place the starter in the
run
directory. - Add
-v $home/run/linux-boot-arm64:/opt/pamirs/run/boot-starter
to thestartup.sh
command to replace the starter in the image. - Delete the docker container and then execute the
startup.sh
script to restart the image.