Overview

The process of running DUW upgrade scripts can be automated. The basic process is for a workflow rule to go through all the DUW scripts in sequence and run each one. This process uses the Archibus Automatic Database Updates table ( afm_autodbupdate ) to determine the current database version and previous scripts that have been applied.

Continuous database updates are useful for:

• Archibus staff use this procedure for Archibus SaaS deployments
• Business Partners can use this process for customers they host.
• Anyone can use this update method, especially if they have a non-custom schema.

Sequence

In general terms, the workflow rule follows this sequence:

1. Determine the current database and scripts that have been run.
2. Start at the folder that is next after the folder for the last successfully-run script. This is indicated in the afm_autodbupdate table (for example, \projects\users\public\dt\24.1.001 ).
3. The rule advances in the list to the folder name that matches the value.
4. The rule advances to the next folder (e.g. \projects\users\public\dt\24.1.002 ).
5. Starting from this folder and for every folder thereafter, the rule executes the update-schema.duw DUW script within each folder (e.g. projects\users\public\dt\24.1.002\database-update.duw ), pausing for one minute between the end of the last script and the beginning of the new one.
6. For each folder name (e.g. projects\users\public\dt\24.1.002 ), the rule:
   • Inserts a new record into th e afm_autodbupdate table. The insert statement includes the date_run and script_folder values, but leaves the success value at its default of No (0).
   • Runs the update-schema.duw script in that folder.
   • If the DUW script succeeds:
     • The rule sets the afm_autodbupdate.success value for this script_folder to 1 (Yes).
     • The rule continues to the next folder in the list.
   • If the DUW script fails:

     • The rule stops and does not process the next DUW script in the next folder folder.

     • If all DUW scripts have succeed, create the empty file \archibus\users\public\dt\database_update_wizard.done . (In this way, an external batch file will know when the script has finished.)

Executing continuous update workflow

In a future release, users will be able to invoke the continuous database update feature. Currently, Archibus staff use this procedure for Archibus SaaS deployments .

Config file

The \WEB-INF\config\autodb-update.properties file stores the run script configuration for Continuous Database Updates workflow.

Workflow

Use cases