Should we use system or user-maintained MQTs? What does it take to implement a complete system of MQT maintenance, encompassing complete refresh, incremental and recasting processes and utility scripts that are robust, maintainable and restartable? Such processes must be designed with operability in mind, i.e. they must have predictable and reasonable run times, must allow monitoring, provide regular progress status, must be idempotent and restartable, and must be adaptable for special fixes and manual corrections.
Script Generation and Automation is a requirement for large environments. A simple scheme based on templates and Unix scripting to auto-generate all the code needed to support a robust sophisticated aggregation strategy.