In this lesson you start the MobiLink server. You start the MobiLink server (mlsrv11) using the -c option to connect to your consolidated database. You use the -sl java or -sl dnet option to load your Java or .NET class.

To start the MobiLink server for direct row handling

• Connect to your consolidated database and load .NET or Java classes on the mlsrv11 command line.

  For Java, run the following command. Replace c:\MLdirect with the location of your Java source files.

  mlsrv11 -c "dsn=mobilink_db" -o serverOut.txt -v+ -dl -zu+ -x tcpip -sl java (-cp c:\MLdirect)

  For .NET:

  mlsrv11 -c "dsn=mobilink_db;uid=DBA;pwd=sql" -o serverOut.txt -v+ -dl -zu+ -x tcpip -sl dnet (-MLAutoLoadPath=c:\MLdirect)

  The MobiLink server window appears.

  Below is a description of each MobiLink server option used in this tutorial. The options -o, -v, and -dl provide debugging and troubleshooting information. Using these logging options is appropriate in a development environment. For performance reasons, -v and -dl are typically not used in production.

  Option	Description
  -c	Precedes the connection string.
  -o	Specifies the message log file serverOut.txt.
  -v+	The -v option specifies what information is logged. Using -v+ sets maximum verbose logging.
  -dl	Displays all log messages on screen.
  -zu+	Adds new users automatically.
  -x	Sets the communications protocol and parameters for MobiLink clients.
  -sl java	Specifies a set of directories to search for class files, and forces the Java Virtual Machine to load on server startup.
  -sl dnet	Specifies the location of .NET assemblies and forces the CLR to load on server startup.

Further reading

For a complete list of MobiLink server options, see MobiLink server options.

For more information about loading Java and .NET classes see -sl java option and -sl dnet option, respectively.