Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
Specifies the incremental upload size.
qaagent -iu upload-size [ K | M ] ...
This option specifies the size in bytes of the upload part of a message transmission. Use the suffix K or M to specify units of kilobytes or megabytes, respectively.
When the QAnywhere Agent starts, it assigns the value specified by this option to the ias_MaxUploadSize message store property. This message store property defines an upper bound on the size of an upload. When a transmission is triggered, the Agent tags messages for delivery to the server until the total size of all messages reaches the limit set with this option. When the limit is reached, these messages are sent to the server. As long as the messages arrive at the server and an acknowledgement is successfully sent from the server to the client, these messages are considered to be successfully delivered, even if the download phase of the transmission fails. The Agent continues sending batches of messages to the server until all queued messages have been delivered. Transmission rules are re-executed after each batch of messages is transmitted so that if a high priority messages gets queued during a transmission, it jumps to the front of the queue.
Messages that exceed the upload threshold are broken into multiple smaller message parts. Each message part can be uploaded separately, resulting in the gradual upload of the message over several synchronizations. The complete message arrives at its destination once all of its message parts have arrived.
The incremental upload size is an approximation. The actual upload size depends on many factors beyond the size of the message.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|