What the data for this category looks like
The core data for this category comes from cell banks and seed lots, process analysis, cleanroom monitoring, MES, LIMS, and equipment integrity testing. Daily documents include cell bank or seed lot records, culture and purification records, aseptic filling records, environmental monitoring, media fill simulation, sterility testing, and batch release materials. These documents include fixed fields such as batch number, culture temperature (℃), cleanroom sedimentation bacteria concentration (cfu/㎡), and equipment operating duration (hours). Data update frequencies fall into three categories: per batch, real-time, and per monitoring plan. The update interval for some real-time monitoring data does not exceed 15 minutes.
What constraints these characteristics impose during deployment and upgrades
Dispersed multi-source data requires support for interfacing with multiple systems during deployment, to avoid data synchronization interruptions that affect production document integrity. Data with different update frequencies need to support both incremental synchronization and batch import modes. The upgrade phase must be compatible with legacy data structures to prevent historical records from becoming unsearchable due to skipped-level upgrades. Complex document fields and strict compliance requirements require custom field mapping during configuration, while ensuring data access permissions are only available to authorized personnel to avoid leakage of sensitive production data.
How to configure the settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 records/minute | Adapt to concurrent requests from multiple data sources such as MES and LIMS, and avoid data synchronization failures caused by connection pool exhaustion |
MONGODB_URI | Point to a dedicated MongoDB cluster storing aseptic manufacturing records | Isolate business data from general data to ensure access permissions and stability of production documents |
REDIS_URL | Configure as a local cache node with an expiration time set to 30 minutes | Cache real-time cleanroom monitoring data to reduce network overhead from repeated LIMS queries |
STORAGE_S3_ENDPOINT | Connect to an enterprise-compliant object storage service endpoint | Store original scanned copies of media fill simulation and sterility test records to meet data retention requirements |
FILE_TOKEN_KEY | Configure a key linked to the enterprise IAM system | Ensure upload and download permissions for process documents and exception reports are only available to authorized production personnel |
Three common mistakes
- Skipping directly to FastGPT v4.17.0 during upgrade will cause indexes of legacy process documents to fail to search normally. Failing to follow version iteration compatible upgrade steps and skipping intermediate version database structure migrations will cause historical data to fail correct parsing.
MONGODB_URIconnection failures occur when deploying on the openEuler arm64 system. Not using an arm64-optimized MongoDB image will cause incompatibility between the database driver and system architecture, preventing a valid connection from being established.- A 403 status code is returned when calling the interface to create a text collection. Failing to correctly configure
FILE_TOKEN_KEYwill cause document upload permission verification to fail, resulting in blocked interface requests.
How to confirm the configuration is complete
- Run a database connectivity test script to verify the connection status of
MONGODB_URIandREDIS_URL, and confirm that the concurrent connection count does not exceed theDB_MAX_LINKconfiguration value. - Upload a scanned copy of a media fill simulation record to verify that
STORAGE_S3_ENDPOINTstorage and reading functions work normally, and that the file can be previewed correctly. - Initiate a real-time cleanroom monitoring data retrieval request to confirm that returned result latency meets the preset threshold, with no timeout errors.
- Call the specified interface to create a text collection, verify that the returned result includes a valid document ID, and that no permission-related error messages are present.
The values provided here are common starting points and should be evaluated against the reader's own samples.