Skip to content

KB-101 – BlackERP Infrastructure

Knowledge Base ID: KB-101 Project: BLACK ERP Version: 1.1 Status: Certified Last Update: 2026-06-26

Change History

Version Date Description
1.0 2026-06-26 Initial infrastructure document created.
1.1 2026-06-26 Certified Tomcat Runtime documented. Infrastructure recovery validated.

1. Objective

Document the infrastructure architecture of the BLACK ERP platform, including the operating system, middleware, application server, runtime structure, deployment model, and certified infrastructure components.

This document is the primary technical reference for infrastructure maintenance, deployments, troubleshooting, disaster recovery planning, and future upgrades.

2. Environment Overview

Component Value
ERP ADempiere 3.9.4 LTS
Operating System Ubuntu 24.04 LTS
Database PostgreSQL 16
Java OpenJDK 11
Application Server Apache Tomcat 9
Reverse Proxy Nginx
API Platform NestJS
SSL Let's Encrypt

3. Domains

Domain Purpose
erp.blackerp.cloud ADempiere WebUI
api.blackerp.cloud REST API

4. Certified Runtime Architecture

The ADempiere runtime must always be considered a single logical deployment unit.

The certified runtime consists of the following directories:

tomcat/
│
├── bin/
├── conf/
├── lib/
├── webapps/
├── logs/
├── temp/
└── work/

Runtime Components

Directory Purpose
bin Tomcat startup and shutdown scripts.
conf Complete Tomcat configuration (server.xml, web.xml, context.xml, logging, etc.).
lib Shared runtime libraries used by all deployed applications.
webapps Deployed ADempiere applications and WAR packages.
logs Application and Tomcat logs.
temp Temporary runtime files.
work JSP compilation and Tomcat working directory.

5. Core Libraries

Primary runtime libraries:

  • Adempiere.jar
  • AdempiereSLib.jar
  • adempiereApps.jar
  • adempiereRoot.jar
  • CSTools.jar
  • CCTools.jar
  • postgresql.jar

Deployment packages:

  • webui.war
  • admin.war
  • wstore.war
  • adempiere.war
  • ROOT.war
  • ADInterface-1.0.war
  • mobile.war

6. Installed Packages

Current server packages include:

  • Manufacturing Management
  • Warehouse Management
  • Distribution Management
  • Finance Management
  • Fixed Asset Management
  • Freight Management
  • Cashflow Management
  • Human Resource & Payroll
  • Production Light
  • Store Integration
  • Telegram Notifier
  • Discord Notifier
  • OpenID Connect Authentication
  • ADempiere POS

Equivalent ZK packages are also installed.

7. Certified Infrastructure Validation

Validation Date

2026-06-25

Objective

Validate the recovery of the ADempiere application runtime using the certified application backup.

Backup Used

blackerp_application_v1.tar.gz

Validation Scope

The validation covered the restoration of:

  • Apache Tomcat Runtime
  • Web Applications
  • Shared Libraries
  • Runtime Configuration
  • Startup Scripts

The PostgreSQL database was intentionally excluded from this validation because the objective was to certify the application runtime.

Validation Result

The recovery process was successful.

Validated services:

Component Status
WebUI ✅ Operational
Admin ✅ Operational
WStore ✅ Operational
Runtime ✅ Certified

The following endpoints were successfully validated:

/webui    → HTTP 200
/admin    → HTTP 200
/wstore   → HTTP 200
/          → HTTP 302 (/admin)

8. Engineering Principles

Infrastructure modifications shall always follow the following engineering workflow:

  1. Understand the current architecture.
  2. Document the existing infrastructure.
  3. Perform a complete backup.
  4. Evaluate the impact.
  5. Execute the change.
  6. Validate every affected service.
  7. Update the corresponding Knowledge Base document.

Infrastructure documentation is considered part of the implementation process.

No infrastructure change shall be considered complete until its corresponding Knowledge Base document has been updated.

9. Operational Notes

The certified application runtime must always be restored as a complete unit.

The following directories are considered inseparable during recovery operations:

bin/
conf/
lib/
webapps/

Restoring only one of these components (for example webapps) may result in:

  • HTTP 404 responses
  • HTTP 500 responses
  • Missing runtime libraries
  • Filter initialization failures
  • Context startup failures
  • Incomplete application deployment

10. Next Related Documents

  • KB-102 – Disaster Recovery
  • KB-103 – Deployment Procedure
  • KB-104 – Rollback Procedure
  • KB-105 – Backup & Restore Strategy
  • KB-106 – Nginx Configuration
  • KB-107 – Troubleshooting Guide

11. Revision History

Version Date Description
1.0 2026-06-26 Initial infrastructure document created.
1.1 2026-06-26 Certified runtime architecture and recovery validation added.