3.6. set verb

Passing to the CLI the verb set would include the given value in the selected XML element. The verb is the third argument passed to the CLI (see Usage section). The element is given by a dot-separated string accessing the configuration parameter to be set (see Configuration parameter access section). The set command requires usually at least the value desired for the specified element.

Note

There are exceptions in which the verb set does not need a value, as in the default_profile attribute cases for datareader, datawriter and participant entities.

The snippet below shows different examples:

$ fastddsqosprof file set datareader[dr_profile].qos.durability volatile

$ fastddsqosprof file set datareader[dr_profile].default_profile

$ fastddsqosprof file set datawriter[dw_profile].qos.reliability.duration.max_blocking_time 1 100

$ fastddsqosprof file set participant[p_profile].name "My participant"

$ fastddsqosprof file set participant[p_profile].use_builtin_transports true

$ fastddsqosprof file set participant[p_profile].user_transports[] td_profile

$ fastddsqosprof file set transport_descriptor[td_profile].kind shm

The following XML configuration file represents the result of the consecutive CLI commands run.

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<dds xmlns="http://www.eprosima.com/XMLSchemas/fastRTPS_Profiles">
    <profiles>
        <data_reader is_default_profile="true" profile_name="dr_profile">
            <qos>
                <durability>
                    <kind>VOLATILE</kind>
                </durability>
            </qos>
        </data_reader>
        <data_writer profile_name="dw_profile">
            <qos>
                <reliability>
                    <max_blocking_time>
                        <sec>1</sec>
                        <nanosec>100</nanosec>
                    </max_blocking_time>
                </reliability>
            </qos>
        </data_writer>
        <participant profile_name="p_profile">
            <rtps>
                <name>My participant</name>
                <useBuiltinTransports>true</useBuiltinTransports>
                <userTransports>
                    <transport_id>td_profile</transport_id>
                </userTransports>
            </rtps>
        </participant>
        <transport_descriptors>
            <transport_descriptor>
                <transport_id>td_profile</transport_id>
                <type>SHM</type>
            </transport_descriptor>
        </transport_descriptors>
    </profiles>
</dds>