MobiLink Synchronization Reference
MobiLink Synchronization Client
dbmlsync options
Pings a MobiLink synchronization server.
dbmlsync -pi -c connection_string -e sv=script_version
[-n pubname ] [ -u ml_username ]
The ping option allows you to test that your connection information is correct. When you use -pi, dbmlsync does not initiate synchronization.
In order to be able to ping, dbmlsync must have a unique address for the MobiLink synchronization server. This means that you must include connection parameters and a script version, as well as the publication name, MobiLink user name, or both. The publication or user hold connection information for the remote. You need to specify both when the user is subscribed to multiple publications or the publication has multiple users. For example, if there is only one subscription to the publication, you can specify the publication without the user.
When the MobiLink synchronization server receives a ping request, it connects to the consolidated database, authenticates the user, and then sends the authenticating user status and value back to the client (dbmlsync or UltraLite).
If the ping succeeds, the MobiLink server issues an information message. If the ping does not succeed, it issues an error message.
If the MobiLink user name cannot be found in the ml_user system table and the MobiLink server is running with the command line option -zu+, the MobiLink server adds the user to ml_user.
The MobiLink synchronization server may execute the following scripts, if they exist:
begin_connection
authenticate_user
authenticate_user_hashed
end_connection
The client cannot synchronize while it is pinging the server.