Migration from previous FESA3 versions

FESA3 4.3.1 5.0.x

Basic migration steps

To migrate existing FESA software from the previous FESA3 version 4.3.1 to the latest version FESA3 5.0.x perform the following steps in the FESA Eclipse Plug-in:

• 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'

Alternatively take a look at the FESA3 command line tool and the script templates.

Detailed information

• 'Update FESA Version' will increase the FESA version number of classes and deploy-units, copy your design 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.

FEC

• Adaption of links in /common/export/nfsinit/<FEC> depending on environment, e.g.

FESA Version	Initialization Script	SAFTlib
FESA3 4.3.1	e.g. ln -s ../global/fesa_64bit_dev_environment 30_fesa or ln -s ../global/fesa_64bit_pro_environment 30_fesa	e.g. ln -s ../global/timing-rte-tg-doomsday-v4.0.4 20_timing-rte
FESA3 5.0.1	e.g. ln -s ../global/fesa_64bit_dev_environment 30_fesa or ln -s ../global/fesa_64bit_pro_environment 30_fesa	e.g. ln -s ../global/timing-rte-tg-doomsday-v4.0.4 20_timing-rte

Older FESA versions

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

---

Structural Changes

FESA Class Designs

• Removal of element //equipment-model/information/repository-path

FESA Deploy-Unit Designs

• Removal of element //deploy-unit/repository-path

• Removal of element //deploy-unit/build-time

FESA Instance Files

• New: optional attribute in // instantiation-unit/classes/<class-name>/events-mapping/<event-name>/event-configuration/Timing/hardware-event: @beam-in .