Friday Aug 23, 2013

How the Project Was Documented

I happened today to come across the by-now-familiar-and-classic-to-many cartoon of project management, and have to say, the "How the project was documented" panel once again had me in stitches.

The great advantage of wiki publication, which we use for Communications Suite, is the ability to get beyond that "panel" and continually improve our documentation. With that in mind, I wanted to alert our Calendar Server users that I have completed a revamp of the Calendar Server 7 Command-Line Utilities page. Not only have I described some of the options more accurately now, but I think the page is more usable as I have moved deprecated options to a separate section at the end of the page.

As usual, feel free to leave a comment if  you have a documentation related question or idea for improvement.

Sunday Dec 09, 2012

Communications Suite: New Patches Available

Two new patches for the following Unified Communications Suite component products are now available:

  • Calendar Server 6.3 patch 53
  • Connector for Outlook 7.3 Update 1 patch 17

Download details:

Reminder: As a workaround to learning about new Communications Suite patches, you can use the Confluence watch feature to monitor the Communications Suite Component Patches page. When new patches are available, this page is updated with that information. You then receive an email message that this page has been updated. The watch feature is available under the Tools menu when you are logged in to wikis.oracle.com.

Friday Oct 19, 2012

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:

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:

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

Wednesday Sep 26, 2007

Sun Java System Calendar Server: Calling All Best Practices

Someone was asking recently about Calendar Server best practices information on one of the support aliases. So I went searching the Calendar Server documentation, and discovered this best practice tip:

Note –

Duplicate parameters are allowed in the ics.conf file. The system takes the value of the last instance of the parameter in the file.

Best Practices: To avoid confusion, add your customizations to the end of the file in a section you create for that purpose. For example, you can create a comment line with the following text: ! My ics.conf Changes. Then add any new parameters or any parameters that you are modifying, and their values. Add comments to each parameter describing why the change was made and add the current date. This will give you a history of the changes made to the system for later reference.

If you make extensive customizations, to improve processing efficiency, you might consider commenting out the original parameter that you are replacing. Also, periodically review the file, commenting out obsolete duplicate parameters.

Other BP tips that folks suggested include:

Take nightly backups then run csdb check on the backup DP, to capture any DB corruption.

Implement the Calendar Server automatic backup facility.

These were just a few tips that came up. Have a Calendar Server best practice? Feel free to add to this entry by posting in the Comments.

Friday Sep 14, 2007

Software Upgrades: Feeling the Pain

Our internal Sun Java System Calendar Server hosts (yes, we do use our own products) recently went through an upgrade, but alas, an error was encountered where email reminders were not getting sent out. As a Calendar Server end user, I was left to my own devices to discover this: and along the way, I found out just how much I've come to depend on this seemingly trivial technology to help drive my corporate life. Yes, I need those email reminders about upcoming meetings and events!

Now, granted this was a fairly trivial post-upgrade situation, and our IT folks quickly remedied the situation. Nevertheless, for all those who have had an upgrade bite you in the \*\*\*, I feel your pain.

About

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

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today