What this category’s data looks like
Data sources for pulp and paper technical documents include wood pulp and waste paper batch ledgers, DCS/QCS systems, on-paper-machine measurement equipment, laboratory instruments, energy and water treatment systems. Daily generated documents cover pulp preparation sheets, beating records, paper machine operation logs, online quality curves, laboratory reports, and sheet break and product change ledgers. Data update frequencies include real-time, per shift, and after each roll of paper is completed. Fields include stock consistency, beating degree, paper machine speed, grammage, moisture content, and other metrics, with standardized units attached.
Constraints on deployment and upgrade
Data sources for this category are scattered, and update frequencies vary widely. During deployment, configuration logic for multi-source data access must be adapted. During upgrades, synchronization mechanisms for data streams of different frequencies must be compatible. Documents include structured ledgers and visual quality curves. During deployment, index rules that support mixed-format parsing must be configured. Record data volume per roll of paper fluctuates significantly. During upgrades, storage expansion thresholds must be planned in advance. Cross-departmental document reuse requirements mandate that unified permission mapping rules be configured during deployment.
Configuration settings
This configuration applies to FastGPT v4.17.0. Specific recommended values are as follows:
| Configuration Item | Recommended Setting | Basis |
|---|---|---|
DB_MAX_LINK | 120–180 concurrent connections/second | Adapt to real-time data streams from on-paper-machine measurement equipment |
MONGODB_URI | Local cluster node address | Adapt to storage requirements for mixed-format documents |
PG_URL | 1000 MB storage space | Meet storage requirements for documents generated per shift |
FE_DOMAIN | Internal enterprise business domain name | Adapt to integration requirements of existing systems |
FILE_TOKEN_KEY | 32-bit random string | Ensure security of document access |
ROOT_KEY | Configured by permission hierarchy | Adapt to cross-departmental document reuse requirements |
Three common configuration mistakes
- Phenomenon: Front-end page fails to load after deployment, with a 404 error prompt. Cause:
FE_DOMAINis not configured as the internal enterprise business domain name, and is not added to the allowed access list. - Phenomenon: Storage overflow error occurs during Docker Compose deployment. Cause: Storage configuration is not adjusted based on pulp and paper document data volume, and the set value is lower than actual demand.
- Phenomenon: Residual data remains after executing a conversation record cleanup operation. Cause: Storage caches corresponding to
MONGODB_URIandPG_URLare not cleaned up synchronously.
How to confirm correct configuration
- Run multi-source data access tests, check whether the connection status of
DB_MAX_LINKis normal. - Submit documents such as pulp preparation sheets and quality curves, verify that index generation progress meets the concurrent connection requirements specified in the configuration.
- Access the internal enterprise business domain name, confirm that the front-end page loads normally without 404 errors.
- Execute the conversation record cleanup operation, verify that data in both the cache and database has been cleaned up.
The values provided are common starting points and should be measured against the reader's own samples.