X

Recent Posts

Communications Suite 7

Unified Communications Suite Documentation: A New Direction

OTN Path Ahead With the availability now of Unified Communications Suite 7.0.6 (shipped on August 13), you'll notice that we are also transitioning to publishing product documentation on the Oracle Documentation Site (also referred to as Oracle Technology Network, or OTN), at: http://www.oracle.com/technetwork/documentation/oracle-communications-185806.html Scroll to the bottom of this page to view the links to the UCS documentation. For the Unified Communications Suite 7.0.6 release, documentation for the following component products is published to OTN: Connector for Outlook 8.0.2.2.0 Contacts Server 8.0 Instant Messaging Server 9.0.2.6.0 This documentation is only on OTN, and not on the Communications Suite wiki. You'll find pointers to this OTN documentation where you would normally expect to find it on the wiki. Suite-wide documentation for 7.0.6, as well as for the other component products (Messaging Server, Calendar Server, Indexing and Search Service, and so on) is updated on the wiki for this release. Thus, for this release, and perhaps one or two more, the Communications Suite documentation is on both the wiki and OTN. Going forward, we expect to get all of our documentation onto OTN. With that in mind, here is a mini-FAQ to help you with this new documentation direction: Why are we moving the UCS documentation to OTN?We are moving the UCS documentation to OTN where other Oracle documentation resides so customers are able to find our documentation where they expect it to be. The UCS documentation will also have the same look and feel as other Oracle CGBU documentation that our customers use, allowing for a common user experience across CGBU products. Will the CommSuite wiki go away?No. Previously released documentation will stay on the wiki. Can I still leave documentation comments?Yes. You can still log in to wikis.oracle.com and leave comments. By the way, OTN also enables you to email comments, which are forwarded to us.

OTN Path Ahead With the availability now of Unified Communications Suite 7.0.6 (shipped on August 13), you'll notice that we are also transitioning to publishing product documentation on the Oracle...

Messaging Server

Saving Time: Flip the Switch to Handle iMIP

Messaging Server 7 Update 5 and Calendar Server 7 Update 3 Combine to Process Calendar Invites Dalí Clockface by Philippe Halsman, 1953 As with any new release of software, there may be new features that don't immediately jump out at you or that fly under the radar. So here's one that might fall into that case for the Communications Suite 7 Update 4 release: you can configure Messaging Server and Calendar Server to automatically process calendar invitations from "external" users. By "external," we mean users who reside either on a different Calendar Server deployment administered by a separate group, or on an outside calendaring system, such as Exchange, Google Calendar, and so on. Technically, what we are talking about here is configuring Messaging Server to post a calendar event received in an iMIP (iCalendar Message-Based Interoperability Protocol) message to Calendar Server by using the iSchedule protocol. That way, users don't have to do any manual processing on the external calendar invite. The Calendar Server deployment automatically processes these invitations coming from external calendar systems, and to users, handling an external calendar invite then appears just like an calendar internal invite. Time saved, users more happy, what could be better than that? See the following documentation for more of the techie details and procedures to set up your Messaging Server 7 Update 5 deployment: Using the iSchedule Channel to Handle iMIP Messages

Messaging Server 7 Update 5 and Calendar Server 7 Update 3 Combine to Process Calendar Invites Dalí Clockface by Philippe Halsman, 1953 As with any new release of software, there may be new...

Messaging Server

Oracle Communications Messaging Server: To Compile or Not to Compile

Compiled Versus Non-Compiled MTA Configurations: Which Strategy Is Best? Recently, we had a discussion around the pros and cons of using a compiled MTA configuration for Messaging Server. What follows is a summary of this discussion, and also how this relates to the new Unified Configuration. Pros of using a compiled configuration: "The main reason for compiling configuration information is performance."In the past, say back in Messaging Server 5 days, this used to be important but with current releases is no longer a factor. "Configuration changes can be tested more conveniently because the configuration files themselves are not 'live' when a compiled configuration is in use."This is the main reason now for using a compiled MTA configuration. Cons of using a compiled configuration: Introduces some complexity in management. Non-MTA components do not share the same options with MTA components, so changing a compiled configuration could cause some components to be "live" (non-MTA) before others (MTA). This behavior is independent of the configuration type (legacy or Unified). On non-production systems, compiled configuration is probably not worth the additional overhead. Compiled configuration was the default prior to the Messaging Server 7 Update 4 release. So it is important for new installations (Messaging Server 7 Update 5) to understand whether to use a compiled configuration. Still, it seems likely that most sites would and should use a compiled configuration. The command imsimta cnbuild -remove causes a system to stop using a compiled configuration. To test configuration changes before committing them and going live, use the following command structure: imsimta test -rewrite -noimage_file you@example.com You can use the following flags to set the path to the configuration file: -configuration_file= -mapping_file= -option_file= These enable you to carefully clone then customize the configuration files before testing. About Unified Configuration Unified Configuration has the ability to save a history of changes and roll back to previous configurations. (See the msconfig history command). Thus, if an undesired configuration behavior takes place, even though a configuration may have passed its validity checks, you can still return easily to a previous configuration. Does Unified Configuration obsolete a compiled configuration? Not yet. Does not address the more complex issues of MTA configuration change coordination. You still need to coordinate multiple configuration changes and test them thoroughly prior to going live. Reference Compiling the MTA Configuration msconfig syntax

Compiled Versus Non-Compiled MTA Configurations: Which Strategy Is Best? Recently, we had a discussion around the pros and cons of using a compiled MTA configuration for Messaging Server. What follows...

Messaging Server

Oracle Communications Messaging Server: Tips to Get Started with Unified Configuration

Introduced in the latest Messaging Server release (7 Update 5 Patch 28), Unified Configuration offers up a more "unified" approach to administering your messaging configuration: You don't have to manage multiple configuration files with differing formats, and that you have to edit by hand (and so risk potentially causing an error): instead, you use one administrative tool, msconfig, and all legacy configuration files (with some small exceptions) are consolidated into three configuration files (config.xml being where most configuration data is stored). In addition, Unified Configuration performs validation checking to prevent introducing some configuration errors. You no longer have to deal with configuration settings that themselves are not that straight-forward, and in Unified Configuration, you can use the same settings for many options among the MMP, MTA, and message store configurations. Getting started with Unified Configuration, I found the following tips and information very useful: Use the configutil -H command to translate the legacy configutil option names to Unified Configuration names. For example: # configutil -H -o logfile.imap.expirytime Configuration option: logfile.imap.expirytime Unified Config Name: imap.logfile.expirytime Upgrading to Messaging Server 7 Update 5 (patch 28) does not mean that you HAVE to run Unified Configuration. You can upgrade and continue to run just as you are in legacy configuration. When/if you want to start using Unified Configuration, then you would use the configtoxml Command to update the configuration. You can run msconfig in either interactive or non-interactive mode. As I have been getting used to Unified Configuration, I find that using interactive mode is very helpful, as the parser lets you know if you have entered an incorrect syntax. Also, you don't have to accept the configuration change until you write it to the configuration. Getting more help: run the msconfig help command to get a list of online help topics. When you deal with editing blobs like channels, invoke the editor like this: msconfig edit channels, or for a specific channel, msconfig edit tcp_local. The msconfig edit command invokes the editor specified by the EDITOR shell variable. This is a much easier way to edit things than by trying to use an msconfig set command.

Introduced in the latest Messaging Server release (7 Update 5 Patch 28), Unified Configuration offers up a more "unified" approach to administering your messaging configuration: You don't have to...

Communications Suite News

Unified Communications Suite: Upcoming Training Opportunities

Learn How to Administer UCS, Troubleshoot Messaging Server, and Customize Convergence The following info comes my way via Jim Vonick, thanks Jim! Do you need to learn how to install, configure and administer Oracle Communications Unified Communication Suite?  Training is available through Oracle University in a Live Virtual Class format, which offers live instructor-led training with labs delivered over the Internet.  Classes are currently scheduled for the following courses: Unified Communications Suite Administration (5 day course): This course provides the necessary skills to administer Unified Communications Suite, including Messaging Server, Calendar Server, Instant Messaging Server, and Indexing and Search Service. First, understand the communications suite architecture and then learn how to install, configure, manage, and monitor the services. (Link: http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=609&get_params=dc:D73442GC10,p_preview:N&intcmp=WWOU12014584MPP023C002) Upcoming Classes: Starting June 3 and August 12 Messaging Server Administration and Troubleshooting (3 day course): This course teaches you how to administer Oracle Communications Messaging Server, including how to install, configure, manage, and monitor an email messaging service. (Link: http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=609&get_params=dc:D76263GC10,p_preview:N&intcmp=WWOU12014584MPP023C002) Upcoming Class: Starting August 28 Unified Communication Suite Convergence Customization (2 day course): This course enables you to effectively customize the Convergence client. Learn how to perform Convergence client customizations including working with themes, layout, CSS, localization, and adding new services to Convergence.  (Link: http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=609&get_params=dc:D73631GC10,p_preview:N&intcmp=WWOU12014584MPP023C002) See a list of all Oracle Communications classes at http://education.oracle.com/pls/web_prod-plq-dad/ou_product_category.getFamilyPage?p_family_id=41&p_mode=Training.

Learn How to Administer UCS, Troubleshoot Messaging Server, and Customize Convergence The following info comes my way via Jim Vonick, thanks Jim! Doyou need to learn how to install, configure and...

Communications Suite News

Unified Communications Suite Summit 2013

Reconnecting with Comms The UCS group gathered last week at our Santa Clara office for our annual Comms Summit. For me, it was a great opportunity to reconnect with Comms co-workers across all disciplines and geographies, and to participate in interactive sessions on the product. My boss and I did a preso on knowing the audience that you are writing for, which got me thinking about how to use the wiki to provide some "role-based" views of the information. For example, say you are new to UCS and you are looking for product overview and capability type information. What you want to see is different from say what a current user of the product might want. The current user might want a view that is weighted towards administration and troubleshooting. A third user, for example, a developer, might want a view that provides easy access to API and customization information. But, before charging ahead on seeing what it would take to get the wiki to do this, I got some other feedback: that some folks still appreciate just the PDF view of documentation. This audience (especially implementors) wants a standard spreadsheet of titles, such as Installation Guide, Administration Guide, and so forth, with the ability to see the title either in HTML (in our case, Wiki), or to download a PDF. So, What's The Takeaway? For the traditional PDF view, we do already cover the bases. You can use the Home2 view of the documentation to access the high-level doc titles by current release and product, and get a PDF. What about those of you who want more of a role-based view of the documentation? My first suggestion would be to provide some education on how to better search for what you want. Right now, my number one recommendation is to use this Google Custom Search Engine (GCSE) that I put together: Oracle Communications Unified Communications Suite Documentation Search The next step would be for me to try and do some doc rearchitecting to utilize the power of the wiki to carve out some distinct, separate role-based views. It occurs to me that a quick-and-dirty way of providing some role-based views would be to utilize the Confluence label feature and the content-by-label macro, to assemble some index-like pages.  So, as a UCS user, let me know if this is something that you would like to see. As always, either drop me a line or leave a comment.

Reconnecting with Comms The UCS group gathered last week at our Santa Clara office for our annual Comms Summit. For me, it was a great opportunity to reconnect with Comms co-workers across all...

Messaging Server

Email Phishing Casting Ever Longer Lines

Think Spam Has Gone Away? Guess Again. Osterman has another well-written post up, this time about the enhanced phishing technique referred to as "longline phishing." The term comes from commercial longline fishing, in which "...a main line of up to several miles in length contains hundreds or thousands of short lines with hooks, each loaded with their own bait." Email longline phishing tries to accomplish something similar by using high volumes, highly customized messages, and  zero-day exploits that bypass existing anti-virus methodologies. As Osterman says: "The genius behind the longline phishing attack is that a) volumes of any one message are extremely low, which makes recognition of these attacks difficult; b) overall volumes of messages received per potential victim are also low, often not triggering conventional anti-spam or anti-malware defenses; c) the attacks exploit vulnerabilities for which no defense is yet available; and d) botnets are used to distribute the attack across a wide range of sending IP addresses – one such attack, designed “Letter.htm” by Proofpoint, found in excess of 25,000 unique senders IPs in use." Longline phishing is also particularly effective because "the perpetrators will compromise legitimate Web sites to distribute malware in order to gain higher clickthrough rates from potential victims." Now, for you long-time savvy Unified Communications Suite administrators, this comes as no news. (Indeed, see my post from 2009: Email Phishing: Still a Big Problem.) But perhaps it has been a while since you have looked at your anti-spam setup and techniques, so as a reminder, I'll point you to the document, Protecting Against Spammers who Compromise Messaging Server User Accounts, for best practices on combating this issue. And go read Osterman's entire article, it's worth it. Bonus: I updated the Unified Communications Suite wiki tag cloud so that if you look under either antispam or spam, you can see at a glance all the related documentation on this topic.

Think Spam Has Gone Away? Guess Again. Osterman has another well-written post up, this time about the enhanced phishing technique referred to as "longline phishing." The term comes from commercial...

Documentation Issues

Unified Communications Suite: Creating Custom Applications Using ENS

Choosing the Correct Event Notification Service Documentation Recently we received an inquiry through the software forums about creating custom applications for Messaging Server dealing with message notifications. This started a conversation about the ENS documentation that I would like to clarify. Sidebar: Event Notification Services, ENS, is the underlying publish-and-subscribe service available in Messaging Server. ENS provides a server and APIs for publishers and subscribers. A publisher makes an event available to the notification service. A subscriber tells the notification service that it wants to receive notifications of a specific event. Going forward with Messaging Server 7 Update 4, you should be using the ENS C API as the simplest and most stable way to interact with events provided by Messaging Server. The ENS C API is documented in the Current Event Notification Service C API Reference page. And so we come to a source of confusion. The documentation for the older style API is still available on the Communications Suite wiki, and so if you search for say, "ENS API," you are likely to find it. I would link to it, but I really don't want to send anyone there. Indeed, that page will be removed shortly so as to not cause confusion anymore. Just to reiterate, use the ENS C API as documented in Current Event Notification Service C API Reference. I hope this helps move beyond the "clear as mud" situation that we sometimes find ourselves in.

Choosing the Correct Event Notification Service Documentation Recently we received an inquiry through the software forums about creating custom applications for Messaging Server dealing with...

Personal

The Demise of Email Has Been Prematurely Reported

source In 2009, I found many claims on the demise of email. Back then, my own, for-what-it-was-worth opinion was "no way." Perhaps that was a knee-jerk reaction on my part, or perhaps it was a statement that arose out of my own use and dependance upon email and I needed to deny the rise of social networks. Well, it now appears that those reports were perhaps just a bit exaggerated. According to Michael Osterman of Osterman Research, email is alive as ever, in fact, email use is up. Today he writes (emphasis mine): In the 2009 to 2011 timeframe, there were a number of articles in the trade and popular press about the demise of corporate and personal email.  Many believed that email use would dwindle as younger people entered the workforce, those weaned on social media and text messaging.  Email was for the “grups” (you’re welcome, original Star Trek fans), while newer forms of communication would replace it. Maybe someday, but not now.  We just completed a survey with corporate email users to determine if that was the case.  What we found is that 42% of email users are employing email more today than they were 12 months ago, while only 10% are using it less.  The remainder are using email at about the same level they were a year ago. Our research also found that email continues to be the dominant communication tool used in the workplace. Moreover, I completely agree with his statement that one of the reasons that email remains and grows in popularity is that it serves as a: ...repository of emails, contacts, files and other information that acts as something of a flat-file database in which we can store content that is easily searchable. This Is Where Indexing and Search Service for Oracle Communications Unified Communications Suite Comes In If you are like me, you not only need the ability to search the subjects and bodies of your email message, you need the ability to search your email attachments. Indeed, more and more, my email inbox has become my go-to storehouse of documents, spreadsheets, presentations, PDFs, and so on. So finding data, and finding it fast, is where email inboxes need to go. Which brings me to Oracle's Indexing and Search Service product. If you haven't heard by now, Indexing and Search Service enables you to quickly search and view your email attachments. Here are some cool facts about Indexing and Search Service: Integrated with our Messaging Server and Convergence products, enabling nearly instantaneous results from complex searches such as cross-folder searches. Because it is deployed as a separate service, the actual search effort is offloaded from Messaging Server. Any IMAP client that can communicate with Messaging Server can take advantage of this powerful search service. Rather than go on in more detail, refer to the following Indexing and Search Service blog posts and documentation links for more information. Indexing and Search Service: Time to Have the Talk ... Convergence: Viewing and Searching Attachments Overview of Indexing and Search Service Indexing and Search Service Deployment Planning Indexing and Search Service 1 Update 3 and 1 Update 4 Installation and Configuration

source In 2009, I found many claims on the demise of email. Back then, my own, for-what-it-was-worth opinion was "no way." Perhaps that was a knee-jerk reaction on my part, or perhaps it was a...

Documentation Issues

Unified Communications Suite: Wiki Documentation Changes

As longtime UCS-ers know, we have been providing wiki docs for many years now. One of the benefits of wiki docs is that writers can and do update content more frequently than with a static documentation environment. While this means that documentation issues get addressed more readily, it could also present a small problem in knowing when a doc (aka wiki page) has been updated. In addition, you might want to know not only that the page changed but how can you easily spot that change? Was the change cosmetic or substantive? And so on. In the interest of making this knowledge a bit easier to come by, and to highlight the continuing work that the UCS InfoDev team is putting into our documentation, here are a few ways in which you can determine when a doc has been updated: Look at the page history.On any page, from the Tools menu, select Page History. You then see a list of versions, dates, who made the change, and (hopefully) a comment on what was changed. For example, here is the page history for the Calendar Server 7 Administration Guide. Once you are on the Page History page, you can compare versions. Click the check boxes beside the versions you want to compare then click the Compare selected versions button. A quick and easy way to see what pages have changed recently is to choose Pages from the Browse menu, then select Recently Updated. You see a list of recently changed pages for the entire wiki space. This list is convenient in that you also get a view change link that takes you to a Page Comparison page, showing the changes. If you have a standard Oracle ID, you can "watch" a page and be automatically notified by email when a change occurs.To watch a page: Log in to wikis.oracle.com. Go to the page that you want to watch. Click the Tools drop down menu and select Watch.When we make a change to the page, wikis.oracle.com sends you an email. So there you have it. You now have all the info you need to stay up-to-date on our CommSuite wiki changes.

As longtime UCS-ers know, we have been providing wiki docs for many years now. One of the benefits of wiki docs is that writers can and do update content more frequently than with a static...

Documentation Issues

Communications Suite Documentation: Wiki Structure

From time to time, I get questions on how to find a particular piece of documentation on the Unified Communications Suite documentation wiki. So I thought it would be useful to give an explanation of our wiki structure and how to approach, at least on one basic level, looking for a particular document. In a nutshell, we have structured the Communications Suite documentation into two information buckets: "release-specific" content (Release Notes, New Features (formerly What's New), Installation Guides, and Upgrade Guides); and "non-release specific" content (Administration Guides, Developer Guides, Customization Guides, Tuning Guides, and the like). Release-specific content is always located on its own wiki space (in effect, its own web site), whereas the non-release specific content is always on the same "home" wiki space. In terms of URLs, what you have is this: Non-release Specific Content Release Specific Content https://wikis.oracle.com/display/CommSuite https://wikis.oracle.com/display/CommSuite7U2https://wikis.oracle.com/display/CommSuite7U1https://wikis.oracle.com/display/CommSuite7and so on... Thus, for each new Communications Suite release, such as Communications Suite 7 Update 2, we publish the aforementioned release-specific content on its own wiki space. The thought here is that customers appreciate having everything they need to install or upgrade a particular release in one location, and don't have to click around to get what they need. Nor do they want to be encumbered by other extraneous content that only gets in the way of the installation or upgrade process. Notice that the release specific content URLs follow the naming convention CommSuite<v>U<n>, where <v> is the major version and <n> is the update. So knowing that, if, for example, you wanted the release specific documentation for Communications Suite 6 Update 2, you now understand that you would use the following URL: https://wikis.oracle.com/display/CommSuite6U2. Simple, eh? On the other hand, when dealing with say, administration information, we made the decision to not publish a release-specific Administration Guide for each new Communications Suite version. This is different from other typical publishing environments, where you would expect a new Administration Guide to be published for each new release, even if little to nothing changed. Instead, in the Communications Suite world, you always go to the same guide (you don't have to look around for version x update y of the guide), whose URL remains the same. For example, the Calendar Server Administration Guide is located at https://wikis.oracle.com/display/CommSuite/Calendar+Server+7+Administration+Guide. So, how do you know if a change was made to a product feature and in what release, you ask? We use a versioning panel to indicate the introduction of a new feature, or a change to an existing feature. Here is an example from the Calendar Server Administration Guide: So, to summarize: If you want release notes, and installation and upgrade information, go to the release-specific wiki for the release that you need. For all other content, including administration, customization, developer, and tuning information, go to the "home" (non-release specific) wiki. One more note: The home Comms wiki space always has links to the current release specific documentation in the right-hand "Guides" panel. So that's another place to start looking for release notes, installation, and upgrade information.

From time to time, I get questions on how to find a particular piece of documentation on the Unified Communications Suite documentation wiki. So I thought it would be useful to give an explanation of...

Calendar Server

Oracle Communications Calendar Server: Upgrading to Version 7 Update 3

It's been some time since I have posted an entry. Now, with the release of Oracle Communications Calendar Server 7 Update 3, it seems high time to jump start this blog again. To begin with, check out what's new in this release: Authenticating Against an External Directory Booking Window for Calendars Changes to the davadmin Command Enable and Disable Account Autocreation LDAP Pools New Configuration Parameters New Languages New populate-davuniqueid Utility New Schema Objects Non-active Calendar Accounts Are No Longer Searched or Fetched Remote Document Store Authentication The upgrade is a bit more complicated than normal, as you must first apply some new schema elements to your Directory Server(s). To do so, you need to get the comm_dssetup 6.4 patch, patch the comm_dssetup script, and then run the patched comm_dssetup against your Directory Server(s) instances. In addition, if you are using the nsUniqueId attribute as your deployment's unique identifier, you'll want to change that to the new davUniqueId attribute. Consult the Upgrade Procedure for details, as well as DaBrain's blog, before forging ahead with this upgrade. Additional quick links: Problems Fixed in This Release Known Issues Calendar Server Unique Identifier Changes to the davadmin command Get the Calendar Server patch Get the comm_dssetup patch

It's been some time since I have posted an entry. Now, with the release of Oracle Communications Calendar Server 7 Update 3, it seems high time to jump start this blog again. To begin with, check out...

Communications Suite 7

Oracle Communications Unified Communications Suite 7 Update 2 Ships

In case you hadn't heard, Oracle Communications Unified Communications Suite has released its latest version, 7 Update 2, and it's available for download from the Oracle Software Delivery Cloud. Highlights for this release include the following: Oracle Communications Calendar Server Support for Oracle DB 11g release 2. Outlook connectivity offered via Outlook Connector has been enhanced to support Calendar Server 7 Update 2 (through the WCAPbis protocol). Support for both Apple iCal and Microsoft Exchange Style Delegation models enables users to share their calendars and delegate calendar management to others. Support for certificate based authentication for use in secure environments, as well as support for virus scanning of attachments included with events and appointments. Oracle Communications Instant Messaging Server Support for external IM networks, including real time Instant Messaging and Presence connectivity, for Yahoo, AOL, MSN, Google, and Facebook. Federation with SIP/SIMPLE based IM networks. Indexing and Search Service for Unified Communications Suite has been enhanced to deliver a more highly available and reliable service. Here's a set of links to get you started: What's New Release Notes Get the Software

In case you hadn't heard, Oracle Communications Unified Communications Suite has released its latest version, 7 Update 2, and it's available for download from the Oracle Software Delivery Cloud. Highlig...

Communications Suite News

Oracle Communications Unified Communications Suite Legacy Documentation Gets a New Home

Still looking to docs.sun.com  for Communications Suite legacy documentation and information? As of last week, this documentation has been migrated to the Oracle Documentation site. But of course, information on the Comms Wiki is still in place and continues to be the site for new documentation. Unfortunately, you currently need to know the direct link to find this legacy documentation. We are in the process of correcting this situation. In the meantime, use the following table to get the direct link to the legacy documentation that you are looking for. Update, 2/1/11: Added links to Japanese translations at the end of this table. Library Name New Url Calendar Server http://download.oracle.com/docs/cd/E19057-01/index.html iPlanet Calendar Server 2.0 http://download.oracle.com/docs/cd/E19207-01/index.html iPlanet Calendar Server 2.1 http://download.oracle.com/docs/cd/E19697-01/index.html iPlanet Calendar Server 5.0 http://download.oracle.com/docs/cd/E19222-01/index.html iPlanet Calendar Server 5.1 http://download.oracle.com/docs/cd/E19605-01/index.html Messaging Server http://download.oracle.com/docs/cd/E19079-01/index.html Oracle Communications Unified Communications Suite Version 7 Update 1 http://download.oracle.com/docs/cd/E19143-01/index.html SJS Instant Messaging 7 2006Q1 http://download.oracle.com/docs/cd/E19812-01/index.html Sun Calendar Server 1.0 http://download.oracle.com/docs/cd/E19184-01/index.html Sun Java Communications Suite http://download.oracle.com/docs/cd/E19299-01/index.html Sun Java Communications Suite 5 http://download.oracle.com/docs/cd/E19566-01/index.html Sun Java Communications Suite 6 http://download.oracle.com/docs/cd/E19799-01/index.html Sun Java Communications Suite 7 http://download.oracle.com/docs/cd/E19516-01/index.html Sun Java Enterprise System 2003Q4 http://download.oracle.com/docs/cd/E19199-01/index.html Sun Java Enterprise System 2004Q2 http://download.oracle.com/docs/cd/E19263-01/index.html Sun Java Enterprise System 2005Q1 http://download.oracle.com/docs/cd/E19396-01/index.html Sun Java Enterprise System 2005Q4 http://download.oracle.com/docs/cd/E19636-01/index.html Sun Java Enterprise System 5 http://download.oracle.com/docs/cd/E19528-01/index.html Sun Java Enterprise System 6 http://download.oracle.com/docs/cd/E19316-01/index.html Sun Java Enterprise System 7 http://download.oracle.com/docs/cd/E19575-01/index.html Sun Java System Calendar Server 6 2004Q2 http://download.oracle.com/docs/cd/E19559-01/index.html Sun Java System Calendar Server 6 2005Q1 http://download.oracle.com/docs/cd/E19955-01/index.html Sun Java System Calendar Server 6 2005Q4 http://download.oracle.com/docs/cd/E19305-01/index.html Sun Java System Calendar Server 6.0 http://download.oracle.com/docs/cd/E19875-01/index.html Sun Java System Calendar Server 6.3 http://download.oracle.com/docs/cd/E19653-01/index.html Sun Java System Communications Express 6.3 http://download.oracle.com/docs/cd/E19284-01/index.html Sun Java System Instant Messaging 6 2004Q2 http://download.oracle.com/docs/cd/E19577-01/index.html Sun Java System Instant Messaging 6.1 http://download.oracle.com/docs/cd/E19950-01/index.html Sun Java System Instant Messaging 7 2005Q1 http://download.oracle.com/docs/cd/E19610-01/index.html Sun Java System Instant Messaging 7.0.1 2005Q4 http://download.oracle.com/docs/cd/E19154-01/index.html Sun Java System Instant Messaging 7.2 http://download.oracle.com/docs/cd/E19893-01/index.html Sun Java System Messaging Server 6 2004Q2 http://download.oracle.com/docs/cd/E19522-01/index.html Sun Java System Messaging Server 6 2005Q1 http://download.oracle.com/docs/cd/E19142-01/index.html Sun Java System Messaging Server 6 2005Q4 http://download.oracle.com/docs/cd/E19796-01/index.html Sun Java System Messaging Server 6.0 http://download.oracle.com/docs/cd/E19752-01/index.html Sun Java System Messaging Server 6.3 http://download.oracle.com/docs/cd/E19563-01/index.html Sun ONE Calendar Server 5.1.1 http://download.oracle.com/docs/cd/E19258-01/index.html Sun ONE Instant Messaging 6.0.1 http://download.oracle.com/docs/cd/E19195-01/index.html Sun ONE Messaging Server 5.2 http://download.oracle.com/docs/cd/E19444-01/index.html iPlanet Delegated Administrator 4.5 iPlanet Messaging Server 5.0 iPlanet Messaging Server 5.1 Netscape Collabra Server Netscape Messaging Server 3.0 Netscape Messaging Server 3.5 Sun Internet Mail Server 3.5 Sun Internet Mail Server 4.0 Sun Java System Connector for Microsoft Outlook 6.0 Sun ONE Synchronization 1.1 http://download.oracle.com/docs/cd/E19957-01/index.html Japanese TranslationsiPlanet Messaging Server 5.2 Admin Guide JAiPlanet Messaging Server 5.2 Admin Reference JASun Java System Messaging Server 6.3 Admin Guide JA http://download.oracle.com/docs/cd/E19957-01/816-5017-01/ http://download.oracle.com/docs/cd/E19957-01/816-6005-10/contents.htm http://download.oracle.com/docs/cd/E19299-01/820-0511/index.html

Still looking to docs.sun.com  for Communications Suite legacy documentation and information? As of last week, this documentation has been migrated to the Oracle Documentation site. But of course,...

Calendar Server

Oracle Communications Calendar Server(s) - Which One For You?

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: Calendar Server 6 and Calendar Server 7 Comparison and Coexistence  Calendar Server 7 Update 1 What's New Installation Scenario - Oracle Communications Calendar Server for CALDAV Clients

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...

Communications Suite 7

Sun Convergence: Viewing and Searching Attachments

Hat Tip Bill A. Attachment View in Convergence This is very cool. The new update to Sun Convergence, Convergence 1 Update 3 (shipping as part of Communications Suite 7), in conjunction with our new Indexing and Search Service 1 product, presents users with a grid of attachments in their email. (Click image at left for larger view.) In a nutshell, here's how all this functionality comes together: - The ISS server "collects" all the attachments across all a user's email.- The Convergence client displays a new virtual folder, “Attachments," in the folder tree for this collection.- Convergence presents the attachments in three views. (This image shows the grid view.)- Users can search the attachment list by filtering mechanisms (see below).- Operations for viewing the message the attachment belongs to and creating a message with a selected attachment are available.- Note: If ISS is not deployed, this feature is not presented. Filter View of Attachments in Convergence Here's a view of the Convergence Filter Attachments (click image at right for larger view). You can filter your search based on the sender of the attachment, adate range when you received the attachment, or the type of file thatyou are searching. This image is showing how to filter by sender. In the filtered view, you still have the capability for viewing the message the attachment belongs to and creating a message with a selected attachment. Film Strip View of Attachments in Convergence As the image to the left shows (click for larger view), you can also view attachments in film strip mode. The film strip is displayed on right-hand side, you can arrow or mouse down, select one by one, and the selection is displayed in the middle of the Convergence UI. Convergence also supplies a slideshow view, which takes over the entire browser. Controls are displayed at the bottom for navigating through attachments left and right, as well viewing them on a timed basis (that is, using a timer to view them). Searching Attachments By Using ISSWhen you do a search from the attachments grid, one choice is to search by body. By using ISS, you get to have a fast body search, which is more than just a body search, your attachments are searched as well. And if you're like me, I have tons of attachments in email that I'm constantly looking for. Attachments can be in a variety of formatssuch as PDF; Microsoft Word, Excel, PowerPoint, and Visio;StarOffice/Open Office; HTML; and more.

Hat Tip Bill A. Attachment View in Convergence This is very cool. The new update to Sun Convergence, Convergence 1 Update 3 (shipping as part of Communications Suite 7), in conjunction with our new Ind...

Communications Suite 7

Sun Java Indexing and Search Service: Time to Have the Talk

Hat Tip Jeff A. Looking to get the most out of your email inbox? Then you'll want to have at look at Sun Java Indexing and Search Service 1, shipping as part of the newly released Sun Java Communications Suite 7. The Email Inbox, Your De Facto Database: So Search Is Your De Facto Navigation Companies and enterprises all over know the hard facts: their data sets are growing at an exponential rate. Thus, one of their most important business needs is finding data. Enter Search as the de facto method of navigating large amounts of data. And with email becoming personal data stores for all kinds of info--text, video, spreadsheets, presentations--searching inboxes becomes an all important activity. Search makes navigation easier. Saved searches can become virtual folders. And with Indexing and Search Service, you make all of that data available and accessible that right now, is either stuffed away in one of hundreds of folders or attached to an email and so not able to participate in searches. Architecture Overview ISS Key Capabilities Open search interface Standards-based RESTful web service supporting JSON; search feeds available via RSS/ATOM You are not limited to the client connections supported out-of-the-box Real-time indexing of content Sun Java System Messaging Server generates events that trigger updates of ISS indexes Built for both vertical and horizontal scalability Supports a variety of data types out of the box, including OpenOffice, MS Office, PDF, JPEG, HTML, XML, plain text, vCard Attachment thumbnail images generated and can be returned in search results.  ISS Benefits Multi-folder search is fast Integration with Sun Java System Messaging Server means faster search without any change in user behavior Expensive body search operations are offloaded from the messaging server Context-aware search means that the content is searched, not the markup Great variety of search facilities: fuzzy, near, and wildcard searches, search by attachment type. What Clients Can You Use? Convergence 1 Update 3 Integrated with attachment view IMAP Server Sophisticated searches that are completed very quickly Search inside attachments, search based on date or sender, and so on Arbitrary client Consumes RESTful web services For More Information See the Indexing and Search Service Documentation.

Hat Tip Jeff A. Looking to get the most out of your email inbox? Then you'll want to have at look at Sun Java Indexing and Search Service 1, shipping as part of the newly released Sun...

Communications Suite 7

Communications Suite 7: Installation Tips

Hat Tip David L. I attended a webinar today on the Communications Suite 7 installer. Passing along some notes. Installation Is a Two-Step Process Remember that in the Comms world, "installation" consists of installing the software bits and then configuring them. The Communications Suite installer only lays down the software bits. It does not configure them. Eachindividual Communications Suite component product has its own configurator that you then run. We wanted to separate thesetwo steps for robustness, as configuration is where the majority of thework actually occurs in a Comms installation. 32-Bit Versus 64-Bit In Communications Suite 7 and going forward, Messaging Server on Solaris (SPARC and x86) is only available in 64-bit. Messaging Server is only in 32-bit for Red Hat Linux (no 64-bit support yet, this is forthcoming, but no timeframe). Also, Messaging Server has dropped support for Solaris OS 9, Solaris OS 10 32-bit, and Red Hat Linux 3. Installation for Power Users Power users: You can use --OSversionOverride switch to install some Communications Suite component products on Solaris OS 9 or other dropped platforms. See http://wikis.sun.com/display/CommSuite7/commpkg+-+General+Syntax+and+Commands for more information. Note that you will only see the products that are runable on that OS platform. Forexample, you wouldn't see Indexing and Search Service 1 nor Calendar Server 7 on Red Hat Linux 4 32-bit, because those two new component products arenot officially supported on that platform. On Solaris OS 9 SPARC, the Communications Suite installer would not show you you MessagingServer 7 Update 3. And so on. Where's Communications Express 6.3? Going forward, Communications Express is deprecated in favor of Convergence, so you will not see it in the Communications Suite 7 installer. Communications Express is still supported. If you are looking to install Communications Express now, I guess you'd need to get the Communications Suite 6 Update 2 bits. New Component Products Brand new in this release: Calendar Server 7 (our CalDAV product), and Indexing and Search Service 1 (gives you the ability to index and then search your email attachments). Note that you'll continue to see Calendar Server 6.3 in the Communications Suite 7 installer, as Calendar Server 7 is not yet supported by Convergence. Also of interest. You can have a coexistent deployment of Calendar Server 7 and Calendar  6.3. See http://wikis.sun.com/display/CommSuite/Creating+a+Calendar+Server+6+and+Calendar+Server+7+Coexistent+Deployment for more information. Calendar Server 7 uses MySQL as its backend, and the Communications Suite installer treats it as a shared component. The CI checks if there is an existing MySQL version but will not upgrade oruninstall MySQL. If that's your case, you'll need to refer to the MySQL docs on how to upgrade or uninstall. Installing Just a Calendar Server 7 Back End It's a bit tricky, but doable: See http://wikis.sun.com/display/CommSuite7/Communications+Suite+7+Installation+Scenario+-+Calendar+Server+7 for more information. Basically, you preface the Calendar Server 7 component with a tilde (~) to just install its dependent component products, which in this case is just MySQL.

Hat Tip David L. I attended a webinar today on the Communications Suite 7 installer. Passing along some notes. Installation Is a Two-Step Process Remember that in the Comms world, "installation"...

Communications Suite News

Communications Suite 7 On the Horizon

The next update to Sun Java Communications Suite is getting close to shipping. Communications Suite 7 includes both new products and feature enhancements to existing products. Here's a quick look at what's new: What's New in Sun Convergence 1 Update 3What's New in Messaging Server 7 Update 3What's New in Calendar Server 7What's New in Calendar Server 6.3What's New in Indexing and Search Service 1What's New in Instant Messaging 8 Update 2What's New in Delegated Administrator 7What's New in Connector for Outlook 7.3 Update 1 What's New in Sun Convergence 1 Update 3 Convergence 1 Update 3 includes the following changes and new features: POP Access to External Email Sender Identities Single Click Creation of Events Attachment Search Autocomplete Addresses from Corporate Directory Multiple Select in Address Book Support for Internet Explorer 8 Single Click Selection of all Messages Exporting Selected Entries from Address Book Toolbar Changes Address Book Notifications Group-wise Listing of Configuration Parameters Support for Sun GlassFish Enterprise Server 2.1 Anti-Spam Functionality What's New in Messaging Server 7 Update 3 Messaging Server 7 Update 3 includes the following changes and new features: Red Hat Enterprise Linux 5 Support Elimination of setuid binaries from Messaging Server pipe_master and l_master Running the Directory Server Setup Script ( comm_dssetup.pl) Required What's New in Calendar Server 7 Calendar Server 7 includes the following new features: CalDAV Support iCal Support Authentication Scheduling Support WebDAV Sync Free-Busy Servlet Installation and Configuration Logging Service Notifications Admin Servlet Administrative Utilities Administrators Group LDAP Integration Collection tag or ctag Support for Multiple Back-end and Front-end Servers to Achieve Horizontal Scalability Hosted Domains CalDAV Support Calendar Server 7 provides support for the calendaring extension to WebDAV as defined in RFC 4791.The CalDAV draft extends the basic HTTP and WebDAV commands to enableall the functionality required for calendaring and schedulingactivities. Included in Calendar Server 7 is support for the following: PUT, POST, GET, MULTIGET, REPORT, HEAD, OPTIONS, PROPFIND, and PROPPATCH methods MKCALENDAR method, for creating multiple calendars per user Enhancedquery reports, to both return recurring events and tasks in expandedform (in UTC), and to return only requested properties or parameters iCal Support Calendar Server 7 supports the iCalendar data format as defined in RFC2445bis. The following components are supported: VEVENT VTODO VFREEBUSY VTIMEZONE VALARM Recurring rules and exceptions are also supported. Authentication Calendar Server 7 supports basic HTTP authentication andauthentication over SSL. With HTTP authentication you can do thefollowing: Restrict access to authenticated users only Provide userid and password and execute commands on a calendar Scheduling Support Calendar Server 7 supports scheduling as defined in Version 04 of the CalDAV Scheduling draft.This specification defines explicit scheduling, where invitations andreplies are placed in the recipient's inbox. It is then the client'sresponsibility to view and move them to the appropriate calendars. Thelatest version of the draft, which defines implicit scheduling, will beimplemented in a future release. The following list provides more information about scheduling support in Calendar Server 7: Free-busy queries on attendees. Calendar-outbox and calendar-inbox for every user, as well as the ability to use the POST command for invitations and replies. iTIP and iMIP protocols, as defined in RFC 2446 and RFC2447. Invitation emails are sent out for recipients without accounts on the calendar server, with all event details. iScheduleprotocol, which enables Calendar Server to act as a client and performscheduling with servers from other products that support iSchedule. WebDAV Sync Calendar Server 7 supports WebDAV Sync, an extension of the WebDAV protocol as described in the WebDAV Sync draft.WebDAV Sync defines a protocol for an HTTP client to query an overviewof the data changes on the HTTP server. The result is that clients canefficiently synchronize their local data cache with the server. Free-Busy Servlet Calendar Server 7 provides a free-busy servlet to enable non-CalDAVclients to at least check users' freebusy information by using theupcoming free-busy-read URL standard. This standard is compatible withthe free-busy URLs used by Calendar Server 6.0 through Calendar Server6.3. Installation and Configuration You install Calendar Server software by using the CommunicationsSuite installer. You then configure a Calendar Server instance by usingthe init-config configurator, which makes configurationsettings for your Directory Server, GlassFish Enterprise Server, andCalendar Server (DAV server) hosts. In addition, Sun Service Tagsare used solely to identify Sun products to Sun. Sun uses service taginformation to better support you. Registration data is only collectedwhen your system administrator requests gear discovery. Calendar Server7 enables you to use the Service Tag Facility on Solaris OS 10. Logging Service The Calendar Server 7 logging service is a multilevel, configurable,logging module to help capture activity or debugging issues. Notifications Calendar Server 7 provides Java Message Service (JMS) notificationsand email notifications for database changes and event or task emailalarms. You can configure the server to produce JMS notifications forevery database change and every alarm. If you choose, you can writeyour own subscribers to these notifications. In addition, CalendarServer 7 provides a subscriber program, which you can configure, thatconsumes the JMS notifications and sends email for database changes andemail alarms. Admin Servlet Calendar Server 7 contains an admin servlet, providing a webinterface with which you view and even delete contents in yourcollections. You can also use the admin servlet to import iCal data tospecific calendar collections. Administrative Utilities By using the davadmin command, you can perform the following tasks: Obtain server version information Read and modify the server configuration Obtain, modify, or delete information about user collections and resources You can use Jconsole to perform these tasks. Calendar Server 7 also provides database utilities to back up and restore calendar collections. Administrators Group A predefined Admin group in LDAP is created during initialconfiguration, to which you can can add users for proxy login andmanagement of any user account. The default administrator user addedduring initial configuration is calmaster. LDAP Integration Calendar Server 7 uses Directory Server with the latestCommunications Suite schema to store and manage user information in itsLDAP database. Support includes: Capability of obtaining principal information from LDAP Capability of matching principals to their calendar collections Use of LDAP information for auto-creation of basic calendars on login or invitation Use of LDAP caching for faster lookup results Use of LDAP rollover support to use a backup LDAP server if primary LDAP server is not available Collection tag or ctag Calendar Server 7 supports "Calendar Collection Entity Tag (CTag),"an extension to CalDAV that provides a fast way for a client todetermine if the contents of a calendar collection have changed. Support for Multiple Back-end and Front-end Servers to Achieve Horizontal Scalability The Calendar Server 7 architecture enables you to deploy multiplefront-end calendar servers and multiple back-end mySQL database serversto achieve horizontal scalability. See Calendar Server Logical Architecture for more information. Hosted Domains Like the rest the the Communications Suite products, Calendar Server7 supports virtual domains, also called hosted domains, which is theability to support users in more than one domain, on a singledeployment. A default domain is configured during the initialconfiguration. What's New in Calendar Server 6.3 This version of Calendar Server 6.3 includes bug fixes only. What's New in Indexing and Search Service 1 Indexing and Search Service 1 includes the following new features: Index Search Indexing and Search Service and Convergence Index Rapid Indexing of Existing Email: Email messages in auser's mailbox can be indexed. During this operation content is taggedin various ways to enable sophisticated searches. Real-time Indexing:As email messages are received, sent, and moved to various folders, theindex is updated in real-time. This reduces to near zero the chances ofa false search result based on stale index information. Search Attachment Search: Users can search the body ofattachments for keywords or phrases. Attachments can be in a variety offormats such as PDF; Microsoft Word, Excel, PowerPoint, and Visio;StarOffice/Open Office; HTML; and more. Body Search:Users can search the body of a message for any relevant content. WithIndexing and Search Service, body search includes search of supportedattachment types as well as the plain text body of a message. Search Integration with Sun Convergence:Indexing and Search Service integrates with Convergence through itsexisting search interface. Body searches are much faster and morepowerful because they now not only search message text but alsoattachment contents. Search Integration with Messaging Server:Other email clients can leverage improved body search and expandedattachment body search by using Messaging Server's IMAP searchintegration with Indexing and Search Service. The underlying searchmechanism is transparent to a Messaging Server client. RESTful Search Web Service API:Based on the OpenSearch 1.1 specification, the RESTful Search WebService API provides RSS 2.0, Atom 1.0 or JSON format output. Thisinterface is used by Messaging Server when it redirects IMAP SEARCHrequests to Indexing and Search Service and by the sample search userinterface. It can also be used by developers to mash up their emailsearch results with other applications if desired. Indexing and Search Service and Convergence ISS integrates with Convergence through its existing searchinterface, that is, Convergence continues to execute searches by usingthe compact WMAP protocol with the mshttpd daemon. The mshttpddaemon continues to service these requests by using the IMAP protocol.Messaging Server integrates with ISS through an enhanced IMAP SEARCHfunctionality, and a subset of these search requests (particularly,body searches) go to ISS for fulfillment. Messaging Server consumes theISS output and reformats it for the email client. The result is that no changes are needed to Convergence orThunderbird clients because ISS integrates with Messaging Server ratherthan the end-client. The long-term plan for integrating Convergence and Thunderbird(through a plug-in) with ISS will be to have the clients communicatedirectly with ISS directly by using ISS's RESTful web service forsearch. What's New in Instant Messaging 8 Update 2 Instant Messaging 8 Update 2 includes the following changes and new features: Using Shoal for Automatic Discovery of Peer Servers in a Pool Support for Red Hat Enterprise Linux 5 What's New in Delegated Administrator 7 Delegated Administrator 7 includes the following changes and new features: Provisioning for Calendar Server Users Provisioning for Calendar Server Users Delegated Administrator 7 now supports Calendar Server 6.x andCalendar Server 7 provisioning. What's New in Connector for Outlook 7.3 Update 1 This version of Connector for Outlook 7.3 Update 1 includes the following new features: Viewing Quota and Size Information Saving File Attachments in Optimized Mode

The next update to Sun Java Communications Suite is getting close to shipping. Communications Suite 7 includes both new products and feature enhancements to existing products. Here's a quick look...

Calendar Server

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

Hat Tip DougGIt 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:Introduction to Calendar Server 7Calendar Server 6 and Calendar Server 7 Comparison and CoexistenceCalendar Server 7 What's NewComplete list of Calendar Server 7 documentation

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,...

Oracle

Integrated Cloud Applications & Platform Services