How to make web integration service as DDS publisher

Hi Yanyang,

From what I understand, you want Web Integration Service to behave as a DDS Publisher application. That is, you want to Web Integration Service to publish over DDS information that you pass to it via POST HTTP requests.

To do that, you have to add to your Web Integration Service application (under the appropriate <applications>tag) a DataWriter of the corresponding DDS Topic. For example:

<application name="ExampleApplication">
    <domain_participant name="MyParticipant" domain_id="0">
        <register_type name="HelloWorldType" type_ref="HelloWorld"/>
        <topic name="HelloWorldTopic" register_type_ref="HelloWorldType"/>
        <publisher name="MyPublisher">
            <data_writer name="HelloWorldWriter"
                    topic_ref="HelloWorldTopic"/>
        </publisher>
    </domain_participant>
</application>

This would create a DataWriter for HelloWorldTopic, which will be instantiated upon the execution of:

 $ rtiwebintegrationservice -cfgName ExampleApplication

Then you can write and send DDS data through Web Integration Service by doing a POST on the URL corresponding to the HelloWorldWriter DataWriter:

POST /dds/rest1/applications/ExampleApplication/domain_participants/MyParticipant/publishers/MyPublisher/data_writers/HelloWorldWriter HTTP/1.1
Host: <host>[:<port>]
Content-Type: application/dds-web+xml
Content-Length: 101
Cache-Control: no-cache

<data>
    <sender>Fernando</sender>
    <message>Hello World!</message>
    <count>0</count>
</data>

You will find more information on how to send and receive data, please refer to the Tutorials section of the RTI Web Integration Service User's Manual.

Is this the solution you were looking for?

Thanks,
Fernando.

Hi Yanyang,

I understand. So you want to integrate the information you're publishing using Web Integration Service (as a result of a POST operation from a non-DDS application) into a larger DDS system where you have Database Integration Service running.

Database Integration Service can directly ingest the information that is sent by Web Integration Service. All you need is to configure Database Integration Service to subscribe to the DDS Topic or Topics you are publishing from Web Integration Service. To do that, you will need to configure a subscription in Database Integration Service as follows:

<types>
     <!-- Types you defined for Web Integration Service -->
</types>
<!-- ... -->

<postgresql_connection>
    <!-- ... -->
    <subscriptions>
        <subscription>
            <table_owner>MyUser</table_owner>
            <table_name>Mytable</table_name>
            <domain_id>0</domain_id>
            <topic_name>HelloWorldType</topic_name>
            <type_name>HelloWorldTopic</type_name>
        </subscription>
    </subscriptions>
</postgresql_connection>

Where:

• table_owner and  table_name configure the table where the information will be stored.
• domain_id points to the DDS Domain where Web Integration Service is publishing the information.
• topic_name is the name of the Topic Web Integration Service is publishing (the name of the Topic the DataWriter writes).
• type_name is the name under which the Type associated with the Topic Web Integration Service is publishing was registered.

However, if want other applications to subscribe to the data sent by Web integration Service; that is, other DDS applications that are not Database Integration Service. You can, as you mentioned create static DDS applications using the type definitions you used in Web Integration Service. You can simply pass the Web Integration Service types to rtiddsgen in XML format (creating a file with just the  <types> part or passing the whole configuration file) and it will generate code for those types -- you don't need to transform the information to IDL because rtiddsgen can already process XML.

Also, if you want to do manual tests as you mentioned, you can use rtiddsspy or RTI Admin Console for Data  Visualization. However, note that if your types (i.e., larger than the default maximum type serialized size setting, which in the case of rtiddsspy is 4096 bytes), you will need to increase the maximum type object serialized size setting as follows:

rtiddsspy -domainId <domainId> -tcMaxSize <SIZE> -printSample

Please, let me know if this helps.

Thanks!
Fernando.