Routing Service - publish topic to another domain

3 posts / 0 new
Last post
Offline
Last seen: 3 years 11 months ago
Joined: 06/10/2014
Posts: 49
Routing Service - publish topic to another domain

Hi,

I'm tryint to use the Routing Service as a simple way to publish some topics to another domain.  I don't need to make any changes to the topic or data. I just want to republish the same topic on another domain. This is part of my configuration file:

<domain_route name="ManagerToCoordinator">

<participant_1>
  <domain_id>2</domain_id>
</participant_1>

<participant_2>
  <domain_id>3</domain_id>
</participant_2>

<session name="Session1">
  <topic_route name="MyTopicRoute">
    <input participant="1">
      <topic_name>MyTopicName</topic_name>
      <registered_type_name>MyTopicTypeName</registered_type_name>
   </input>
   <output>
      <topic_name>MyTopicName</topic_name>
      <registered_type_name>MyTopicTypeName</registered_type_name>
    </output>
  </topic_route>
</session>

When I set the verbosity to 6, this is some of the output. It looks like the route is found.

ROUTERTopicRoute_startMonitoring: [ManagerToCoordinator::Session1::MyTopicRouteRoute] status publication started
ROUTERSession_startMonitoring: [Session1] status publication started
[ManagerToCoordinator] Domain route STARTED [dds(2) <=> dds(3)]

DL Notice: : [ManagerToCoordinator::Session1::MyTopicRoute] Route matching output stream found (MyTopicName)

Does anyone know what is wrong with this configuration?

Thanks,

Anne Fiore

Organization:
Offline
Last seen: 1 year 2 months ago
Joined: 05/23/2013
Posts: 50

Hi Anne,

The setting looks fine. Have you used the default QoS settings in your publishers and subscribers?

Thanks,
Kyoungho

Offline
Last seen: 3 years 11 months ago
Joined: 06/10/2014
Posts: 49

Yes, that was the problem. I had to set the reader/writer qos in the routing service configuration file to match the end point writers/readers. Thanks!