Welcome Guest! To enable all features please Login or Register.



Go to last post Go to first unread
#1 Posted : Wednesday, November 2, 2011 12:28:08 AM(UTC)

Rank: Administration

Groups: SyncJob Calendar Moderator, Administrators
Joined: 9/13/2011(UTC)
Posts: 160

Thanks: 5 times
Was thanked: 2 time(s) in 2 post(s)
The command line version of SyncJob Calendar is ideal to schedule an automatic synchronization. It's a bit harder to set up than the UI version, but uses the exact same synchronization engine. The command line version does not have configuration files that store the links. You have to specify one link at the time use the command-line switches. One run will synchronize one pair of calendars.

What does it share with the UI version?
It shares the DAT files, with exception of the passwords that are in there.

What are DAT files
A DAT files contains a number of timestamps that say something about the last synchronization. There is 1 DAT file per GW-calendar/Google-calendar combination. It contains the timestamp of the last synchronization, and the last time horizon (start/end of the calendar it has seen). It helps the SyncJob engine to know which meetings were removed and which need to be created, so if you use the UI and command-line versions together, its important that they share the DAT files.

What about the settings in the Config folder?
Those are strictly for the UI version only.

What command line options are there?
-gwu=[GroupWise Username]
Username of GroupWise user without domain.

-gwp=[GroupWise Password]
Password of GroupWise user

-gws=[GroupWise Server]
Hostname of GroupWise server

-gwc=[GroupWise Calendar]
Optional, name of Goupwise calendar. default: 'Calendar'

Optional, include GroupWise subcalendars, default: true

Optional, include pending appointments/invites, disables MultiLogin! default: false Requires -gda to be set to true!

-gdu=[Google Username]
Google username, typically xxx@gmail.com

-gdp=[Google Password]
Google password

-gdc=[Google Calendar]
Name of Google calendar

Specifies wether the participants of appointments should be written to Google Calendar or not. default: false. This option is required in order to make accept/decline of appointments in Google possible.

Enable storage of password, default: true

syncjobcalendar.exe -gwu=username -gwp=xxxxx -gws=gwserver -gwc=Calendar -gwm=false -gdu=myaccount@gmail.com -gdp=xxxx -gdc=Work -gdi=true

This line synchronizes the Groupwise main calendar ("Calendar") with the Google Calendar named "Work". Any GroupWise subcalendars are not included in the synchronization. Invitations (unaccepted appointments) are included in the synchronization and will show up as invite in the Google "Work" Calendar (AND in the Google Main calendar)

How does the password storage work
By default, SyncJob will store the password in the DAT file. If you have run SyncJob Calendar successfully once (for a specific Groupwise Calendar/Google Calendar combination) it will store the passwords and you don't need to specify them again (you can simply omit the -gwp and -gdp command line switches). If you don't want the passwords to be stored, you can use the command line switch -sps=false.

What about the encryption?
The passwords are stored using TripleDES. Obviously, the encryption key needs to be stored in the SyncJobCalendar.exe executable, but it's not in there in plain text. SyncJobCalendarUI.exe uses a different key, which is also stored in the executable in an obfuscated way.

Edited by user Tuesday, April 10, 2012 10:48:09 AM(UTC)  | Reason: Not specified

Niels Schoot
Syncjob Developer
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.