Add a migration tool page (MGNLMIGRATION-166)

[MGNLMIGRATION-168] migration tool page: a button to run or re-run migration of template scripts Created: 08/Nov/12  Updated: 10/Feb/14  Resolved: 07/Feb/14

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.8

Type: Sub-task Priority: Major
Reporter: Philipp Bärfuss Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLMIGRATION-285 Make possible the migration of FTLs/J... Closed
duplicate
duplicates MGNLMIGRATION-45 Migration processes must be re-runnab... Closed
Template:

 Description   

It is cumbersome (and tacky) to re-trigger the updating code by changing the version in the configuration tree followed by a restart.
After migration of template scripts, some new areas can be found and these must be added to module configuration.
Previously, the only way to verify the result was putting the generated Delta tasks (MGNLMIGRATION-164) to VersionHandler of module and restarting the instance.

This is no longer the case though, because the configuration is updated right away and user
copies the Delta tasks only after he finds that migration was successful.

The process:

  1. backup the snapshot of the old configuration and templates
  2. trigger the migration
  3. restore the original from backup or export migrated modules' bootstraps.

Generated at Mon Feb 12 10:17:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.