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.
install-path\win32\condmgr\condmgr.dll— The utility DLL that locates the HotSync installation path and registers the conduit with HotSync.
install-path\win32\ulcond10.exe— The UltraLite HotSync Conduit Installation utility that installs or removes the UltraLite HotSync conduit on the desktop computer. See UltraLite HotSync Conduit Installation utility for Palm OS (ulcond10).
install-path\win32\dbhsync10.dll— The conduit DLL that is called by HotSync.
install-path\win32\dblgen10.dll— The language resource library. For languages other than English, the letters en in the file name are replaced by a two-letter abbreviation for the language, such as dblgde10.dll for German, or dblgja10.dll for Japanese.
Stream DLLs Optional. The stream DLL required for encrypted network communication between the UltraLite HotSync conduit and the MobiLink server.
For RSA encryption with TLS and HTTPS, install-path\win32\mlcrsa10.dll.
For ECC encryption with TLS and HTTPS, install-path\win32\mlcecc10.dll.
For RSA FIPS encryption with TLS and HTTPS, install-path\win32\mlcrsafips10.dll.
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 http://www.ianywhere.com/products/separately_licensed_components.html .
For information about component and platform support, see the Separately licensed components sections of the SQL Anywhere, UltraLite, and MobiLink tables in SQL Anywhere 10.0.1 Components by Platform.
For the most up-to-date supported component and platform support information, see http://www.ianywhere.com/products/components_platforms_1001.html.
On the end-user's desktop, create the following directories:
Deploy a copy of the following files to the MyDir\win32\ directory:
Deploy a copy of the Condmgr.dll file to the MyDir\win32\condmgr directory.
Locate the following registry key:
Create a value named Location in this key and set this value data as the root deployment folder for the conduit. For example, MyDir.
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.
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
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,
Check that a conduit is deployed:
In the computer's system tray, right-click HotSync Manager.
From the popup menu, choose Custom.
A list of conduits is displayed for each HotSync user. Verify that the conduit is listed. If the conduit is listed, you can then proceed to start the MobiLink server and test your synchronization operation.