Backend Development 8 min read

Wukong CRM 9.0 Java Backend Installation and Deployment Guide

This article provides a comprehensive guide to installing and deploying the Wukong CRM 9.0 Java version, detailing its backend stack, required environments, configuration files, Maven dependencies, Undertow/Tomcat deployment options, and front‑end Vue setup, along with QR‑code download instructions.

Top Architect
Top Architect
Top Architect
Wukong CRM 9.0 Java Backend Installation and Deployment Guide

Wukong CRM is an enterprise management suite (CRM/HRM/OA/ERP) that offers development, implementation, marketing, consulting, training, and support services. The Java edition follows a front‑back separation model and includes pre‑built Vue front‑end assets.

Main Technology Stack

Core framework: JFinal 3.8

Cache: Redis, Caffeine

Database connection pool: Druid

Utilities: Hutool, FastJSON, POI‑ooxml

Scheduled tasks: jfinal‑cron

Build tool: Maven

Web containers: Tomcat, Undertow (default)

Front‑end MVVM framework: Vue.js 2.5.x

Router: Vue‑Router 3.x

HTTP client: Axios

UI framework: Element‑UI 2.6.3

Installation Steps

Prepare Java, Redis, and MySQL environments.

Import doc/crm9.sql into MySQL. (For initial install only this file is needed; later updates require the corresponding dated SQL file.)

Edit the database configuration in resources/config/crm9-config.txt .

Update Redis connection details in resources/config/redis.json .

Modify Undertow port in resources/config/undertow.txt if necessary.

Default credentials: username admin , password 123456 .

Deployment Options

1. Undertow (default)

<dependency>
    <groupId>com.jfinal</groupId>
    <artifactId>jfinal-undertow</artifactId>
    <version>1.9</version>
</dependency>

Uncomment the above dependency, comment out the Tomcat servlet API dependency, change the packaging to jar , run mvn package , upload the generated crm9-release.zip to the server, unzip, and start the service with 72crm.sh or 72crm.bat .

2. Tomcat Deployment

<dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>javax.servlet-api</artifactId>
    <version>4.0.1</version>
    <scope>provided</scope>
</dependency>

Comment out the Undertow dependency, comment out the main method in com.kakarote.crm9.Application , change the packaging to war , run mvn package , and place the resulting war file in tomcat/webapps . Adjust ux/config/prod.env.js if a context path is needed, then redeploy.

The project includes pre‑built front‑end files under webapp . If you do not modify the front‑end, you can access the application directly; otherwise replace the dist/static folder and index.html after rebuilding.

For static file serving, you may use nginx as a reverse proxy, keeping the back‑end API‑only.

Front‑end Deployment

Install node.js (version 6.0+).

Navigate to the ux directory and run npm install to install dependencies.

Adjust configuration: Change API base URL in config/dev.env.js (default localhost ). Modify the development server port in config/index.js if needed (default 8090).

Start the front‑end with npm run dev . Ensure port 8090 is free before launching.

System Overview

The article also includes screenshots of the CRM’s UI and a QR code that, when scanned, provides the source code download link. Users are encouraged to reply with specific keywords (e.g., “架构” or “架构整洁”) to receive a surprise gift package.

Additional promotional content invites readers to join a “Top Architect” community via WeChat and provides disclaimer about copyright.

BackendJavaDeploymentVueInstallationCRMJFinal
Top Architect
Written by

Top Architect

Top Architect focuses on sharing practical architecture knowledge, covering enterprise, system, website, large‑scale distributed, and high‑availability architectures, plus architecture adjustments using internet technologies. We welcome idea‑driven, sharing‑oriented architects to exchange and learn together.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.