---

Run a FESA3 class on the Blade center

---

The Blade Center environment (asl720,asl721,asl722,asl723 and asl724) primary should be used to develop FESA3 classes. Anyhow it is as well possible (and maybe useful) to run FESA3 classes there within some restrictions:

• It is not possible to use RT-Priorities, instead NICE-scheduling is used. This could have a strong impact on your class behaviour!!
• Since normal user do not have root-rights on the Blade-Center, possibly some operations of your class cannot be performed.
• It is not possible to connect any additional Hardware to the Blade-Center!

Deliver FESA3 equipment

• It is not possibility to deliver FESA3 equipment to the Bladecenter

Run FESA3 equipment

1. Go to the folder of your instantiation document
2. # cd [YourWorkspace]/[FESA3ProjectName]/[Classname]/[Version]/src/Test/[asl7XX]/
3. If you want to connect to your equipment, using RDA client software, you need to load the FESA3 environment by executing:
4. # . /common/fesa/[Version]/fesa-environment-gsi/[Version]/fesa3_environmentBladeCenter.conf
5. Run the DeployUnit-binary from there
6. # ../[DeployUnitName]/[binaryFile]

   ---

Run a FESA3 class on any productive or test-FEC

---

A developer can deploy his FESA3 equipment on a testing or productive FEC. For testing several test-!FEC's are available. Here you can take a look on a list of all available front-ends

Deliver FESA3 equipment

Since the concept of DeployUnit project does not yet work, here a quick hack to allow class + deploy Unit delivery:

• compile your class and your deployUnit (The temporary one in the Test-folder)
• execute this script in the "Test" directory of your class. As parameter you have to pass the Name of the DeployUnit you want to deliver.
• The script will:
  • Deliver the instantiation files of this class to each defined FEC
  • Deliver the test-deploymentUnit, which is has to be passed as paramete, for a specified architecture ( as well passed as parameter)
  • Generate a start-script for each FEC
  • Copy the class library to the class delivery directory

The procedure later:

• Define a DeployUnit project and create a DeployUnit in which you specify all relevant FESA3 classes.
• Create the necesarry source code and compile the deploy Unit
• Add your class and your DeployUnit to the Fesa-GSI SVN repository
• Press the "deliver" button in the FESA3-eclipse plugin while you are on the DeployUnit document to deliver the equipment binary file and create a startup-script
• Press the "deliver" button in the FESA3-eclipse plugin while you are on the class design of each involved FESA3 class, to deliver all instantiation files

Run FESA3 equipment

1. Enter the FEC as root, using a SSH client (the password has to be requested by the FESA-team)
2. Go to the folder of your startup-script
3. # cd /opt/fesa/local/scripts/[test or prod]/
4. Start your Equipment (FESA3 environment to connect to the equipment via RDA client software is loaded automatically)
5. # ./[Equipmentname]