FESA Database

To store FESA designs in the FESA3 database a variety of ideas exist on how to improve the procedure.

A FESA design can be exported

• during the release procedure or
• on demand

In all cases certain restrictions have to be met. A FESA design must meet these restrictions so it can be imported into the database.

The API changes in a FESA design to the database are currently handled by the version (format: Major.minor.tiny) in the FESA designs. The version is adapted manually by the FESA developers in the FESA designs. Otherwise it is not possible (yet) to decide whether something in the FESA design or the underlying software has changed compared to what is already stored in the database.
The LSA database retrieves device information from the FESA database for devices. For updates in the LSA database the maintainers request at least a minor version change. Then the maintainers can trigger the import procedure.

For a FESA developer the LSA database restrictions are invisible. The rules to decide which FESA design change must lead to increasing which part of the version are not fixed yet. Therefore it would help to see which version is already in the LSA database.

TBD

FESA Design Export Implementation

At the moment each FESA design is exported to the database one by one. If Subsets of FESA designs are available each subset design is generated and exported to the FESA database one by one. The config-db-client-library is used in all cases.

The export of multiple FESA class designs, FESA deploy-unit designs or FESA instances to the database might help to improve the implementation of the export procedure in the FESA Eclipse Plug-In. This affects the export of

• subsets of FESA class designs
• subsets of FESA deploy-unit designs
• subsets of FESA instances AND
• the export of FESA instances for multiple FECs (independent of subsets)

One could go a step further and think of exporting multiple FESA class designs for several FESA classes to the database at once.

Previous

https://www-acc.gsi.de/wiki/FESA/FESA3DatabaseWorkflow300

https://www-acc.gsi.de/wiki/FESA/FESA3DataBaseIntegration

https://www-acc.gsi.de/wiki/FESA/FESA3RESTInterfaceToFESADB

-- SolveighMatthies - 03 Dec 2020