What the data for this category looks like
Internal enterprise MES manufacturing execution systems, OA approval management systems, and safety operation procedure manuals supply business process guidance data for refinery and chemical production. Updates occur when production plans adjust or approval processes optimize. Document structures include fields such as operation type, approval hierarchy, required materials, and time limit requirements. Some fields use professional units: material usage uses tons as the unit, and operation duration uses hours as the unit. Individual process documents can be up to several thousand characters long.
Constraints on Deployment and Upgrade
Refinery and chemical business process data comes from heterogeneous internal enterprise systems. Configure corresponding database connections during deployment to adapt to different types of business data storage. Data fields include professional units and structured approval nodes. Calibrate field mapping rules during deployment to avoid data parsing errors. Process documents have long lengths, and update frequencies shift dynamically with production plans. Maintain compatibility with old data formats during upgrade to prevent business process interruptions. Some data involves production safety sensitive information. Configure encryption parameters during deployment to secure data transmission and storage.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://[username]:[password]@[intranet IP]:27017/fastgpt?authSource=admin | Stores long process documents and approval records for refinery and chemical business processes, adapts to unstructured data storage needs |
PG_URL | postgresql://[username]:[password]@[intranet IP]:5432/fastgpt | Stores business fields with professional units, such as material tonnage and approval duration, to ensure field precision |
REDIS_URL | redis://:[password]@[intranet IP]:6379/0 | Caches frequently called approval node rules to reduce database query pressure, adapts to concurrent request volumes of refinery and chemical business |
FE_DOMAIN | https://[intranet business domain name of refinery and chemical enterprise] | Binds the enterprise internal access domain name, ensures business process pages are only accessible via intranet, complies with enterprise security specifications |
FILE_TOKEN_KEY | Randomly generated 32-bit string | Encrypts download links for approval attachments during business process handling, prevents leakage of sensitive production documents |
DB_MAX_LINK | 100–150 connections | Adapts to concurrent request volumes of refinery and chemical business processes, avoids database connection exhaustion |
Three Common Configuration Mistakes
- Symptom: After modifying the configuration file, the service on port 3005 cannot respond normally, and access returns a 502 error. Cause: The mapping relationship between
FE_DOMAINand the intranet access port is not configured correctly, causing communication interruption between front-end and back-end services. - Symptom: After upgrading to FastGPT v4.17.0, cross-department refinery and chemical business process knowledge bases cannot be shared. Cause: The
ROOT_KEYpermission parameter is not configured correctly, resulting in unopened cross-department access permissions. - Symptom: After local deployment and attempts to integrate with existing business systems, only API access is available, and embeddable front-end pages cannot be generated. Cause:
FE_DOMAINis not configured correctly, causing the front-end build script to fail to generate static resources required for embedding.
How to Verify Successful Configuration
- Access the business process page corresponding to the configured
FE_DOMAIN, verify that the process node list for refinery and chemical business loads normally. - Submit a simulated refinery and chemical business process application, verify that data can be correctly written to the databases corresponding to
MONGODB_URIandPG_URL. - Download a business approval attachment, verify that the link can open normally and has no permission exceptions.
- Restart the service, check that the cache service corresponding to
REDIS_URLconnects normally, with no timeout errors.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.