Printable Communications Suite 6 Update 2 Release Notes

Skip to end of metadata
Go to start of metadata
Contents

Common Release Information for Sun Java Communications Suite 6 Update 2 Component Products

These release notes contain important release information that is common for all component products of Sun Java Communications Suite 6 Update 2.

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 Update 2

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 Update 2 release includes the following components:

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 Communications Suite 6 Update 2 What's New document.

Deprecated and Removed Features for Communications Suite

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

Communications Express 6.3

Going forward, no new features will be added to the Communications Express user interface. It has been deprecated in favor of Sun Convergence. Communications Express will be removed from the product in a future release.

No patches will be issued for Communications Express versions prior to 6.3.

Delegated Administrator 6.4

Going forward, no new features will be added to Delegated Administrator 6.4. It has been deprecated in favor of Delegated Administrator 7.

Connector for Microsoft Outlook 7.1 , 7.2, and 7.2 Update 1

Going forward, no new features will be added to the Connector for Microsoft Outlook 7.1, 7.2, and 7.2 Update 2. They have been deprecated in favor of Connector for Microsoft Outlook 7.3.

Communications Sync

Going forward, no new features will be added to Communications Sync. All versions of Communications Sync have been deprecated. If you are using Communications Sync, consider moving to Sun Java Mobile Communications.

Requirements for Communications Suite 6 Update 2

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 Update 2 products? Table 1-1 lists the Sun Java System product versions that are compatible with the Communications Suite 6 Update 2 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 Update 2

Product Version Required or Optional?
Sun Java System Directory Server 5.x, 6.x Required. 6.3 or later recommended.
Sun Java System Message Queue 4.3 Optional. Communications Suite installer automatically installs Message Queue as a shared component.
Sun Java System Access Manager 7.1 Optional.
Sun Java System Application Server 9.1 Update 2 9.1 Update 2 is required as the web container for Sun Convergence 1 Update 2.
Sun Java System Web Server 7.0 Update 2 Instant Messaging, Communications Express, and Delegated Administrator require a web container. Use either Web Server 7.0 Update 1, Application 8.2P2, or Application Server 9.1 Update 2 (recommended).

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 2, see the Sun Java System Application Server 9.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 Update 2 Component Dependencies

Product Component Dependencies Required or Optional? Must Be on Local Host?
Messaging Server 7 Update 2
(64-bit or 32-bit)
Directory Server 5.x, 6.x
Recommended: 6.3 or later
Required. To store user/group and domain information for authentication, authorization, and email delivery. No
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 6 Update 2 installer.
Required. To prepare the LDAP directory for Messaging Server. No. Must be on the same host as Directory Server.
  Access Manager 7.1 (for SSO) Optional. To provide single sign-on (SSO) authentication and authorization service. You can also use the Messaging Server Trusted Circle SSO. No
  Delegated Administrator 7 Optional. To manage user and group data; to manage the directory schema. No
Calendar Server 6.3 Directory Server 5.x, 6.x
Recommended: 6.3 or later
Required. To store user/group and domain information for authentication, authorization, and calendar account provisioning. No
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 6 Update 2 installer.
Required. To prepare the LDAP directory for Calendar Server. No. Must be on the same host as Directory Server.
  Messaging Server 6.x, 7.0, 7 Update 1, 7 Update 2
Recommended: 7 Update 2
Optional. To provide email notifications. No
  Access Manager 7.1 (for SSO) Optional. To provide single sign-on (SSO) authentication and authorization service. You can also use the Messaging Server Trusted Circle SSO (if you have installed Messaging Server). No
  Delegated Administrator 7 Optional. To provision users of calendar services; to manage the directory schema. No
Instant Messaging 8 (Server) Directory Server 5.x, 6.x
Recommended: 6.3 or later
Required. To store user, conference room, and news channel data. No
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 6 Update 2 installer.
Required. To prepare the LDAP directory for Instant Messaging. No. Must be on the same host as Directory Server.
  Messaging Server 6.x, 7.0, 7 Update 1, 7 Update 2
Recommended: 7 Update 2
Optional. To support offline delivery of instant messaging alerts and chat archives as email messages. No
  Calendar Server 6.x
Recommended: 6.3
Optional. To support Calendar Server event reminder notifications. No
  Access Manager 7.1 (for SSO) Optional. To provide authentication, authorization single sign-on (SSO), and policy services. You can use a local Access Manager client SDK, which provides access to a remote Access Manager Server; if you deploy the SDK, a remote Access Manager Server must be deployed to support it. No. However, if you want IM to use a remote Access Manager, the Access Manager SDK must be installed on the host where the IM server is installed.
  Web container, one of:
Application Server 9.1 U2
Application Server 8.xRecommended: AS 9.1 U2
Web Server 7 or higher
Optional. To support distribution and downloading of the Instant Messenger Java client and to provide IMPS Gateway and HTTP Gateway functionality. Yes.
If you want the IM client to use SSO, the IM client must be deployed to the same web container as Access Manager.
Directory Server Setup Script (comm_dssetup.pl)
(Version bundled with Communications Suite 6 Update 2 installer)
Directory Server 5.x, 6.x
Recommended: 6.3 or later
Required. To set up the LDAP directory, which the comm_dssetup.pl script updates with Communications Suite components' schema. Yes
Delegated Administrator 7 Directory Server 5.x, 6.x
Recommended: 6.3 or later
To enforce unique values for mail attributes, you must install one of these releases:
Directory Server 6.xDirectory Server 5.2.5 or later
Directory Server 5.2.4, and you must apply patch 5.2_Patch_4_6313027
Required. To store user, group, and domain data that Delegated Administrator provisions for the Communications Suite components. No
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 6 Update 2 installer.
Required. To prepare the LDAP directory for Delegated Administrator. No. Must be on the same host as Directory Server.
  Access Manager 7.1 Optional. To provide authentication and authorization services when Delegated Administrator accesses the LDAP directory data. Yes
  Web container, one of:
Application Server 9.1 U2
Application Server 8.xRecommended: AS 9.1 U2
Web Server 7 or higher
Web Server 6 (compatible with Delegated Administrator 7, although WS 6 is not available for new installation)
Required. Delegated Administrator must be deployed to one of these web containers. The Delegated Administrator server must be deployed to the web container used by Access Manager. Yes
  Messaging Server 6.x, 7.0, 7 Update 1, 7 Update 2
Recommended: 7 Update 2
Required to provide mail service for users and groups provisioned by Delegated Administrator. Not required if you do not provision mail users. No
  Calendar Server 6.x
Recommended: 6.3
Required to provide calendar service for users and groups provisioned by Delegated Administrator. Not required if you do not provision calendar users. No
Convergence 1 Update 2   For details about Convergence dependencies, see Convergence 1 Update 2: Product Version Compatibility Requirements.  
Communications Express 6.3 Directory Server 5.x, 6.x
Recommended: 6.3 or later
Required. To store user/group data in the LDAP directory; to store address book data in the LDAP directory. No
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 6 Update 2 installer.
Required. To prepare the LDAP directory for Communications Express. No. Must be on the same host as Directory Server.
  Access Manager 7.1 Optional. To provide single sign-on (SSO) authentication and authorization services for Communications Express users. No
  Web container, one of:
Application Server 9.1 U2
Application Server 8.xRecommended: AS 9.1 U2
Web Server 7 or higher
Required. Communications Express must be deployed to one of these web containers. Yes
  Messaging Server 6.x, 7.0, 7 Update 1, 7 Update 2
Recommended: 7 Update 2
Required to provide mail service for Communications Express users. No. However, we recommend deploying the Webmail Server component of Messaging Server on the same host as Convergence for scalability and performance.
  Calendar Server 6.x
Recommended: 6.3
Required to provide calendar service for Communications Express users. No

NSS Requirements

Communications Suite 6 Update 2 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 Update 2: Product Version Compatibility Requirements

The information in this section provides you with all the product requirements and minimum product versions 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 Update 2

Product Version Required or Optional? Must Be on Local Host?
Sun Java System Directory Server Enterprise Edition Release 5 and later, Release 6 and later Required. At least version 6.3. For the recommended version to download, see Get the Software. No
Sun Java System Application Server 9.1 Update 2
Note
It is recommended that you upgrade to Sun Java System Application Server 9.1 Update 2 Patch 08 or later for better performance.

.

Note
The following patches that were released after the release of Sun Java System Application Server 9.1 Update 2 do not work with Sun Convergence 1 Update 2:
  • Patch 06
    • Solaris SPARC - 128640-08 (package-based), 128643-08 (file based)
    • Solaris x86 - 128641-08 (package-based), 128644-08 (file based)
    • Linux - 128642-08 (package based), 128645-08 (file based)
  • Patch 07
    • Solaris SPARC - 128640-09 (package-based), 128643-09 (file based)
    • Solaris x86 - 128641-09 (package-based), 128644-09 (file based)
    • Linux - 128642-09 (package based), 128645-09 (file based)

Required. For the recommended version to download, see Get the Software. Yes
Sun Java System Access Manager 7.1 Optional. Required only if you want to use Access Manager for authentication and/or SSO.
Convergence supports both Access Manager Realm mode (the default) and Legacy mode for providing authentication and SSO.
No
Sun OpenSSO Enterprise 8.0 Optional. Required only if you want to use Sun OpenSSO Enterprise for authentication and/or SSO. No

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 Update 2

Product Version Communications Suite Release Required or Optional? Must Be on Local Host?
Messaging Server - Webmail Server 7 Update 2 6 Update 2 (for MS 7 Update 2 Required to provide mail service in Convergence. No, but you should deploy Webmail Server on the same host as Convergence for scalability and performance.
Messaging Server - all other MS components 6.3, 7.0, 7 Update 1, 7 Update 2 5 (for MS 6.3)
6 (for MS 7.0)
6 Update 1 (for MS 7 Update 1)
6 Update 2 (for MS 7 Update 2
Required to provide mail service in Convergence. No
Calendar Server 6.3, patch level -35 or higher 5 + apply patch level -35
6 + apply patch level -35
6 Update 1 + apply patch level -35
6 Update 2
Required to provide calendar service in Convergence. To support Convergence, Calendar Server 6.3 must be at least at the -28 patch level. No
Instant Messaging 8 Update 1 6 Update 2 (for Instant Messaging 8 Update 1) Required to provide Instant Messaging service in Convergence. No
Directory Server Setup script, comm_dssetup.pl You must use the version that is bundled with the Communications Suite 6 Update 2 installer. 6 Update 2 Required. You must run comm_dssetup.pl on the hosts where Directory Server is installed. No
Delegated Administrator 6.4, 7.0-0.00
5, 6, or 6 Update 1, or 6 Update 2 Optional. No

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 Update 2 Compatibility with Communications Express, Connector for Microsoft Outlook, Address Book Store, and LDAP Schema

Product Version Communications Suite Release Required or Optional?
Communications Express 6.3 5, 6, or 6 Update 1 Optional. You can deploy Communications Express with the same Messaging Server, Calendar Server, and Directory Server as Convergence 1 Update 2. You can configure end users to access Communications Suite services through either client.
Connector for Microsoft Outlook 7.3, 7.3 Update 1 6 (for 7.3)
6 Update 1 (for 7.3 Update 1)
Optional. You can deploy Connector for Microsoft Outlook with the same Communications Suite products and Directory Server as Convergence 1 Update 2. End users of Outlook (configured via the Connector for Microsoft Outlook) can access the same Communications Suite services as those accessed via Convergence and Communications Express.
Personal Address Book store Can be configured by either Convergence 1 Update 2 or Communications Express 6.3 N/A. (The Address Book store resides in an LDAP directory.) You can configure Convergence 1 Update 2, Communications Express 6.3, and Connector for Microsoft Outlook 7.3 to use the same Address Book store.
Convergence end users can access and update an existing Address Book store configured on an existing Directory Server by using Communications Express. Conversely, you can configure Communications Express end users to access and update an Address Book store originally configured via Convergence 1 Update 2.
Updates to the Address Book made in one client are visible and accessible on the other client.
New Address Book features provided by Convergence do not invalidate Address Book LDAP entries originally configured by using Communications Express. From the perspective of the Communications Express client, the Address Book functions as it did before Convergence was installed.
A Note About Corporate Address Books:
Convergence can be configured to support one Corporate Address Book for each hosted domain. Users of Communications Express who use a single Corporate Address Book can also access and update that Address Book through Convergence.
Caveat: Communications Express users who access multiple Corporate Address Books (in their domain) can only use the first Corporate Address Book through Convergence. The others are not accessible through Convergence.
LDAP Schema Schema 1 or 2
Schema 2 only if Access Manager is deployed with Convergence.
N/A If you use Access Manager (Realm Mode or Legacy Mode) to provide Single Sign-on (SSO) for Convergence, you must use Schema 2.
If you use Delegated Administrator (DA) to provisions users, you must use Schema 2, because DA depends on Access Manager (Legacy Mode), which requires Schema 2.

Memory and Disk Space Requirements

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

Product Disk Space RAM Other
Sun Java System Calendar Server Approximately 500 Mbytes of disk space for typical installation. For production systems, at least 1 Gbyte. 128 Mbytes of RAM. For production systems, 256 Mbytes to 1 Gbyte for best performance. RAID storage for fast access (recommended for large databases).
Sun Convergence Approximately 100 Mbytes of disk space for initial installation. 1 Gbyte minimum.  
Sun Java System Messaging Server 1 Gbyte for production deployment or 500 Mbytes for evaluation installation. You also need adequate space for message store, database configuration directory, and log files, depending upon your site size. 1 Gbyte minimum.  
Sun Java System Instant Messaging Approximately 300 Mbytes of free disk space for the software.
Approximately 5 Kbytes of disk space for each user.
At least 256 Mbytes of RAM. The amount of RAM needed depends on the number of concurrent client connections, and whether the server and multiplexor are deployed on the same host.  
Delegated Administrator The disk requirements for Delegated Administrator are the same as those of the Web container to which Delegated Administrator is deployed.
For information about the Web container's hardware requirements, see the current release notes for this Java Enterprise System component.
The memory requirements for Delegated Administrator are the same as those of the Web container to which Delegated Administrator is deployed.
For information about the Web container's hardware requirements, see the current release notes for this Java Enterprise System component.
 
Communications Express Approximately the same as Messaging Server/Calender Server. 1 Gbyte minimum.  

Operating System Requirements

This release supports the following platforms:

Table 1-7 Operating System and Platform Support

Operating System CPU Comments
Solaris OS 10 SPARC, x86, x64  
Solaris OS 9 SPARC, x86  
Red Hat Enterprise Linux 4
Advanced Server (32-bit and 64-bit versions)
Enterprise Server (32-bit and 64-bit versions)
x86, x64
  • Distinct 32-bit x86 and 64-bit AMD64/Intel EM64T distributions exist.
  • Advanced Server and Enterprise Server provide identical functionality. Essentially ES limits CPU/memory support.
Red Hat Enterprise Linux 3
Advanced Server (32-bit and 64-bit versions)
Enterprise Server (32-bit and 64-bit versions)
x86, x64
  • Distinct 32-bit x86 and 64-bit AMD64/Intel EM64T distributions exist.
  • Advanced Server and Enterprise Server provide identical functionality. Essentially ES limits CPU/memory support.
Windows 2000 (SP 3 or higher); XP (SP 1 or higher); 2003 Terminal Server; Vista x86 For Sun Java System Connector for Outlook only.

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.

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

If you wish to locate patches for the Sun Java Communications Suite products, the following table lists the keywords used for each Communications Suite product. You can use the specific keyword to search for relevant patches on Sunsolve.

Patch Keywords for Communications Suite Products

Product Keyword
Calendar Server "Calendar Server"
Communications Express "communications express"
Convergence "convergence"
Delegated Administrator commcli
Dssetup comm_dssetup
Instant Messaging "Instant Messaging"
Messaging Server "Messaging Server"
Connector for Microsoft Outlook "Outlook Connector"

High Availability Support

Table 1-9 Supported High-Availability Products

Product Supported Versions
Calendar Server 6.3
  • Sun Cluster
    • SPARC: 3.0, 3.1 Update 4, 3.2
    • x86: 3.1 Update 4, 3.2
    • Linux: Not Supported
  • Veritas
    • SPARC: Not Supported
    • x86: Not Supported
    • Linux: Not Supported
Instant Messaging 8
  • Sun Cluster
    • SPARC: 3.1 Update 4, 3.2
    • x86: 3.1 Update 4, 3.2
    • Linux: Not Supported
  • Veritas
    • SPARC: Not Supported
    • x86: Not Supported
    • Linux: Not Supported
Messaging Server 7 Update 1
  • Sun Cluster
    • SPARC: 3.0, 3.1 Update 4, 3.2
    • x86: 3.1 Update 4, 3.2 U1
    • Linux: Not Supported
  • Veritas
    • SPARC: 3.5, 4.0, 4.1, 5.0
    • x86: 3.5, 4.0. 4.1, 5.0
    • Linux: 4.1,5.0

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

MS High-Availability Agent Version Compatible Messaging Server Versions
MS_SCHA 7.0 Messaging Server 64-bit version 6.3 or later
Messaging Server 64-bit will not work with MS_SCHA 6.x.
MS_SCHA 7.0 Messaging Server 32-bit version 6.3-1.02 or later.
MS_SCHA 6.x Messaging Server 32-bit version 6.3

Browser Requirements for Communications Suite Clients

The following browsers are supported for Communications Suite clients.

Table 1-10 Supported Browser Versions for Convergence Clients

Browser Windows XP Windows 2000 Windows Vista Solaris Red Hat Linux Mac OS 10.x
Microsoft Internet Explorer 7.x N/A 7.x N/A N/A N/A
Firefox 2.0.0.11 minimum
3.0.x
2.0.0.11 minimum
3.0.x
2.0.0.11 minimum
3.0.x
2.0.0.11 minimum
3.0.x
2.0.0.11 minimum
3.0.x
2.0.0.11 minimum
3.0.x
Safari N/A N/A N/A N/A N/A 3.1.x

Table 1-11 Supported Browser Versions for Communications Express Clients

Browser Windows XP Windows 2000 Solaris Red Hat Linux Mac OS 10.x
Microsoft Internet Explorer 7.0 6.0 SP1 N/A N/A N/A
Safari N/A N/A N/A N/A 3.0
Firefox 2.0 2.0 2.0 2.0 2.0

Table 1-12 Supported Browser Versions for Delegated Administrator Clients

Browser Windows XP Windows 2000 Solaris
Microsoft Internet Explorer 6.0 SP1 and 7.0 6.0 SP1 and 7.0 N/A
Firefox 2.0 2.0 2.0
Mozilla 1.4 or later 1.4 or later 1.4 or later
Netscape Navigator 7.2 7.2 7.2

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 10 U4 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
  • 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

Operating System Browser
Solaris OS 10 JDS Desktop Netscape Communicator, minimum 8.0, Mozilla minimum 1.7.12, Mozilla Firefox minimum 1.5.0
Red Hat Linux Desktop Minimum 7.0 Netscape Communicator, minimum 8.0, Mozilla minimum 1.7.12, Mozilla Firefox minimum 1.5.0
Red Hat Linux Desktop Minimum 9.0 Netscape Communicator, minimum 8.0, Mozilla minimum 1.7.12, Mozilla Firefox minimum 1.5.0
Windows 98/ME/NT/2000/XP No restrictions
Mac OS X No restrictions

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

Product Version Communications Suite Release Required or Optional?
Messaging Server 6.3, 7.0 5 (for 6.3) or 6 (for 7.0) Required to provide mail service.
Calendar Server 6.3, 6.3.1 5 Required to provide calendar service.
Convergence 1.0 6 Optional (Recommended). Either Communications Express or Convergence can be used to provide address book service, mail filters and out of office message features.
Communications Express 6.3 6 Optional.
Directory Server 5.2, 6.0 or higher 4 (for 5.2), 5 (for 6.0 or higher) or 6 (6.3 or higher) Required for GAL - corporate address book service.
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

Product Keyword
Calendar Server "Calendar Server"
Convergence TBD
Communications Express "communications express"
Delegated Administrator commcli
Dssetup comm_dssetup
Instant Messaging "Instant Messaging"
Messaging Server "Messaging Server"
Connector for Microsoft Outlook "Outlook Connector"
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

Label and State File Parameter Default Directory Comment
Access Manager
CMN_IS_INSTALLDIR
Solaris OS: /opt/SUNWam
Linux: /opt/sun/identity
 
Application Server
CMN_AS_INSTALLDIR
Solaris OS and Linux: /opt/SUNWappserver Contains Application Server utilities, executables, and libraries.
Application Server Domains
CMN_AS_DOMAINSDIR
Solaris OS and Linux: /opt/SUNWappserver/domains Default area under which administrative domains are created.
Calendar Server
CMN_CS_INSTALLDIR
Solaris OS and Linux: /opt/sun/comms/calendar  
Convergence
CMN_IWC_INSTALLDIR
Solaris OS and Linux: /opt/sun/comms/iwc  
Communications Express
CMN_UWC_INSTALLDIR
Solaris OS and Linux: /opt/sun/comms/ce  
Delegated Administrator
CMN_COMMDA_INSTALLDIR
Solaris OS and Linux: /opt/sun/comms/da  
Directory Preparation Tool
CMN_DSSETUP_INSTALLDIR
Solaris OS and Linux: /opt/sun/comms/dssetup  
Directory Server Core
DSEE_BASE
Solaris OS: /opt/SUNWdsee/ds6
Linux: /opt/sun/ds6
Separately located subcomponents of Directory Server EE include Directory Server Core, Directory Service Control Center, and Directory Proxy Server.
Directory Service Control Center
DSEE_BASE
Solaris OS: /opt/SUNWdsee/dscc
Linux: /opt/sun/dscc
 
Directory Proxy Server
DSEE_BASE
Solaris OS: /opt/SUNWdsee/dps
Linux and HP-UX: /opt/sun/dps
 
Directory Server Instance Directory
DSEE_INSTANCE_DIR
Solaris OS: /var/opt/SUNWdsee/dsins1
Linux: /var/opt/sun/dsins1
 
HADB
CMN_HADB_INSTALLDIR
Solaris OS: /opt/SUNWhadb
Linux: /opt/SUNWhadb
HADB install locations are not relocatable in Communications Suite installation.
  Solaris OS: /var/opt/SUNWhadb
Linux: /var/opt/SUNWhadb
HADB Repository Data and Log location.
  Solaris OS: /etc/opt/SUNWhadb
Linux: /etc/opt/SUNWhadb
HADB Management Agent Config File
  Solaris OS: /etc/init.d/ma-initd
Linux: /etc/init.d/ma-initd
HADB Management Agent Startup Script
Instant Messaging
CMN_IIM_INSTALLDIR
Solaris OS and Linux: /opt/sun/comms/im  
Instant Messaging Resource Directory
CMN_IIM_DOCSDIR
Solaris OS and Linux: /opt/sun/comms/im/html  
Instant Messaging Online Help Directory
CMN_IIM_DOCSHELPDIR
Solaris OS and Linux: /opt/sun/comms/im/html/en/imhelp  
Message Queue
You cannot change the installation directories, so no field is in the installer or parameter in the state file.
Not applicable Solaris OS:
/usr/bin /usr/share/lib /usr/share/lib/imq /etc/imq /var/imq /usr/share/javadoc/imq /usr/demo/imq /opt/SUNWimqLinux:
/opt/sun/mq /etc/opt/sun/mq /var/opt/sun/mq
Messaging Server
CMN_MS_INSTALLDIR
Solaris OS & Linux, 32 bit: /opt/sun/comms/messaging
Solaris OS 64-bit: /opt/sun/comms/messaging64
Messaging Server also uses /var/opt/sun/comms/messagingand /var/opt/sun/comms/messaging64 as the read-write area for configuration, queue, log, store, and other miscellaneous data.
Monitoring Console
CMN_MC_INSTALLDIR
Solaris OS: /opt/SUNWjesmc
Linux: /opt/sun/jesmc
 
Sun Cluster
You cannot change the installation directories, so no is field in the installer or parameter in the state file.
Not applicable Sun Cluster software is installed in the following locations on Solaris OS:
/ /usr/opt /usr/cluster
Web Server
CMN_WS_INSTALLDIR
Solaris OS: /opt/SUNWwbsvr7
Linux: /opt/sun/webserver7
 
Web Server Instance Directory
CMN_WS_INSTANCEDIR
Solaris OS: /var/opt/SUNWwbsvr7
Linux: /var/opt/sun/webserver7
 

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

Product Component Port Purpose
Access Manager 58946 UNIX authentication helper
  58943 Secure ID authentication helper (Solaris SPARC only)
Application Server 8080 Standard HTTP port
  3700 Standard IIOP port
  4848 Administration Server port
  7676 Standard Message Queue port
  8686 JMX port
  8181 HTTPS port
Calendar Server 80 Standard HTTP port
  389 LDAP port
  57997 ENS
  59779 DWP
Common agent container 11162 JMX port (TCP)
  11161 SNMP Adaptor port (UDP)
  11162 SNMP Adaptor port for traps (UDP)
  11163 Commandstream Adaptor port (TCP)
  11164 RMI Connector port (TCP)
Common agent container for Sun Cluster and Sun Geographic Edition 10162 JMX port (TCP)
  10161 SNMP Adaptor port (UDP)
  10162 SNMP Adaptor port for traps (UDP)
  10163 Commandstream Adaptor port (TCP)
  10164 RMI Connector port (TCP)
Directory Server 389 Standard LDAP listener
  636 LDAPS over SSL
HADB 1862 Management Agent Port (JMX)
  15200 Default Portbase
Instant Messaging 5222 Multiplexer port
  5269 Instant Messaging server-to-server port
  45222 Server port used for multiplexer communication
Message Queue 80 Standard HTTP port
  7676 Port Mapper
  7674 HTTPS Tunneling Servlet Port
  7675 HTTP Tunneling Servlet Port
Messaging Server 25 Standard SMTP port or MMP SMTP Proxy Note 1
  110 Standard POP3 port or MMP POP3 Proxy Note 1
  143 Standard IMAP4 port or MMP IMAP Proxy Note 1
  225 Default port for communications to back-end store through LMTP
  465 SMTP/SUBMIT over SSL or MMP SMTP Proxy over SSL Note 1
  587 Standard Message Submission (SMTP SUBMIT) port
  993 IMAP over SSL or MMP IMAP Proxy over SSL Note 1
  995 POP3 over SSL or MMP POP Proxy over SSL Note 1
  7997 Event Notification Service port
  8990 mshttpd daemon port
  8991 mshttpd over SSL daemon port
  27442 Used by Job Controller for product internal communication
  49994 Used by the Watcher for internal product communication
Monitoring Console 6789 Accessed through Sun Java Web Console
  8765 Job Factories port for Master Agent Web Services Adaptor
  11161 SNMP port for Monitoring Framework
  11164 RMI port for Monitoring Framework
  63837 Used by MeterMaid for internal product communication
  54320 Multicast port for Monitoring Framework discovery protocol
Web Server 8800 Admin HTTP port
  8989 Admin SSL port. For Admin Server, SSL port is required, HTTP port is optional.
  80 Instance HTTP port

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

Communications Suite Compatibility Issues

For compatibility issues affecting Communications Suite products and dependent products and shared components, Communications Suite 6 Update 2 Compatibility Issues.

Problems Fixed in This Release of Communications Suite

This section lists problems fixed in this release of Sun Java Communications Suite.

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 Red Hat Linux) the Calendar Server installation fails.

6669238

The Communications Express configuration process results in an error when you configure the Webmail host and port settings.
You get the warning, "Unable to connect to the Webmail Server" while configuring Communications Express against Messaging Server 7.0.

Known Issues in Sun Java Communications Suite

This section describes the known issues that exist in this release of Sun Java Communications Suite. Specifically, this section describes installation and upgrade issues.

JDK upgrade may affect other products' upgrade

The JDK upgrade may affect the upgrade of other products. For details, see Communications Suite 6 Update 2 Compatibility Issues.

6785668

When you install comm_dssetup only, the Communications Suite installer does not install the SASL, NSS, and ICU shared components.
The comm_dssetup script requires SASL because ldapsearch needs it.

This issue occurs only if you run the Communications Suite installer and select comm_dssetup without selecting any other Communications Suite products. This scenario may occur in a multi-host deployment, where comm_dssetup is installed with Directory Server on separate machines, and no Communications Suite products are installed on those machines.

The shared components are installed when you install Communications Suite products such as Messaging Server with comm_dssetup on the same machine.

Note: comm_dssetup is installed and run on machines where Directory Server is located. This issue occurs when you install Directory Server with the Directory Server zip file version, which does not install the SASL, NSS, and ICU shared components in the standard location. This installation method is recommended on the Communications Suite software download site.

If you install Directory Server with the Java ES installer (not recommended because it installs an older version of DSEE), these shared components are installed.

Workaround: When you run commpkg install, when you are prompted to select components to install, select ~1, 3.

This selection directs the Communications Suite installer to install comm_dssetup (selection 3) and the shared components associated with Messaging Server (selection ~1). It does not install the Messaging Server software.

The tilde (~) prefixed to a product selection directs the Communications Suite installer to install the shared components associated with a product, but not the product itself.

6766549

comm_dssetup.pl is unable to locate ldapsearch. comm_dssetup.pl may not be able to locate ldapsearch if you install it in an altroot location.
Workaround: Install comm_dssetup.pl in the default root location.

pkgadd will fail on systems with greater than 2 TB of space.

Currently this issue occurs only on ZFS file systems that are available only on Solaris 10. This is due to Solaris bug 6514450, which is fixed in patch 119254-61(sparc)/119255-61(sol x86) or later.

Workaround: Download and apply the patch.

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.

6653773

Access Manager 7.1 fails to start if it is deployed to a non-enterprise (EE) version of Application Server 9.1.
For details, see Communications Suite 6 Update 2 Compatibility Issues.

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 to the current version of comm_dssetup, run commpkg upgrade and select 3. If you are upgrading comm_dssetup only, see issue 6785668, above.

Unable to render {include} Couldn't find a page to include called: Sun Convergence 1 Update 1 Release Notes

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

Platform Patch Number (English and Localized Languages)
Solaris OS, SPARC 121657-36
x86 121658-36
Linux 121659-36

After patching, csversion will show the product version as "6.3-15.01".

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

Solaris Default Directories
cal-svr-base=/opt/sun/comms/calendar/
/etc/cal-svr-base/SUNWics5/config
/var/cal-svr-base/SUNWics5
Linux Default Directories
cal-svr-base=/opt/sun/comms/calendar/
/etc/cal-svr-base/config
/var/cal-svr-base/
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 an Earlier Version of 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 an Earlier Version of Calendar Server

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

File Names Solaris Locations Linux Locations
Administrator utilities: start-cal, stop-cal, csattribute, csbackup, cscal, cscomponents, csdb, csdomain, csexport, csimport, csmonitor, csplugin, cspurge, csrename, csresource, csrestore, csschedule, csstats, cstool, and csuser cal-svr-base/SUNWics5/cal/lsbin cal-svr-base/sbin
Migration utilities: csmig and csvdmig cal-svr-base/SUNWics5/cal/sbin cal-svr-base/sbin
Configuration files: ics.conf, version.conf, counter.conf, and sslpassword.conf After installation, files are located at: cal-svr-base/SUNWics5/cal/lib/config-template

During configuration, the various files from the above directory are moved to the locations specified by the configuration options you choose. The default location is: /etc/cal-svr-base/SUNWics5/config
After installation, the files are located at: cal-svr-base/lib/config-template

During configuration, the various files from the above directory are moved to the locations specified by the configuration options you choose. The default location is: /etc/cal-svr-base/config
Mail formatting (*.fmt) files After installation, the files are located at: cal-svr-base/SUNWics5/cal/lib/config-template

After configuration, the files are located at: /etc/cal-svr-base/SUNWics5/config/language

where language is en, de, es, fr, ja, ko, zh-TW, or zh-CN.
After installation, the files are located at cal-svr-base/lib/config-template

After configuration, the files are located at: /etc/cal-svr-base/config/language

where language is en, de, es, fr, ja, ko, zh-TW, or zh-CN.
Library (.so) files

SSL utilities: certutil and modutil
/var/cal-svr-base/SUNWics5/cal/lib/ cal-svr-base/lib
Session database /var/cal-svr-base/SUNWics5/data/http /var/cal-svr-base/data/http
Counter statistics files: counter and counter.dbstat cal-svr-base/SUNWics5/cal/lib/counter cal-svr-base/lib/counter
timezones.ics file /etc/cal-svr-base/SUNWics5/config /etc/cal-svr-base/config

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:
  1. Before indexing, time how long it takes to run the following LDAP command:

    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.
  2. Run indexing for icsCalendarOwned.
  3. Again run the following LDAP command, and time it:

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

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

Restoring Backups

As of Calendar Server 6.0, you can restore a specific calendar using csrestore from any backup including backups saved with Hot Backup or Archival Backup. To do so, issue the following command:

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:

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

Incompatibility Impact Comments
Access Manager now has two install types: Legacy and Realm. At installation, you must choose Legacy as the install type on the following panel:

Access Manager: Administration (1 of 6)
If the wrong Access Manager is installed, you will not be able to run Delegated Administrator.
The Directory Preparation Tool (comm_dssetup.pl) under /opt/SUNWics5 doesn't work. 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.
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/sbin/config-commda

for Linux /opt/sun/comms/config-commda
Upgrade to the new Delegated Administrator when installing this version of Calendar Server.
This release of Communications Express is incompatible with the previous version of Calendar Server. If you upgrade Communications Express, you must also upgrade Calendar Server. This also applies to Messaging Server.
Due to a change in the way packaging is done, Calendar Express must do string substitution at runtime. Significant Performance Degradation Call technical support to receive a script you can run before starting Calendar Server operations. The script performs all the required string substitutions.

Calendar Express is deprecated and will not be included in a future release of Calendar Server. This problem will not be fixed.
Due to a program code change in SSL processing, the following parameter no longer works:

service.http.ssl.certdb.path
Scripts and configuration files still using the old parameter to point to the SSL directory will not work. SSL is not enabled. A new parameter was added to the ics.conf file:\\


local.ssldbpath = "/etc/opt/SUNWics5/config"

Password to certificate database is no longer held in ics.conf parameter:

service.http.ssl. certdb.password
SSL password can't be found. Error message:

General Error: http_ssl_init(): SSL initialization failed.
Password to certificate database is now found in the following file located in the config directory:

sslpassword.conf

Format of password is:

Internal (Software) Token:password
Non-domain environments no longer allowed. Scripts that modify LDAP entries must now include a default domain. When Calendar Server is installed and configured, it runs a silent conversion program on all LDAP entries to add the default domain you specified.

Requests that come in (WCAP commands) without the domain will be automatically assumed to be for the default domain.

But any scripts you run that directly modify LDAP entries must include the new default domain.
The service.admin.calmaster.userid and service.admin.calmaster.cred parameters in the ics.conf file are not used anymore. You cannot set the Calendar user preferences and credentials using these old parameters. The service.admin.calmaster.userid parameter is changed to service.siteadmin.userid and service.admin.calmaster.cred parameter is changed to service.siteadmin.cred. In case of an upgrade these parameters are migrated by the patch scripts.
Windows and HP-UX versions of Calendar Server are no longer available. The only operating system platforms supported by server-side Calendar Server software are Solaris and Linux. This does not effect client-side software, such as the Connector for Microsoft Outlook. See the individual client component Release Notes for a list of supported operating systems.

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

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.

6780694

There are missing apostrophes in the French OLH

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

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

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

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

Unable to render {include} Couldn't find a page to include called: Messaging Server 7.0 Release Notes
Unable to render {include} Couldn't find a page to include called: Instant Messaging 7.3 Release Notes
Unable to render {include} Couldn't find a page to include called: Delegated Administrator 6.4 Release Notes

Sun Java System Communications Express 6.3 Release Notes

The Release Notes document contains important information available at the time of the patch release of Sun Java System Communications Express 6.3 including:

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.

What's New in This Release of Communications Express

See the What's New document.

About Communications Express

Sun Java System Communications Express 6.3 provides an integrated web-based communication and collaboration client that consists of three client modules - Mail, Calendar, and Address Book. The Mail, Calendar, and Address Book client modules are deployed as a single application on any web container and are collectively referred to as Unified Web Client (UWC).

Deprecated and Removed Features for Communications Express

Going forward, no new features will be added to the Communications Express user interface. It has been deprecated in favor of Sun Convergence. Communications Express will be removed from the product in a future release.

No patches will be issued for Communications Express versions prior to 6.3.

Communications Express will only support use of Directory Server on Solaris and Linux; not on Windows or HP-UX or any other platform. Communications Express does not support Web Server version 6.

Communications Express Browser Requirements

Communications Express 6.3 requires a JavaScript-enabled browser. See Supported Browser Versions for Communications Express Clients for more information.

Communications Express Compatibility Issues

The following table lists the known incompatibilities between Communications Express 6.3 and earlier versions

Incompatibility Impact Comments
The User Interface for creation of a new calendar event has been changed from earlier versions of Communications Express 6.3 release. In this release, when users create new calendar events, the Start Time, and End Time of the event has to be supplied. In previous releases, only the Start Time and Duration had to be supplied (6305790).   The change has been made only in the User Interface. The behavior of the way events are created is not affected.
Java Enterprise System (Java ES) 4 release of Communications Express is incompatible with Java ES3 version of Messaging Server Multiplexor (6328658). A HTTP 502 error is displayed when users log in with valid credentials when Communications Express is upgraded with the Java ES 4 version. If you upgrade Communications Express to Java ES 4, you must also upgrade Messaging Server Multiplexor to Java ES 4.
Java ES 4 release of Communications Express is not compatible with the Communications Suite version 5 version of Messaging Server. This incompatibility is seen in a setup containing a Java ES 4 version of Messaging Server, Communications Express, Calendar Server, and Access Manager are installed on the same machine, if only Messaging Server is upgraded to the Communications Suite 5 version, some functionality in Communications Express is broken (6395931). Some of the Communications Express functionality such as compose mail, search, and folder management do not work. If Messaging Server is on one machine and Webmail, Messaging MultiPlexor, and UWC are on different machines, Messaging Server can be upgraded to Communications Suite 5 version. If you upgrade only Webmail and Messaging Multiplexor without upgrading Communications Express, some of the Communications Express functionality do not work.

Problems Fixed in This Release of Communications Express

This list describes problems fixed in the Communications Express 6.3 patch.

6798573

Provide entry point into Access Manager from Communications Express.

6290436

Anonymous Access over https to the Calendar is not working in Communications Express.

6467668

Deleting members after adding them in a new group using Quick Add does not delete the members.

6652350

Unable to create or edit events and tasks and manage Calendar with Java Desktop Kit 6.

6555329

An error message "Unknown error(266)" is displayed when you remove the empty space member from the Edit Group window.

6574496

Edit Calendar Group window is closed when you press the Enter key after adding a member.

6577268

In Internet Explorer, the 'Please select the file to remove' pop-up window is displayed when you press the Enter key after entering the task name

6591085

A Java script error message is displayed when you save the email address from the 'To' field link in received mail.

6634696

In Internet Explorer 6 and 7, a Java script error message is displayed when you save the draft for a new message.

6640117

Selecting Recurrence Frequency to yearly/monthly results in internal server error.

6645414

An error message is displayed when you move a mail from one folder to another in the View Mail page.

6657429

Clicking Edit Event button results in internal server error.

6676514

Email address is lost when you import the contact in LDIF format.

6691849

Communications Express 6.3 Options page is blank when viewed from Safari 2.x.

6758714

Web Address & Calendar Address data is lost for a group when you import the contact in LDIF format

6784374

Able to add a member to a group with display name as space characters.

6793990

Cross script issues in Sun Java System Communications Express.

6797155

Unable to create a task in a subscribed calendar.

6804133

In Internet Explorer, the Add Addresses pop-up window does not close.

6804692

Importing an event in the Calender results in server error.

6808535

Internet Explorer does not display inline images in messages under the Double-bytes folder.

6813636

Stepping back through messages from second screen results in Java script error.

Known Issues and Limitations in Communications Express

This section contains a list of the known issues with Communications Express 6.3. The following product areas are covered:

Generic Issues

6398159

Communications Express Login Screen Does Not Honor CSS Definition in themes.propertiesThe login.jsp file in Communications Express has hard-coded style--- sheet information. As a result of this, new skin-definitions cannot be applied for the style-sheets used with the login page.

6798573

Error Message Displayed When You Upgrade To Latest Patch With Identity Enabled
If you have identity enabled in your current version and upgrade to the Communications Express 6.3 patch available with the Communications Suite 6 Update 2 release, then an error message is received when you try to login.
Workaround: You must set one of the following parameters in the uwcauth.properties file:

6691303

View Group Details link does not work properly
When you create a new group and click the View Group Details link, you are directed to the same page instead of the Group Details page.

6272426

UWCAuth Servlet Throws a NullPointer Exception
In a deployment scenario where the dependent components of Communications Express (deployed on Sun Java System Application Server) are deployed across multiple nodes, the Communications Express UWCAuth Servlet throws a NullPointer Exception.
Workaround: Restart the Application Server.

6527879

Communications Suite Installer Does Not Permit Installation in a Local Zone
An attempt to install Communications Express with and Access Manager using the Communications Installer 14a into a sparse zone results in the following message regarding shared components:

Workaround: Install the shared components in the global zone using the pkgadd command. This allows the installation to proceed without any problems.

6482226

Communications Express Online Help Contains JavaScript Error.
When accessing to Communications Express Online Help using Internet Explorer 6.0, JavaScript errors are displayed.

6517599

Java ES 5-B14a: Linux RH4.0: Unable to load Communications Express Login Page in a Multi-tiered Deployment
The login page fails to load even if the user logs in with valid credentials in a Multi-tired deployment topology. This issue is seen in the following scenario:

  • Communications Express and webmail host are installed on one node
  • Directory Server, Calendar Server on separate nodes
  • Calendar Server, Messaging Server, and Communications Express configured with SSO
  • Access Manager is enabled in the uwcauth.properties by setting the property auth.identity.enabled to true

The web container logs a series of exceptions indicating a problem with Access Manager when Communications Express tries to execute code that makes calls to Access Manager SDK. This happens when a user tries to log on to Communications Express.

6717711

Communications Express Online Help Window Titles Do Not Show Correct Information.
The Communications Express Online Help windows display incorrect title information.

Configurator Tool Issues

This section contains a list of known issues in the Configurator tool for Communications Express.

6688505

Communications Express uwc-config failed when set up with Messaging Server 7.0
When configuring Communications Express 6.3 for Messaging Server 7.0, you can receive the following message:

Workaround: You can safely ignore this message. The Communications Express 6.3 configuration will be completed correctly.

6415155

Communications Express Does Not Allow Users to Log in After a Patch is Backed Out
Communications Express brings back the login page when users try to log on to Communications Express with valid credentials, after a patch is backed out. This issue is seen when users upgrade Communications Express by installing a patch using the patch-config and install-newconfig commands but later run the backout-newconfig to back out of a patch. The backout-newconfig utility does not warn users that some of the JSP files may have been cached by the web container.
Workaround: Remove the ClassCache directory for your web container and restart the web container on which Communications Express is deployed. The ClassCache directories for Web Server and Application Server are:
Web Server: /opt/SUNWwbsvr/https- <servername>/ClassCache/https- <servername>, where <servername> is the domain on which Communications Express is deployed.
Application Server: /var/opt/SUNWappserver/domains/domain1/generated/jsp/j2ee-modules/ <uwc_module_name>, where <uwc_module_name> is the name of the module deployed on the Application Server.

5104756

Configurator Tool for Communications Express Does Not Support the `Unconfigure' Option
The Communications Express Configurator does not allow you to undeploy, remove files at the time of configuration, and remove files created during runtime.
Workaround: To Unconfigure Communications Express:

  1. Remove the Communications Express package. For example on Solaris type:
    pkgrm SUNWuwc
  2. Remove the deploy directories.
  3. Remove the WEBAPP entry from Web Server or Application Server server.xml file.

5028906

Communications Express Configurator: devinstall Dumps Core for Unresolved Host Aliases
Communications Express configuration wizard fails to complete the configuration process if your system is not configured for host name aliases.
Workaround: Ensure that you have configured one or more host name aliases for your system.
To configure one or more host name aliases on UNIX systems:

  1. Provide the configuration for the hosts in /etc/nsswitch.conf file:
    hosts: files dns nisThis configuration indicates to the name service the lookup order it should use to resolve host names and host aliases. The name service lookup order is: files, dns, and nis.
  2. Ensure that the /etc/hosts file contains two or more host names defined against your machine's IP address.
    For example, if your system IP address is 129.158.230.64, then in /etc/hosts file, you can configure the IP address as:
    129.158.230.64 budgie.siroe.varrius.com budgieor
    129.158.230.64 budgie.siroe.varrius.com budgie loghostExample of an incorrect IP address:
    129.158.230.64 budgie

4996723

GUI Configuration Input Fields are Truncated because Input Fields are Right Aligned
The field names and browser buttons are truncated or not visible when the configuration wizard is invoked in a language other than English.
Workaround: Resize the configuration panels to view its contents properly.

4982590

The Components for Communications Express are Shown to be Zero Bytes
The configurator tool for Communications Express shows the component size as 0 bytes while displaying the Mail and Calendar components for Communications Express.

6283991

Java Exception on Web Server Startup after Configuration of Communications Express
In an installation scenario where Communications Express and Access Manager are installed and configured on separate nodes, the Web Server installed on the node containing Communications Express throws a Java exception on restart. This is due to the incorrect settings in the Web Server's classpath (on the node where Communications Express is installed).
Workaround: Edit the web-svr-base /config/server.xml file on the Web Server instance of the node where Communications Express is installed, and ensure that the following entries are available in the Web Server's classpath:

6298931

Communications Express Configurator Fails to Validate Application Server Port and as a Result the Configuration Hangs
The Communications Express configurator does not validate the Application Server port during configuration and thus the configuration hangs if a wrong Application Server port number is specified.

6264589

Configuration of Communications Express Hangs if Web Server is Running
The configuration of Communications Express hangs when the Web Server is running. This is due to an UnsatisfiedLinkError error.
Workaround: Gracefully shutdown the Web Server by executing the command /web-svr-base/web-svr-domain_name /stop. This will allow the Communications Express configuration to proceed.

Calendar Issues for Communications Express

12652656

Check Availability Help Text Suggests Searching on "Display Name"
When checking and invitee's availability to a new event, the Invitee box in the Check Availability frame suggests using search for invitees is based on Display Name, Email Address, or Calendar ID. However, users cannot search for invitees based on Display Name as this will return the following error: The invite failed, invitee is name is not a valid calendar name or Email address. The invitee window in the New Event frame uses the correct text when describing how to invite a user. For example: Type the Invitee's Email address or Calendar ID, then click add.
Workaround: Edit the i18n.properties file for the Communications Express cal-client.

  1. Update the following line in i18n.properties, remove the word "Display name."
  2. Stop Web Server hosting the Communications Express client.
  3. Clear the Web Server classCache.
  4. Start the Web Server hosting Communications Express.

6723521

Cannot Create an Event That Spans More Than Two Years.
When you create an event in the Calendar that spans more than two years, the following error is displayed:

6199523

Cannot Edit Imported Events and Tasks in Calendar.
If you create calendars A and B and provide permissions to edit both of them, and try importing events and tasks to one of these calendars, the Edit button is not displayed restricting you from editing the events.

6199523

Cannot Edit Imported Events and Tasks in Calendar
Communications Express does not allow editing of Events and Tasks that are imported from one calendar to the other (with allow... permissions set on both), for the same calendar owner.

6528031

Communications Express Calendar Web Exception When Searching Calendar Groups for an Event
The Communications Express calendar client displays an exception if a user searches a calendar group consisting of owned and subscribed calendars for events of interest. If a user creates a calendar group and wants to search this group for a particular event, the Communications Express client returns with an error that the page cannot be displayed. As a result, a user cannot search the calendar group for an event and will need to search each calendar individually.
This problem depends on the alphabetical ordering of the event names. If the event in the owner's calendar is alphabetically before the event in the subscribed calendar, the problem may not occur. This problem occurs when the event in the subscribed calendar begins with a letter that is alphabetically before the event in the owner's calendar.

Mail Issues for Communications Express

6425114

Direct Delivery of Mails to a Multi-byte Shared Folder Corrupts the Recipients Email Address
When mails are sent to a multi-byte shared folder, the recipient's email address is corrupted and the mail is not delivered to the multi-byte shared folder, instead it is delivered to the inbox of the user where the multi-byte shared folder is created. It only works if the recipient's shared folder is created using IMAP-MUTF 7
Workaround: Disable the popup blocker for this URL in your browser.

6691269

Multi-byte data becomes garbled for Folder names and in Search field in Mail tab(Safari only)
Case1: While being logged in as Non-English user, when you create a new folder in the Mail tab, the Non-English folder name gets garbled.
Case2: When you enter Non-English search text in the Search field in the Mail tab, the characters get garbled.
Workaround: None.

6691274

Cannot open or share "Sent" folders in Non-English versions
While being logged in as Non-English user, when you try to open (by clicking) or share a "Sent" folder in the Mail tab, an error "Folder does not exist" is displayed.
Workaround: None.

6329862

Communications Express Does Not Behave as Desired when Popup Blockers are Enabled in Browsers
When users enable the pop-up blocker feature in their browsers, the Compose, Reply, Reply All, Forward, and Forward Inline windows of Communications Express are not displayed even though they are valid pop-ups with respect to the application. Communications Express does not let the browsers know that this is a valid pop---up.

6501841

When User Logs in Through a Domain Specific URL Without Providing @virtualdomain.com, the Mail Tab is Missing
This bug is seen when users log on to Communications Express that is configured with hosted domain support. In a hosted domain scenario, users should log on using the uid along with the virtual domain name. For example uid@virtualdomain.com. If the user logs on to Communications Express without specifying the hosted domain, the Mail tab does not appear.
*Workaround:*While logging on to the virtual domain, provide the virtual host URL on the browser, for example <virtualdomain>.siroe.com, and then log on to the virtual domain using uid@virtualdomain.com the mail tab is shown. Here:

  • <virtualdomain> is the configured virtual domain name under the default domain (siroe.com in the example)
  • uid is the user id of the user on the virtual domain

Address Book Issues

6383327

The Address Book Component of Communications Express Does Not Validate the Format of the File That is Being Imported
Communications Express does not validate the file formats when trying to import already exported address book contacts. As a result of this, if a file exported in one file format is imported as another file format, inappropriate error messages are displayed, and in certain cases incorrect contact data is imported.

  • For example, if users try to import an LDIF file by selecting the Import Format as Microsoft CSV or Address book CSV type from the Import and Export Address Book window of the Address Book component, the following error message is displayed:

    The Address Book component does not validate the file format that is being imported.

  • If an LDIF format type file is imported as a Thunderbird CSV format, Address book creates 10 contacts for the one contact exported.
  • If a Microsoft CSV format type file is imported as a Thunderbird CSV format, Address book creates multiple contacts.

6355706

Communications Express Displays a Configuration Error When Users Try to Search in the Corporate Directory With a Valid Keyword
Communications Express displays the following error message when users try to search the corporate directory with a valid keyword:

6514534

Some of the Fields Are Ignored When Exporting Communications Express Address Book
When exporting the Communications Express Address Book using Mozilla Thunderbird CSV format, some of the fields are ignored.
For example, Middle Name, email(3), Pager, Work Street, Home Street, Calendar Address, Availability Address, Nickname (1), Nickname (2),Birthday, and Anniversary.

6337537

Compose Window is Not Displayed to the User When Popup Blocker is Enabled in the Browsers
This issue is seen when users enable the popup blocker feature in their browser. On enabling popup blockers, when users click on the email address of their contacts in the Address Books, Communications Express does not open the mail compose window even when this is a valid pop up window.
Workaround: Disable the pop-up blocker feature for the domain.

4995472

The Address Book Name Cannot be Localized by defaultps/dictionary-<lang\>.xml for Every Session
The address book name cannot be localized because the localized value which is based on the resolved session language and the domain specific defaultps/dictionary-<lang\>.xml is assigned when the address book is accessed for the first time.
The "Name" and "Description" entered in the Address Book Options page are also not displayed in the current Address Book drop-down list that appears on the Address Book tab page.

6540765

The Sequence of Phone Numbers Changes When The Exported File is Imported in Microsoft Outlook CSV Format
When you import an exported file in Microsoft Outlook CSV format, the sequence of phone numbers changes.

6308706

Importing Data from Outlook CSV Format Creates Invalid Birthday and Anniversary.
When users try to import Microsoft Outlook data in CSV format into Communications Express, the entries for Birthday and Anniversary are incorrectly set to 00/00/00.

Options Issues

6693973

User Cannot Log In to Communications Express Immediately After Changing the Password.
When you try to login to Communications Express after changing your password, the following error message is displayed:

Workaround: Wait for about 2minutes before you login again.

Localization Issues for Communications Express

6387130

Users Unable to Localize Date Format in Event View and Check Availability View
Communications Express allows users to define localized date and time formats. The localized date and time formats can be defined in the i18n.properties files. However, the localized date and time cannot be displayed for the following views and pages: There is no corresponding properties for these pages in the i18n.properties file.

  • Event View
  • Check Availability View
  • Mini Calendar.

6186520

Importing CSV from Localized Microsoft Outlook Express Version 6.00.2800.1123 Does Not Work
Communications Express cannot import CSV data from a localized Microsoft Outlook Express.

6472240

Communications Express Calendar, Multi-byte Attachment Filename will be Garbled when it is Opened in Internet Explorer 6.0.
This bug is seen when users try to create a task or event in Communications Express using Internet Explorer 6.0. When users try to attach a file with a multi-byte name and save the attachment, the file name in the save dialog box is gets garbled.

6480589

Opposite First Name and Last Name Entry when Adding a Contact in Japanese
Communications Express does not add contacts in Address book based on the locale. When users try to add a Japanese contact in Japanese locale, the contact is added as per the rules of English. The contacts are added in the order of First Name and Last Name. Japanese locale requires that the user's last name appears before the first name.

6480593

Cannot Add Proper Name to Address Book from 'Add Address' Button.
When users try to add email address to address book using the 'Add Address' button from a received message, the view name is duplicated the contact does not get added properly.

6494315

Communications Express does not Handle Password Policies as Desired
Communications Express has the following issues when setting up password policies:

  • When a password lock is set on entering a wrong password, say for three consecutive tries, on the next correct entry, Communications Express displays a Server Error (500) Page instead of displaying an appropriate message.
  • When users try to log in with an expired password, the following error is displayed.

    This message is ambiguous and is not correct.

  • When users try to login to Communications Express with a policy 'Need to reset the password at the first login', the user is not prompted to reset his password.

SMIME

6225672

Certification Revocation List Not Working
Communications Express does not display any error message when encrypted messages are sent to users whose certificates have been revoked.

Documentation Updates

Documentation Errors

12763208

ldapusersession.ldappooltimeout description incorrect in Communications Express 6.3 Administration Guide
Currently, the description for ldapusersession.ldappooltimeout states:

Parameter in uwcconfig.properties Description
ldapusersession.ldappooltimeout Specifies the number of seconds before timing out an LDAP connection. Increase this value to accommodate large search results.

The description of ldapusersession.ldappooltimeout should be changed to the following:

Parameter in uwcconfig.properties Description
ldapusersession.ldappooltimeout Specifies the number of seconds before timing out a new LDAP connection establishment.

ldapusersession.ldapsockettimeout no description in Communications Express 6.3 Administration Guide
The description should state the following:

Parameter in uwcconfig.properties Description
ldapusersession.ldapsockettimeout Specifies the number of seconds before timing out an LDAP connection. Increase this value to accommodate large search results or large data transmission.

12261762 (SUNBT6803302)

webmail.port description incorrect in Communications Express 6.3 Administration Guide
Currently, the description for webmail.port states:

Parameter in uwcconfig.properties Description
webmail.port Specifies the port number Communications Express HTTP Server listens to

The description of webmail.port should be changed to the following:

Parameter in uwcconfig.properties Description
webmail.port Specifies the port number on which the Messaging Server's HTTP service mshttpd is running

Exporting Address Book Contacts as vCards

Communications Express supports only UTF-8 encoded files for import and export of vCards in the Address Book. To configure Address Book to support import and export of files with other encoding:
For importing, in the following file:

change

For exporting, in the following file:

change

to

You must restart the container for the changes to take place. Currently, Communications Express does not support multiple encoding formats for vCard.

Note:
Both the settings are application wide, and will be enforced for all users in all locales. Changing from UTF-8 may not be suitable if different locales are to be supported.
Limitations of the vCard Export Feature

When you create a contact in the Communications Express Address Book, you can label the telephone numbers in the following categories:

  • Home
  • Work
  • Fax
  • Other

When a contact is created with the label as "Other" and exported as a vCard, then this number is not exported because vCard with telephone number labeled as "Other" is not supported. So, if vCard is the medium of exchange of contact data, then ensure you don't label the telephone numbers as "Other".

Also, if you create a contact in Communications Express with more than two telephone numbers with the same label such "Home", "Work", "Fax", and so on, and export the contact as a VCard, then only one of them is exported while the other similarly labeled number is ignored. Communications Express supports export and import of only one number for each type of telephone number.

Unable to render {include} Couldn't find a page to include called: Connector for Microsoft Outlook 7.3 Release Notes

Chapter 9 Communications Sync 3.1

Note: The following link directs to you the Sync 3.0 Release Notes. Sync 3.1 is the same as 3.0 with additional fixes.

http://docs.sun.com/source/819-4706/index.html

Labels:
printable printable Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.