All MobiLink clients synchronize through the MobiLink server. None connect directly to a database server. You must start the MobiLink server before a MobiLink client synchronizes.
The MobiLink server opens database connections, via ODBC, with your consolidated database server. It then accepts connections from remote applications and controls the synchronization process.
To start the MobiLink server, run mlsrv17. Use the -c option to specify the ODBC connection parameters for your consolidated database.
You must specify connection parameters. Other options are available, but are optional. These options allow you to specify how the server works. For example, you can specify a cache size and logging options.
The MobiLink server needs an ODBC Data Source Name (DSN) to communicate with the consolidated database. A DSN includes information for the ODBC Driver Manager on where to load the ODBC driver. On Windows, ODBC data sources can be created with the Microsoft ODBC Data Source Administrator. The bitness of the MobiLink server must match the bitness of the DSN. More precisely, a 64-bit MobiLink server must use a 64-bit DSN created via ODBC Data Source Administrator (64-bit).
The following command starts the MobiLink server using the ODBC data source SQL Anywhere 17 CustDB to identify the consolidated database. Enter the entire command on one line.
mlsrv17 -c "DSN=SQL Anywhere 17 CustDB;UID=ml_server;PWD=sql" -zs MyServer -o mlsrv.log -vcr -x tcpip(port=3303)
In this example, the -c option provides a connection string that contains an ODBC data source name (DSN) and authentication. The -zs option provides a server name. The -o option specifies that the message log file should be named mlsrv.log. The contents of mlsrv.log are verbose because of the -vcr option. The -x option opens a port for version 10 and later clients.
You can also start the MobiLink server as a Windows service or Unix daemon.