Migration from previous FESA3 versions

FESA3 4.0.0 4.2.0

Basic migration steps

To migrate existing FESA software from the previous FESA3 version 4.0.0 to the latest version FESA3 4.2.0 perform the following steps:

• Open the FESA class design
  • Press 'Update FESA Version'
  • Press 'Synchronize Source Code'
• Open the FESA deploy-unit
  • Press 'Update FESA Version'
  • Press 'Synchronize Source Code'
• Open the FESA instantiation document
  • Press 'Update FESA Version' if required
  • Press 'Promote Instances'

Detailed information

• 'Update FESA Version' will increase the FESA version number of classes and deploy-units, copy your file to *.backup and then run a python script to automatically modify the XML design if required. Please check the Eclipse console output for details.
• 'Synchronize Source Code' will update the generated C++ code and the XML design of the deploy-unit and/or instantiation file according to the changes in the current XML design.
• 'Promote Instances' will modify the FESA instantiation file if required according to the updated XML schema.

The following issues are automatically performed by the migration tool:

• class design: the responsible name of the beam diagnostics department will be updated to the result of the latest decisions
• instance file: switches the position of accelerator and timing domain element

FEC

• Adaption of links in /common/export/nfsinit/<FEC>

FESA Version	Initialization Script	SAFTlib
FESA3 4.0.0	e.g. ln -s ../global/fesa_64bit 30_fesa	e.g. ln -s ../global/timing-rte-R8-balloon_0 20_timing-rte
FESA3 4.2.0	e.g. ln -s ../global/fesa_64bit_dev_environment 30_fesa or e.g. ln -s ../global/fesa_64bit_pro_environment 30_fesa	e.g. ln -s ../global/timing-rte-R8-balloon_0 20_timing-rte

Older FESA versions

If you want to migrate from an older FESA3 version to 4.2.0, please contact FESA support.