MicroCommunity SaaS Property Management System

HC MicroCommunity (HC小区管理系统) is a SaaS-based property management system. It provides a comprehensive suite of tools for managing real estate, owners, fees (including online payments), repairs (online reporting), complaints/suggestions, procurement, inspections, parking, access control (gates/barriers), monitoring, workflows, questionnaires, and announcements.

The ecosystem consists of four main components:

1. Property Management Web Frontend: For property staff using desktop computers.
2. Property Management Backend: The core business logic processing engine.
3. Owner Mobile App: For residents to use services like complaints, payments, and repairs.
4. Property Staff Mobile App: For property employees to use on mobile devices.

The common module provides shared utility implementations used across the microcommunity project. Its primary responsibilities include:

• String Validation: Utilities for checking and validating string formats.
• Encryption: Tools for generating encrypted information and managing security-related data.

The config module in microcommunity manages the core application settings. It provides structured configuration for the following components:

• Spring Configuration: Manages the Spring Framework environment and bean definitions.
• MySQL Configuration: Handles database connection settings, including host, port, username, password, and database name.
• MyBatis Configuration: Manages MyBatis-specific settings such as mapper locations, type aliases, and SQL execution behavior.

The MicroCommunity system is composed of four distinct repositories catering to different user roles and platforms:

1. Property system backend (wuxw7/MicroCommunity): The core business logic and processing engine.
2. Front end of property system (java110/MicroCommunityWeb): Web terminal for property staff to manage operations via computer.
3. Property mobile version (java110/PropertyApp): Mobile terminal for property staff.
4. Owner's mobile phone (java110/WechatOwnerService): Mobile interface for residents/owners to handle complaints, payments, and repairs.

The HC Microcommunity system uses a database named TT. The corresponding schema file is TT.sql.

Database Requirements

• Recommended Version: MySQL 5.6.
• Compatible Versions: MySQL 5.7 and MySQL 8.0.
• Warning: Other database engines have not been officially tested; use them with caution.

MySQL 5.7 and 8.0 Configuration

If you are using MySQL 5.7 or 8.0, you must disable the following settings to ensure compatibility:

1. Case sensitivity (MySQL case sensitivity settings).
2. GROUP BY strict mode/behavior.
3. Date non-null validation (ONLY_FULL_GROUP_BY and related strict modes).

Verification

After importing the TT.sql script, verify that the TT database contains more than 570 tables.

-- Target database name: TT
-- Schema file: TT.sql

You can test the system using the public demo environment:

• Web URL: http://demo.homecommunity.cn
• Administrator Credentials: admin / admin
• Property Staff Credentials: wuxw / admin
• Developer Credentials: dev / (password must be changed manually)

To learn how to modify the developer password, refer to the Password Modification Guide.

In Spring Boot mode, you only need to focus on the springboot service. Other services starting with service are automatically compiled into the Spring Boot executable and do not need to be started separately.

Option 1: Run via JAR

You can start the service using the generated JAR file:

java -jar springboot\target\MicroCommunityBoot.jar

Option 2: Run via Java Class

Alternatively, you can run the application directly using the entry point class:

BootApplicationStart.java

Installation procedures are divided into two paths depending on your target environment:

• Development environment: Follow the Development environment installation guide for local setup.
• Production environment: Follow the Production environment installation guide for deployment-ready setups.

After running the environment switch script, you must recompile the project to apply the Spring Boot configuration. Run the following Maven commands from the project root:

mvn clean install
mvn clean package