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 » Writing QAnywhere client applications


QAnywhere message addresses

A QAnywhere message address has two parts, the client message store ID and the application queue name:


The queue name is specified inside the application, and must be known to instances of the sending application on other devices. For information about client message store IDs, see Setting up the client message store.

Each address can have at most one application associated with it at a time. More than one application running with the same address can result in undefined behavior during message retrieval.

When constructing addresses as strings in an application, be sure to escape the backslash character if necessary. Follow the string escaping rules for the programming language you are using. If your JMS destination contains a backslash, you must escape it with another backslash.

The address cannot be longer than 255 characters.

System queue

Notifications and network status changes are both sent to QAnywhere applications as system messages. System messages are the same as other messages, but are received in a separate queue named system.

See System queue.

Sending a message to a JMS connector

A QAnywhere-to-JMS destination address has two parts:

  • The connector address. This is the value of the ianywhere.connector.address property.

    See Configuring JMS connector properties.

  • The JMS queue name. This is a queue that you create using your JMS administration tools.

The form of the destination address is:


For more information about addressing messages in a JMS application, see:

System queue