|
The QAnywhere Agent (qaagent) is a separate process running on the client device. It monitors the client message store and determines when message transmission should occur.
The QAnywhere Agent transmits messages between the server message store and the client message store. You can run multiple instances of the QAnywhere Agent on the same device, but each instance must be connected to its own message store. Each message store must have a unique message store ID.
You can run the Agent on the command line using command line options. At a minimum, you need to start the Agent with the following options:
Connection parameters to connect to the client message store.
In the Agent Configuration file properties dialog, this is the information on the Message Store tab. In the qaagent command line, this is specified with the -c option. See -c option.Client message store ID to identify the client message store. The first time you run qaagent after you have initialized a client message store, you can optionally use this option to name the message store; if you do not, the device name is used by default. After that, you must use the -id option every time you start qaagent to specify a unique client message store ID.
In the Agent Configuration file properties dialog, this is specified on the General tab. In the qaagent command line, this is specified with the -id option. See -id option.Network protocol and protocol options to connect to the MobiLink server. This is required unless the MobiLink server is running on the same device as the QAnywhere agent and default communication parameters are used.
In the Agent Configuration file properties dialog, this is the server information on the Server tab. In the qaagent command line, this is the -x option. See -x option.For a complete list of all QAnywhere Agent options, see qaagent syntax.
On Windows CE, you might want to start the QAnywhere Agent in quiet mode by specifying the -qi option.
See -qi option.
You can run multiple instances of qaagent on a device. However, when you start a second instance:
The second instance of QAnywhere Agent must be started with a different database file.
You must specify a unique message store ID using the -id option.
See -id option.
To stop the QAnywhere Agent, click Shutdown on the console.
When you start the QAnywhere Agent in quiet mode, you can only stop it by running qastop.
See -qi option.
The QAnywhere Agent starts other processes to handle various messaging tasks. Each of these processes is managed by the QAnywhere Agent, and does not need to be managed separately. When you start the QAnywhere Agent, it spawns the following processes:
dbmlsync The dbmlsync executable is the MobiLink synchronization client. The the dbmlsync executable is used to send and receive messages.
| Caution
Do not run dbmlsync on a QAnywhere message store independently of qaagent. |
dblsn The dblsn executable is the Listener utility. It receives push notifications. If you are not using push notifications, you do not need to supply the dblsn executable when you deploy your application, and you must run qaagent with -push none.
See -push option.database server The client message store is a SQL Anywhere database. QAnywhere Agent requires the SQL Anywhere database server to run the database. For Windows CE, the database server is dbsrv10.exe. For Windows, the database server is the personal database server dbeng10.exe.
The QAnywhere Agent can spawn a database server or connect to a running server, depending on the communication parameters that you specify in the qaagent -c option. See -c option.For deployment information, see Deploying QAnywhere applications.
Determining when message transmission should occur on the client