Data aggregation - migration
Why is the DAM tool changing?
The Data Aggregation Manager (DAM) originally relied on three solution extensions (SXs) that executed direct SQL on the Planon database:
• ContainerSX
• ReportSX
• CalculateSX
Although this worked for on-premise, single-tenant setups, this approach no longer fits modern cloud / Planon-as-a-Platform standards.
There are three main reasons for the change:
1. Platform strategy
Planon is phasing out legacy, non-platform extensions. The DAM SXs belong to this category and are controlled by the improved feature
Disable DAM tool (non-platform) extensions functionality. To keep DAM available after this switch is enabled, the logic behind it must move into standard product code.
2. Stability, security and supportability
Direct SQL in SXs is hard to control and has proven capable of causing serious production issues (performance, locking, even outages). It also opens a “back door” to data that bypasses normal product safeguards and is difficult to test and monitor. By replacing SXs with a productised engine driven by configuration, Planon can:
◦ Validate and control SQL execution centrally.
◦ Test and support DAM consistently across all customers.
◦ Better align aggregations with authorization and platform rules.
3. More flexible configuration
In the SX-based model you effectively had one configuration per aggregation definition (one SX registration per UDBO). The new approach introduces Data aggregation parameters and related BOs, allowing multiple configurations per definition and making DAM behavior configurable in BO records instead of Java code.
The following sections describe the steps you should take when moving from the SX-based Data aggregation to the productized, next generation Data aggregation.