Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > Zimbra Collaboration Suite > Mobility > Zimbra Mobile

Welcome to the Zimbra - Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Display Modes
  #31 (permalink)  
Old 10-19-2007, 05:08 AM
Intermediate Member
 
Posts: 17
Default

Thx Hillman for your help.

Yes, I use the separate admin tool. It works untill the depth where I can see the different modules. When I want to open the zimbra module it gives me an unexpected error.

But I'm still not able to sync. I always get: "Unable to open database" on my device and there is nothing relative in the logs. Any idea?

Last edited by DenRaf : 10-19-2007 at 06:00 AM.
Reply With Quote
  #32 (permalink)  
Old 10-19-2007, 06:34 AM
Active Member
 
Posts: 47
Default helping

Ok hillman,
can you post the rigth way to configure the conector to work with postgresql?
I mean the install.properties and the server.xml files...
Do you have any doc for the bugs you are working on?
Thanks
Juan
Reply With Quote
  #33 (permalink)  
Old 10-19-2007, 12:27 PM
Moderator
 
Posts: 69
Default

Quote:
Originally Posted by DenRaf View Post
Yes, I use the separate admin tool. It works untill the depth where I can see the different modules. When I want to open the zimbra module it gives me an unexpected error.

But I'm still not able to sync. I always get: "Unable to open database" on my device and there is nothing relative in the logs. Any idea?
I still don't know that much about how this all works, but it sounds like the Zimbra connector may not be initializing properly. When you installed the module, did you answer 'yes' when it asked you if you wanted to re-install the database when it got to the Zimbra module?

As for logging, you can drastically increase the logging level:

Edit Sync4j/server/config/sync4j/server/logging/Logging.xml

In the first block of properties (the one that ends with "logs/syncserver.log"), set the property "level" to "ALL" and restart the server.
Reply With Quote
  #34 (permalink)  
Old 10-19-2007, 12:38 PM
Moderator
 
Posts: 69
Default

Quote:
Originally Posted by jproig View Post
Ok hillman,
can you post the rigth way to configure the conector to work with postgresql?
I mean the install.properties and the server.xml files...
Do you have any doc for the bugs you are working on?
Thanks
Juan
Sorry, I've never set postgresql up. The .doc file that came with the Zimbra connector includes numerous changes you need to make if you want to run with mysql (I assume the changes for postgresql would be similar), but none of those changes are necessary if you use the bundled hysqldb (which is the default). Since hysqldb still writes everything to disk, and since I'm only doing development work, I saw no need to add more complexity by adding an external database to the mix.

As far as bugs go: The big one right now is timezone shifting, at least on the Windows Mobile 2003 PDA that I'm testing with right now. Meetings in Zimbra are reported using the local time zone, whereas on the PDA they're reported (via SyncML) in GMT. The connector is not properly accounting for this so it mangles the meetings whenever they sync from the PDA back to Zimbra - meetings shift by 7 hours (in my case), and all-day meetings become 24 hour meetings that stretch from 7am-6:59am (this is because the iCalendar format doesn't have an "allday" flag, it represents all-day meetings as going from 00:00 to 23:59, but when they get shifted by 7 hours, they no longer match this "allday" pattern)

Once that's fixed, I think there are issues to do with fields being lost when they get synced back to Zimbra. The problem is that the iCalendar format can't represent every field that Zimbra can, so the PDA contains a subset of what's in Zimbra. When you change a meeting on the PDA side, it appears that, at least under some circumstances, it's resynced back by first deleting the meeting in Zimbra and then recreating it. The right thing to do would be to fetch all of the extra fields from Zimbra before deleting the meeting (if it's even necessary to delete them).

And then of course there's the much bigger project of porting to Funambol 6.
Reply With Quote
  #35 (permalink)  
Old 10-21-2007, 08:59 PM
Active Member
 
Posts: 47
Default to v6

What we need to start? lets do it
I dont know where to start, but we can organize.
Juan
Reply With Quote
  #36 (permalink)  
Old 10-22-2007, 02:57 AM
Intermediate Member
 
Posts: 17
Default

Quote:
Originally Posted by hillman View Post
I still don't know that much about how this all works, but it sounds like the Zimbra connector may not be initializing properly. When you installed the module, did you answer 'yes' when it asked you if you wanted to re-install the database when it got to the Zimbra module?

As for logging, you can drastically increase the logging level:

Edit Sync4j/server/config/sync4j/server/logging/Logging.xml

In the first block of properties (the one that ends with "logs/syncserver.log"), set the property "level" to "ALL" and restart the server.
There isn't anything new anymore in those logs. If I use syncml 1.2, which is not supported, I get some errors in syncserver.log. When I 1.1, like it should, I don't get any logging, even when it is on ALL. Only in catalina.out I see some logging.
Reply With Quote
  #37 (permalink)  
Old 10-23-2007, 09:36 AM
Moderator
 
Posts: 69
Default

If you figure it out, let us know -- I didn't have any problems getting the logging to work, or getting the zimbra connector to load, so I don't really have any experience with a "broken" server.

Re: How to start. Assuming you can get the connector working and successfully sync to a PDA, start finding bugs. Then dive into the code and figure out how it all works. Depending on your java experience, that could take you anywhere from a few hours (java developer) to several weeks (me). Then we'll take it from there..
Reply With Quote
  #38 (permalink)  
Old 10-23-2007, 10:07 PM
Active Member
 
Posts: 47
Default cant make work

Hillman, i cant make it work.
I am using the tar.gz you have posted.
In my blackberry 8700 using the sync4j-blabkberry 1.2
when i try to sync i get this in my phone: Synch failed. Error Sync Modification: Synchronization failde, connection broken
an in the server log:
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: XMLReponse: lifetime = 172800000
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: XMLReponse: sessionId = 56490
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: XMLReponse: pref = (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: Setting timezone to (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: XMLReponse: prefs = (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: XMLReponse: AuthResponse = (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: Init sync4j.zimbra.engine.source.ZimbraContactSyncSourc e with sourceUri: vcard
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: CachedSyncSource: datasource lookup
[Oct 23, 2007 10:47:06 PM][sync4j.zimbraConnector] FINEST: CachedSyncSource: datasource lookup done using java:comp/env/ prefix
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: ZimbraOfficer authenticate() Start
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: Username: juan.roig@globant.com
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: SENDING REQUEST: <ns0:AuthRequest xmlns:ns0="urn:zimbraAccount"><account by="name">juan.roig@globa
nt.com</account><password>XXXXXX</password><prefs><pref name="zimbraPrefTimeZoneId"/></prefs></ns0:AuthRequest>
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: sessionId = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: mbx = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: tags = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: grant = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: acl = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: link = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: link = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: folder = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: refresh = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: change = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: context = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: soap:Header = null
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: authToken = 0_64e0052312b28d185f9eb9d91e419e48cac5393a_69643d3 3363a30316337326664652d6
23134362d343066342d626133382d616530616565626139313 5373b6578703d31333a313139333337303238343937313b
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: lifetime = 172800000
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: sessionId = 56517
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: pref = (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: Setting timezone to (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: prefs = (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: XMLReponse: AuthResponse = (GMT-03.00) Buenos Aires / Georgetown
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: Init sync4j.zimbra.engine.source.ZimbraContactSyncSourc e with sourceUri: vcard
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: CachedSyncSource: datasource lookup
[Oct 23, 2007 10:50:59 PM][sync4j.zimbraConnector] FINEST: CachedSyncSource: datasource lookup done using java:comp/env/ prefix



And in my zibra server i see the auth successed
any ideas?
Reply With Quote
  #39 (permalink)  
Old 10-24-2007, 01:46 AM
Intermediate Member
 
Posts: 17
Default

Does this only work on the Network edition or does it work also on the opensource version?
Reply With Quote
  #40 (permalink)  
Old 10-24-2007, 11:20 AM
Moderator
 
Posts: 69
Default

It will work with either version. The connector just uses Zimbra's standard SOAP calls to communicate with the server.

Re: Blackberry sync problem. I don't see anything in that log that indicates why it's dropping the connection. But I also don't know whether the blackberry syncml client that's available actually works. I seem to remember reading somewhere that it doesn't, and a colleague of mine was unable to get it to work with Oracle's SyncML interface.

When I'm back at work next week, I'll get him to try his Blackberry against my Zimbra connector and see if we get any further than you did. In the meantime, you could try other SyncML clients (e.g. Outlook, Mozilla, etc) and see if you get any further.
Reply With Quote
Reply


Thread Tools
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

Zimbrablog.com




 

Search Engine Optimization by vBSEO 3.1.0