Thanks Patrick... Patrick Ohly <patrick.ohly@...> writes: > > On Wed, 2013-01-16 at 21:18 +0000, Gary wrote: > > Hi
> The Oracle Calendar is accessed via SyncML, right? Yes, Oracle Calendar is a syncML source. A couple more questions if I may.. r > > Right. Now also set databaseUsername and databasePassword for "@Google > calendar". > When you say add databaseUser and databasePassword, do I add these in the same line that I define the google calendar target-config settings as well as the database= and password= items? So, something like: syncevolution --configure calendar/backend=caldav username=<my google user> password=<my google password> calendar/database=https://www.google.com:443/calendar/dav/<calendarID>/events databaseUser=<my google user> databasePassword=<my google password> target-config@Google calendar Not sure I understand why I need to add it twice? > > 2) Create a sync profile that connects to the Oracle Calendar... > > No. Instead do it as quoted above. > So, like this: syncevolution --configure username=<my oracle username> password=<my oracle password> syncURL=<oracle calendar address> uri="./Calendar/Events?/dr(-14,60)" oracle@Google calendar If I ONLY ever want to copy events from oracle to google, am I right in assuming sync=one-way-from-server is correct here? Not sure I now know which end is regarded as client and which as server! Also assuming here that because I have named this oracle@Google, it knows to use the target-config@Google as the 'other' end of the sync? And to run the sync I run syncevolution oracle@Google Sorry for the multiple questions... Many Thanks Gary _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
