Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.0 » QAnywhere » Creating QAnywhere Applications » Message stores » Client message stores


SQL Anywhere and UltraLite client differences

QAnywhere client applications can now use an UltraLite database as the client message store. This provides a lighter-weight solution for pure messaging applications on mobile devices. By pure messaging applications, we mean applications that use store and forward messaging, but not data synchronization.

Some of the key advantages of UltraLite are:

Keep in mind the following limitations of UltraLite when deciding between SQL Anywhere and UltraLite:

In general, UltraLite should be used rather than SQL Anywhere in all cases where SQL Anywhere is not already present. SQL Anywhere is available for circumstances where you want to add messaging along side an already implemented SQL Anywhere data synchronization solution. However, UltraLite is recommended in all pure messaging environments.

From an application perspective, the client API remains the same for UltraLite as for SQL Anywhere with the following exception: the QAManager configuration properties should include the setting DATABASE_TYPE=UltraLite for UltraLite message stores. If the property DATABASE_TYPE is not set, the default is SQLAnywhere.

The client APIs supported for UltraLite are C# (for Microsoft .NET) and Java. For UltraLite, the C++ and SQL APIs are not supported.

The other difference from an application perspective is that the QAnywhere Agent for UltraLite is qauagent.exe. The QAnywhere Agent for UltraLite supports many of the same options as the QAnywhere Agent, with the following exceptions:

In general, transmission rules are fully supported by the QAnywhere Agent for UltraLite. The one limitation is the support for Property attributes. Transmission rules can only use the following attributes of the predefined property ias_Network:

See also