MobiLink provides various information and facilities that you may find helpful when debugging your Java code. This section describes where you can find this information and how you can exploit these capabilities.
The MobiLink server writes messages to an output log file. The synchronization server log file contains the following information:
See -v option.
You can debug your Java classes using a standard Java debugger. Specify the necessary parameters using the -sl java option on the mlsrv11 command line.
See -sl java option.
Specifying a debugger causes the Java virtual machine to pause and wait for a connection from a Java debugger.
Alternatively, you may choose to add statements to your Java methods that print information to the MobiLink output log, using java.lang.System.err or java.lang.System.out. Doing so can help you track the progress and behavior of your classes.
Printing information in this manner is a useful monitoring tool, but is not recommended in a production scenario.
The same technique can be exploited to log arbitrary synchronization information or collect statistical information on how your scripts are used.
You may want to write your own driver to exercise your Java classes. This approach can be helpful because it isolates the actions of your Java methods from the rest of the MobiLink system.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|