Which actions are required to complete a dynamic configuration in Historian?

Dynamic configuration in the AVEVA Historian allows users to make changes to the system settings or configuration while the server is running, without requiring a restart. The key actions required to complete a dynamic configuration involve committing changes and modifying objects in the Runtime database.

Committing the changes to the system is essential because it ensures that any alterations made are saved and effectively implemented in the current configuration. Modifying objects in the Runtime database is also necessary since these objects represent the configuration parameters and data structures that govern how the Historian operates, and any adjustments made here directly impact the server's performance and data management.

By using both of these actions—modifying the Runtime database and committing the changes—you ensure that the updated configuration is active and functioning as intended, which is the essence of dynamic configuration. This allows users to adapt to operational needs and system changes efficiently without any service interruptions, which is crucial in environments where uptime is vital.