• 首页
  • 产品中心
    • 数式Oinone四大产品

      低代码开发平台无代码开发平台集成开发平台AI大模型开发
    • 数式Oinone体系能力

      用户与组织权限管理文件管理消息中心国际化业务审计
    • 数式Oinone核心产品特性

      低无一体面向软件公司场景无限制应用级扩容可分可合
  • 服务中心
    • 客户服务

      预约演示方案咨询私有部署找人定制
    • 开发者

      问答下载
    • Oinone学院

      社区学习

    《精讲面向软件公司的低代码平台——以Oinone为例》

  • 合作伙伴
    渠道申请伙伴名录专家库
  • 关于数式
0571-88757863

Environment Deployment:Backend No-Code Designer Jar Package Startup Method


I. Download Oinone Exclusive Starter

oinone-boot-starter.zip

(Ⅰ) 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

  1. The java -jar command used above is exactly the same as the conventional usage.
  2. 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

  1. Install the Go language environment on the physical machine.
  2. Download the boot.go file and place it in the run directory. (You need to ask Oinone customer service for the latest boot.go file)
  3. Enter the run directory and execute the command go build -o "boot-starter" "boot.go".
  4. Add -v $home/run/boot-starter:/opt/pamirs/run/boot-starter \ to the startup.sh command to mount the file to the container.
  5. 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

  1. Download oinone-boot-starter.zip and unzip it to obtain the linux-boot-arm64 starter.
  2. Place the starter in the run directory.
  3. Add -v $home/run/linux-boot-arm64:/opt/pamirs/run/boot-starter to the startup.sh command to replace the starter in the image.
  4. Delete the docker container and then execute the startup.sh script to restart the image.
Edit this page
Last Updated:1/15/26, 4:02 AM
Prev
Environment Deployment:Deploy Designer on NeoKylin (mips64 Architecture)
Next
Login Extension:Oinone Login Extension:Docking with SSO
默认页脚
Copyright © 2026 Mr.Hope