Tuesday Apr 26, 2011

Calendar Server for CALDAV Clients 7 Update 1: New Patch Available

Oracle Communications Calendar Server for CALDAV Clients 7 Update 1 has shipped a new patch (patch 3). The patch IDs by platform are:
  • Solaris: 142785-03
  • Solaris x86: 142786-03
  • Red Hat Linux: 142787-03

To obtain patches:

  1. Log in to support.oracle.com.
  2. Select the Patches and Updates tab.
  3. Type the patch id in the search box and Search for the patch.
    Selecting the patch will take you to the patch information page.
  4. Click the Download button.

Tuesday Oct 27, 2009

daBrain Scripting Export/Import of Calendar Server Data for Mac iCal

Why get bored with exporting/importing your calendar? From daBrain:

Export and Import is an easy way to get your Mac iCal up to date. But doing it manually is boring, therefor I thought it would be nice to have this scripted ...My result so far now is a small shell script which export your calendar from the Calendar Server, save it as export.ics and open iCal with the exported.ics file, you only have to click OK for the import.

Thursday Oct 22, 2009

CalDAV Support for Symbian OS

Sun Microsystems working on CalDAV support for Symbian OS.

Wednesday Oct 14, 2009

Calendar Server 7: Coexistence with Calendar Server 6

As the Calendar Server 7 docs state:

(you can)...set up Calendar Server 7 (CalDAV Server) in an existing Calendar Server 6 deployment, where calendar users exist on both the Calendar Server 7 and Calendar Server 6 environments. In such a deployment, you enable both freebusy lookup and iCalendar Transport-Independent Interoperability Protocol (iTIP) invitation between the two Calendar Server deployments. That is, users should have the capability to check freebusy information of users on any server, and the capability to invite any user. Invitations to users on a different server would be delivered by using iTIP.

Now, Andreas has some more info on this setup, here.

(Photo Credit: muhammad younas)

Thursday Oct 08, 2009

Calendar Server 7 Installation Experience

Interesting write-up by one of our TSC engineers, who just completed a Comms 7 Installation. Focus of the writeup is on our new product, Calendar Server 7.

Note: The single host deployment example (for SPARC), referenced in the above blog entry, is not yet publicly available. There is, however, this document for Red Hat Linux, that is available.

Wednesday Sep 23, 2009

Calendar Server 7: A Look at Sun's Upcoming CalDAV Release

Hat Tip DougG

It might not be widely known at this point, but Sun has been a leader in the CalDAV community, and our investments are about to pay off with the upcoming shipment of Calendar Server 7, included in the Communications Suite 7 release.

Sun is firmly committed to making CalDAV our calendaring protocol of choice. Sun has been very active in the CalConnect community to make sure that our CalDAV service interacts with other vendors and their services. Project Aries has been the name of Sun's CalDAV effort, and for the past year, we've enabled customers to get a taste of our technology through a hosted preview.

Why the need anyways for a CalDAV server?

The challenge in the calendaring space has always been about getting everyone to agree on a standard protocol that enables data to be exchanged between a calendar client and a calendar server, regardless of vendor. To date, we've been using the iCalendar data format for calendar and task data, as specified in RFC 2445. The good news has been that Sun and others have used this common data format. The bad news with this approach has been that, lacking a standard protocol, you end up using one big file to store all your calendar events. Reading calendar info may be fine, but making changes is not. Because your calendar database is essentially one big flat file, the only way a change can be made is for the client to upload a new version of a user's entire calendar data file and overwrite the copy on the server. That's a lot of data to move, for example, when all you have to do is push out a meeting change of one hour. The situation worsens if multiple users want to update a calendar. The last user to overwrite the copy on the server wins and changes other people have made are lost.

Having a real calendar access protocol would solve these problems and provide other nice features, such as calendar sharing, change logs, and free/busy lookups. The first attempt at such a protocol came in 1999 with the creation of the Calendar Access Protocol (CAP). WCAP, or Web Calendar Access Protocol, is an implementation of CAP over HTTP. Sun Java System Calendar Server 6.3 uses this protocol. Unfortunately, timing is everything. When the dot-com bubble burst, work on WCAP fizzled out. The result: Vendors went back to using their proprietary protocols.

Luckily, the situation did not remain the same. Though it took awhile, a new idea emerged to extend the WebDAV protocol to provide calendar specific support. The result was CalDAV and is documented in RFC 4791.

Of course, having an open protocol buys you nothing if vendors do not implement it in popular products. That is a big reason why CAP didn't take off. Fortunately, CalDAV seems to have gained enough momentum to stick around, as envinced by the CalConnect industry consortium, whose charter is to make sure CalDAV implementations work together and are widely adopted.

Yes, calendaring "nirvana" might still be a long way off, but we are getting closer with Calendar Server 7.

For more information on Calendar Server 7, see the following pages:

Wednesday Sep 03, 2008

CalDAV comes to Comms

Check out Project Aries.
Project Aries is the code-name for Sun's advanced calendar server based on CalDAV. As standards-based calendar usage increases, the ability to share calendars and support multiple calendar clients becomes increasingly important. Aries satisfies this need by introducing a standards-based calendar server that supports Apple iCal, Mozilla Lightning, and other standards-based clients. Project Aries is a key component of Sun Java Communications Suite. This Hosted Preview provides you the opportunity to view and test drive this new calendar server. While not all functionality is implemented yet, we want to share this exciting new product with you for your review and feedback.

Tuesday May 01, 2007

Calendar Protocol Faceoff

For those interested in calendar developments, head over to arnaudq's blog, where you'll find a great comparison of WCAP (Web Calendar Access Protocol,Sun's proprietary calendar protocol), and the proposed standard calendar protocol CalDAV. As Jim Parkinson pointed out here, we're looking at a "a calendar server based on the latest CalDAV standard."


Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.


« July 2016