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

SQL Anywhere 11.0.1 (Français) » QAnywhere » Messages

 

Understanding destinations

With QAnywhere, messages are addressed to a destination. A destination always consists of an identifier and a queue name, separated by a backslash (\). For example:

ianywhere.connector.tibco\SomeQueue
 DEV007\app_queue1
 SalesTeam\queue1

The meaning of the identifier before the backslash depends on whether the message is addressed to a JMS application, destination alias, or a mobile application.

The first example illustrates the case where the message is addressed to a JMS application. In this case the identifier is the ID of a JMS connector running in the MobiLink server. See JMS connectors.

The second example illustrates the case where the message is addressed to a mobile application. In this case, the identifier is a message store ID of a QAnywhere message store. See Setting up the client message store and -id option.

The third example illustrates the case where the message is addressed to a destination alias. In this case, the identifier is a destination alias name. See Destination aliases.

The queue name in a destination refers to a queue defined in the JMS system when the identifier is a JMS connector ID, and refers to a QAnywhere application queue when the identifier is either a message store ID or a destination alias.

Note

QAnywhere destinations should always be specified using EN characters.

For more information on destinations and sending QAnywhere messages, see: