Both FEP and ADTF come with their own property system. FEP Properties describe a participant from the perspective of the FEP system. ADTF Properties configure a filter graph, so not all ADTF properties are also of interest to other participants in the FEP System.
So it is possible to instantiate the ADTF participant multiple times in an FEP system with different parameterization but with the same ADTF Session. This increases the reusability of an ADTF Session.
To synchronize these two property systems, ADTF provides the
FEP Property Sync Service. This service publishes all properties of the top level Filter Graph into the FEP System.
All you have to do is add
FEP Property Sync Service and link the property do you want to appear on the Fep System into the Filter Graph:
How to create FEP Property in FilterGraphList the FEP Properties of your ADTF Participant
> ./adtf_control -u fep://default_adtf_system -e fep::getprops default_session ... /rti_dds_simulation_bus : /rti_dds_simulation_bus/participant_domain : 5 /adtf : /adtf/fep_property_filename :
How to configure a howl FEP System with the FEP Meta Model
Require more details ? The next will show you how deep the rabbit hole goes.