Chapter 1 Common Release Information for Sun Java Communications Suite 6 Component Products

This chapter contains important release information that is common for all component products of Sun Java Communications Suite 6.

These release notes contain the following sections:

Third-party URLs are referenced in this document and provide additional, related information.

Note Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

About Sun Java Communications Suite, Version 6

The Sun Java Communications Suite integrates a number of Sun server and client products to support distributed communication and collaboration applications.

The Sun Java Communications Suite 6 release includes the following components:

• Sun Convergence 1.0 Release Notes
• Sun Java System Calendar Server 6.3 Release Notes
• Sun Java System Messaging Server 7.0 Release Notes
• Sun Java System Instant Messaging 7.3 Release Notes
• Sun Java System Delegated Administrator 6.4 Release Notes
• Sun Java System Communications Express 6.3 Release Notes
• Sun Java System Connector for Microsoft Outlook 7.3 Release Notes
• Sun Java System Communications Sync 3.1

The Release Notes for Sun Java System Communications Sync 3.1 can be found at http://docs.sun.com/source/819-4706/index.html.

What's New in this Release of Sun Java Communications Suite

See the What's New document.

Requirements for Communications Suite 6

This section describes the operating system, patch, client software, and any additional software requirements for this release of Communications Suite. This section contains the following topics:

Product Version Compatibility Requirements

This section answers the following questions:

• Which Sun Java System products are required to support the Communications Suite 6 products? Table 1-1 lists the Sun Java System product versions that are compatible with the Communications Suite 6 products.

• To install a particular Communications Suite product, which other components do I need? Table 1-2 lists the individual Communications Suite products and shows the components on which they depend, including other Communications Suite components.

Table 1-1 Sun Java System Product Version Compatibility Requirements for Communications Suite 6

For information about requirements for Directory Server, Access Manager, Web Server, and Application Server, see the current release notes for these products.

For installation instructions for Application Server 9.1 Update 1, see the Sun Java System Application Server 9.1 Update 1 Installation Guide.

For installation instructions for Directory Server Enterprise Edition 6.3, see the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

For installation instructions for the other components, see the Sun Java Enterprise System 5 Update 1 Installation Guide.

Table 1-2 Communications Suite 6 Component Dependencies

NSS Requirements

Communications Suite 6 requires the use of the shared security component NSS version 3.11.7.

For more details about product version dependencies, see Shared Components Bundled With the Communications Suite Installer.

Convergence 1.0: Product Version Compatibility Requirements

The information in this section brings together all product requirements and minimum product versions for those who want to install Convergence in these deployments:

• A new Communications Suite 6 deployment (fresh installations)
• An existing Communications Suite deployment (a combination of upgrades and fresh installations)

In general, the requirements for operating system, memory and disk space, browsers, and most other software products are the same for Convergence as for other Communications Suite products.

However, Convergence has a few specific product and version dependencies. The Convergence client also depends on other Communications Suite products to provide services such as mail and calendar.

The following tables list the product requirements, dependencies, and compatibilities specific to Convergence:

• Sun Java System Product Requirements
• Communications Suite Component Requirements
• Compatibility with Communications Express and the Address Book Store

Note that some of this information repeats the information shown in Table 1-1.

Table 1-3 Sun Java System Product Requirements for Convergence 1.0

For information about requirements for Directory Server, Application Server, and Access Manager, see the current release notes for these products.

Table 1-4 Communications Suite Component Requirements for Convergence 1.0

Note: Messaging Server, Calendar Server, and Instant Messaging are required for Convergence only if you want to configure Convergence with the services they provide. For example, if you do not want IM service, you do not need Instant Messaging.

Table 1-5 Convergence 1.0 Compatibility with Communications Express, Connector for Microsoft Outlook, Address Book Store, and LDAP Schema

Memory and Disk Space Requirements

Table 1-6 Memory and Disk Space Requirements for Communications Suite 6

Operating System Requirements

This release supports the following platforms:

Table 1-7 Operating System and Platform Support

Notes:

• Messaging Server, Calendar Server, Instant Messaging, Communications Express, and Delegated Administrator are no longer supported on HP-UX or Windows platforms.
• The Communications Suite installer checks for required platform patches. You must install all required patches or the installation process does not continue.
• The performance of your Communications Suite deployment depends on many factors, including CPU power, available memory, disk space, file system performance, usage patterns, network bandwidth, and so on. For example, throughput is directly related to file system performance. If you have questions about sizing and performance, contact your Sun Java Communications Suite representative.

System Virtualization Support

System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations. This testing helps validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on nonvirtualized systems.

Communications Suite supports the VMware container (VMware ESX Server 3). As support for such virtualization platforms as LDOMs and the xVM Server becomes available, this document will be updated.

For information about Sun support for Sun Java System products in virtualized environments, see http://docs.sun.com/doc/820-4651.

Communications Suite Patches

For the most current list of required patches for Sun Java Communications Suite, go to http://sunsolve.sun.comand select either Patches or Patch Portal. As operating system patch requirements change and patches to Communications Suite and Java Enterprise System components become available, updates will be distributed on the SunSolve database, initially in the form of recommended patch clusters.

At the time of general release of the Sun Java Communications Suite 6, the following patches are available:

Table 1-8 Sun Java Communications Suite 6 Component Patches

A fresh installation of Calendar Server 6.3, Communications Express 6.3, and Delegated Administrator 6.4, through the Communications Installer, puts you at the above patch levels for those products.

To deploy Calendar Server 6.3 with Convergence, Calendar Server must be at least at the -28 patch level.

High Availability Support

Table 1-9 Supported High-Availablity Products

Table 1-9a Compatibility Between Messaging Server and the MS High-Availability Agent Versions

Client Requirements

The following browsers are supported for Communications Suite clients.

Table 1-10 Supported Browser Versions for Convergence Clients

Table 1-11 Supported Browser Versions for Communications Express Clients

Table 1-12 Supported Browser Versions for Delegated Administrator Clients

Additional Software Requirements for Individual Communications Suite Components

Messaging Server

Recommended File Systems for Message Stores

The following file systems are recommended for message stores:

• LUFS (Logging UFS).
• VxFS (Veritas File System). Veritas File System provides good system performance if configured properly. If you use VxVM, the Veritas Volume Manager, you need to watch carefully that the volumes and the log file for the volumes are set to be regularly striped.
• HAStoragePlus File System for Sun Cluster installations. The HAStoragePlus File System provides better performance than the default Sun Cluster Global File System.
• NFS (Network File System). You can use NFS on MTA relay machines, for LMTP, for autoreply histories, and for message defragmentation. See the Sun Java System Messaging Server 6.3 Administration Guide for more information. In addition, NFS can be supported on BSD-style mailboxes (/var/mail/) as well as for message stores. The Sun StorEdge 53xx NAS have been certified for use with Messaging Server. See Using Sun StorageTek 53xx NAS with Messaging Server Message Store for more information.
• ZFS. As of Messaging Server 6.3, Messaging Server supports the ZFS file system. See Messaging Server ZFS Support for more information.

DNS Server and Messaging Server

A high-quality caching DNS server on the local network is a requirement for a production deployment of Messaging Server. Messaging Server depends heavily on the responsiveness and scalability of the DNS server.

Additionally, your DNS configuration needs to be clearly specified as to how to route to hosts that are not on the local subnet by ensuring the following:

• The /etc/defaultrouter file should contain the IP address of the gateway system. This address must be on a local subnet.
• The /etc/resolv.conf file exists and contains the proper entries for reachable DNS servers and domain suffixes.
• In the /etc/nsswitch.conf file, the hosts: line has the files, dns, and nis keywords added. The keyword files must precede dns and nis. For example, the lines should not look like this:
  

  hosts:  nis dns files
  ipnodes:  nis dns files
  

  
  The lines should be changed to this:
  

  hosts:  files nis dns
  ipnodes:  files nis dns
  

  
  

• In the /etc/hosts file, the FQDN is the first host name.

For example, if your Internet host table in your /etc/hosts file should not look like this:

123.45.67.89 budgie.west.sesta.com
123.45.67.89 budgie loghost mailhost

Change the host table so that only one line is shown for the IP address of the host. Be sure that the first host name is a fully qualified domain name. For example:

123.45.67.89 budgie.west.sesta.com budgie loghost mailhost

Note On Solaris OS 10 U3 and earlier platforms, you not only have to add the fully qualified domain name (FQDN) to the /etc/hosts file, but also to the /etc/inet/ipnodes file. Otherwise, you will receive an error indicating that your host name is not a fully qualified domain name. From Solaris OS 10U4 onward, the contents of the /etc/inet/ipnodes and /etc/hosts files have been merged together into just the /etc/hosts file. Applying kernel patch 120011-14 on any Solaris 10 system also performs the merge, and subsequent removal of the /etc/inet/ipnodes file.

Delegated Administrator

The following Java Enterprise System components, tools, and LDAP schema version are required for this release of Delegated Administrator:

• Directory Server 5.x or 6.x
  To enforce unique values for mail attributes, you must install one of these releases:
  • Directory Server 6.x
  • Directory Server 5.2.5 or later
  • Directory Server 5.2.4, and you must apply patch 5.2_Patch_4_6313027
• Access Manager 6.2 or later.
• Either Messaging Server 6 or Calendar Server 6, or both
• Java Enterprise System Web container. You must deploy Delegated Administrator to one of the following Web containers:
  • Sun Java System Web Server 6.1 or higher
  • Sun Java System Web Server 7 or higher
  • Sun Java System Application Server 7.x
  • Sun Java System Application Server 8.x
  • Sun Java System Application Server 9.1
• Directory Server Setup script, comm_dssetup.pl: Use the version that is bundled with the current version of the Communications Suite installer.
• LDAP Schema 2
  This release of Communications Suite Delegated Administrator is designed for provisioning users in an LDAP Schema 2 directory.

Instant Messaging

Instant Messaging Client Hardware Requirements

Instant Messenger uses between 50 and 70 Mbytes of memory on most platforms. You should estimate the memory requirement by including the requirements of other applications (including operating systems) used on the client machine. In most cases, at least 256 Mbytes RAM is recommended to run Instant Messenger and other applications comfortably. This number becomes higher when using memory-intensive operating systems.

Instant Messaging Client Operating System Requirements

This release supports the following client platforms:

• Solaris OS 9, and 10
• Microsoft Windows 98, ME, NT (SP 6a), 2000, XP
• Mac OS X, minimum 10.1
• Red Hat Linux, minimum 7.2

On Windows, you can run Instant Messenger by using the browser's Java Plugin from the following browsers:

• Netscape, minimum 7.2
• Mozilla, minimum 1.7
• Mozilla Firefox, minimum 1.0
• Internet Explorer, minimum 6.0 SP 2

If the client machine has Java 1.5 minimum installed, there are no additional requirements to use either Java Plugin or Java Web Start. Netscape Navigator v7 as well as the recent versions of the Mozilla browser include Java v1.5 minimum. Internet Explorer does not include the latest version of Java. JDK 5.0 is included with Sun Java System Instant Messaging.

If the client machine does not have Java v1.5 minimum installed, you need to install Java Web Start. You can download and install Java v1.5 from the Java Technology website (http://java.sun.com/j2se).

You can download and install Java Web Start from the Java Web Start Technology website (http://java.sun.com/products/javawebstart).

HTML links can be exchanged over Instant Messenger and activated from the messenger by clicking them. When a link is activated, the messenger invokes a browser. The following table lists supported operating system and browser combinations.

Table 1-13 Supported Client OS and Browser Combinations for Instant Messaging

Connector for Outlook

This section describes the requirements and recommendations for Sun Java System Connector for Microsoft Outlook.

The following operating systems are supported:

• Microsoft Windows 2000 (Service Pack 3 or higher)
• Microsoft Windows XP
• Microsoft Windows 2003 Terminal Server
• Microsoft Vista

The following versions of Microsoft Outlook are supported:

• Outlook 2007
• Outlook 2003

Table 1-14: Communications Suite Component Requirements for Sun Java System Connector for Microsoft Outlook 7.3

Note Calendar Server customers who have deployed previous versions of Sun Java System Calendar Server need to engage with Sun Professional Services to enable their data to be converted and migrated to the new format. A Sun Professional Services offering is available. This migration is required for the use of Outlook, and is necessary because of the underlying changes in the storage and management of recurring events. No migration service is required for new customers of Calendar Server 6 2004Q2 minimum.

Locating Patches for Sun Java Communications Suite Products

To locate patches for the Sun Java Communications Suite products, check the following table, which lists the keywords used for each Communications Suite product. You can use the specific keyword to search for relevant patches in the SunSolve database.

Table 1-15 Patch Keywords for Communications Suite Products

Note The double quotes should be used to search for the text string and word space.

Sun Java Communications Suite Installation and Upgrade Notes

Default Installation Directories and Ports

The Communications Suite installer automatically installs product components in default directories unless you specify otherwise. In most cases, you can specify a custom location to override a default location when you are specifying configuration values during or after installation, with the following exceptions:

• Sun Cluster components. You cannot change the location of the installation directories.
• Message Queue. You cannot change the location of the installation directories.

  Note Use the default installation directory when installing product components, if possible. If you specify an alternative installation directory, you are responsible for consistently pointing components to that installation directory during configuration.

  The following table lists the default installation directories for the Communications Suite product components.

Table 1-16 Default Installation Directories

Default Port Numbers

When the Communications Suite installer requests that you enter a port number, the installer performs a runtime check on the ports in use and displays an appropriate default value. If the default port number is being used by another component or by another instance of the same product component, the installer presents an alternative value.

The following table lists the default Communications Suite product component port numbers and the purpose of each port.

Note Convergence, Access Manager, Communications Express, and Delegated Administrator are not listed in this table because they use the port numbers of the web container into which they are deployed.

Table 1-17 Product Component Default Port Numbers

Note 1 - Port Number Conflicts. If these servers (such as the IMAP4 server and MMP IMAP Proxy) are installed on the same machine, you will encounter port number conflicts. If possible, install products with conflicting port numbers on separate hosts.

If you have installed two servers that are attempting to access the same port number, you need to change the port number of one of the conflicting products. To change port numbers for Messaging Server components, use the configutil utility. See the Sun Java System Messaging Server 6.3 Administration Reference for instructions.

The following example uses the service.http.port configutil parameter to change the standard HTTP port number to 8080:

configutil -o service.http.port -v 8080

Known Issues in Sun Java Communications Suite

This section describes the known issues that exist in this release of Sun Java Communications Suite.

6659438

The Communications Installer fails when a directory contains a space.
The commpkg utility fails when the current directory has a space in its name.
Workaround: Do not use commpkg in a path that contains a space in its name.

No Localization Files for Communications Express

No localization files are available for Communications Express.
You see only English in the Communications Express interface, even if you try to change the preferred language to another choice.

comm_dssetup Utility

If you installed Directory Server Java ES (for example, Java ES 5 U1), the comm_dssetup utility is also installed. The Communications Installer comes with a newer version of comm_dssetup that you need to use.
Workaround: To "upgrade" the comm_dssetup initially installed with Directory Server, apply patch 118245-15, which is located in the Communications Suite 6 distribution in the SunOS_sparc/DSSETUP/Patches directory. (For Solaris x86, use the SunOS_i386 path, and for RedHat Linux, use the Linux_i686 or Linux_x86 path.) Alternatively you can use the Communicatations Installer to first uninstall then install the newer version of comm_dssetup from the Communications Suite 6 distribution.

Communications Express configuration process results in an error

The Communications Express configuration process results in an error when you configure the Webmail host and port settings.
The error is due to a missing default.html file. The error is:

Verifying whether the Webmail Server Instance connection is alive
null->Error: com.sun.comms.client.install.panels.WebmailHostPortPanel: Error in verifyService()- java.io.FileNotFoundException: http://host:8990

Unable to connect to the Webmail Server "host.com:8990".

Ignore the error and proceed with configuring Communications Express. The default.html file is not required for Communications Express to operate.

Uninstall prior Calendar Server localization packages before installing Communications Suite 6

(CI 6.0-0.02 and later, this issue does not exist on CI 6.0-0.01): You must uninstall the prior Calendar Server localization packages before installing Communications Suite 6. Otherwise (at least on Linux) the Calendar Server installation fails.

• To uninstall, use the commpkg uninstall command, or uninstall manually:
• To uninstall prior Calendar Server localization packages on Solaris OS, remove the following packages if they exist, by running the following commands:
  pkgrm SUNWics-l10n
  pkgrm SUNWfrics
  pkgrm SUNWdeics
  pkgrm SUNWesics
  pkgrm SUNWjaics
  pkgrm SUNWkoics
  pkgrm SUNWzhics
  pkgrm SUNWtwics
• To uninstall prior Calendar Server localization packages on Linux, remove the following packages if they exist, by running the following commands:
  rpm -e sun-calendar-core-l10n
  rpm -e sun-calendar-core-fr
  rpm -e sun-calendar-core-de
  rpm -e sun-calendar-core-es
  rpm -e sun-calendar-core-ja
  rpm -e sun-calendar-core-ko
  rpm -e sun-calendar-core-zh
  rpm -e sun-calendar-core-zh_TW

Chapter 2 Sun Convergence 1.0 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Convergence 1.0 including:

About Convergence 1.0

See Introduction to Convergence.

What's New in This Release of Convergence

See the What's New document.

Requirements for Convergence 1.0

For Communications Suite requirements, see the Requirements for Communications Suite 6.

For requirements specific to Convergence, see the Requirements for Convergence 1.0.

Convergence Installation Notes

See Communications Suite 6 Installation Guide for information on installing Convergence.

Convergence Compatibility Issues

If necessary, this section should list any compatibility issues.

Problems Fixed in This Release of Convergence

6702118

When you select a subfolder to be a system folder (such as Sent or Trash), the original system folder is no longer available, and the subfolder is displayed twice.

6700973

Application Server fails under a stress test, giving a NullPointer exception.

6700674

In Japanese, the "Forwarding" selection in the Options --> Mail page is mistranslated.

6700489

When you search tasks in calendar, there is a search criterion called "Attendees," which does not pertain to task searches.

6700311

Subscribing to multiple calendars causes issues with displaying events and the color of the events.

6700133

In Agenda view, if you create an event with a duration of two hours or longer, the duration is shown twice, and the label "hours" is not displayed.

6699743

In the address book, searches for text strings inside the text of a contact name or other fields do not return search results.

6697481

You cannot give specific access (such as read access) to a calendar for a particular user if other users are given no access to the calendar.

6687949

In Instant Messaging, adding from the Address Book tab should also list the corporate Address Book contacts.

6687362

The Convergence online help does not document how to sort IM buddies alphabetically or by presence status.

6616046

When you reply to an HTML message, and enter text inline (within the quoted HTML in the original message), the replies are formatted incorrectly.

Known Issues and Limitations in Convergence

The Convergence known issues are grouped in the following categories

Known Issues: General and Authentication

6701184

The Note field in the Create or Edit Contact screen does not highlight a misspelled word in Internet Explorer 6 and 7.

6702002

Creating a group saves the help text if the user does not enter any values.

6701368

In Internet Explorer 7, when you try to export the address book, a security warning message is displayed. You need to click the message and click Allow Download to export the address book.
Clicking this link refreshes Convergence.

6699749

When you import a v-card created using a Macintosh address book, the email addresses are lost though they are in the right format.

6699051

If pop-up windows are blocked in the user's browser, functions such as printing dialog, IM, timeout warning, and navigate away warnings do not work.
From the user's perspective, it appears that these functions do not work. Convergence does not display a dialog telling users to enable pop-ups.

6698171

In some cases, when you log in to Convergence, the browser does not respond, and a dialog appears stating that a slow script is making the browser unresponsive.

6697453

No option to set default photo or delete photo.
There is no option to set default photo or delete photo from the Address Book. Address Book should have the same kind of option as in Instant Messaging for setting default photo.

6691137

Timeouts are reported in dialogs as formatting errors.
If you take an action such as creating a mail folder and wait until the action times out, the error dialog tells you there was a formatting error in the folder label. It does not say that your action timed out.

6690719

Pressing the Tab repeatedly gives usability issues in Create Contact.
When creating an Address Book contact, click the work email field then keep pressing the Tab key. After the Notes field, if you press the Tab key, focus shifts to the Buddy List.

6686058

Presence alert does not close completely (or right away) when clicking Close button.

6686064

The Show Contact in presence alert should highlight the contact in the roster.

6688678

Restoring the default photo from the Avatar properties widget does not ask for confirmation before saving.

6679055

In Internet Explorer 6, logging in to the Convergence client consumes 99% of CPU resources.
For some time after logging in (for example, for one minute in some cases), the browser is unresponsive.

6610071

Reloading the page causes the Mail tab to be displayed, no matter which tab was displayed originally.
For example, if you are viewing the Address Book and reload the page, the Mail view is displayed.

Known Issues: Mail

No Issue ID

In Internet Explorer, if you open a compose window and try to paste a list of addresses into the To: or CC: field that exceeds 4000 characters, the field is populated with blank spaces. If you highlight the field, you can see the addresses.
This is a known IE issue. It does not occur with other browsers.

Workaround: You can fix this problem with a registry modification. For details, see http://support.microsoft.com/kb/240121

6739123

With Internet Explorer 7, if you send a message larger than 100 KB, the message does not get delivered and the browser stops working.
This is an IE7 issue; it does not occur with other browsers. It does occur with IE7 in other mail clients as well as Convergence. You must exit and restart the IE7 browser to use it again.

6702084

If you use the shift key and arrow keys to select multiple mail messages, all messages displayed in the current folder disappear.
This problem occurs when there are many (100 or more) messages in the current folder. If only a few messages are in the folder, using the shift and down-arrow keys to select messages selects the only first two messages and the last message.
Workaround: Click the up or down arrow in the scrollbar to display messages again.

6701571

If mail service goes down and is started again, the client does not appear to reconnect to the mail service, and mail is not available in the client UI.
Workaround: Log out of Convergence and log in again.

6701392

In Internet Explorer 7, when you send a long message with a large amount of text, Convergence takes a long time to send it and appears to be unresponsive.
For example, when you send a text message with 35K of text, Convergence can take 1 to 2 minutes to respond. The recipient receives the message without any issues.

6700482

In Internet Explorer 7, if you tab from the Subject: field in a message, the cursor focus goes to the sign-out button instead of to the body text.
This issue does not occur on Firefox.

6694908

In Safari, when you drag and drop a message into a folder, a larger area of the screen than only the folder is selected.

6694440

When you perform a mail function that takes time to complete, the dialog buttons that handle the function are not disabled, and the cursor does not change to a wait symbol.
For example, if you select all messages in a folder, the related dialog button should be disabled and the cursor should become a wait symbol until all messages are selected.

6693443

An error message inadequate for end users is displayed when the Messaging Server goes down during a mail session in Convergence.
If you are using mail in Convergence and the Messaging Server goes down, a pop-up error message states "Mail Service: connection refused" rather than displaying a user-friendly message such as "A temporary problem has occurred. We'll be back soon," or "Working on your request..."

6692441

In Internet Explorer 7, when you compose a message, the cursor does not focus properly in the compose text window.
For example, if you open compose message, enter information in the To: line, click the Tab key, enter information in the Subject: line, then click the Tab key, the cursor does not focus in the message text area.

6692400

A message being composed is not auto-saved if the only change was in message priority or receipt status.
If you compose a message and make any change since the message was created or since the last save, the message will be saved automatically at the end of the auto-save period (by default, every five minutes). However, auto-save does not occur if the only change is in message priority or receipt status.

6657490

An email message containing more than 170 KB of text is received as an attachment.
This issue occurs on Solaris SPARC and x86 platforms. It does not occur on Linux. This maximum value is specified with the maxtext parameter in the client configuration.

6630169

In certain cases, users can read mail and contact details after they have logged out of Convergence.
For example, if a user starts Convergence, then opens the Convergence url in a new tab, then logs out of Convergence in the new tab, the user can still read mail and see contact information in the first tab.

6625314

When the unread message count is disabled, the Convergence mail application selector always shows the message count as zero.
This issue occurs when the Messaging Server configutil option local.service.http.showunreadcounts is configured not to return the unread message count data (configutil local.service.http.showunreadcounts=0). When this option is disabled, the unread message count appears as 0 in the Convergence mail application selector. This option should not be shown to the end user if Messaging Server is configured not to return the unread message count data.

Known Issues: Calendar

6700603

If you attach a file to one instance of a recurring event and specify that the attachment applies to "only this occurrence," the event is attached to all occurrences of the event.

6699600

When you mouse over a button, it remains highlighted even when you do not click it.

Workaround: Switch to a different view (such as month view), and the highlighted buttons will be unselected.

6699058

In the calendar, the printing button looks like this ">>" and does not have a label, which is inconsistent with the printing buttons in other services.

6698967

In Safari, after you change the calendar view a few times (for example, from week to day to month view), the button indicating which mode is selected is no longer highlighted.

6691971

The More link in a calendar continues to be displayed after the calendar is deleted.
If you add events to a calendar until the More link appears, and then delete the calendar, the More link remains displayed until you refresh the browser.

6691933

In Agenda view, if you add an event and change the calendar you are viewing, the new event continues to show up in the second calendar until you refresh the browser.
In Agenda view, the same event is shown twice, once in the original calendar and once in the second calendar.

6691922

Changing the days of the work week in your calendar has no effect when you create recurring events.
For example, if you include Saturday as a work day and create a recurring event that occurs daily, the event does not show up on Saturdays.

6645274

A recurring event specified to end "never" actually ends after 60 recurrences.
If you specify that a recurring event end "never," Convergence uses the default value for the number of recurring events, which is 60. You can only find out about this limit by scrolling through your calendar, as Convergence does not indicate the limit.

6641358

When you add a new event in month view, using natural language to specify its duration does not yield the correct event duration.
For example, if you add a new event in the Calendar, specify event details such as "Lunch at 1:15 tomorrow for 45 minutes," the event is created as one hour long (1:15 - 2:15) instead of 45 minutes.
Note that if you enter event details using a different format, such as "Lunch tomorrow 1:15 P.M. - 2:00 P.M.," the correct duration is created.
Workaround: Change the length of the event in day or week view, or edit the event. 

6692011 

Calendar Online Help needs updates

The calendar module of the online help contains incorrect information in the following areas: Event operation (specifically creating, editing, and deleting), Cloning, Views, and calendar printing.

Known Issues: Address Book

6704130

In Address Book, the Manage Group option does not have a rename option.
Workaround: Right-click on the list of contact groups in the left panel of the UI. This displays the context menu, which includes a rename option.

6676645

The print option does not take all the contents in a contact.
When you print an address book contact, some fields, such as the country, nickname, and notes, are not printed.

6654530

In the address book, no contact is displayed when the wildcard search value is set to greater than 0.
By default, the value of the ab.pstore.wildcardsearch property is set to 0. This enables the wildcard search function to begin returning results as soon as the end user enters the first character.

The feature does not operate as expected if you set ab.pstore.wildcardsearch to greater than 0. For example, if you set the property to 2, the user must enter two characters before the wildcard search returns results. That is, a value of 2 functions as follows: 2 - entry/displayname=aa*
Workaround: Reset the value of ab.pstore.wildcardsearch to 0.

6649025

The Address Book Properties window displays incorrect information.

6646169

In the Address Book, the Sr/Jr option is not displayed in view mode.
When you create or edit a contact, you can select the Sr or Jr option to add to the contact's name, but the Sr or Jr does not appear when you view the contact.

6638802

When you create or edit a contact in the Address Book, the contact fields such as email address and phone number are not validated.
You can enter any text in these fields, such as alpha characters in the phone number field.

6637775

Advanced Search in the Address Book is not working.
When you select the Advanced Search option in the Address Book, enter search criteria, and press Search, no results are returned.

6609983

Incorrectly formatted address/bad address still shows "map" in address book.
If you incorrectly specify an address book address entry (home or business), the resultant "map" entry points to an invalid place. The fields are not marked and bogus entries still get mapped.

6673188

User is not able to copy contacts from one address book to another group using drag and drop.

6688097

Cannot make default address book as corporate address book.

6690711

In the corporate address book, details of a contact are displayed in the right pane, though no contact is selected in the search pane.

6656871

The Up/Down arrow keys do not work in Address Book.
This problem pertains to Safari and Internet Explorer 6 and 7.

6692518

Pressing the Enter Key opens the Compose Mail screen.
When selecting an Address Book contact and pressing the Enter key, the Compose Mail screen is opened. Because an Edit screen is associated with the contact, the Edit screen should be opened when pressing the Enter key.

6699217, 6654031

Accented characters are not imported or exported properly, nor are they sorted properly in the address book.

6702142

Though the corporate address book search does not display any contact, the following message is displayed: "Only 100 entries is displayed."*

6697558

After importing an LDIF file with lists into Convergence, the list is displayed only after re-logging in.

6702725

In Internet Explorer 7, if you click the email ID of a contact in the Corporate Directory, an error message is displayed.
You can click OK to navigate to the Mail module.

6697581

After importing a Microsoft Outlook CSV file into Convergence, the birthday and anniversary are lost.

6699694
After importing a CSV file that is exported from Convergence into Microsoft Outlook, the following information is lost: Middle Name, Title, Suffix, other address, birthday, and anniversary.

6693923

Address Book Online Help needs updates

The online help for the Address Book component needs updates.  Specifically, the online help contains incorrect or missing descriptions in the following areas: Contacts, Groups, Corporate Directory, and Print options.

Known Issues: Instant Messaging

6704008

The Avatar does not function when the Instant Messaging Server requires SSL (when you require secure communication between Convergence and the Instant Messaging back end).
When the iim_server.requiressl parameter is set to true, the server throws a ServletException. If SSL is not set, the Avatar works properly.

6698876

Presence information is not shown in an email header (the sender, to:, or cc: list) because the IM Add Buddy icon only accepts the uid@domain in the user name field when you add an IM buddy.
When you add a buddy in IM, you must use the uid&domain format for the user name. You cannot use the user's email address. However, once the buddy is entered as uid@domain, that user's email address, as shown in the email header, is not recognized, and therefore the presence information does not appear in the email header.

6696027

In Instant Messaging, adding from the Address Book always adds the buddy to Friends group.

Workaround: Manage the group then add the contact.

6689431

Buddies in the Instant Messaging roster can be duplicated in the same group.
You cannot delete the duplicate entry; if you delete one entry, all the entries for that buddy are deleted.

6688269

Unable to chat with buddy using Instant Messaging if pop-up blockers are enabled.
If you select a buddy on buddy list, then select the pop-up menu item, "Send message to," does not generate any activity.

Workaround: Disable pop-up blockers and restart your browser.

6684054

Instant Messaging chat window: Click a URL link in chat, opens up new tab in chat window not main browser window.

6668868

Users in a buddy list who are in Do Not Disturb or Away status are not sorted.
If you sort users (for example, in alphabetical order), the users in the following modes are not sorted: Do not disturb; Away; BRB; On the phone; Out to lunch; Gone home.

6665909

Offline messages do not show up or are not emailed.
If a user opens a chat session with another user and one user refreshes the browser, messages are not received if messages were sent before the user's browser has been refreshed.

6665897

When you create a new chat session and refresh or reload the browser, the old chat session remains.
The old chat session should be closed after a browser reload or refresh.

6664158

You cannot add the first contact to any group other than Friends.
When a user adds the first contact to the buddy list, that first contact must be in the Friends group.

6662902

An IM user cannot receive chat messages if the user started the session with "block pop-up windows" configured.

6632069

The IM client disconnects automatically in some cases.
After a period of time, the IM client goes offline automatically, although the keep-alive packets are being sent from the client. This issue occurs intermittently.

Known Issues: Options

6697285

No warning message is given when Convergence strips the content between < and > symbols.
If there is meaningful content between the < and > symbols, the user would lose that data without being warned by a dialog.

6694006

When you create a mail sieve filter, if you want to include special characters in the mail filter name, you must use Character Predeclared Entities.
For example, a & or < characters are special characters in XML, and if you enter them in the mail filter name without using a Character Predeclared Entity, an "invalid formatting" error will be returned.

6676645

The Print option does not take all the contents in a contact.
If you create a contact with all the details then choose Print > Print Group, not all details are displayed.

6654595

The Mail Forwarding options page displays a warning message that the page contains unsaved changes when no changes were made.

6648561

There is no option that allows you to save a custom (or personalized) message.

Known Issues: Customization

6745772

When adding a new right-to-left language such as Arabic or Hebrew to Convergence, the UI text is not right-to-left.
This issue occurs if you enable customization and perform the steps to add a custom language to Convergence, then log in as a user created in LDAP with a language preference set to the custom language (for example, Arabic). The UI displays text and aligns widgets left-to-right instead of right-to-left.

6745757

When adding a new language to Convergence, Convergence hangs if no resources.js file is directly under the allDomain directory.
This issue occurs if you enable customization and perform the steps to add a custom language to Convergence, creating a directory structure as shown in this example:

/iwc_static/c11n/allDomain/nls/
/iwc_static/c11n/allDomain/nls/<_new language_>/
/iwc_static/c11n/allDomain/nls/<_new language_>/resources.js

In this situation, Convergence does not load the files; it does not bring up the UI.

Workaround: Add an empty resources.js file directly under the /iwc_static/c11n/allDomain/nls/ directory. Note that you still must create the resources.js file under the /iwc_static/c11n/allDomain/nls/<new language>/ directory. For example:

/iwc_static/c11n/allDomain/nls/
/iwc_static/c11n/allDomain/nls/resources.js
/iwc_static/c11n/allDomain/nls/<_new language_>/
/iwc_static/c11n/allDomain/nls/<_new language_>/resources.js

Known Issues: Localization

Known Issues: Documentation and Online Help

6714325

The Convergence online help has unsupported features details in the Calendar Preferences section.

Redistributable Files for Convergence

In the future, this section should list any redistributable files for Convergence.

Chapter 3 Sun Java System Calendar Server 6.3 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Calendar Server 6.3 including:

About Calendar Server 6.3

Calendar Server is a scalable, web-based solution for centralized calendaring and scheduling for enterprises and service providers. Calendar Server supports user calendars for both events and tasks as well as calendars for resources, such as conference rooms and equipment.

Calendar Server offers two graphical user interfaces, Convergence and Communications Express. It also offers customers the flexibility to use the Web Calendar Access Protocol (WCAP) to access calendar data directly in either text/calendar or text/xml format.

What's New in This Release of Calendar Server

For details, see the What's New document.

Deprecated and Removed Features for Calendar Server 6.3

For Sun Java System Calendar Server 6.3, the following features have been deprecated:

• The Calendar Express graphical user interface (GUI) has been deprecated and will be removed from the distribution in the the next major feature release.
• The WCAP attachments parameter, used by both storeevents and storetodo, has been deprecated. For backward compatibility, this parameter is still honored. But in a future release this parameter will no longer be recognized. Change any scripts you have using this parameter.
• The cstool utility that you use for monitoring Calendar Server activity has been removed in the Calendar Server 6.3 release.
• Calendar Server software is no longer available for Windows and HP-UX platforms.

Requirements for Calendar Server 6.3

See Requirements for Communications Suite 6.

Important Upgrade Patch Information for Calendar Server 6.3

The following Calendar Server 6.3 product upgrade patches are as follows:

Table 3-1 Calendar Server 6.3 Upgrade Patches

You can find the most current product patches at Sun Solve. For how to find patches on Sun Solve, use the following procedure:

How to Find Patches on SunSolve

1. For the current list of required patches for Sun Java System Calendar Server, go to:
   http://sunsolve.sun.com
2. Select either "Patches" or "Patch Portal".
3. Follow the Sun Java System Calendar Server links.
   As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.

Calendar Server Installation Notes

This section contains information you should know before you install Calendar Server 6.3. This section contains the following subsections:

Caution Calendar Server does not support Network File System (NFS) mounted partitions. Do not install or create any part of Calendar Server, including executable, database, configuration, data, temporary, or log files, on an NFS-mounted partition.

Default Calendar Server Installation Directories on Solaris and Linux Platforms

The following table shows the default installation directory paths for Solaris and Linux:

Table 3-2 Default Calendar Server Installation Directories

Tip In the documentation, the default installation directory for Calendar Server is referred to as cal-svr-base.

OS Patches

You must apply the required operating system patches before installing Calendar Server. The Communications Suite installer checks for required platform patches. You must install all required patches or the installation process does not continue.

Required Privileges

To run the Communications Suite 6 installer or the Calendar Server 6.3 configuration program on a Solaris OS system, log in as or become the superuser (root).

Upgrading From a Version Prior to Calendar Server 6

Upgrade to the latest Calendar Server 6.3 patch by using patchadd process.

For more information about upgrading to Calendar Server 6.3 from previous Calendar Server versions, see Sun Java Communications Suite 5 Upgrade Guide.

Upgrading Your Calendar Database

If you are upgrading from a Calendar Server version prior to 6.3 to the current 6.3 version, you must upgrade your databases also, using various database tools named in this section. More information about the migration tools can be found in the Sun Java System Calendar Server 6.3 Administration Guide.

Upgrading From a Version Prior to Calendar Server 5.1.1

If the version of your previous Calendar Server software predates version 5.1.1, first call Sun Support Services for assistance in migrating your databases to be Calendar Server 5.1.1 compatible. You can not migrate directly to any of the Calendar Server version 6 releases. In the process recommended by Sun Support Services, you are required to install Calendar Server 5.1.1. After your database files are Calendar Server 5.1.1 compatible, install Calendar Server 6.3 and run the following database tools in the order listed.

cs5migrate

Run this utility to upgrade your databases from version 5.1.1 to version 6.2 level. This is an intermediate step that is required before you run the csmigrate utility to bring it up to version 6.3 level. The cs5migrate utility can be found in the sbin directory after you install Calendar Server 6.3.

You must specify the -r option. The cs5migrate utility then creates master and exception records for all recurring events and tasks. Going forward these records will be automatically generated by Calendar Server.

This utility performs the following changes to your databases:

• Migrates your Calendar Server 5.1.1 LDAP database to be Calendar Server 6.2 compatible
• Migrates your Berkeley Data Base to version 4.2
• Writes the migration status to csmigrate.log log file
• Writes errors to csmigrateerror.log log file

csmig

Run this utility so the LDAP CLD plug-in works properly.

csvdmig

Run this utility to convert your non-domain calendar databases to single domain databases compatible with a multiple domain environment.

csmigrate

Now that your Calendar Server Databases are in version 6.2 mode, run the csmigrate utility to migrate your Calendar Server 6.2 databases to be compatible with Calendar Server version 6.3.

You can find the csmigrate utility, along with other administrative tools, in the sbin directory of your newly installed Calendar Server 6.3 software. For more information on csmigrate, see Sun Java System Calendar Server 6.3 Administration Guide.

Caution If you are upgrading from a much older version of Calendar Server that was configured for limited virtual domain mode or has multiple instances of Calendar Server on the same machine, contact your Sun Microsystems, Inc. sales account representative for an evaluation of your migration requirements and to ensure that you have the specific migration utility that supports those requirements. And, as always, never migrate your database without first performing a full backup.

Upgrading Your Calendar Server Version 6.0, 6.1, or 6.2 Databases to be Calendar Server Version 6.3 Compatible

Run csmigrate to upgrade your calendar databases to version 6.3 level.

You can find the csmigrate utility, along with other administrative tools, in the sbin directory of your newly installed Calendar Server 6.3 software. For more information on csmigrate, see Sun Java System Calendar Server 6.3 Administration Guide.

Caution If you already have a Calendar Server 6.3 installation and you just upgraded to the latest patch, no migration utilities need to be run.

Upgrading to Calendar Server 6.3 Patch 121658-20 or Later on Solaris x86 Platforms

Data created in the Solaris x86 version of Calendar Server 6.3 patch 121658-19 or earlier is corrupted when you upgrade to patch 121658-20 or later. This issue occurs on Solaris x86 platforms only (CR 6642958).

With patch 121658-20 and later, Calendar Server uses the new Berkeley Database library, which is incompatible with the database created by earlier versions. In order to use the database created by patch 121658-19 (or prior) with this patch, you must update the database.

Follow this procedure:

1. Make sure the Calendar Server installation is patch 121658-19 or prior.
2. Important: Take a copy of the current database.
3. Check to make sure the database is in good condition by running db_verify and csdb check.
4. Dump the data using db_dump.
   a. Set LD_LIBRARY_PATH to cal-svr-base/SUNWics5/cal/lib.
   For example: ./db_dump -r -f /var/opt/SUNWics5/dump/ics50alarms.db.txt /var/opt/SUNWics5/csdb/ics50alarms.db
   b. Do the same for all the databases.
   This dumps the ics50alarms.db to ics50alarms.db.txt (text file) and is placed in the "dump" directory.
5. Apply this patch (121658-24 or later).
6. Load the data dumped in the preceding step to the database files using the cs_dbload utility provided in this patch.
   a. Set LD_LIBRARY_PATH to cal-svr-base/SUNWics5/cal/lib.
   b. Run cs_dbload to load files dumped in step 4.
   For example: ./cs_dbload -f /var/opt/SUNWics5/dump/ics50alarms.db.txt /var/opt/SUNWics5/dbload/ics50alarms.db
   c. Do the same for all the databases.
   This loads the records present in ics50alarms.db.txt to the ics50alarms.db in the "dbload" directory. A new "dbload" directory is chosen in order not to overwrite the original database.
7. Run csdb check or csdb rebuild on the database files created in the preceding step.

FAQ: Solaris x86 Upgrade to Calendar Server 6.3 Patch 121658-20 or Later.

Question: Is this a problem only for Solaris x86?
Answer: Yes, this is problem only for Solaris x86. SPARC and Linux platforms are not affected.

Question: Do you have to perform this task for every patch? Or only one time?
Answer: This is a one-time only task. Once you convert the database to work with this patch, you do not have to repeat these steps for future patches. You can just perform a patchadd.

Question: If I have patch -17 or -18, what should I do?
Answer: Follow the previous procedure.

Question: If I have patch -21, -22, or -23, and I have not previously done a dump/load, what should I do?
Answer: We don't expect Calendar Server to run without crashes on these patch levels if the dump/load procedure is not performed. If you have these patches installed and do not see any issue, then please contact technical support on how to move forward with the patches.

Question: If I have already applied patch -24, and I've already done a dump/load, and I want patch -25 or the Communications Suite 6 software, what should I do?
Answer: Perform a patchadd of patch -25. No additional steps are required.

Question: If I have Communications Suite 5 (Calendar Server 6.3) and I want to be a Beta customer, what should I do?
Answer: If you want to move data from your existing database to the new database, you will have to perform the dump/load procedure described in patch -24.

Calendar Server Postinstallation Configuration

After installing or upgrading to Calendar Server 6.3 and before you can use Calendar Server, you must configure it according to the instructions in Calendar Server 6.3 Initial Configuration.

Automatic Base 64 Encoding of Passwords

In the past, the Calendar Server configuration file stored some passwords in clear text. Though the ics.conf file has read permission restrictions, the passwords could be visible to someone else when the administrator edits the configuration file. In Calendar Server 6.3, the passwords have been moved to another file and obfuscated by base 64 encoding them. The base 64 encoding prevents someone from accidentally seeing the passwords. You must still protect the file with read permission restrictions, and keep the file secure so that no unauthorized user can get to it, to keep the passwords secure.

If you are installing Calendar Server for the first time, the configuration program encodes the passwords that you create during the configuration process, and stores them in a separate password configuration file.

If you are upgrading your existing Calendar Server software to the Calendar Server 6.3 version, the configuration program encodes the existing passwords found in the ics.conf file, and moves them to the password configuration file.

In both cases, the configuration program also adds a new ics.conf parameter to indicate the location of the password file, as shown in the following example:

local.passwordfile="/etc/opt/SUNWics5/config/icspassword.conf"

Do not change this configuration parameter.

Due to this change, the following configuration parameters have been moved out of the ics.conf file:

• local.authldapbindcred
• local.enduseradmincred
• local.lookupldapbindcred
• service.siteadmin.cred

Note The LDAP bind passwords that are generated by the configurator are re-generated each time you run the configurator, once they are moved out of the ics.conf file.

Where to Find Calendar Server Data and Program Files

The following table shows where to find various files and programs referred to in the documentation for both the Solaris and Linux platforms:

Table 3-4 Location of Calendar Server Files

Tuning Directory Server Performance for Calendar Server

To improve the performance of your LDAP directory server, especially if you are using calendar searches of the LDAP directory consider the following items:

Indexing the LDAP Directory Server Attributes

To improve performance when Calendar Server accesses the LDAP directory server, add indexes to the LDAP configuration file for various attributes.

The configuration program, comm_dssetup.pl, will optionally do the indexing for you.

Tip To see the performance difference indexing can give you, perform the following test: Before indexing, time how long it takes to run the following LDAP command: ldapsearch -b "base" "(&(icscalendarowned=* user*)(objectclass=icsCalendarUser))" Where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Search dialog. Run indexing for icsCalendarOwned. Again run the following LDAP command, and time it: ldapsearch -b "base" "(&(icscalendarowned=*user*)(objectclass=icsCalendarUser))" Where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user is the value that an end user can enter in the Calendar Search dialog. Compare the times. There should be a measurable time difference.

Checking and Setting the Size Limit and the Look Through Limit Parameters

To determine if the Look Through Limit (nsslapd-lookthroughlimit) and Size Limit (nsslapd-sizelimit) parameters are set to appropriate values, try the following command:

ldapsearch -b "base" "(&(icscalendarowned=*
user ID*)
(objectclass=icsCalendarUser))"

where base is the LDAP base DN of the directory server where the user and resource data for Calendar Server is located, and user ID is the value that an end user can enter in a calendar search dialog in Communications Express.

If the LDAP server returns an error, the nsslapd-sizelimit or the nsslapd-lookthroughlimit parameter might not be large enough. Follow these guidelines to set these parameters:

• Ensure that the value for the nsslapd-sizelimit parameter in the slapd.conf or equivalent file is large enough to return all the desired results; otherwise, truncation can occur, and no results will be displayed.

• Ensure that the value for the nsslapd-lookthroughlimit parameter in the slapd.ldbm.conf or equivalent file is large enough to complete a search of all the users and resources in the LDAP directory. If possible set nsslapd-lookthroughlimit to -1, which causes no limit to be used.

Using Schema 1 with Calendar Server and Communications Express

There are two issues with Schema 1 in Communications Express:

• If you are running Communications Express with Sun LDAP Schema 1, before running the Communications Express configuration program, you must add the DC root node to your LDAP using ldapmodify. The entry should look like this:

dn: o=internet
objectClass: organization
o: internet
description: Root level node in the Domain Component (DC) tree

• The Calendar Server utility used to provision users in Schema 1, csuser, was designed for Calendar Express and does not enable a user for Address Book service as is needed for Communications Express.

Calendar Server Provisioning Tools

There are two tools for provisioning users, groups and domains for Calendar Server: The Delegated Administrator and Calendar Server utilities. Delegated Administrator has two user interfaces: the Console, a graphical user interface, and the Utility, a command-line interface. For information on Delegated Administrator, see the Sun Java System Delegated Administrator 6.4 Administration Guide. Instructions on use of the Console can be found in the Delegated Administrator Console online help.

For information on the Calendar Server utilities, see the Sun Java System Calendar Server 6.3 Administration Guide.

Caution Do not attempt to provision users through the Access Manager Console. Though it is possible to create users and assign them a calendar service, do not use this method as results will be unpredictable and will negatively impact your deployment.

Calendar Server Documentation Updates

csversion command

The csversion command was introduced in Calendar Server 6.3 in Communications Suite 5 and replaces the cscal version command that was present in earlier releases. It outputs the version information of Calendar Server. There are no additional arguments required.

Example:

# ./csversion
Sun Java(tm) System Calendar Server 6.3-12.01 (built Jan 12 2009)
SunOS siroe 5.10 Generic_118833-36 sun4u sparc SUNW,A70
#

6544548

The Sun StorEdge Enterprise Backup software (formerly Solstice Backup) and Legato Networker (legbackup.sh and legrestore.sh) are no longer distributed with Calendar Server 6.3. The Sun Java System Calendar Server 6.3 Administration Guide still documents these utilities in section "17.3 Using Sun StorEdge Enterprise Backup or Legato Networker," in "Chapter 17: Backing Up and Restoring Calendar Server Data." Ignore this information, as it is out of date.

Calendar Server Compatibility Issues

The following table lists the known incompatibilities between Calendar Server 6.3 and earlier versions.

Table 3-5 Calendar Server Incompatibilities

Problems Fixed in This Release of Calendar Server

The list that follows are problems reported fixed for this patch of Calendar Server 6.3:

6697835

A "freebusy" failure should not cause http error to be returned for XML/JSON output
Calendar Server returns http error 404 when doing a "freebusy" lookup on a non-existing calendar.

6683707

get_freebusy.wcap crashes cshttpd

6681812

csdb rebuild should not change the modified timestamp

6680028

cshttpd crashes when a "freebusy" lookup is done on ldapgroup

6677838

Unauthorized WCAP request should return response with http code 401-Unauthorized for JSON payload

6676306

Time zone names are wrong for daylight times in Australia

6674186

Implement handling of SMS reminders

6673980

Calendar Server fails to stay running in Sun Cluster HA when configured in read-only mode

6662778

Event Accepted Notification emails are not sent if multiple calendar ID's are invited

6662417

Integration of localization files into core patch for Communications Suite 5 and 6

6659624

JSON syntax error returned when "freebusylist" is empty in getfreebusy.wcap

6657860

JSON format error returned in get_freebusy.wcap

6657246

There is a memory leak for every login if the authentication filter is configured

6657242

There is a memory leak when fetching a multivalued attribute from ldap

6656154

Calendar Server needs to implement the Communications Suite Installer upgrade interfaces

6651348

SMF needs to have unique names for Messaging Server and Calendar Server watcher services

6650915

Can't start Calendar Server using SMF

6650391

SMF: watcher fails to start (path to binaries is incorrect in calexe)

6650270

SMF : watcher.xml references Messaging Server

6649304

Passwords are put back (twice in the ics.conf with empty value after using removing the latest cs631 patch

6649300

patchadd produces error "cannot access /opt/SUNWics5/cal/lib/com.sun.cmm.cs.xml.new

6649297

Linux only: Old password related fields left in ics.conf

6646891

Calendar Express cannot modify time format if service.http.numprocesses is greater than 1

6642958

Bad data representation with patch 121658-19 for the x86 version of Calendar Server 6.3

6642312

The csversion utility is missing on Linux

6642081

Anonymous login to calendar is not working

6641750

fetchattachment.wcap returns incorrect mime output

6640527

csadmind crashes when accessing an attachment with an encoded file size that is an exact multiple of the page size

6640009

There is no SMF support in the Calendar Server build

6635743

Configuring CS fails with a java exception error

6629318

cspassword reveals passwords to all

6626685

There is a memory leak every time an attachment is fetched

6626674

There is a cshttpd memory leak under stress

6626006

csdb rebuild and csrestore from backup fails due to sbin directory ownership issue

6625765

Calendar Server import process causes attachments to be truncated

6624889

Calendar Server encoding session id makes Outlook Connector unstable*

6624747

cshttp thread lock issue in ASock_Recv

6623038

Build failure with Sun Studio 12

6622866

PROPFIND causes a denial of service of the Calendar Server

6622081

csexport should have the ability to export events including the attachment data

6622015

get_calprops.wcap not sending the correct response if calid parameter is of a calendar group

6621290

JSON syntax error: storeevents.wcap} with {{alarmpop

6621234

JSON syntax error: list_subscribed.wcap

6621213

JSON syntax error: list.wcap

6621128

JSON syntax error: get_freebusy.wcap

6620937

Calendar Server is returning incorrect ICAL output when an event contains an attachment

6620263 *

cscomponent command is missing for the Communications Suite 5 Linux installation

6620139

JSON syntax error: set_userprefs.wcap

6620122

JSON syntax error: get_userprefs.wcap

6620046

JSON syntax error: search_calprops.wcap

6619357

{{cshttpd{{ crashes with memory corruption

6618932

patchadd error message

6618247

patchrm error message

6618196

JSON syntax error: storeevents.wcap with timezone ID

6617799

JSON syntax error: get_all_timezones.wcap

6617787

JSON syntax error: deletecomponents_by_range.wcap

6617784

JSON syntax error: deletetodos_by_range.wcap

6617782

JSON: deletetodos_by_id.wcap syntax error

6616433

config-servicetags exits abnormally on Linux

6615480

JSON output has syntax errors

6615475

Calendar Server needs to locate correct product path when the Communications installer is used with altroot

6615440

Calendar Server needs to create /var/opt/sun/install on Linux

6612742

There is a cshttpd crash in print_event_detail

6612651

nswcalCALID should be removed from Calendar Server 6.3 LDAP update code

6611728

While creating an event if you invite a resource, it shows the RSVP status as "Accepted" if autoaccept is enabled

6609386

config-mfwk and config-servicetag scripts are needed for Uniformity in Documentation for Calendar Server and Messaging Server*

6607940

New calendar creation mail feature causes functional test failures

6607478

com.sun.cmm.cs.xml has hard-coded values

6605715

Update timezones.ics file with the Venezuela time zone change

6604662

You cannot add more invitees to an event when another existing user is removed from LDAP

6603427

Calendar Server emits malformed XML if an event contains an attachment*

6602903

csrename causes a core dump while renaming the calendars

6597809

Double-booking restrictions are ignored when importing an event

6596706

The cshttpd process is crashes when you try to update the attachment information for a recurring series

6596628

Implement getVersion for Calendar Server

6592804

The cshttpd process crashes in the DWP setup due to memory corruption when fetching the attachment*

6592448

A cshttpd crash occured in loginincorrect_negative

6591407

The cshttpd process crashes if the master copy of the recurring event is missing*

6590680

cshttpd may crash in attachment-related functions for the events created with patch-17 in DWP setup*

6589856

cshttpd is crashing in shtml_command when browser.cache.enabled is set to "yes"

6588744

Inviting resources to an event shows wrong RSVP status if autoaccept is enabled

6588737

Calendar Server emits broken XML if the email field contains quotes

6588557

Error 81 is returned when an attendee is removed from a single instance of a recurring event

6585886

Recurring events are not shown in Outlook Connector after running csrename

6583657

Change output from "error" to "debug" for caldb_pvt_ScanDeleteLog: Resurrected entry

6580129

fetchcomponents_by_id.wcap could cause cshttpd to crash when it returns error 81

6578849

Emit calendar data in JSON format

6577773

Sun Java Enterprise System Monitoring Framework product identifying tag needs to be fixed

6572538

There is no jmqclient bundled in Calendar Server 6.3.1 on Linux

6571479

admind.log shows confusing log message for jmqInit

6569278

Creating an event by inviting a resource calendar fails with "Unknown Error 80"

6568622

httpd does not start with Message Queue 3.7 on Linux

6567265

Make number of Berkeley database locks configurable

6565532

csdwpd crashes if there are any errors while reading the calendar properties

6564744

cshttpd crashes with fetchcomponents.wcap when run under libumem

6563558

The cshttpd process memory grows very quickly if many events or to do's are fetched in a single request

6563284

dbstore_is_archivebackup_enabled contains an incorrect return value

6561930

Update timezones.ics file with the new DST changes in New Zealand

6559166

hotbackup and archive should copy all .db files*

6558709

*The front-end system receives a "backup failed" error email even when archive and hotbackup are disabled.

6555671

The copyright for Calendar Express is still 2006

6554012

httpd crash on freebusy query uses mail if redirect is on

6548178

Alarm retry feature may result in thousands of event reminders

6546804

The icsSubscribed attribute is not removed from LDAP by cscal when deleting a calendar created by Communications Express

6546620

fetchattachment.wcap over DWP may return a corrupted file

6546549

A memory leak occurs when an event with attachment is saved

6546541

Uploaded files are not getting deleted after the attachment is saved

6546535
The cshttpd process crashes in ac_fetchattachment() if the event in the database does not have an attachid

6546532

csimport crashes when you try to import an event with an attachment

6545488

There is a crash in wcap_login on Linux

6545035

attachid is missing in fetchcomponents_by_.wcap in DWP setup*

6542989

csconfigurator.sh creates an invalid DWP configuration

6541912

fetchcomponents returns a malformed WCAP response for calendar events having an LDAP group as an attendee

6541320

The Calendar Express window title shows incorrect version 6 5

6540503

Attachment store needs to open with a hash flag to maintain only a single copy for each back end

6538972

• Notification and reminder timings are off by an hour with the new DST dates*

6537923 \

The copy file utility function fails silently with large files

6537359

In Calendar Server 2005Q4, the timezones.ics file does not account for 2007 DST differences in Mexico

6531658

csrename returns a segmentation fault and crashes in csadm_rename_in_ldap()

6530207

csrestore is unable to restore a calendar from the backup database. It cannot connect to the watcher process.

6525791

csrename stops abruptly without renaming the LDAP database

6524804

Calendar creation begins to degrade as the number of calendars increases for a single user when using bulk load

6522147

Users can log in with icsstatus=inactive

6520001

Hide passwords

6516438

You cannot login to Calendar Server after an upgrade. You will see "Backend Host Unresolvable" on the login page

6509780

Follow new versioning policy

6505280

Introduce daylight savings for Western Australia

6500444

*There is an HTTP Request Smuggling security issue in cshttpd

6498903 There is a cshttpd crash in caldb_pvt_ReadLinkedComponent()*

6498212

The configurator throws a java exception when you choose which server to use as a back end in DWP setup

6497774

csmigrate should create the target directory with the owner icsuser:icsgroup if it is run by root

6497116

The configurator window's title shows Sun Java System Calendar Server Version 6 5

6496627

Changing the calendar event case in Calendar Express with no spaces added or removed fails the first time

6496601

Deleting the secondary calendar does not remove it from the database

6496586

When switching from December to January using the monthly view, Calendar Express displays January of current year

6496353

There are memory leaks in cshttpd

6494811

admind dumps core when JMQ is enabled

6494557

There is a WCAP problem replacing X-properties on recurring components

6494514

All-day events are shifted by one day after importing a .ics file*

6489729

Calendar Server's HTTP server crashes while accepting invitations

6486422

Calendar Express does not display all-day events in some views (Day/Overview)

6480935

Recovery function for databases failed

6479810

There are session database issues

6475187

WCAP deleteevents_by_id returns non-published iErr -5010

6475106

cshttpd uses too much memory

6474557

Database handles remain open during environment close

6472348

The csadmind process is spinning and using 100% CPU

6461762

Change the absolute path to relative path in the post install script

6456901

watcher.log date/time stamp diverge from the standard used in other log files

6442769

Calendar Server should add the X-Sun-calendar-msg: ITIP Method in calendar notifications

6442476

User calendars automatically created at login have auto-provisioning turned off resulting in calendars not being created on the server

6422917

Notification of an event contains garbled multi-byte characters

6407790

Use the output "This command is not valid for schema 2" message for csattribute, csuser, and csdomain with any option

6406628

JMQ notifications are not triggered for advanced options

6391858

csstats is no longer reporting authentication, alarm, disk, or response statistics*

6378975

Online Help is not available for new panels in the Calendar Server configurator

6331404

Exception invitations do not show up in Outlook using the connector

6289810

By default, invitations should be "Accepted" for resource calendars

6282134

Some strings need to be translated in event notifications in zh-CN and zh-TW versions of Communications Express

6280808

*The title of the tasks List in the Spanish version is corrupted.

6280710

Month names should begin with lower case letters in the Spanish version

6279597

The text for introducing the time in the new-task dialog in the Spanish version is incorrect

6279591

The initials for the days in the Calendar Server web client are incorrect in the German, Spanish, and possibly the French versions*

6278714

There is an unnecessary tilde in the message warning about deletion of repeating tasks

6278698

The copyright year 2003 on the Calendar Express login page is incorrect

6275914

The Calendar Server configurator online help is out of sync with the Spanish GUI

6236637

The version of the administration tools displays the wrong build date

6214765

The string in the Spanish versio of the "Create Group" window is corrupted

5109953

The createcalendar.wcap command writes errors to the directory server logs

5069988

cscomponents -e date removes all tasks after the end date

4924536

HTML is not rendered under the "Preview" tab of "Edit Event" dialog

Known Issues and Limitations in Calendar Server

This section contains known issues at the time of this Calendar Server 6.3 release:

• Calendar Server Issues
• Documentation Issues in Calendar Server

Calendar Server Issues

Calendar Server Upgrade on x86 Platforms Using the Installer is Not Supported

Upgrading Calendar Server using Communications Suite 6 installer (specifically commpkg upgrade) is not supported on x86 platforms. Instead follow the manual steps to upgrade Calendar Server on x86 platforms.

6688858

*There are some issues when upgrading Calendar Server HA and SC_SCHA via the Communications Installer."
Workaround: After the upgrade, mount the config directory and run csconfigurator.sh -nodisplay -noconsole -novalidate.

6695856

./csconfigurator fails to create the values from ics.conf to the cspassword file during upgrade from Calendar Server 6.2 to 6.3

6568622

httpd does not start when running Message Queue 3.7 on Linux

Calendar Server Doesn't Start After Patchadd Because New Parameters Are Added to ics.conf With value UNKNOWN (CR 6722736)

At some sites, the calendar server might not start during a patch process. If this problem occurs, use the following procedure. This procedure needs to be performed only once.

1. Set the configutil parameters below to valid values in ics.conf. For example:

caldb.berkeleydb.archive.maxdays="6"
caldb.berkeleydb.archive.mindays="3"
caldb.berkeleydb.hotbackup.maxdays="6"
caldb.berkeleydb.hotbackup.mindays="3"

2. Run the following:

./csconfigurator.sh -noconsole -nodisplay -novalidate

Contact regular support channels if this procedure does not solve the problem.

Documentation Issues in Calendar Server

Incorrect Description of icsAllowedRights Values

This issue occurs in the Sun Java System Calendar Server 6.3 Administration Guide, in the following section: D.9.3.1 icsAllowRights Attribute: csdomain Utility.

This section describes the icsAllowRights attribute and properties that you can set with the csdomain utility. The following statement is incorrect:

"If a bit corresponding to a specific right is set (value=1), the right is not allowed. If the bit is not set (value=0), the right is allowed."

The correct statement is as follows:

"If a bit corresponding to a specific right is set (value=1), the right is explicitly allowed. If the bit is not set (value=0), the right is determined by the corresponding ics.conf parameter value."

In addition, in Table D-15, icsAllowRights LDAP Directory Attribute and Properties, the values documented for the individual attribute bits are incorrect.

For example, this statement is incorrect: "allowCalendarCreation: If set (bit 0=1), do not allow calendars to be created."

This statement should read as follows: "allowCalendarCreation: If set (bit 0=1), allow calendars to be created."

Redistributable Files for Calendar Server

Sun Java System Calendar Server 6.3 contains the following set of files for which Sun Microsystems, Inc. grants you a non-exclusive, non-transferable, limited license to reproduce and distribute in binary form.

In addition, you may copy and use but not modify the listed header files and class libraries solely to cause your resulting binaries to be able to interface with Sun’s software APIs.

Sample code is provided solely for reference purposes pursuant to creating the above mentioned binaries.

All the redistributable files for Calendar Server are for the plug-in API, known as CSAPI. The API is described in the Sun Java System Calendar Server 6 2005Q4 Developer's Guide.

In the following files, cal-svr-base is the directory into which Calendar Server was installed. The default for Solaris is /opt/SUNWics5/cal, for Linux it is /opt/sun/calendar

Redistributable files are found in various subdirectories of cal-svr-base/csapi :

• authsdk Redistributable Files
• bin Redistributable Files
• classes Redistributable Files
• include Redistributable Files
• plugins Redistributable Files
• samples Redistributable Files

authsdk Redistributable Files

The following are the redistributable files in this subdirectory ( cal-svr-base/csapi/authsdk/):
cgiauth.c
expapi.h
login.html
nsapiauth.c

bin Redistributable Files

The following are the redistributable files in this subdirectory ( cal-svr-base/csapi/bin/):
libcsapi_xpcom10.so
libicsexp10.so

classes Redistributable Files

The following are the redistributable files in this subdirectory ( cal-svr-base/csapi/classes/):
ens.jar
jms.jar

include Redistributable Files

The following are the redistributable files in this subdirectory ( cal-svr-base/csapi/include/):
IIDS.h
csIAccessControl.h
csIAuthentication.h

csICalendarDatabase.h
csICalendarLookup.h
csICalendarServer.h
csIDBTranslator.h
csIDataTranslator.h
csIMalloc.hplugins
csIPlugin.h
csIQualifiedCalidLookup.h
csIUserAttributes.h
mozIClassRegistry.h
mozIRegistry.h
nsAgg.h
nsCOMPtr.h
nsCRT.h
nsCom.h
nsDebug.h
nsError.h
nsHashtable.h
nsIAtom.h
nsICaseConversion.h
nsICollection.h
nsID.h
nsIEnumerator.h
nsIEventQueueService.h
nsIFactory.h
nsIPtr.h
nsIServiceManager.h
nsIServiceProvider.h
nsISizeOfHandler.h
nsISupports.h
nsISupportsArray.h
nsMacRepository.h
nsProxyEvent.h
nsRepository.h
nsString.h
nsTraceRefcnt.h
nsVector.h
nsUnicharUtilCIID.h
nsXPComCIID.h
nsXPComFactory.h
nscore.h
pasdisp.h
publisher.h
subscriber.h
xcDll.h
xcDllStore.h

plugins Redistributable Files

This directory (cal-svr-base/csapi/plugins/) has redistributable files in the following subdirectories:

• accesscontrol Redistributable Files
• authentication Redistributable Files
• datatranslator Redistributable Files
• userattributes Redistributable Files

accesscontrol Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/plugins/accesscontrol/ ):
csAccessControl.cpp
csAccessControl.h
csAccessControlFactory.cpp

authentication Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/plugins/authentication/ ):
csAuthentication.cpp
csAuthentication.h
csAuthenticationFactory.cpp

datatranslator Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/plugins/datatranslator/ ):
csDataTranslator.cpp
csDataTranslator.h
csDataTranslatorFactory.cpp

userattributes Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/plugins/userattributes/ ):
csUserAttributes.cpp
csUserAttributes.h
csUserAttributesFactory.cpp

samples Redistributable Files

This directory (cal-svr-base/csapi/samples/) has redistributable files in the following subdirectories:

• samples/authentication Redistributable Files
• samples/datatranslator Redistributable Files
• samples/ens Redistributable Files
• samples/userattributes Redistributable Files

samples/authentication Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/samples/authentication/ ):
authlogon.c
authlogon.h
authtest.c
csAuthenticationLocal.cpp
csAuthenticationLocal.h
csAuthenticationLocalFactory.cpp

samples/datatranslator Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/samples/datatranslator/ ):
csDataTranslatorCSV.cpp
csDataTranslatorCSV.h
csDataTranslatorCSVFactory.cpp

samples/ens Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/samples/ens/):
apub.c
asub.c
rpub.c
rsub.c

samples/userattributes Redistributable Files

The following redistributable files are found in this subdirectory ( cal-svr-base/csapi/samples/userattributes/ ):
csUserAttributesDB.cpp
csUserAttributesDB.h
csUserAttributesDBFactory.cpp

Chapter 4 Sun Java System Messaging Server 7.0 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Messaging Server 7.0 including:

About Messaging Server 7.0

Messaging Server is a high-performance, highly secure messaging platform that can scale from thousands to millions of users. It provides extensive security features that help ensure the integrity of communications through user authentication, session encryption, and the appropriate content filtering to reduce spam and viruses. With Messaging Server, enterprises and service providers can provide secure, reliable messaging services for entire communities of employees, partners, and customers.

Messaging Server provides a powerful and flexible solution to the email needs of enterprises and messaging hosts of all sizes by using open Internet standards.

What's New in This Release of Messaging Server

See the Communications Suite 6 What's New document.

Deprecated and Removed Features for Messaging Server

Support for the following features may be eliminated in a future release, have already been removed in this release, or were removed in a previous release:

Messenger Express

The Messenger Express webmail interface has been removed from this release. During upgrade or migration, any existing Messenger Express files will be saved off in a backup directory and must be manually restored after downgrade. The default port for mshttpd has been changed from 80 to port 8990 to signify the removal of web page serving function of mshttpd. For an upgrade or migration, the mshttpd port will be set to the existing value.

Note This removal also includes the removal of the Messenger Express Mail Filter User Interface (msg-svr-base /SUNWmsgmf/MailFilter.war ).

NSS Security Tools

The NSS security tools (certutil, modutil, pk12util, and ssltap are no longer distributed with Messaging Server. Instead, these tools are bundled with the new Communications Installer.

Administration Console

The Sun Java System Administration Console has been removed from the Messaging Server product.

Administration functions should be performed through the Messaging Server command-line interfaces or configuration files. References in the documentation to using the console haven't yet been corrected.

DIGEST-MD5

When clients connect via IMAP, POP or SMTP to the Messaging Server, they must use a SASL (RFC 2222) authentication mechanism or a simple password to prove their identity to the server. When the LDAP directory is configured to store user passwords in the clear, all user passwords are migrated to this format and the sasl.default.ldap.has_ plain_passwords option is set on the Messaging Server, then three additional authentication mechanisms are enabled: APOP, CRAM-MD5 and DIGEST-MD5. All three of these mechanisms transmit a one-way encoding of the password over the wire rather than the password itself. Due to its limited deployment and complexity, the DIGEST-MD5 mechanism is deprecated leaving only the APOP and CRAM-MD5 mechanisms.

LMTP Native Channel

The LMTP native channel for delivery to /var/mail (tcp_lmtpn_server) has been removed in this release. LMTP is now only supported for delivery to the message store.

Messenger Express Multiplexor

The Messenger Express Multiplexor has been removed in favor of the Webmail Server. See: Webmail Server Supports IMAP.

imsimta refresh

This command has been deprecated. Use imsimta cnbuild in Sun Java System Messaging Server 6.3 Administration Reference and imsimta restart in Sun Java System Messaging Server 6.3 Administration Reference instead, as appropriate.

imsimta stop and imsimta start

New start-msg and stop-msg commands have replaced imsimta start and imsimta stop, which are deprecated and will be removed in a future release.

See start-msg in Sun Java System Messaging Server 6.3 Administration Reference and stop-msg in Sun Java System Messaging Server 6.3 Administration Reference for more information.

MMP Section and Instance features

The optional SECTION and INSTANCENAME features of the ServiceList MMP configuration parameter are deprecated and will be removed in a future release. These features make the MMP configuration more complex than necessary and it is believed the more commonly used virtual domain feature of the MMP provides sufficient configuration flexibility.

Direct Editing of MTA Databases

MTA access to database files and the imsimta tools to manipulate MTA database files are deprecated.

Netscape Browser Support

Netscape browser support will be removed at a future date.

Red Hat Linux 3 Support

Red Hat Linux 3 platform support has been deprecated in this release and will be removed in a future release. Communications Suite 6 continues to be supported on Red Hat Linux 4.

Event Notification Service (ENS)

In this release, there are two notification services for event notifications and alarms: Sun Java System Message Queue (JMQ) and Event Notification Service (ENS). For this release, Messaging Server, Calendar Server, and Instant Messaging still have internal dependencies to ENS. By default, ENS is not enabled in this release. To enable ENS, set local.ens.enable to 1.

Prior to Messaging Server 7, if you wanted to use IMAP IDLE, you had to configure an ENS notification plug-in. In this release you can use JMQ to provide IMAP IDLE notifications.

You can use JMQ for message notifications by configuring a JMQ notification plug-in. (Messaging Server allows you to configure multiple notification plug-ins.) To enable JMQ notifications, see "How do I enable JMQ event notifications?" on MsgServerDocWiki.

Ignored imta_tailor settings

As part of a future project to support an XML configuration, the MTA's tailor file is in the process of being deprecated. As previously documented, some options in that file should not have been edited or otherwise changed. With this release of Messaging Server, only eight options in that file are honored. All other options specified in the tailor file are ignored, even if they were set to non-default values. The eight options which are still honored are IMTA_LANG, IMTA_RETURN_PERIOD, IMTA_RETURN_CLEANUP_PERIOD, IMTA_RETURN_SPLIT_PERIOD, IMTA_TMP, IMTA_USER, IMTA_USER_USERNAME, and IMTA_WORLD_GROUP.

Obsolete configutil Parameters

The configutil parameters listed in the following table are obsolete and have been removed from the Messaging Server product.

Note If Messaging Server is upgraded from an earlier release to Messaging Server 7.0, the parameters listed in the following table are deleted from the configuration after upgrade. Before upgrading, Sun recommends that you save the configutil output to a file.

Certain options have been removed from the configuration, specifically local.serverroot and local.installeddir.

Because you may have used these options to detect the location of the installed server, configutil has been modified always to return the current server installation directory for these options when queried. You can now only use configutil to query these options. The configutil command still permits you to set values for these names (as it allows any unrecognized option name while generating a warning), but such a value is ignored. The configutil command always returns the correct install directory when your request the value of one of these options.

Deleted configutil Parameters

Requirements for Messaging Server 7.0

See Requirements for Communications Suite 6.

Note For information about upgrading to Messaging Server 7.0 from a previous version of Messaging Server, see Messaging Server Installation Notes.

Messaging Server Installation Notes

These installation notes pertain to the Messaging Server 7.0 release. This section contains the following subsections:

Installation Overview for Messaging Server

Use the Communications Services installer to install Messaging Server.

For installation instructions, see the Communications Suite 6 Installation Guide.

Next, you must configure Messaging Server by:

• Running the Directory Server Preparation Tool, comm_dssetup.pl .
• Running the Messaging Server configuration program.

For configuration instructions, see the Communications Suite 6 Initial Configuration information.

comm_dssetup.pl Changes for this Release

The following changes were implemented in the latest version of comm_dssetup.pl, the program that prepares Directory Server for Messaging Server use:

1. Silent Installation: password change
   -w dirmanager_passwd has been deprecated in favor of -jpasswd_file
2. See Messaging Server Compatibility Issues for more changes to the comm_dssetup.pl program.

Upgrade Instructions for Messaging Server

If you are upgrading to Messaging Server 7.0 from an earlier release, follow the upgrade instructions in the Communications Suite 6 Upgrade Guide.

Checking the /etc/hosts file entry

If you are installing Messaging Server for the first time or upgrading from an earlier version of Messaging Server, ensure that you have your host's IP address in the /etc/hosts file, for example:

129.158.230.64 budgie.siroe.varrius.com budgie

Note On Solaris OS 10 U3 and earlier platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the /etc/inet/ipnodes file. Otherwise, you will get an error indicating that your host name is not a Fully Qualified Domain Name. From Solaris OS 10U4 onwards, the contents of the /etc/inet/ipnodes and /etc/hosts files have been merged together into just the /etc/hosts file. Applying kernel patch 120011-14 on any Solaris 10 system will also perform the merge, and subsequent removal of the /etc/inet/ipnodes file.

Increasing ulimit For Files After Upgrade

Due to bug 6767802 (Store daemons fail to start under cluster control due to file descriptor limits enforced by cluster), fixed in Messaging Server 7.0P3, after upgrading to Messaging Server 7.0, you must increase the number of file descriptors by setting the ulimit as follows:

ulimit -n number_of_file_descriptors

For example:

ulimit -n 100000

For more information about the upgrade procedure, see the Communications Suite 6 Upgrade Guide. For more information on Solaris tunable parameters, see Solaris Tunable Parameters Reference Manual.

This is fixed in Messaging Server 7.0P3

Messaging Server Compatibility Issues

To purge users with iPlanet Delegated Administrator when you are running Messaging Server 6.3, see Purging Users with iPlanet Delegated Administrator and Messaging Server 6.3.

The following table describes compatibility issues with Messaging Server:

Incompatibility	Workaround	Comments
comm_dssetup.pl, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Interactive Mode: Server-root and Directory Server Instances	Directory Server instance(s) reside in the server-root, or an explicit Directory Server instance directory Previous versions of Directory Server used the notion of a server-root where multiple instances and configuration info would be housed. Directory Server 6 no longer uses a server-root. Instances may be anywhere. In this question, a user needs to: 1) specify the instance directory. Or, if the user is using previous versions of Directory Server, the user can: 2) specify the server-root directory where the instances are housed. You will be prompted with an additional question to pick an instance from the server-root. Or, 3) a user who has used Directory Server 5x and is now using Directory Server 6 might manually put all of her Directory Server instances under a parent directory (what we used to call a server-root). Note Server-root terminology has been removed from Directory Server 6.	no additional comments
comm_dssetup.pl, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Silent Installation: server-root directory	In previous versions of Silent installation, you would specify both a server-root and an instance directory. If you are using Directory Server 5.x, this still holds true. Since there is no server-root directory in Directory Server 6.0, you will need to specify the parent directory of the Directory Server instance.	no additional comments
The location of the Directory Preparation Tool (comm_dssetup.pl) has changed.	comm_dssetup.pl is now in its own package installed in /opt/SUNcomds for Solaris, and /opt/sun/comms/dssetup for Linux Existing scripts that specify the old path need to be updated.	To install the package, be sure the Directory Preparation Tool is selected in the appropriate installer panel.
In Messaging Server 5.x, an administrator could use the IMAP listcommand to display all folders in the message store. In a typical message store, this caused the server to display an unusually long list. In Messaging Server 6.x, when an administrator runs the IMAP list command, it displays only the explicitly shared folders.	To list all folders in the message store, use the mboxutil utility.	For more information on the mboxutil utility, see the Sun Java System Messaging Server 6.3 Administration Guide.
The configuration program for the Delegated Administrator has changed.	Install Delegated Administrator and run the configuration program. The current program is located at: for Solaris, /opt/SUNWcomm/bin/config-commda for Linux /opt/sun/comms/config-commda	Upgrade to the new Delegated Administrator when installing this version of Messaging Server.
Upgrading Messaging Server with Webmail over IMAP protocol change (6397425, 6397451, 2137362)	The back-end server must be upgraded before upgrading the front-end server. Both the Webmail over IMAP protocol as well as the back-end message stores must be the same product version. See the Sun Java Communications Suite 5 Upgrade Guide for details.	no additional comments
This release of Communications Express is incompatible with the previous version of Messaging Server.	If you upgrade Communications Express, you must also upgrade Messaging Server.	This also applies to Calendar Server. For more information on Communications Express, see Chapter 6, Sun Java System Communications Express 6.3 Release Notes.
Clarification is needed on RTF/HTML editing and browser compatibility for Messenger Express and Communications Express. (6311363)	On Messenger Express, you are able to use RTF/HTML editing for Internet Explorer browsers. You are unable to use RTF/HTML editing with Mozilla or Netscape browsers. In the JES 2004Q2 version of Communications Express, you are able to use RTF/HTML editing for Internet Explorer browsers. You are unable to use RTF/HTML editing with Mozilla or Netscape browsers. In the JES 2005Q1 version of Communications Express, you are able to use RTF/HTML editing for Internet Explorer 5.5 or later, Mozilla 1.3 or later, or Netscape 7.2 or later.	No additional comments.
"session.timeout Login Again" pop-up error displays when you click Communications Express in Portal Server. (6417988)	Ignore the pop-up error, close the window, and continue to use Communications Express.	No additional comments.
If you use Messaging Server with Access Manager Single Sign-on, it does not support Java Enterprise System 2004Q2 Access Manager Server. However, Access Manager 6.3 and later is supported.	The specific versions of Messaging Server that do not support Java Enterprise System 2004Q2 Access Manager Server are: Messaging Server 6.2-6.01 and later Messaging Server 6.3	Upgrade Access Manager (JES 2004Q2) before upgrading Messaging Server.
Access Manager now has two installation types: Realm (version 7.x style) and Legacy (version 6.x style).	If you are installing Access Manager with Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator, or Portal Server, you must select Legacy mode (version 6.x style). See: Sun Java System Access Manager 7 2005Q4 Release Notes	If the wrong Access Manager is installed, you will not be able to run Delegated Administrator.

Messaging Server Documentation Updates

Messaging Server Compatibility Issues

Problems Fixed in This Release of Messaging Server

6676443

Messaging Server configure utility reports an installation task failure if SNMP is not installed

4991650

Messaging Server does not support a staged rolling upgrade with minimum downtime in a symmetric HA environment

Known Issues and Limitations in Messaging Server

This section describes known issues in the Messaging Server product.

6686339

When imap.numprocesses is set to 10, IMAP flag updates are not working in an IDLE session
When service.imap.numprocesses is set to 1 (default), FLAG updates in an IDLE session can be seen. But if service.imap.numprocesses is set to 10, then flag updates are not seen.

Workaround: Change the MaxNumProducers setting to -1 when using JMQ with IMAP.

6648157

Messaging Server upgrade from 6.3 to 7.0 has one diff3 error in the imta_tailor.new file.
This problem is present in the beta, but is resolved in the beta refresh. If a pre-existing 6.3 or below installation is upgraded to 7.0, patch-config will report a diff3 error in the imta_tailor.new file. The workaround is to manually merge these changes. Open imta_tailor.new in an editor, delete the line beginning with "<<<<<<<" and every line up to and including "=======" except the "IMTA_WORLD_GROUP" line, then leave in any remaining lines which remain except the "IMTA_WORLD_GROUP" line. Finally, and delete the line starting with ">>>>>>>".

For example, if this is the file you begin with:

! $Revision: 1.33 $
!
IMTA_USER=mailsrv
IMTA_USER_USERNAME=nobody
<<<<<<< /opt/sun/comms/messaging/install/migrate/from-6.3-0.15/save/config/imta_tailor.new
IMTA_WORLD_GROUP=mail
IMTA_ROOT=/opt/sun/comms/messaging
[...]
IMTA_HOLD=/opt/sun/comms/messaging/config/hold_list
=======
IMTA_WORLD_GROUP=<local.servergid>
>>>>>>> /opt/sun/comms/messaging/install/migrate/from-6.3-0.15/backout/lib/config-templates/imta_tailor.new.sed

You should edit it manually to become:

! $Revision: 1.33 $
!
IMTA_USER=mailsrv
IMTA_USER_USERNAME=nobody
IMTA_WORLD_GROUP=mail

6569452

The following mailbox database error message can be displayed: "Environment reference count went negative."
The message store processes do not call the underlying database method that generates this error. The error message is thus irrelevant.

Workaround: Ignore the error message.

6654364

The IMAP server closes down a client's connection after the fetch command.
The client's connection to the server should remain open.

No Issue ID

After an upgrade, when you restart the server, the Berkeley Database issues a log version error, issuing the following message: 'Skipping log file...historic log version.'
This is expected behavior. Ignore this message. The Berkeley Database creates a new log file and continues logging into the new file. For example, it creates log.0000000002 and continues.

Redistributable Files for Messaging Server

The following redistributable files are provided with Messaging Server 6.x:

• You can redistribute the following files in source (HTML and Javascript) or binary form (GIF files) within a licensed Messaging Server distribution only:
  • msg-svr-base/config/html (and subdirectories)
  • msg-svr-base/install/config/html (and subdirectories)
    You are not permitted to distribute these files by themselves.

• You can copy and use (but not modify) the following header files solely to create and distribute programs to interface with Messaging Server APIs, to compile customer written code using the documented API to interoperate or integrate with Messaging Server, and only as expressly provided in the Messaging Server documentation:
  • msg-svr-base/examples/meauthsdk/expapi.h
  • msg-svr-base/examples/tpauthsdk/authserv.h
  • All files in the msg-svr-base/include directory (default location)

• The following files are provided solely as reference for writing programs that use the documented API to integrate with Messaging Server:
  • msg-svr-base/examples/meauthsdk/
  • msg-svr-base/examples/tpauthsdk/
  • msg-svr-base/examples/mtasdk/

Chapter 5 Sun Java System Instant Messaging Software Version 7.3 Release Notes

This chapter contains important release information about Sun Java System Instant Messaging Software version 7.3. The release notes contain the following sections:

About Instant Messaging Version 7.3

Sun Java System Instant Messaging software delivers secure presence and extended real-time messaging, enabling user communities to communicate and collaborate instantly and securely. It combines the instant-messaging capabilities with conferences, alerts, news, polling, and file transfer, to create a rich collaborative environment. It leverages an existing community that can be managed by using LDAP, Sun Java System Access Manager, or Sun Java System Portal Server.

What's New in This Release of Instant Messaging

See the What's New in This Release of Communications Suite 6 document.

Deprecated and Removed Features for Instant Messaging 7.3

Instant Messaging 7.3 does not have any deprecated features or removed features for this release.

Requirements for Instant Messaging 7.3

See Requirements for Communications Suite 6 and Requirements for Instant Messaging.

Instant Messaging Installation and Uninstallation Notes

This section contains important information about installing and uninstalling Sun Java System Instant Messaging software. If you are using Sun Java System Access Manager with Instant Messaging, install the Legacy (version 6 style) Access Manager by using the Sun Java Enterprise System installer. This version of Instant Messaging is not compatible with the Realm (version 7 style) Access Manager.
If you use Access Manager to store policies when configuring Instant Messaging, the following policies are created:

• Ability to administer Instant Messaging and Presence Services
• Ability to change your own Instant Messaging settings
• Ability to manage Instant Messaging Conference Rooms
• Ability to manage Instant Messaging news channels
• Ability to send Instant Messaging alerts
• Ability to watch changes on other Instant Messaging users
• Default Instant Messaging and presence access

Instant Messaging Documentation Issues

This section contains information about known issues in the documentation.

Instant Messaging Administration Guide

This section lists information that is not documented in the Administration Guide.

Instant Messaging Online Help and Quick Reference

The following information is not described in the product online help or the quick reference guide.

Instant Messaging Compatibility Issues

The following table lists the compatibilities issues in Instant Messaging 7.3.

Table 5-1 Instant Messaging 7.3 Compatibility Issues

Problems Fixed in This Release of Instant Messaging

This section describes the problems fixed in the Instant Messaging version 7.3 release.

Known Issues and Limitations in Instant Messaging

This section contains a list of known issues at the time of release of Instant Messaging version 7.3.

Instant Messaging Installation, Upgrade, and Uninstallation Issues

chown -R imuser:imgroup /var/opt/sun/comms/im/default
chown -R imuser:imgroup /etc/opt/sun/comms/im/default

file /opt/sun/im/lib/imService.ldif from    \
install of sun-im-install-7.2-24 conflicts with    \
file from package sun-im-ident-7.0-13

Instant Messaging Server-to-Server Communication Issues

Instant Messaging Configurator Tool Issues

Instant Messaging XMPP/HTTP Gateway Issues

Instant Messaging Redirect Server Issues

Instant Messaging News Channel Issues

Instant Messenger Issues

This section contains a list of known issues at the time of release of Instant Messenger version 7.3.

Instant Messenger General and Usability Issues

Instant Messenger Login, Logout, and Connectivity Issues

Instant Messenger Chat Issues

Instant Messenger Printing Issues

Instant Messenger Policy Management Issues

Instant Messenger Conference Room Issues

Instant Messenger Alerts Issues

Instant Messaging Single Sign-On (SSO) Issues

Other Known Issues

Starting Server                      [OK]
Starting Multiplexor                 [OK]
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.
[Fatal Error] :1:1: Premature end of file.

/opt/sun/comms/im/sbin/imadmin [options] migratepropstore \\
[error_log]

/opt/sun/comms/im/sbin/imadmin migratepropstore \\
[options] [error_log]