Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
This section explains the architecture of QAnywhere messaging applications. The discussion begins with a simple messaging scenario and then progresses to more advanced scenarios.
Client applications send and receive messages using the QAnywhere API. Messages are queued in the client message store. Message transmission is the exchange of messages between client message stores through a central QAnywhere server message store.
The following typical messaging scenarios are supported by QAnywhere:
Local application-to-application messaging For exchanging messages between applications using a SQL Anywhere database as the local message store. Messages are transmitted between applications via their connection to the database.
Simple client/server messaging For exchanging messages among QAnywhere clients. Client applications control when to transmit messages between the client and server message stores.
Client/server messaging with push notifications For exchanging messages among QAnywhere clients. In this scenario, the MobiLink server can initiate message transmission between clients. This is done by exchanging messages between client and server message stores.
Client/server messaging with external messaging systems For exchanging messages among QAnywhere clients over an external system that supplies a JMS provider, such as BEA WebLogic or Sybase EAServer.
Push notifications and external messaging systems can be used together, providing the most general solution.
Application-to-application messaging scenario
Simple messaging scenario
Scenario for messaging with push notifications
Scenario for messaging with external messaging systems
Discuter à propos de cette page dans DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|