Oracle Communications Unified Communications Suite (formerly Sun Java Communications Suite) has been providing calendaring services for many years. What might have flown under the radar is that the latest version, known first as Calendar Server 7 and then rebranded to Oracle Communications Calendar Server for CALDAV Clients, supports the CalDAV protocol, the calendar access protocol standard. By supporting the CalDAV protocol, Calendar Server 7 enables you to use CalDAV-enabled devices, like the Apple iPhone, as your calendar client.
What this also means is that Communications Suite actually currently contains two calendar servers: the original, Sun Java System Calendar Server 6 (now rebranded to Oracle Communications Calendar Server), and the new, updated version, Calendar Server 7/OCCS for CALDAV Clients. So, when it comes to making your deployment choice, which calendar is best for you?
If you are performing a fresh, greenfield installation of Communications Suite, and you plan on using only CalDAV clients, or the Convergence 2 web client, deploy Calendar Server 7 (the current version is 7 Update 1). The Convergence 2 web client, as of the Communications Suite 7 Update 1 release, is now integrated with Calendar Server 7 Update 1.
If you have an existing Calendar Server 6.3 deployment, you can use the OCCS for CALDAV Clients migration utility to migrate your data to the new format used by Calendar Server 7 Update 1.
If you have an existing deployment depending upon Connector for Microsoft Outlook clients, you'll need to continue to use the older calendar product, SJS Calendar Server/OCCS 6.3. Eventually, you want to deploy the new OCCS for CALDAV Clients, as Calendar Server 6.3 has been deprecated. However, to support Connector for Microsoft Outlook, Connector needs to come out with support for the WCAPbis protocol. OCCS for CALDAV Clients includes WCAPbis support as of the current release (7 Update 1). Now we have to wait for Connector to do the same.
For more information, see the following documentation: