HI
I have some binaries which are using RTI but they are located in differrent location but in the same machine. For communication we need USER_QOS_PROFILES.xml where we override some default QOS. But the expectation is this file should be present in the same directory from where we are launching the bienaries. As in our case its distrubuted in diferrent folders we need to create a separate copy everywhere. Is there any way to tell RTI to refer USER_QOS_PROFILES.xml from a dedicated location.
there's an environment variable you can use. Use the search bar on this page to look for 'NDDS_QOS_PROFILES', and more info is availabe in the documentation.
..for a stand-alone app which may not be able to expect an environment variable set, I see it's possible to set using a URL. I can find a struct with likely looking members (DDS_ProfileQosPolicy) I cannot fathom from the docs how to use it.
Is there an example?
Hi,
Yes you can use the DDS_ProfileQosPolicy for this. Specifically the string_profile field which is basically a string (actually a sequence of strings).
It is documented here:
https://community.rti.com/static/documentation/connext-dds/5.2.0/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/PROFILE_QosPolicy__DDS_Extension__.htm?Highlight=string_profile
There is a very short example of how this is used here:
https://community.rti.com/static/documentation/connext-dds/5.2.0/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/XML_String_Syntax.htm?Highlight=string_profile
Gerardo
Tried to get the URL version working having copied the example out of the docs - it doesn't work at all. Tells me it can't use the self-same-file I'd just been using and renamed from USER_PROFILE_QOS.xml in a path I know exists (and checked, and changed).
Bizarrely also, there's a nasty interaction with the logging set_output_file - calling "factoryQos.profile.url_profile.from_array" seems to disregard/reset the previously set "set_output_file" and sticks up a black-dialog-of-doom.
DDSDomainParticipantFactory *factory = DDSDomainParticipantFactory::get_instance();
DDS_DomainParticipantFactoryQos factoryQos;
DDS_ReturnCode_t retcode = factory->get_qos(factoryQos);
if (retcode != DDS_RETCODE_OK)
{
qDebug("get_qos fail");
}
const char *url_profiles[] = { "file:///c:/myqos.xml" };
factoryQos.profile.url_profile.from_array(url_profiles, 1);
// factoryQos.profile.ignore_resource_profile = DDS_BOOLEAN_TRUE;
//factoryQos.profile.ignore_environment_profile = DDS_BOOLEAN_TRUE;
//factoryQos.profile.ignore_resource_profile = DDS_BOOLEAN_TRUE;
factory->set_qos(factoryQos);
I believe that it doesn't mean same file, I think it means same symbols. It's a symbol table that is created, and it is loading USER_QOS_PROFILES.xml on boot, and then you are trying to load the same file (with all the same symbols) again.
What happens if you create a simple myqos.xml that has no name conflicts with the default USER_QOS_PROFILES.xml file?