Platform and dependencies
Oracle database
- Database platform
- Beehive is available exclusively for Oracle Enterprise Database. Confirm the currently approved Oracle version, edition and required options with FRAMETEXX before planning a new environment.
FLink and DataBridge
- Product dependency
- Beehive is an additional module that builds on relational data provided by DataBridge. DataBridge in turn extends the FLink Integration Platform.
- Workflow runtime
- Configure the Beehive processor in FLink Designer, deploy the workflow, and execute and control it through FLink Service.
Database architecture
Three processing areas
- IMP
- Imports DataBridge snapshots and enriches them with company code and bank day.
- STG
- Compares the current bank day with the previous one and determines changed data.
- GDP
- Stores historized records with from/to validity dates as the operational data store.
Oracle processing
- Generated objects
- Configuration-specific tables, sequences and PL/SQL packages implement loading, delta detection, validity calculation and logging.
- Parallel execution
- Oracle Scheduler Jobs provide configurable parallel processing within each stage.
- Storage options
- Compression can reduce storage consumption. Oracle partitioning can support performance and maintenance of large historized GDP tables when the selected Oracle edition and licensing permit it.
Deployment and operations
Generated deployment
FLink deployment creates a Beehive installation script for the Oracle database. It installs or updates the required packages, IMP/STG/GDP tables, GDP sequences and DataBridge snapshot templates. Configuration changes to existing modules, tables or fields can require a planned data migration.
Monitoring
FLink Monitoring exposes Beehive cycles, bank days, processing status and logs. Operators can start, stop and restart cycles, inspect application progress and perform controlled recovery actions.
Capacity planning
As an initial planning baseline, allow at least 4 vCPU and 16 GB RAM for Beehive. Final sizing must account for snapshot volume, daily changes, history retention, indexes, parallel processing, staging copies and migration workspace. Validate the design with representative production volumes.