[cvs] [Wiki] changed: SyncHowTo
Jan Schneider
jan at horde.org
Sat Jun 14 00:18:16 UTC 2008
jan Fri, 13 Jun 2008 20:18:16 -0400
Modified page: http://wiki.horde.org/SyncHowTo
New Revision: 2.18
Change log: Update to current state
@@ -10,44 +10,37 @@
++ General information
Syncing is beta quality code - to help fixing bugs and locating
issues you need to be able to at least read logfiles! Testing is
welcome; please report to the sync list (sync at lists.horde.org), but
please keep in mind that the code is still in development.
-* You have to use at least Horde 3.2 and x.2 versions of the Horde
applications, or Horde Groupware (Webmail Edition) 1.1, or the cvs
version or a cvs snapshot. Horde 3.1.x or Horde Groupware 1.0.x won't
do. Please note that if you are using a cvs checkout or snapshot, you
have to run framework/install-packages.php to install the required
packages into your PEAR path.
-* client configuration is as follows:
+* You have to use at least Horde 3.2 and x.2 versions of the Horde
applications, or Horde Groupware (Webmail Edition) 1.1, or the CVS
version or a CVS snapshot. Horde 3.1.x or Horde Groupware 1.0.x won't
do. Please note that if you are using a CVS checkout or snapshot, you
have to run {{framework/install-packages.php}} to install the required
packages into your PEAR path.
+* Client configuration is as follows:
* The sync URL is http(s)://pathtoyourhordeinstall/rpc.php
- * Username/password: your Horde account data
- * Databases (sometimes called remote settings or 'server path')
must be calendar, tasks, notes, or contacts.
-* For debug output create dir /tmp/sync and make it writeable by web server
-* Set log level to PEAR_LOG_DEBUG in Administration:Horde Setup_Logging.
-* When reporting problems to the mailing list, please include the
/tmp/sync/syncml_log.txt. This greatly helps to figure out what's
going on.
+ * User name/password: your Horde account data
+ * Databases (sometimes called remote settings or server path)
should be calendar, tasks, notes, and contacts, but common default
values from the various clients may work too.
+* For debug output create the directory {{/tmp/sync/}} and make it
writable by web server
+* Set log level to PEAR_LOG_DEBUG in Administration -> Setup -> Horde
-> Logging.
+* When reporting problems to the mailing list, please include at
least the {{/tmp/sync/log.txt}} file. This greatly helps to figure out
what's going on.
++ Information for syncing with Outlook or Blackberry
* You need the Funambol outlook connector. Go to
http://www.funambol.com/ -> Download -> PIM-Only Client Software ->
Version for your client -> Download and install.
* Configure as mentioned above. Device ID must be sc-pim-outlook or
anything containing the text sync4j so that the Horde backend can
identify the connector. If you're using multiple instances of the
connector (one on your home pc, one on your laptop), make sure that
the device ID is different on those.
-* Turn page compression off in {{/horde/config/conf.php}} by setting
{{$conf['compress_pages']}} to {{false}} (Funambol does not support
compressed pages.)
-* !Sync4J Outlook Client needs to have the port configured in the
sync url when using https, i.e.
https://pathtoyourhordeinstall:443/rpc.php
+* @@--- Turn page compression off in {{/horde/config/conf.php}} by
setting {{$conf['compress_pages']}} to {{false}} (Funambol does not
support compressed pages.) @@
+* Funambol Outlook Clients need to have the port configured in the
sync url when using https, i.e.
https://pathtoyourhordeinstall:443/rpc.php
++ Information for syncing PDAs with the Synthesis client
-* The Synthesis is a commercial SyncML client from
http://www.synthesis.ch/. It is available for !PocketPC2002,
!PocketPC2003, Windows Mobile 5, !Smartphone2003 and !PalmOS.
Stability and !SyncML conformance is very good, currently a lot better
than the Funambol Outlook connector. There's a 30 days trial version.
+* The Synthesis client is a commercial SyncML client from
http://www.synthesis.ch/. It is available for !PocketPC, Windows
Mobile, Smartphone and !PalmOS. Stability and !SyncML conformance is
very good. There's a 30 days trial version.
* Make sure to set the events server path to "calendar"
* Uncheck the "only from 30 days before until 90 after today" setting
++ Information for syncing Horde with Evolution
How to configure Horde with Syncevolution (based on Sync4j) :
http://www.estamos.de/projects/SyncML/Compatibility.html#Horde
-
-++ Synchronization of Address Book Data with Turba
-
-The current default Turba address book database structure is not very
suitable for SyncML: only one name field instead of separate first
name last name, address in one multi line field instead of split into
city and so on. Additionally, the default LDAP sources definition
does not properly handle the First Name field.
-
-If you want to replicate your address book using SyncML, you should
consider altering your Turba configuration. See SyncMLTurbaConfiguration
-
++ Sync clients being used succesfully:
-* Synthesis client: that's the primary client used during the development
+* Synthesis client
* Sony Ericsson P800/P900
* Outlook with Funambol !SyncClient PIM outlook 3.0.15
* Nokia E65, E60, E90, N73, N80, N95, 6120 Classic
* Sony Ericsson K800i
@@ -55,43 +48,34 @@
++ FAQ
+++ It's not working! I got a message like "Invalid response" on the
phone or "Server returned error code -1" on Funambol clients
-There's a chance that SyncML processing stopped due some php error in
the server. Like //Object of class PEAR_Error could not be converted
to string in /usr/share/php/SyncML/Backend.php on line 294//. As this
is passed to the phone rather than displayed in a web page, the phone
gets confused because it doesn't receive a valid XML message. To catch
these error message, you need to make php log errors to a file: edit
your php.ini and include a line like error_log =
/var/log/phperrors.log. Then try a sync an check if anything comes up
in this log.
+There's a chance that SyncML processing stopped due some PHP error in
the server. We try to catch these errors, but sometimes they are
passed to the phone so the phone gets confused because it doesn't
receive a valid XML message. To catch even those error message, you
need to make PHP log errors to a file: edit your {{php.ini}} and
include a line like {{error_log = /var/log/php.log}}. Then try a sync
and check if anything comes up in this log.
-Another common pitfall is a bug in some Funambol clients: The clients
propagate that they are able to handle "deflate" encoded HTTP traffic
while in fact they don't. This affects e.g. the 6.0.x series of the
Outlook Plugin, probably others too. This has been fixed with later
versions, i.e. the 6.5.x Outlook Plugins. Either upgrade to a newer
Funambol client, or configure your web server to //not// send deflate
encoded HTTP responses for the horde directory, even if the client
tells to do so.
+Another common pitfall is a bug in some older Funambol clients: The
clients propagate that they are able to handle "deflate" encoded HTTP
traffic while in fact they don't. This affects e.g. the 6.0.x series
of the Outlook Plugin, probably others too. This has been fixed with
later versions, i.e. the 6.5.x Outlook Plugins. Either upgrade to a
newer Funambol client, or configure your web server to //not// send
deflate encoded HTTP responses for the horde directory, even if the
client tells to do so.
-+++ Syncing of events fails with a log entry like "No sync object
found for URI=calendar?dr(-30,90)"
++++ I can't find any *.xml log files in /tmp/sync anymore. They used
to be there!
-Syncing of date ranges as used by the Synthesis client is not yet
supported. Please uncheck the "only from 30 days before until 90 days
after today" checkbox.
+We now use our own WBXML libary in the XML_WBXML package. The WBXML
data gets directly passed and processed, no XML is produced. To see
the XML data, you can manually decode it. You need to install the
WBXML utilities for that. This package contains the programs
{{wbxml2xml}} and {{xml2wbxml}} to convert XML files to WBXML and back.
-+++ I can't find any *.xml log files in /tmp/sync anymore. They used
to be there!
-
-We now use our own wbxml libary in the XML_WBXML package. The wbxml
gets directly passed and processed, no xml is produced. To see the
xml, you can manually decode it like this:
-You need to install the WBXML utils.
-This package contains wbxml2xml and xml2wbxml utils to convert xml
files to wbxml and back.
-On Debian:
+To install them on Debian:
<code>
apt-get install libwbxml2-utils
</code>
-The WBXML Library (aka libwbxml) contains a library and its
associated tools to Parse, Encode and Handle WBXML documents.
-(The WBXML format is a binary representation of XML, defined by the
Wap Forum, and used to reduce bandwidth in mobile communications.)
+The WBXML Library (aka libwbxml) contains a library and its
associated tools to parse, encode and handle WBXML documents.
+(The WBXML format is a binary representation of XML, defined by the
WAP Forum, and used to reduce bandwidth in mobile communications.)
+
+You can decode the data like this:
<code>
for a in *.wbxml; do wbxml2xml -m 1 -i 4 -o `basename $a
.wbxml`_conv.xml $a; done 2>/dev/null
</code>
-
-
-
-+++ I really don't want to upgrade my complete Horde installation.
What can I do?
-
-Nothing. This is cutting edge technology, so you need to invest a bit
if you want to participate at these exciting new features.
+++ It's still not working! What can I do?
Please follow the directions in SyncMLProblemReport and report the
problem to the sync mailing list.
-+++ I Want to test syncing on my pc , does some Palm emulator or
Pocket Pc exist and how do i use it?
++++ I Want to test syncing on my PC, does some Palm or PocketPC
emulator exist and how do i use it?
Please see the PdaEmulators page for info.
More information about the cvs
mailing list