#### 7.5.3 `RTCosScheduling::ServerScheduler`

Server side POAs and objects are defined in a configuration file that can be loaded using `RTCosScheduling.ClientScheduler.Impl.Load_Configuration_File`

On the server side, the user can set up

- object priority, using registered `PriorityMapping` object.
- all RT-CORBA-specific POA configuration parameters.

This file has the following syntax, derived from PolyORB configuration file syntax:

    # Name of the object
    [object object1]

    # Object priority, in RTCORBA.Priority'Range
    priority=10000

In this example, object `object1` is defined with priority `10'000`.

    # Name of the POA
    [poa poa1]

    # PriorityModelPolicy for POA
    priority_model=CLIENT_PROPAGATED
    default_priority=0 # not meaningful for CLIENT_PROPAGATED

    # Threadpools attached to POA
    threadpool_id=1

    # Name of the POA
    [poa poa2]

    # PriorityModelPolicy for POA
    priority_model=SERVER_DECLARED
    default_priority=40

    # Threadpools attached to POA
    threadpool_id=2

    # Name of the POA
    [poa poa3]

    # POA with no defined policies

In this example, Two POAs are defined: POA `poa1` will use the `CLIENT_PROPAGATED` PriorityModel Policy, default value is not meaningful for this configuration, `poa1` will use the Threadpool #1; POA `poa2` will use the `SERVER_DECLARED` PriorityModel Policy, default server priority is 40, `poa2` will use the Threadpool #2. Note that both policies are optional and can be omitted.