Product installation
This section summarizes deployment, runtime requirements, network rules, component dependencies, and database initialization for Datablau products. It is intended for installation, operations, implementation, and delivery teams.
Before deployment
- Prepare a mainstream Linux operating system such as CentOS or Red Hat, together with the server, disk, port, and database resources required by the delivery environment.
- Provide the application server IP and MAC address when a product license is generated. Keep the deployment server isolated from conflicting services.
- Initial Linux service configuration normally requires root access. Create a dedicated
datablauaccount for deploying, starting, and stopping services. - The platform database can be MySQL, Oracle, DM Database, or PostgreSQL, depending on the project. Follow the delivered environment specification for character set, case sensitivity, and version requirements.
Components and network
A typical deployment includes Gateway, Base, User, Workflow, Audit, DAM, DDM, DDC, DDS, Redis, Elasticsearch, Neo4j, Kafka, DolphinScheduler, Zookeeper, Nacos, and Nginx. Confirm service ports, TCP access between components, office network access to Nginx, and database allowlists before deployment.
Database initialization
Create the database instance and deployment account before starting the applications. Startup initializes the required DDL. Confirm the database character set, collation, connection pool, maximum packet size, account privileges, and backup policy in production. Do not reuse sample ports or memory values without validating the target environment.