text: QAnywhere client applications manage the receiving and sending of QAnywhere messages. The applications can be written using one of several QAnywhere APIs:
  QAnywhere .NET API
  QAnywhere C++ API
  QAnywhere Java API
  QAnywhere SQL API
  You can use a combination of client types in your QAnywhere system. For example, messages that are generated using QAnywhere SQL can also be received by a client created using the APIs for .NET, C++, or Java. If you have configured a JMS connector on your server, the messages can also be received by JMS clients. Similarly, QAnywhere SQL can be used to receive messages that were generated by QAnywhere .NET, C++, Java, or JMS clients.
  The QAnywhere .NET API is a programming interface for deployment to Windows computers using the Microsoft .NET Framework and to handheld devices running the Microsoft .NET Compact Framework. The QAnywhere .NET API is provided as the iAnywhere.QAnywhere.Client namespace.
  QAnywhere supports Microsoft Visual Studio .NET 2003 and 2005.
  Versions of the TestMessage sample application are written in Java, C#, and Visual Basic.NET. There is also a .NET compact framework sample.
  For more information about the .NET version of the TestMessage sample application, see Lesson 4: Explore the TestMessage client source code.
  See iAnywhere.QAnywhere.Client namespace (.NET 1.0).
  The QAnywhere C++ API supports Microsoft Visual C++ 6.0, Microsoft Visual Studio .NET 2003, Microsoft eMbedded Visual C++ 3.0, Microsoft eMbedded Visual C++ 4.0, and Visual Studio 2005.
  The QAnywhere C++ API consists of the following files:
  A set of header files (the main one being qa.hpp) located in the QAnywhere\h subdirectory of your SQL Anywhere installation.
  An import library (qany10.lib) located in the ce\arm.30\lib, ce\arm.50\lib, QAnywhere\lib, and ce\x86.30\lib subdirectories of your SQL Anywhere installation.
  A run-time DLL (qany10.dll) located in the win32, ce\arm.30, ce\arm.50\lib, and ce\x86.30 subdirectories of your SQL Anywhere installation.
  Your source code file must include the header file in order to access the API. The import library is used to link your application to the run-time DLL. The run-time DLL must be deployed with your application.
  A version of the TestMessage sample application written in C++ is supplied in samples-dir\QAnywhere\Desktop\MFC. (For information about samples-dir, see Samples directory.)
  See QAnywhere C++ API Reference.
  The QAnywhere Java API supports JRE 1.4.2 and 1.5.0.
  The QAnywhere Java API consists of the following files:
  API reference material, available in this book or in Javadoc format in the docs\en\javadocs\QAnywhere subdirectory of your SQL Anywhere 10 installation.
  Runtime DLLs (qany10jni.dll and qany10.dll), located in the win32 subdirectory of your SQL Anywhere 10 installation.
  An archive of the class files (qaclient.jar), located in the java subdirectory of your SQL Anywhere 10 installation.
  The class file archive must be included in your path when you compile your application. The run-time DLLs must be deployed with your application.
  A version of the TestMessage sample application written in Java is supplied in samples-dir\QAnywhere\Java\. (For information about samples-dir, see Samples directory.)
  See QAnywhere Java API Reference.
  The QAnywhere SQL API is a set of stored procedures that implement a messaging API in SQL. Using the QAnywhere SQL API, you can create messages, set or get message properties and content, send and receive messages, trigger message synchronization, and set and get message store properties.
  See QAnywhere SQL API Reference.
  QAnywhere includes a JMS connector that provides connectivity between QAnywhere and JMS applications. See:
  QAnywhere includes a mobile web services connector for messaging between QAnywhere and web services.
  See Mobile Web Services.