Customising the RTC Supervisor

A number of user extension points are foreseen in the RtcSupervisor which are not yet supported, these include user functions to be invoked when:

  • An error is identified, i.e. the InError method is called

  • A mode is set using the SetMode interface.

  • A Run command is to be implemented to run a particular RTC pipeline.

In addition a mechanism will be provided to add additional command interfaces for application specific commands.

Note

For simplicity reasons, the example uses the file based implementation of OLDB, Persistent and Runtime Configuration Repositories; as well as file based service discovery. This means that the underlying format of configuration and data points is different than the one used when the above mentioned services are used with the standard back-ends such as CII configuration service, CII OLDB, etc.

Configuration of the RtcSupervisor

There are currently only two things which can be configured

  • The list of components to be supervised.

  • Whether the state transitions should be done in series or parallel.

See the Configuration section of the RtcSupervisor manual for details of how to configure these behaviours.

Running RtcSupervisor

Examples of how the RtcSupervisor can be started, configured and used can be found in the end to end example Putting Everything Together for a Minimalistic SRTC System.