Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » MobiLink - Client Administration » Deploying ActiveSync and HotSync for UltraLite clients » HotSync on Palm OS

HotSync synchronization overview Next Page

Deploying the UltraLite HotSync conduit to the end-user's desktop

During development you will have installed UltraLite onto your desktop with the SQL Anywhere installer. However, you then need to deploy required HotSync conduit files on the end-user's computer.

UltraLite HotSync conduit files
Separately licensed component required

ECC encryption and FIPS-approved encryption stream DLLs require a separate license. All strong encryption technologies are subject to export regulations.

To order a separately licensed component, visit [external link] .

For information about component and platform support, see the Separately licensed components sections of the SQL Anywhere, UltraLite, and MobiLink tables in [external link] SQL Anywhere 10.0.1 Components by Platform.

For the most up-to-date supported component and platform support information, see [external link]

To deploy and register the UltraLite HotSync conduit
  1. On the end-user's desktop, create the following directories:

  2. Deploy a copy of the following files to the MyDir\win32\ directory:

  3. Deploy a copy of the Condmgr.dll file to the MyDir\win32\condmgr directory.

  4. Locate the following registry key:

    HKEY_CURRENT_USER\Software\Sybase\SQL Anywhere\10.0\
  5. Create a value named Location in this key and set this value data as the root deployment folder for the conduit. For example, MyDir.

  6. If the end-user requires a certificate to encrypt the communication stream, install the root certificate on the desktop computer so it can be accessed by the conduit.

  7. Run ulcond10, ensuring that you have set connection string for each the UltraLite database with either the -c option, and possibly the -a option. Remember to also set the correct creator ID.

    This deploys and correctly configures the UltraLite HotSync conduit.


    If you are using an encryption key, avoid setting the key in the connection string. This can pose a security risk. Instead, allow the conduit to prompt the user for the key.

    For example, the following command installs a conduit for the application with creator ID Syb2, named CustDB.

    ulcond10 -c "DBF=custdb.udb;UID=DBA;PWD=sql" -n CustDB Syb2 
  8. If you did not include synchronization parameters in your UltraLite application's ul_sync_info structure, configure this information either in HotSync or use ulcond10. See Setting protocol options for MobiLink synchronization,

To check that the HotSync conduit is properly deployed