<?xml version="1.0"?>
<!-- 
Description
XML QoS Profile for centurion

The QoS configuration of the DDS entities in the generated example is loaded 
from this file.

This file is used only when it is in the current working directory or when the
environment variable NDDS_QOS_PROFILES is defined and points to this file.

The profile in this file inherits from the builtin QoS profile 
BuiltinQosLib::Generic.StrictReliable. That profile, along with all of the 
other built-in QoS profiles can be found in the 
BuiltinProfiles.documentationONLY.xml file located in the 
$NDDSHOME/resource/xml/ directory.

You may use any of these QoS configurations in your application simply by 
referring to them by the name shown in the 
BuiltinProfiles.documentationONLY.xml file and listed below: 

* In library "BuiltinQosLib":
** Baseline
** Baseline.5.0.0
** Baseline.5.1.0
** Baseline.5.2.0
** Generic.Common
** Generic.510TransportCompatibility
** Generic.Monitoring.Common
** Generic.ConnextMicroCompatibility
** Generic.OtherDDSVendorCompatibility

* In library "BuiltinQosLibExp":
** Generic.StrictReliable
** Generic.KeepLastReliable
** Generic.BestEffort
** Generic.StrictReliable.HighThroughput
** Generic.StrictReliable.LowLatency
** Generic.Participant.LargeData
** Generic.Participant.LargeData.Monitoring
** Generic.StrictReliable.LargeData
** Generic.KeepLastReliable.LargeData
** Generic.StrictReliable.LargeData.FastFlow
** Generic.StrictReliable.LargeData.MediumFlow
** Generic.StrictReliable.LargeData.SlowFlow
** Generic.KeepLastReliable.LargeData.FastFlow
** Generic.KeepLastReliable.LargeData.MediumFlow
** Generic.KeepLastReliable.LargeData.SlowFlow
** Generic.KeepLastReliable.TransientLocal
** Generic.KeepLastReliable.Transient
** Generic.KeepLastReliable.Persistent
** Generic.AutoTuning
** Pattern.PeriodicData
** Pattern.Streaming
** Pattern.ReliableStreaming
** Pattern.Event
** Pattern.AlarmEvent
** Pattern.Status
** Pattern.AlarmStatus
** Pattern.LastValueCache

You should not edit the file BuiltinProfiles.documentationONLY.xml directly.
However, if you wish to modify any of the values in a built-in profile, the
recommendation is to create a profile of your own and inherit from the built-in
profile you wish to modify. The NDDS_QOS_PROFILES.example.xml file (contained in 
the same directory as the BuiltinProfiles.documentationONLY.xml file) shows how
to inherit from the built-in profiles. 

For more information about XML QoS Profiles see Chapter 17 in the 
RTI Connext user manual.
-->
<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:noNamespaceSchemaLocation="C:/Program Files/rti_connext_dds-6.0.1/resource/schema/rti_dds_qos_profiles.xsd"
     version="6.0.1">
    <!-- QoS Library containing the QoS profile used in the generated example.

        A QoS library is a named set of QoS profiles.
    -->
    <qos_library name="test_library">

        <!-- QoS profile used to configure reliable communication between the DataWriter 
             and DataReader created in the example code.

             A QoS profile groups a set of related QoS.
        -->
        <qos_profile name="test_profile" base_name="BuiltinQosLibExp::Generic.StrictReliable" is_default_qos="true">
            <!-- QoS used to configure the data writer created in the example code -->                
            <datawriter_qos>
                <publication_name>
                    <name>TestDataWriter</name>
                </publication_name>
            </datawriter_qos>

            <!-- QoS used to configure the data reader created in the example code -->                
            <datareader_qos>
                <subscription_name>
                    <name>TestDataReader</name>
                </subscription_name>
            </datareader_qos>
            <participant_qos>

              <property>
                <value>
                  <element>
                    <name>dds.license.license_file</name>
                    <value>C:\Program Files\rti_connext_dds-6.0.1\rti_license.dat</value>
                  </element>
                  <element>
                    <name>rti.monitor.library</name>
                    <value>rtimonitoring</value>
                  </element>
                  <element>
                    <name>rti.monitor.create_function</name>
                    <value>RTIDefaultMonitor_create</value>
                  </element>
                </value>
              </property>
                <!--
                The participant name, if it is set, will be displayed in the
                RTI tools, making it easier for you to tell one
                application from another when you're debugging.
                -->
                <participant_name>
                    <name>TestParticipant</name>
                    <role_name>TestParticipantRole</role_name>
                </participant_name>

            </participant_qos>
        </qos_profile>

    </qos_library>


  <qos_library name="secure_test_library">

    <!-- Default QoS:

             This profile contains the QoS that applications would use by
             default. We can use it as a base profile to inherit from and
             override some parameters.
         -->
    <qos_profile name="secure_test_profile" base_name="BuiltinQosLib::Generic.Security" is_default_qos="true">
      <!-- QoS used to configure the data writer created in the example code -->
      <datawriter_qos>
        <publication_name>
          <name>TestDataWriter</name>
        </publication_name>
      </datawriter_qos>

      <!-- QoS used to configure the data reader created in the example code -->
      <datareader_qos>
        <subscription_name>
          <name>TestDataReader</name>
        </subscription_name>
      </datareader_qos>

      <participant_qos>
        <property>
          <value>
            <element>
              <name>dds.license.license_file</name>
              <value>C:\Program Files\rti_connext_dds-6.0.1\rti_license.dat</value>
            </element>
            <element>
              <name>rti.monitor.library</name>
              <value>rtimonitoring</value>
            </element>
            <element>
              <name>rti.monitor.create_function</name>
              <value>RTIDefaultMonitor_create</value>
            </element>
            <element>
              <name>com.rti.serv.secure.authentication.ca_file</name>
              <value>Security/Cert/CA/ca_cert.pem</value>
            </element>
            <element>
              <name>com.rti.serv.secure.authentication.certificate_file</name>
              <value>Security/Cert/Identity/testclient_cert.pem</value>
            </element>
            <element>
              <name>com.rti.serv.secure.authentication.private_key_file</name>
              <value>Security/Cert/Identity/Private/testclient_key.pem</value>
            </element>
            <element>
              <name>com.rti.serv.secure.access_control.permissions_authority_file</name>
              <value>Security/Cert/CA/ca_cert.pem</value>
            </element>
            <element>
              <name>com.rti.serv.secure.access_control.governance_file</name>
              <value>Security/Xml/signed_governance.p7s</value>
            </element>
            <element>
              <name>com.rti.serv.secure.access_control.permissions_file</name>
              <value>Security/Xml/signed_permissions.p7s</value>
            </element>
          </value>
        </property>

        <participant_name>
          <name>TestParticipant</name>
          <role_name>TestParticipantRole</role_name>
        </participant_name>

      </participant_qos>
    </qos_profile>
  </qos_library>
</dds>