Push notifications are disabled for this agent. The Listener (dblsn) is not started.
Push notifications are enabled for this agent over TCP/IP with persistent connection. The Listener (dblsn) is started by
qauagent and attempts to maintain a persistent connection to the MobiLink server. This mode is useful when the client device
does not have a public IP address or when the MobiLink server is behind a firewall that does not allow UDP messages out. This
is the default.
Push notifications are enabled for this agent over UDP without a persistent connection. The Listener (dblsn) is started by
qauagent but does not maintain a persistent connection to the MobiLink server. Instead, a UDP listener receives push notifications
from MobiLink. This mode is useful in the following scenarios when the client device has a public IP address and is reachable
by UDP or SMS:
The client device is using dial-up networking and connection time charges are an issue.
There is light message traffic over QAnywhere. Persistent TCP/IP connections consume network server resources, and so could
have an impact on scalability.
The client device network coverage is unreliable. You can use the automatic policy to transmit messages when connection is
possible. Trying to maintain persistent connections in this environment is not useful and can waste CPU resources.
Push notifications are enabled for this agent using light weight polling. The poll period for the light weight poll can be
adjusted by including the desired interval in seconds in square brackets following lwpoll. For example, -pushlwpoll sets a QAnywhere agent to use light weight polling with an interval of 5 seconds between polls. If no interval is given,
the default period is 60 seconds.
Clients using light weight polling in a secure environment do not need to register a MobiLink user for the Listener, as required
by other push notification modes.