Note

The mlsrv16 options allow you to specify how the MobiLink server works. To control what the server does during synchronization,
you define scripts that are invoked at synchronization events. See Synchronization events.

To start the MobiLink server, run mlsrv16. Use the -c option to specify the ODBC connection parameters for your consolidated
database. For a list of mlsrv16 command line options, see MobiLink server options.

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. For information about connection parameters,
see -c mlsrv16 option.

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). See Lesson 1: Setting up a MobiLink consolidated database.

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 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.

For more information about the options described in the previous example, see:

You must specify a database user for the MobiLink server to connect to the database server. You specify the database user
with the mlsrv16 -c option or in the ODBC data source. See -c mlsrv16 option.

This database user must have full SELECT, INSERT, UPDATE, and DELETE privileges on the MobiLink system tables, and must also
have the EXECUTE ANY PROCEDURE privilege on the MobiLink system procedures. By default, the database user who runs the MobiLink
setup script has these privileges. To use another database user to run the MobiLink server, you must grant these privileges
for that user on the ml_* tables and the ml_add_*_script system procedures.

The database user also needs the appropriate privilege on all tables referenced in the MobiLink scripts, and EXECUTE privileges
on any procedures referenced in the MobiLink scripts.

Some types of MobiLink consolidated databases require the database user used by MobiLink server to have specific privileges
against system tables and/or views. See the following topics for information about specific consolidated databases:

When using HTTP or HTTPS, with or without the Relay Server, you can use a web browser to verify MobiLink server is listening
for requests. For example, if your MobiLink server command line is as follows:

mlsrv16 ... -x http(port=8080)

and the computer is ml1.mycorp.com, then you can open a web browser and point it to http://ml1.mycorp.com:8080.

MobiLink server responds with a 404 Not Found error that also mentions the MobiLink server's major version.