SQL Anywhere Mobile - what is needed in practice

Author

what is needed in practice

Eric Verhorstert

2005-07-29, 7:24 am

We have build a synchronization with mobilink and ASA as consolidated
and ASA as remote. The book of Breck Carter helped us a lot.

We have written upload scripts, download script, and developed a tool so
we can see the latest download time, the latest upload time and checks
before the synchronization start if the version of database is correct,
if remote table is the same as consolidated tables and more of these
things.

Since we have no experience we would like to know what infomation is
neccesary (handy) to store in the database to support the synchronization.

Thanks
Eric

Eric Verhorstert

2005-08-01, 3:25 am

I have written only downloadscripts, insert, upload scripts and delete
scripts for the synchronization process.

I wonder what information should I store to support the synchronization
in case of errors? Are login scripts necassary, time (duration) of
synchronization, number of concurrent users, error control?

Thanks
Eric

Eric Verhorstert wrote:
> We have build a synchronization with mobilink and ASA as consolidated
> and ASA as remote. The book of Breck Carter helped us a lot.
>
> We have written upload scripts, download script, and developed a tool so
> we can see the latest download time, the latest upload time and checks
> before the synchronization start if the version of database is correct,
> if remote table is the same as consolidated tables and more of these
> things.
>
> Since we have no experience we would like to know what infomation is
> neccesary (handy) to store in the database to support the synchronization.
>
> Thanks
> Eric

Greg Fenton

2005-08-10, 11:26 am

Eric Verhorstert wrote:
>
> I wonder what information should I store to support the synchronization
> in case of errors? Are login scripts necassary, time (duration) of
> synchronization, number of concurrent users, error control?
>

We strongly suggest that any production system have a report_error
script written to log errors and to *avoid* having a handle_error script
if at all possible.

Custom authentication is completely up to the requirements of your
application and/or server configuration. As for timings and
concurrency, you can write your own scripts or you might prefer to use
the MobiLink Monitor which actually hooks into ML using the *_statistics
events. For a full list of events, see in the SQLAnywhere 9.x online docs:

MobiLink Administration Guide
- Synchronization Events

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

David Fishburn

2005-08-17, 1:24 pm

Eric Verhorstert <ontsnapt@hotmail.com> wrote in
news:42ea1e6e$1@foru
ms-2-dub of sybase.public.sqlanywhere.mobilink:

EV> We have written upload scripts, download script, and developed a tool
EV> so we can see the latest download time, the latest upload time and
EV> checks before the synchronization start if the version of database is
EV> correct, if remote table is the same as consolidated tables and more
EV> of these things.

I ususally put in place a method to perform minor schema updates.
Something I can send stored procedures and trigger updates through.
That way when a bug is found I have a mechanism to update the remotes.

There have been quite of few threads on this topic, so you can google
through them for ideas.

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]

Sponsored Links