|
Home > Archive > SQL Anywhere ultralite > September 2005 > Deploying HotSync Conduit
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Deploying HotSync Conduit
|
|
| Joel Goldberger 2005-08-26, 8:23 pm |
| We are distributing a Palm Ultralite application and need an easy way to
deliver the HotSync conduit files for installation on users systems. It
seems that the DLLs all have to be accessable on the "path" prior to running
"dbcond9 XXXX -n zzzz" to configure the conduit.
Does anyone have an installation package built that will install the
required files and then invoke dbcond9 to register the conduit ? I have
been struggling with the "deployment" project facility of VS.NET 2003
without much luck.
Thanks in advance,
Joel Goldberger
MLS Wherehouse LLC
Flagstaff, AZ
| |
| Tom Slee 2005-09-01, 8:23 pm |
| Joel Goldberger wrote:
> We are distributing a Palm Ultralite application and need an easy way to
> deliver the HotSync conduit files for installation on users systems. It
> seems that the DLLs all have to be accessable on the "path" prior to running
> "dbcond9 XXXX -n zzzz" to configure the conduit.
>
> Does anyone have an installation package built that will install the
> required files and then invoke dbcond9 to register the conduit ? I have
> been struggling with the "deployment" project facility of VS.NET 2003
> without much luck.
>
> Thanks in advance,
> Joel Goldberger
> MLS Wherehouse LLC
> Flagstaff, AZ
>
>
There are a few stages to deploying the HotSync conduit. I suspect you
have got through the first few, but just in case...
The instructions for getting dbcond9 running are given at
MobiLink Clients > UltraLite Clients > Synchronizing UltraLite databases
on the Palm Computing Platform > Registering the MobiLink HotSync
conduit to HotSync Manager
At this stage I *think* installing the support DLLs (dblgen9.dll and the
streams DLLs) in the same directory as dbcond9.exe would be sufficient.
The location of the condmgr.dll library is different - it has to be in
the location indicated by the registry setting (see the documentation
listed above).
Once the dbcond9 has been run, HotSync Manager has to be able to find
it. TO manage this, it does indeed have to be in the path, as you say.
If you modify the path during your install, then you have to restart
HotSync Manager to get it to see the new path settings. Apparently
simply restarting it programatically is insufficient (it doesn't quite
shut itself down, so it fails to read the new path, or something).
Instead, you have to kill the process and then start HotSync Manager
once again.
Tom Slee
iAnywhere Solutions Product Management
|
|
|
|
|