EXAMPLES

• Summary
• PingPong
• Tutorial
• HelloWorld
• WaitSet
• Listener
• ContentFilteredTopic
• QueryCondition
• Lifecycle
• Durability
• Ownership
• BuiltInTopics
• NetworkPartitions
• RoundTrip
• Throughput
• Security

QueryCondition

• Running of examples

1) Description

The QueryCondition example is used to illustrate message filtering through use of Queries.

2) Design

It consists of 2 units :

• QueryConditionDataPublisher application generates stock quotes for two ticker symbols, GE and MSFT.
• QueryConditionDataSubscriber filters events through use of Queries.

Configurable:

• symbol: the ticker to subscribe to

symbol allows the selection of the ticker to be subscribed to:

• GE : a ticker for General Electric
• MSFT : a ticker for Microsoft

3) Scenario

The QueryConditionDataPublisher application generates stock quotes for two ticker symbols, GE and MSFT.

In order to subscribe to a particular ticker, the subscriber application QueryConditionDataSubscriber should be run with GE or MSFT as command line arguments.

Usage:

QueryConditionDataPublisher usage:
      QueryConditionDataPublisher
    

QueryConditionDataSubscriber usage:
      QueryConditionDataSubscriber [symbol]
    

Running of examples

• Running examples in Posix
• Running examples in Visual Studio

Running the examples in a Posix environment

Environment Setup

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.

• C Examples
• Java5 examples
• ISO C++ 2 examples

C Executables

Building the examples is described on the Summary page

Two executables are generated in the bin directory when the example is built:

For C

• c_QueryCondition_pub
• c_QueryCondition_sub

Java5 executables

Building the examples is described on the Summary page

Two jars are generated in the java5 directory when the example is built:

For Java5

• sub/java5_QueryCondition_sub.jar
• pub/java5_QueryCondition_pub.jar

ISO C++ 2 Executables

Building the examples is described on the Summary page

Two executables are generated in the bin directory when the example is built:

• isocpp2_QueryCond_pub
• isocpp2_QueryCond_sub

Running the example

Ensure that the environment for OpenSplice is set up correctly as described above for each new terminal used.

It is recommended that you run the subscriber and publisher in separate terminals to avoid mixing the output

Running in single process (heap memory) configuration : the application starts OpenSplice middleware

• OpenSplice is deployed in this mode by default.
• The OpenSplice daemon should not be started manually. Instead the OpenSplice middleware and optional services are implicitly started by the single process applications as required
• Open 2 terminals. Set up the environment and go to the example directory as described above

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.

• Open 2 terminals. In each terminal:
• Setup the environment and go to the example directory as described above
• Set the required configuraton file e.g. OSPL_URI=file://$OSPL_HOME/etc/config/ospl_shmem_ddsi.xml
• Start the OpenSplice daemon. You can do this by typing ospl start

Starting the subscriber and publisher

• In the first terminal start the subscriber by running either
  • c_QueryCondition_sub GE (or MSFT) for C
  • java -jar sub/java5_QueryCondition_sub.jar GE (or MSFT) for Java5
  • isocpp2_QueryCond_sub GE (or MSFT) for ISO C++ 2
• In the second terminal start the publisher by running either
  • c_QueryCondition_pub for C
  • java -jar pub/java5_QueryCondition_pub.jar for Java
  • isocpp2_QueryCond_pub for ISO C++ 2

Running C/C#/ISO C++ 2/Java5 examples on Windows

Environment Setup

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.

• C/C# Examples
• Java5 examples
• ISO C++ 2 examples

C/C# Executables

Building the examples is described on the Summary page

Two executables are generated in the bin directory when the example is built:

For C

• c_QueryCondition_sub.exe
• c_QueryCondition_pub.exe

For C#

• QueryConditionSubscriber.exe
• QueryConditionPublisher.exe

Java5 Executables

Building the examples is described on the Summary page

Two jars are generated in the java5 directory when the example is built:

For Java5

• sub/java5_QueryCondition_sub.jar
• pub/java5_QueryCondition_pub.jar

ISO C++ 2 Executables

Building the examples is described on the Summary page

Two executables are generated in the isocpp2 directory when the example is built:

• isocpp2_QueryCond_pub.exe
• isocpp2_QueryCond_sub.exe

Running the C/C#/ISO C++ 2/Java5 Examples

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

• OpenSplice is deployed in this mode by default.
• The OpenSplice daemon should not be started manually. Instead the OpenSplice middleware and optional services are implicitly started by the single process applications as required
• Open 2 OpenSplice Command Prompts and go to the example directory as described above

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.

• Open 2 OpenSplice Command Prompts. In each window:
• Go to the example directory as described above
• Set the required configuration file e.g. set OSPL_URI=file://%OSPL_HOME%\etc\config\ospl_shmem_ddsi.xml
• Start the OpenSplice daemon. You can do this by typing ospl start

Starting the subscriber and publisher

• In the first terminal start the subscriber by running either
  • c_QueryCondition_sub GE (or MSFT) for C
  • QueryConditionSubscriber GE (or MSFT) for C#
  • java -jar sub/java5_QueryCondition_sub.jar GE (or MSFT) for Java5
  • isocpp2_QueryCond_sub GE (or MSFT) for ISO C++ 2
• In the second terminal start the publisher by running either
  • c_QueryCondition_pub for C
  • QueryConditionPublisher for C#
  • java -jar pub/java5_QueryCondition_pub.jar for Java5
  • isocpp2_QueryCond_pub for ISO C++ 2