The BuiltInTopics example is used to illustrate the use of built-in topics. This application monitors the number of nodes that participate in a DDS domain.
It consists of 3 units :
When it receives the built-in sample, the subscriber displays the number of nodes running and the host name of each node .
Let's call OpenSplice_install_dir the OpenSplice installation directory.
The OpenSplice environment variables must be set in order for the examples to build/run correctly. To do this, open a terminal and source the "OpenSplice_install_dir/release.com" script supplied with the distribution.
Building the examples is described on the Summary page>
One executable is generated in the bin directory when the example is built:
For C
Building the examples is described on the Summary page
One jar is generated in the java5 directory when the example is built:
For java5
Building the examples is described on the Summary page
One executable is generated in the bin directory when the example is built:
Ensure that the environment for OpenSplice is set up correctly as described above for each new terminal used.
Running in single process (heap memory) configuration : the application starts OpenSplice middleware
Running in multiple process shared memory configuration
To enable deployment in this mode, an OpenSplice configuration file must be selected that has shared memory support e.g. one of the ospl_shmem xml configuration files found in the OpenSplice_install_dir/etc/config directory.
Starting the subscriber
Let's call OpenSplice_install_dir the OpenSplice installation directory.
The OpenSplice environment variables must be set in order for the examples to run correctly. To do this open an OpenSplice Command Prompt which will set up the environment variables for OpenSplice automatically. The OpenSplice Command Prompt can be selected from the launcher. Alternatively, open a windows Command Prompt and execute the "OpenSplice_install_dir\release.bat" batch script supplied with the distribution.
Building the examples is described on the Summary page
One executable is generated in the bin directory when the example is built:
For C
For C#
Building the examples is described on the Summary page
One jar is generated in the java5 directory when the example is built:
For java5
Building the examples is described on the Summary page
One executable is generated in the bin directory when the example is built:
Ensure that the environment for OpenSplice is set up correctly as described above for each new command prompt used.
The following steps describe how to run the examples:
Running in single process (heap memory) configuration : the application starts OpenSplice middleware
Running in multiple process shared memory configuration
To enable deployment in this mode, an OpenSplice configuration file must be selected that has shared memory support e.g. one of the ospl_shmem xml configuration files found in the OpenSplice_install_dir\etc\config directory.
Starting the subscriber