Printable Communications Suite 7 Release Notes

Skip to end of metadata
Go to start of metadata
Contents

Common Release Information for Sun Java Communications Suite 7 Component Products

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

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 7

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

Communications Suite 7 Products and Components
Product Version
Messaging Server 7 Update 3
Instant Messaging 8 Update 2
Convergence 1 Update 3
Calendar Server 7
Delegated Administrator 7 (latest patch)
Outlook Connector 7.3 Update 1 (latest patch)
Calendar Server 6.3 (latest patch)
Indexing and Search Service 1
Comms Sync 3.1 (latest patch)
Comms Installer 7
Messaging Server HA Agent (MS_SCHA) 7
Calendar Server HA Agent (CS_SCHA) 6.3
Instant Messaging HA Agent (IM_SCHA) 7.3
comm_dssetup 6.4 (latest patch 6.4p5)

For release notes on individual component products, see the following links:

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

If you need to install Communications Express 6.3, use the Communications Suite 6 Update 2 media to get the software.

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

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:

  • To install a particular Communications Suite product, which other components do I need? The Communications Suite 7 Component Dependencies table lists the individual Communications Suite products and shows the components on which they depend, including other Communications Suite components.

Sun Java System Product Version Compatibility Requirements for Communications Suite 7
Product Version Required or Optional?
Sun Java System Directory Server 5.x, 6.x Required. 6.3 or later recommended. If doing a fresh installation, 6.3.1 is 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.
GlassFish Enterprise Server 2.1 Required as the web container for the following Communications Suite 7 components: Calendar Server 7, Instant Messaging 8 Update 2, and Indexing and Search Service 1.
Sun Java System Application Server 9.1 Update 2 Optional web container for some Communications Suite 7 components.
Sun Java System Web Server 7.0 Update 2 Delegated Administrator requires a web container. Alternately, you can use either Application 8.2P2 or Application Server 9.1 Update 2 (recommended) as the web container.

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

Communications Suite 7 Component Dependencies
Product Component Dependencies Required or Optional? Must Be on Local Host?
Calendar Server 7 Directory Server 5.x, 6.x
Recommended: 6.3.1
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 7 installer.
Required. To prepare the LDAP directory for Messaging Server. No. Must be on the same host as Directory Server.
  MySQL Server 5.1 Required. To store Calendar Server database information. No
  GlassFish Enterprise Server 2.1 Required. To act as the web container. Same host on which you install Calendar Server 7.
  Messaging Server Optional but an SMTP server is required. No
Indexing and Search Service 1 Directory Server 5.x, 6.x
Recommended: 6.3.1
Required. To store user/group and domain information for authentication, authorization, and email delivery. No
  Messaging Server 7 Update 3 Required. No
  GlassFish Enterprise Server 2.1 To act as the web container. Same host on which you install front-end ISS components.
  Java Message Queue 4.3 To generate notifications. No
Messaging Server 7 Update 3 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 7 installer.
Required. To prepare the LDAP directory for Messaging Server. No. Must be on the same host as Directory Server.
  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 7 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, 7 Update 3
Recommended: 7 Update 3
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 Update 2 Directory Server 5.x, 6.x
Recommended: 6.3.1
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 7 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, 7 Update 3
Recommended: 7 Update 3
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:
GlassFish Enterprise Server 2.1
Application Server 8.x
Recommended: GlassFish Enterprise Server 2.1
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 7 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 7 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, 7 Update 3
Recommended: 7 Update 3
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 3   For details about Convergence dependencies, see Sun Convergence 1 Update 3: Product Version Compatibility Requirements.  

Java Requirements

The following products require that you have Java 1.6 installed: GlassFish Enterprise Server 2.1, Calendar Server 7, Indexing and Search Service 1, and Instant Messaging 8 Update 2.

NSS Requirements

Communications Suite 7 requires the use of the shared security component NSS version 3.11.7. If you are using Directory Server 5, and you upgrade to NSS 3.11.7 on the Directory Server host, you need at least Directory Server 5.2 patch 6 due to an NSS incompatibility. See the IMPORTANT NOTE in the NSS patch.

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

Sun Convergence 1 Update 3: 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 7 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 the Sun Java System Product Version Compatibility Requirements for Communications Suite 7 table.

Sun Java System Product vides you with all the product requirements and minimum product versions to install Convergence in these deployments:
  • A new Communications Suite 7 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.

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.

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 the Sun Java System Product Version Compatibility Requirements for Communications Suite 7 table.

Sun Java System Product Requirements for Convergence 1 Update 3
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
Web Container
  • Sun GlassFish Enterprise Server 2.1 Patch 02 (recommended)
  • Sun Java System Application Server 9.1 Update 2
    Note
    If you are using Sun Java System Application Server 9.1 Update 2, 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)
      • Red Hat 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)
      • Red Hat 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.

Communications Suite Component Requirements for Convergence 1 Update 3
Product Version Communications Suite Release Required or Optional? Must Be on Local Host?
Messaging Server - Webmail Server 7 Update 3

(See Note after this table.)
7 (for MS 7 Update 3) 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, 7 Update 3

(See Note.)
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)
7 (for MS 7 Update 3)
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, 7
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 2 7 (for IM 8 Update 2) 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 7 installer. 7 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, 7 Optional. No

Note
For Messaging Server 7 Update 3, if you enable flagged message sort through the Convergence UI, you need to ensure that your wmap_version is equal to or greater than 9. This version is available in patch 137203-11 (Red Hat Linux), 137204-11 (SPARC 64-bit), and 137205-11 (Solaris x86 64-bit) or greater. In addition, the imapd version (Messaging Server back-end host) must have the same patch or greater. Otherwise, flag sorting does not work.

Convergence 1 Update 3 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 3. 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 3. 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 3 or Communications Express 6.3 N/A. (The Address Book store resides in an LDAP directory.) You can configure Convergence 1 Update 3, 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 3.
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

The following table shows the memory and disk space requirements for Communications Suite 7 component products.

Memory and Disk Space Requirements for Communications Suite 7
Product Disk Space RAM Other
Sun Indexing and Search Service Approximately 20 Mbytes must be free in /opt for /opt/sun/comms/jiss.
Roughly 50 percent of the Messaging Server store size will be required for /var/iss directory. As ISS supports more attachment types, the amount of disk space needed for /var/iss/attach will increase. 1
4 Gbytes  
Sun Java System Calendar Server 7 Approximately 20 Mbytes.  
Sun Java System Calendar Server 6.3 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.
 
MySQL Server Approximately 650 Mbytes  
JDK Approximately 450 Mbytes  

1 In Indexing and Search Service, the /var/iss directory is divided into three subdirectories:

  • /var/iss/attach - Stores attachments, including JPG, PDF, ODF, Microsoft Word, Powerpoint, Visio, and Excel thumbnails as well as the original JPG, PDF, ODF, Microsoft Word, Powerpoint, Visio, and Excel files from the email. Because ISS stores the original attachment file here, the size of this directory can grow quite large depending on how many attachments of this type are in the mail store. Turning off the attachment store is a configurable option. Compared to the index store, this directory could probably reside on slower disk.
  • /var/iss/logs - Stores log files.
  • /var/iss/index/store - Stores index files. This tends to take up about 15 percent of the size of the mail store and needs to be on a fast disk as it is frequently accessed.

Operating System Requirements

The following table shows the recommended platforms for Communications Suite 7:

Operating System and Platform Support (Recommended for Communications Suite 7)
Operating System CPU Comments
Solaris OS 10 SPARC, x64 Minimum recommended version: Solaris OS 10 5/08 (Update 5)
See http://docs.sun.com/app/docs/coll/1236.8 for more information.
Red Hat Enterprise Linux 5 Update 3 x64 See http://www.redhat.com/docs/manuals/enterprise/ for more information.

The following table shows all the supported platforms for Communications Suite products.

Operating System and Platform Support (by Communications Suite Component)
Component Solaris OS 9 SPARC, x86 Solaris OS 10 SPARC Solaris OS 10 x86, 32-bit Solaris OS 10 x86, 64-bit Red Hat Linux 3 AS/ES 32- and 64-bit Red Hat Linux 4 AS/ES 32-bit Red Hat Linux 4 AS/ES 64-bit Red Hat Enterprise Linux 5 Server Update 3 64-bit Windows XP (SP1 or higher);
2003 Terminal Server
Windows Vista
Messaging Server 7 Update 3 32-bit
No No No No No Yes Yes Yes No No
Messaging Server 7 Update 3 64-bit No Yes No Yes No No No No No No
Messaging Server HA
No Yes No Yes No No No No No No
Calendar Server 7 No Yes No Yes No No No Yes No No
Instant Messaging 8 Update 2 No Yes No Yes No No Yes (only AS) Yes No No
Instant Messaging HA
No Yes No Yes No No No No No No
Convergence 1 Update 3
No Yes No Yes No No Yes Yes No No
Delegated Administrator 7 No Yes No Yes No Yes No Yes No No
Connector for Outlook 7.3 Update 1 NA NA NA NA NA NA NA NA Yes Yes
Calendar Server 6.3 Yes Yes Yes Yes No Yes Yes Yes No No
Calendar Server 6.3 HA
No Yes No Yes No No No No No No
Information and Search Service 1 No
Yes No Yes No
No No Yes No No
Communications Sync 3.1 NA NA NA NA NA NA NA NA Yes No
Dssetup Yes Yes Yes Yes No Yes Yes Yes No No

Notes:

  • Messaging Server, Calendar Server, Instant Messaging, Communications Express, and Delegated Administrator are no longer supported on HP-UX or Windows platforms.
  • Instant Messaging is not supported on Solaris OS 32-bit and Red Hat Linux 32-bit OS platforms.
  • The Communications Suite installer checks for required platform patches.
  • 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.
Minimal Solaris OS Install Requirements for Indexing and Search Service

The following Solaris OS packages are required for Indexing and Search Service: SUNWgcmn, SUNWgtar, SUNWxcu4, SUNWj5rt. If remote installs are needed, SUNWwgetr and SUNWwgetu are also required. Confirm that they are installed with pkginfo. Multi-machine deployments require SUNWapch2d, SUNWapch2r, and SUNWapch2u to be installed on indexing nodes. If not installed, install them from Solaris OS media before installing Indexing and Search Service.

The following Solaris JumpStart profile represents the minimal set of packages required for Indexing and Search Service.

##
## Minimum Required Software for Reduced Networking Support
## http://blogs.sun.com/gbrunett/entry/foundation_for_minimal_solaris_10
##
cluster SUNWCrnet

##
## Additional basic system services
##
# SSH Daemon, Tools and Dependencies
package SUNWgss add
package SUNWgssc add
package SUNWsshcu add
package SUNWsshdr add
package SUNWsshdu add
package SUNWsshr add
package SUNWsshu add
# NTP
package SUNWntpr add
package SUNWntpu add
# System Admin Tools (showrev)
package SUNWadmfw add
package SUNWadmfr add

##
## Indexing and Search Service Requirements
##
# GNU tar and Dependencies
package SUNWgcmn add
package SUNWgtar add
# XCU4 Utilities - ISS requires for awk and id
package SUNWxcu4 add
# Java 5 Run Time
package SUNWj5rt add
# wget - required only for remote ISS installs
package SUNWwgetr add
package SUNWwgetu add
Minimal Red Hat Linux Installation Requirements for Indexing and Search Service

The Red Hat Linux installation can run on top of the install group @Base in your kickstart.cfg file. The following RPMs must be be installed on Red Hat Enterprise Linux 5:

  • rpm-build
  • elfutils
  • elfutils-libs
  • compat-libstdc++-33
  • ntp
  • sharutils
  • compat-libstdc++-296
  • libxml2
  • xinetd

Multi-machine deployments require that the httpd RPM to be installed on indexing nodes for Red Hat Enterprise Linux 5.

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.

High Availability Support

Supported High-Availability Products
Product Supported Versions
Calendar Server 6.3
  • Sun Cluster
    • SPARC: 3.0, 3.1 Update 4, 3.2, 3.3
    • x86: 3.1 Update 4, 3.2, 3.3
    • Red Hat Linux: Not Supported
  • Veritas
    • SPARC: Not Supported
    • x86: Not Supported
    • Red Hat Linux: Not Supported
Instant Messaging 8 Update 2
  • Sun Cluster
    • SPARC: 3.1 Update 4, 3.2, 3.3
    • x86: 3.1 Update 4, 3.2, 3.3
    • Red Hat Linux: Not Supported
  • Veritas
    • SPARC: Not Supported
    • x86: Not Supported
    • Red Hat Linux: Not Supported
Messaging Server 7 Update 3
  • Sun Cluster
    • SPARC: 3.0, 3.1 Update 4, 3.2, 3.3
    • x86: 3.1 Update 4, 3.2 U1, 3.3
    • Red Hat Linux: Not Supported
  • Veritas
    • SPARC: 3.5, 4.0, 4.1, 5.0
    • x86: 3.5, 4.0. 4.1, 5.0
    • Red Hat Linux: 4.1, 5.0

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 table shows which browsers are supported for Communications Suite clients.

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 and 8.0 N/A 7.x and 8.0 N/A N/A N/A
Firefox
Note
Support for Firefox 2 is deprecated and will be removed in the future. Firefox 3.6.x is supported on Convergence 1 Patch 13 as well as on all later releases.

2.0.0.11 minimum
3.0.x,
3.6.x (See Note)
2.0.0.11 minimum
3.0.x,
3.6.x (See Note)
2.0.0.11 minimum
3.0.x,
3.6.x (See Note)
2.0.0.11 minimum
3.0.x,
3.6.x (See Note)
2.0.0.11 minimum
3.0.x,
3.6.x (See Note)
2.0.0.11 minimum
3.0.x,
3.6.x (See Note)
Safari N/A N/A N/A N/A N/A 3.2.x
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

Calendar Server 7 (CalDAV Server)

Supported Clients for Calendar Server 7
Client Version Notes
Apple iCal At least version 3 iCal 3 comes bundled with Mac OS 10.5.
Lightning 0.8 and 0.9 Lightning 0.8 supports basic CalDAV but does not support invitations and as such cannot be used for scheduling. Lightning 0.9, which does support CalDAV scheduling, is also supported by Calendar Server. Note that the latest version of Thunderbird is version 2.
Convergence   Future integration is planned.

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

The table below lists the supported and unsupported client platforms:

Operating System Supported Platforms Unsupported Platforms
Solaris Solaris OS 10 64-bit Solaris 9, Solaris 10 32-bit
Microsoft Windows Microsoft Windows 98, ME, NT (SP 6a), 2000, XP -
Mac MacOS X, minimum 10.1 -
Red Hat Linux Red Hat Linux 4 and 5, 64-bit Red Hat Linux 4 32-bit, Red Hat Linux 3 and Red Hat Linux 5 32-bit

The table below lists the supported and unsupported server platforms:

Operating System Supported Platforms Unsupported Platforms
Solaris Solaris OS 10 64-bit Solaris 9, Solaris 10 32-bit
Red Hat Linux Red Hat Linux 4 64-bit, Red Hat Linux 5, 64-bit Red Hat Linux 4 32-bit, Red Hat Linux 5 32-bit, Red Hat Linux 3
Note:
Instant Messaging 8 Update 2 requires Java version 1.6 minimum.

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.6 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.6 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.6 minimum installed, you need to install Java Web Start. You can download and install Java v1.6 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.

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

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
Indexing and Search Service "Indexing Search Service"
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 space.

Sun Java Communications Suite Installation and Upgrade Notes

Default Installation Directories and Ports

Reviewers
Need to update this section for Indexing and Search Service 1 and Calendar Server 7

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.

Default Installation Directories
Label and State File Parameter Default Directory Comment
Access Manager
CMN_IS_INSTALLDIR
Solaris OS: /opt/SUNWam
Red Hat Linux: /opt/sun/identity
 
Application Server
CMN_AS_INSTALLDIR
Solaris OS and Red Hat Linux: /opt/SUNWappserver Contains Application Server utilities, executables, and libraries.
Application Server Domains
CMN_AS_DOMAINSDIR
Solaris OS and Red Hat Linux: /opt/SUNWappserver/domains Default area under which administrative domains are created.
Calendar Server
CMN_CS_INSTALLDIR
Solaris OS and Red Hat Linux: /opt/sun/comms/calendar  
Convergence
CMN_IWC_INSTALLDIR
Solaris OS and Red Hat Linux: /opt/sun/comms/iwc  
Communications Express
CMN_UWC_INSTALLDIR
Solaris OS and Red Hat Linux: /opt/sun/comms/ce  
Delegated Administrator
CMN_COMMDA_INSTALLDIR
Solaris OS and Red Hat Linux: /opt/sun/comms/da  
Directory Preparation Tool
CMN_DSSETUP_INSTALLDIR
Solaris OS and Red Hat Linux: /opt/sun/comms/dssetup  
Directory Server Core
DSEE_BASE
Solaris OS: /opt/SUNWdsee/ds6
Red Hat 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
Red Hat Linux: /opt/sun/dscc
 
Directory Proxy Server
DSEE_BASE
Solaris OS: /opt/SUNWdsee/dps
Red Hat Linux and HP-UX: /opt/sun/dps
 
Directory Server Instance Directory
DSEE_INSTANCE_DIR
Solaris OS: /var/opt/SUNWdsee/dsins1
Red Hat Linux: /var/opt/sun/dsins1
 
HADB
CMN_HADB_INSTALLDIR
Solaris OS: /opt/SUNWhadb
Red Hat Linux: /opt/SUNWhadb
HADB install locations are not relocatable in Communications Suite installation.
  Solaris OS: /var/opt/SUNWhadb
Red Hat Linux: /var/opt/SUNWhadb
HADB Repository Data and Log location.
  Solaris OS: /etc/opt/SUNWhadb
Red Hat Linux: /etc/opt/SUNWhadb
HADB Management Agent Config File
  Solaris OS: /etc/init.d/ma-initd
Red Hat Linux: /etc/init.d/ma-initd
HADB Management Agent Startup Script
Instant Messaging
CMN_IIM_INSTALLDIR
Solaris OS and Red Hat Linux: /opt/sun/comms/im  
Instant Messaging Resource Directory
CMN_IIM_DOCSDIR
Solaris OS and Red Hat Linux: /opt/sun/comms/im/html  
Instant Messaging Online Help Directory
CMN_IIM_DOCSHELPDIR
Solaris OS and Red Hat 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/SUNWimq Red Hat Linux:
/opt/sun/mq /etc/opt/sun/mq /var/opt/sun/mq
Messaging Server
CMN_MS_INSTALLDIR
Red Hat Linux, 32 bit: /opt/sun/comms/messaging
Solaris OS 64-bit: /opt/sun/comms/messaging64
Messaging Server also uses /var/opt/sun/comms/messaging and /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
Red Hat 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
Red Hat Linux: /opt/sun/webserver7
 
Web Server Instance Directory
CMN_WS_INSTANCEDIR
Solaris OS: /var/opt/SUNWwbsvr7
Red Hat 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.

Reviewers
Need to update this section for Indexing and Search Service 1 and Calendar Server 7

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

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

6785668 (fixed in R6u2)

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 (fixed in comm_dssetup 6.4p4 which is part of R6u2)

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 (fixed in R6u2)

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

No Localization Files for Communications Express (R7 no longer delivers CE)

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 upgr

Sun Convergence 1 Update 3 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Convergence 1 Update 3, including:

About Convergence 1 Update 3

See Introduction to Convergence.

What's New in This Release of Convergence

See the What's New document.

Requirements for Convergence 1 Update 3

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

For requirements specific to Convergence, see the Requirements for Convergence 1 Update 3.

Convergence Installation Notes

See the Communications Suite 7 Installation Guide for information on installing Convergence.

Running the Convergence Initial Configuration Program in Secure Mode

In some configurations, the Convergence init-config program fails when Convergence uses the secure=true option to run the Application Server asadmin commands. Specifically, the asadmin commands invoked by init-config fail in this situation.

Situation: This issue occurs when the Application Server is configured to run in non-secure mode, and the Convergence init-config program is configured to run the Application Server asadmin commands in secure mode. In the Convergence init-config program, the Secure Administration Server check box is checked by default.

Solution: If you are running Application Server in non-secure mode, when you run the init-config program, uncheck the Secure Administration Server check box in the Application Server: Administration Instance Details panel.

If you are running Application Server asadmin in secure mode, you can accept the defaults when you run init-config.

Problems Fixed in This Release of Convergence

6625314

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

6654031

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

6772119

Some messages and other text strings in the Convergence UI are not translated.
Most of these messages concern S/MIME configurations. One message warns you that a message attachment size exceeds the limits set for this installation.

6780252

When you compose a message with the RTF editor and switch to plain text, double quotes (") are displayed as follows:

"

Similarly, an ampersand (&) in RTF is displayed as &amp. This issue also occurs when you use Reply, Reply All, Forward, and so on.

6779427

When you save a message as a draft in plain text and then reopen the draft, spaces are displayed as &nbsp.
When you first save the message as a draft, the draft is saved correctly. It is only when you open the message again that the &nbsp characters are inserted in place of spaces.

6763513

In Firefox 3.0.x, the chat window editor cursor does not appear when you toggle among multiple IM windows.
This issue occurs only with Firefox 3.0.x.

6679055

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

6698967

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

6739123

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

6688269

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

6691922

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

6784462

Multibyte/European characters in the file name of an event or To-do attachment are garbled.
If you attach a file to a calendar event or to-do list and use multibyte characters in the attachment file name, the file name is garbled.

6775482

In Firefox 3.0.x, the URL for Convergence 1 Update 3 Help page is not properly loaded and displayed.
This issue occurs in Firefox 3.0.x only. The URL for the Help page does not escape the "TM" and spaces in the URL string; thus, the URL link does not connect to the actual Help page, and it is not loaded properly. With other browser versions, the URL string in question appears as: Sun%E2%84%A2%20Convergence%20Help. On Firefox 3.0.x, it appears as: Sun<TM> Convergence Help.

6698876

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

6868597

No error message is shown when S/MIME is disabled for encrypted messages sent using Thunderbird

The issue is resolved with MS and for Convergence patch 10/11/12 to work properly with S/MIME enabled the following minimum patch level is required:

  • 137203-14 - Messaging Server 7u3-14.01 RHEL4.0 RHEL5.0
  • 137204-14 - Messaging Server (64bit) 7u3-14.01
  • 137205-14 - Messaging Server (64bit) 7u3-14.01_x86: core patch

Known Issues and Limitations in Convergence

The Convergence known issues are grouped in the following categories

Known Issues: General and Authentication

6870440

Single Host with Indexing and Search Server: Switching between attachments and Inbox makes the Application Server unresponsive

If Convergence and ISS are deployed on the same instance of application server, the application server becomes unresponsive when users switch between the Attachments folder and Inbox.

To fix this, perform the following steps:

  1. Set number of request processing threads to double the number of CPUs in the system. This can be done by setting the server.http-service.request-processing.thread-count parameter in application server using the asadmin command.
    Here is an example:
  2. Restart the application server.

6881061

Performance Issues seen with concurrent users on Convergence with Instant Messaging enabled.

Convergence experiences performance issues when a number of concurrent login and logout operations are performed. The issue is seen when Instant Messaging is enabled in Convergence deployed on Sun Glassfish Enterprise 2.1 patch 02.

6701184

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

6702002

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

6699051

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

6691137

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

6690719

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

6686058

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

6686064

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

6610071

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

Known Issues: Configuration

6806196

Cannot configure or upgrade Convergence if Application Server is configured with CA signed certificate
When Convergence is configured or upgraded on application server configured with CA signed certificate or SSL, the configuration step where application server deploys the Convergence web archive stalls and does not complete. This is because application server waits on the administrator input to accept the certificate.

Workaround:
Perform the following steps to deploy and configure or upgrade Convergence on Application Server configured with a CA certificate:

  1. Execute any of the Application Server's asadmin command:
    Here is an example:
  2. Accept the CA certificate when prompted.
  3. If you are configuring Convergence for the first time, remove the /var/opt/sun/comms/iwc folder and reconfigure Convergence using the init-config command.
    If you are upgrading Convergence, re-apply the patch.

Known Issues: Mail

6870057

Convergence mangles rich text pasted in from Microsoft Word
This issue is seen with emails that have body content copy-pasted from a Microsoft Word document. Users might see garbled text in XML format displaying Microsoft Word specific tags. This happens when users log in to Convergence using Internet Explorer.

6794669

When composing a mail, the To, Cc, and Bcc labels appear as hyperlinks but do not have any actions associated with them.

Workaround These fields were provided to add contacts from the address book. Click the + symbol adjacent to the fields to add contacts from your address book.

6824767

Filter does not work if folder selected is a subscribed folder
If a mail filter is created in such a way that emails are filtered into a subscribed folder, the filter does not filter messages correctly even if appropriate permissions are granted.

No Issue ID

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

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

6694440

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

6693443

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

6692441

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

669200

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

6657490

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

6630169

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

Known Issues: Calendar

14023594

Inviting Calendars to Events without Invite Permissions Does Not Work Correctly with Calendar Server 6

If you invite a calendar with none or Check Availability permissions to an event, the event is saved in the calendar. This behavior is incorrect; instead, your calendar should refuse to invite users without invite permissions.

6890898

Convergence Calendar freebusy lookup does not work for users on Calendar Server 7
Convergence cannot display the availability (freebusy status) of users configured on Calendar Server 7.

6840464

Quick Add Functionality Does Not Work Correctly in non-English languages
The Convergence calendar module enables you to quickly add and event by using the quick add event functionality. This functionality enables users to create an event based on the description provided in the quick add callout. For example, if the user provides the description 1pm lunch at the Counter in the quick add callout, the event attributes that are assigned to the time, location, and title are 1pm, the Counter, and lunch respectively. However, for non-English locales, the order in which the description is typed might change as the semantics of the language might differ from English. Users are forced to provide the event description in the English language order for the quick add function to work correctly in non-English locales.

6780373

If you select a subscribed calendar on which you have limited permissions, you cannot create events or edit your own user-owned calendar.
This issue occurs when you select a calendar to which you have subscribed, when your permissions on the subscribed calendar are limited. When you then try to modify your own calendar by, for example, adding an event or editing event details, you are unable to do so.

6737224

In calendar, in the Next 7 Days view, the Refresh button does not work.
If you open the Next 7 Days view in calendar, and an action modifies your calendar, clicking the Refresh button does not display the modification. For example, if another user invites you to an event or an event is deleted from the Convergence Server, these changes do not appear after you click Refresh.

6691971

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

6691933

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

6645274

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

6641358

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

Known Issues: Address Book

6880611

Unable to connect to Convergence address book server through Sun Java System Connector for Microsoft Outlook
This issue is seen with Sun Java System Connector for Microsoft Outlook (Outlook Connector) configured with Convergence. When Outlook Connector users try to access address book by clicking on the Address Book tab, the connection to Convergence address book server cannot be established. The following error message is displayed:

6697453

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

6688678

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

6704130

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

6692504

In IE7, apostrophes are not accepted in the Group Name text box.
In IE7, when you create an address-book group and try to use an apostrophe in the group name, the text box does not accept or display the apostrophe. This is not an issue in Firefox.

6676645

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

6654530

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

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

6649025

The Address Book Properties window displays incorrect information.

6646169

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

6638802

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

6637775

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

6609983

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

6673188

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

6688097

Cannot make default address book as corporate address book.

6690711

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

6692518

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

6702142

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

Known Issues: Instant Messaging

6830940

Provide avatar support for Instant Messenger in Server to Server deployment.

Convergence does not provide avatar support in a server to server deployment. When two Instant Messaging servers are configured with Convergence and server to server communication is enabled between the two Instant Messaging Servers, the avatars are not uploaded when users chat from Convergence Instant Messaging client.

6696906

The avatar properties widget should indicate the file-size limit or image dimension limit that can be uploaded.
By default, a text message should indicate these limits, as in the following example: "You can only upload a file size up to 100KB & image dimension up to 2000 x 2000." Without this warning, users are more likely to try to upload oversized pictures for their avatars that will fail to upload properly.

6696027

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

Workaround: Manage the group then add the contact.

6689431

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

6684054

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

6668868

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

6665909

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

6665897

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

6664158

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

6662902

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

Known Issues: Options

6694006

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

6676645

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

6654595

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

6648561

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

Known Issues: Customization

6745772

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

6745757

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

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

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

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

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

Known Issues: S/MIME

6781802

When using S/MIME on Windows Vista with JDK6u1.1, the browser hangs for CAC-card users if the first message in the user's inbox is encrypted.
After the user logs in, as soon as the inbox loads, it tries to decrypt the first message and tries to access the Private key of the user from CAC-card. The browser hangs and the user cannot perform any further operations.

Redistributable Files for Convergence

Sun Convergence 1 Update 3 does not contain any files that you can redistribute.

Sun Java System Calendar Server 7 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Calendar Server 7, including:

About Calendar Server 7

See Introduction to Calendar Server 7.

What's New in This Release of Calendar Server 7

See the What's New document.

Requirements for Calendar Server 7

Calendar Server 7 Installation Notes

See the Communications Suite 7 Installation Guide for information on installing Calendar Server 7.

Calendar Server 7 Compatibility Issues

If necessary, this section should list any compatibility issues.

Known Issues and Limitations in Calendar Server 7

6868370

In a Calendar Server 6/Calendar Server 7 co-deployment scenario, busy information for All Day events are not being shown through the Convergence UI

6846562

Schema 1 support for CalDAV Server
For Calendar Server 7 to support LDAP schema 1, you need to add some ACIs at the domain level, at least the anonymous access. See Configuring Calendar Server 7 to Use LDAP Schema 1 for workaround.

6724653

Logs for Calendar Server 7 JMS consumer for notification emails are embedded in Application Server logs

6737896

Apple iCal uses a new property to determine the privacy restrictions, instead of just using the CLASS property in the event.

6740679

[Appleical]Task creation with Due Date creates 403 error mismatch: DTSTART floating = false
Does not apply to Mac OS X Snow Leopard.
Workaround: Remove dtstart if due=date and dtstart=datetime. Add RELATED=END param to alarm trigger if relative alarm.

6742801

[AppleiCal]Error on removing and adding an attendee in one instance of a recurring series

6748104

Event request notification is not displaying the modified time correctly for modification of a single occurrence of a recurring event

6791801

[AppleiCal]get http 403 when modifying an instance to add an attendee

6795953

davadmin config allows setting of invalid log levels

6799116

Creation of a task in Lightning with due date and alarm fails with invalid calendar data

6879002

davadmin calresource import fails for events with ORGANIZER

6879006

davadmin calresource import fails for events with ATTENDEES

6808801

davadmin config command takes invalid values for log.dav.*.maxlogfiles

6811845

MKCOL with weird body should fail; extended MKCOL support not complete.

6821041

davadmin config command takes invalid value for notification.dav.smtpport

6822646

Deleting a range of all day recurring events by using davadmin fails if the range includes an exception

6834023

Error while modifying a single instance of recurring event in Thunderbird

6834152

ical:Single instance of time based event cannot be modified into all day event in recurring event

Redistributable Files for Calendar Server 7

This release of Calendar Server 7 does not contain any files that you can redistribute.

Indexing and Search Service 1 Release Notes

Topics:

About Indexing and Search Service

Sun Java Indexing and Search Service is a general-purpose indexing and searching server. As email inboxes become increasingly larger, the importance of a fast, efficient indexing and search service cannot be underestimated. Consequently, Indexing and Search Service initially supports email data in the message store, including embedded data in a variety of formats. However, ISS will offer an open-ended index and search web service capable of indexing and searching other types of data in other data stores such as calendar data, address book data, and more. This web service provides a RESTful web services interface for search, thus any client capable of interacting with such a service will be supported. Sun Java System Messaging Server consumes ISS services to bring search services to any IMAP-based mail client. Message body searches done from your mail client can use the ISS engine to perform fast, comprehensive searches of message bodies and attachments.

Initially, ISS supports Sun Java Communications Suite data such as the Messaging Server message store. This includes embedded data in text, HTML, XML, Open Office, Microsoft Office, and PDF formats. Also, metadata is created for JPEG files.

What's New in This Release of Indexing and Search Service

See the What's New document.

Requirements for Indexing and Search Service

See Requirements for Communications Suite 7.

Product Version Compatibility Requirements

See Communications Suite 7 Product Version Compatibility Requirements.

Known Issues and Limitations in Indexing and Search Service 1

No issue ID

No search capability yet for calendar, address book, and instant messaging content.
This feature might be supported in a future release.

6857221

/var/iss/logs is left over after uninstall.
Uninstalling ISS will not remove the /var/iss/logs directory. This directory should be manually removed if desired after uninstallation.

6868898

Specifying the component as a parameter for setup.sh should be case insensitive.
setup.sh requires that component names be specified in lower case.

6871171

Communications Suite Installer (switching from infraprov) uninstall leaves appserver startup.
If a successful uninstall using infraprov has not occurred (infraprov was the installer/uninstaller for the ISS beta), it is possible that a subsequent install of ISS using Communications Suite Installer will not be successful. As a workaround, ensure that the uninstall using infraprov succeeds before upgrading.

6870440

Single Host with Indexing and Search Server and Convergence in same instance of GlassFish Enterprise Server: Switching between attachments and Inbox makes the GlassFish Enterprise Server unresponsive

If Convergence and ISS are deployed on the same instance of GlassFish Enterprise Server, GlassFish Enterprise Server becomes unresponsive when users switch between the Attachments folder and Inbox.

To fix this, perform the following steps:

  1. If you are deploying Convergence and ISS on the same host and on the same GlassFish Enterprise Server web container, you must increase the number of GlassFish Enterprise Server request processing threads to two times the number of CPUs on the system.
    1. Determine the number of CPUs on the system.
      • Red Hat Linux:
        cat /proc/cpuinfo | grep processor | wc -l
        
      • Solaris OS:
        mpstat | grep -v CPU | wc -l
        
    2. Set the number of request processing threads to two times the number of CPUs determined above.
      cd /opt/SUNWappserver/bin
      ./asadmin set server.http-service.request-processing.thread-count = <2 x number-of-cpus> 
      
  2. Restart GlassFish Enterprise Server.
    cd /opt/SUNWappserver/bin
    ./asadmin stop-domain domain1
    ./asadmin start-domain domain1
    

6786334

When running as root, running issadmin.sh with folder names like jeff's email will not work.
If the folder name contains a single quote or other characters that need to be escaped on the command line, it cannot run as root. Instead, run the command as the ISS user, for example:

su - jiss
/opt/sun/comms/jiss/store/scripts/issadmin.sh --user jeff --checkfolder --folder jeff\'s\ email

6787743

Concurrent --checkaccount runs produce wrong results.
Concurrent --checkaccount runs against the same user return wrong results. Avoid running --checkaccount against the same user at the same time. Running against different users at the same time is fine.

6805757

Transitory --checkaccount mismatches might be reported due to latency between Messaging Server message store & ISS store.
While the --checkaccount command is running, real time events might arrive, causing the Messaging Server message store and ISS store to appear to be out of sync. Typically this shows up as a message indicating "mismatched message count" and "last UID mismatch." If this happens, before running --sync, run --checkfolder on the folder for which such a message occurs. If the message disappears, this transitory problem has been fixed. If the message recurs, then run --sync to fix the folder. This problem might be addressed in a future release.

6839144

issadmin.sh --checkaccount can miss out-of-sync state.
isssadmin.sh --checkaccount compares the first and last valid UIDs and the message count to determine whether a folder is in sync. It is possible for these values to match, but for there still to be differences.

6744853

issadmin.sh --storepath option fails silently when index service is running.
The --storepath option to issadmin.sh requires that the index service not be enabled at the time the command is run. If the index service is running, the command will be executed by the index service, which is using the configured store path and not the non-standard path provided by the --storepath option.

6861561

issadmin.sh behaves poorly while batch processing.
Running the issadmin.sh command with the --accountlist option will abort on the first failure rather than continue to the next account if a failure is encountered.

6719204

Content-MD5, Content-ID, Message-ID are indexed, but can't be searched.
The values for each of these fields almost always contain punctuation marks, so no search query will match correctly because punctuation is treated like blanks. This problem might be addressed in a future release.

6652023

Unable to match strings with underscore, /, . etc characters.
Punctuation characters are generally treated as blanks. Try searching for substrings delimited by them. This issue might be addressed in a future release.

6828600

Count of emails containing attachments is not maintained correctly.
issadmin.sh returns a count of emails containing attachments and while this is correct after bootstrapping an account, it is not maintained properly as changes are made to the account.

6747455

Searches coming through Messaging Server are not compliant with IMAP RFC.
Several IMAP features are not currently implemented by ISS. These features should be handled by the Messaging Server when a satisfactorily compliant search result cannot be returned. This issue might be addressed in a future release.

6800930

Search query using wildcard can fail with org.apache.lucene.search.BooleanQuery$TooManyClauses.
To support wildcarding, the query is expanded to match many possible patterns. Sometimes this exceeds a predetermined limit, which causes the search to abort. Reducing the scope of the wildcard in the query might avoid this problem. Try to make the match as restricted as possible, such as matching "+to:harry*" instead of "+to:h*". This problem might be addressed in a future release.

6855529

Searches for stop words generate the wrong results.
Searches for words such as "the" and "this" will yield no matches because "stop" words such as these are not indexed.

6696346

Index lock not cleaned up after abort.
Should a command that modifies an account, such as issadmin.sh --synch or indexSvcBootstrap.sh abort for some reason, the indexWriter that was used might not be cleaned up properly. This situation might then cause various issadmin.sh commands, such as --accountinfo to produce strange results. To check if something is wrong, run the following command, for example:

find /var/iss/index/store -name write.lock

If you find any such files in the index of an account that you had been modifying, stop the server, delete those write.lock files, and restart the server before you continue. This problem might be addressed in a future release.

6881401

Multiple account state listeners cause harmless jms error messages in log.
Error message such as following:

com.sun.comms.iss.common.AccountStateListener sendResponse WARNING: Unable to obtain JMS objects to send message response: [SEND_REPLY(9)] [C4036]: A broker error occurred. :[500] com.sun.messaging.jmq.jmsserver.util.BrokerException: Destination Q:temporary_destination:__queue_10.5.185.151_49983_1 could not be found in the store user=misoadmin, broker=isshost.example.com:7676(62279)

might appear in JMQConsumer and appserver log when account state is changed, it indicates the listener couldn't send back a confirmation message, but there is no impact on functionality. This kind of error messages can be ignored. Sending response to the account state topic might be removed in a future release.

6694980

Some of the PDF thumbnails do not show the content in first page of the PDF file.
Some PDF thumbnails are cropped from the center of the first page of the file. The thumbnail might not not show the content in the first page if the content is not in the cropped area.

6735477

Allow all supported attachment types to be downloaded from attachment store (not just PDF,ODF,JPEG, Microsoft Office files).
At present, the attachment store plugin only stores Microsoft Office files, PDF, ODF, and JPEG attachments. Other attachment types are parsed and indexed and can be searched, but no thumbnail is generated and the original document is not stored in the attachment store. The original document can still be retrieved on the Messaging Server.

6867806

Internet Explorer: Attachments with multi-byte names may have garbled names in the "Save As" dialog when downloaded.
ISS transfers an attachment's file name in the Content-Disposition field, which Internet Explorer does not interpret properly for some non-ASCII characters. A garbled name may appear if such an attachment is saved to the client system within Convergence's Attachment Search interface.

6681801

ISS doesn't support the Word 2007 .docx file format or other Microsoft Office 2007 OpenXML formats.
This feature might be in a future release.

6741064

Failed to index PDF attachment: Error parsing the input stream: expected hex character and not :32.
Some PDF files cannot be parsed and generate errors similar to this one. This issue might be addressed in a future release.

6756525

Failed to index: MSVisioConverter: Found a chunk with a negative length, which isn't allowed.
Some Microsoft Visio files are not able to be parsed and generate errors similar to this one.

6804279

MSVisio Attachment: Unable to extract content java.lang.ArrayIndexOutOfBoundsException.
Some Microsoft Visio files are not able to be parsed and generate errors similar to this one.

6713676

SearchUI should provide a way to proceed to next 100 items.
SearchUI only displays the top 100 results. Until this is fixed, to see all matches, use the RESTful web search directly, or narrow the search query with more terms to ensure there are fewer than 100 total results.

6887552

Real-time events with Content-type: text/* and Content-disposition: inline are not indexed.
The message body from emails with Content-type: text/* and Content-disposition: inline is not handled properly when arriving as a real-time event, resulting in a failure to search within the message body of such emails. A fix may be forthcoming in patch 1 of ISS, and after ISS is patched, all users must be re-bootstrapped.

Redistributable Files for Indexing and Search Service

None.

Sun Java System Calendar Server 6.3 Release Notes

As of Communications Suite 7, Calendar Server 6.3 has been deprecated.
If you are not installing Sun Convergence, you should no longer be installing Calendar Server 6.3. Instead, install Calendar Server 7.

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:

Calendar Server 6.3 Upgrade Patches
Platform Patch Number (English and Localized Languages)
Solaris OS, SPARC 121657-40
x86 121658-40
Linux 121659-40

After patching, csversion will show the product version as "6.3-19.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.2 with latest patch available on SunSolve (116577-42 for Sparc, 116578-42 for x86 and 117851-42 for Linux).

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:

# Make sure the Calendar Server installation is patch 121658-19 or prior.

  1. Important: Take a copy of the current database.
  2. Check to make sure the database is in good condition by running db_verify and csdb check.
  3. 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.
  4. Apply this patch (121658-24 or later).
  5. 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.
  6. 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

The csclean Utility Works in Schema 1 and Schema 2

The Communications Suite 5 version of Calendar Server 6.3 Administration Guide incorrectly states that the csclean utility only works in Schema 2.

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:

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

Sun Java System Messaging Server 7 Update 3 Release Notes

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

About Messaging Server 7 Update 3

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

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

What's New in This Release of Messaging Server

See the What's New document.

Deprecated and Removed Features for Messaging Server

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

Removed: Solaris 9, Solaris 10 32-bit, Red Hat Linux 3

Solaris OS 9, Solaris OS 10 32-bit version (on both SPARC and x86), and Red Hat Linux 3 platform support has been removed in this release. Red Hat Linux 5 support was added in this release.

Red Hat Linux 32-bit version and Red Hat Linux 4

Support for the 32-bit Red Hat Linux version of Messaging Server and support for the Red Hat Linux 4 platform is deprecated and may be removed in favor of a 64-bit Red Hat Linux 5 version in a future release.

Removed: local.servergid and MMP BeTheGroup options

In previous releases, there was an unspecified requirement that these settings be the same as the primary group of the user specified via the local.serveruid or MMP BeTheUser option. If these settings were different, certain interactions between the MTA and store would fail. In this release, these options are now ignored and the primary group of the user specified via the local.serveruid and MMP BeTheUser option is used as the process group for server processes. The MTA has always used the primary group of the user specified by the IMTA_USER imta_tailor setting as the process group for MTA server processes.

Removal of Support for the Sun Java System Monitoring Framework

Support for the Sun Java System Monitoring Framework has been removed from the Messaging Server starting with this release.

Event Notification Service (ENS) and Sun Java System Message Queue (JMQ)

The Java MQ C SDK is not presently available for 64-bit Linux so a future version of the Comms Installer may not include the SDK necessary for Messaging Server to use Java MQ on Linux. Linux customers should consider using ENS instead of JMQ or contact the Java Message Queue product team for further information on 64-bit Linux C SDK availability.

Requirements for Messaging Server 7 Update 3

See Requirements for Communications Suite 7.

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

Messaging Server Installation Notes

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

Installation Overview for Messaging Server

Use the Communications Suite installer to install Messaging Server.

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

Next, you must configure Messaging Server by:

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

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

comm_dssetup.pl Changes for this Release

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

  1. Messaging Server 7 Update 3 requires that you run the version of comm_dssetup.pl in Communications Suite 7.
  2. See Messaging Server Compatibility Issues for more changes to the comm_dssetup.pl program.

Upgrade Instructions for Messaging Server

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

Messaging Server Documentation Updates

There are no Messaging Server Documentation Updates at this time.

Messaging Server Compatibility Issues

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

The following table describes compatibility issues with Messaging Server:

Incompatibility Workaround Comments
comm_dssetup.pl, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Interactive Mode: Server-root and Directory Server Instances Directory Server instance(s) reside in the server-root, or an explicit Directory Server instance directory Previous versions of Directory Server used the notion of a server-root where multiple instances and configuration info would be housed. Directory Server 6 no longer uses a server-root. Instances may be anywhere. In this question, a user needs to: 1) specify the instance directory. Or, if the user is using previous versions of Directory Server, the user can: 2) specify the server-root directory where the instances are housed. You will be prompted with an additional question to pick an instance from the server-root. Or, 3) a user who has used Directory Server 5x and is now using Directory Server 6 might manually put all of her Directory Server instances under a parent directory (what we used to call a server-root).
Note

Server-root terminology has been removed from Directory Server 6.
no additional comments
comm_dssetup.pl, the program that prepares the directory server for Messaging Server (Calendar Server and Delegated Administrator) has been modified to work with both Directory Server 6.0 and Directory Server 5.x: Silent Installation: server-root directory In previous versions of Silent installation, you would specify both a server-root and an instance directory. If you are using Directory Server 5.x, this still holds true. Since there is no server-root directory in Directory Server 6.0, you will need to specify the parent directory of the Directory Server instance. no additional comments
The location of the Directory Preparation Tool (comm_dssetup.pl) has changed. comm_dssetup.pl is now in its own package installed in /opt/sun/comms/dssetup for Solaris and Linux
Existing scripts that specify the old path need to be updated.
To install the package, be sure the Directory Preparation Tool is selected in the appropriate installer panel.
In Messaging Server 5.x, an administrator could use the IMAP listcommand to display all folders in the message store. In a typical message store, this caused the server to display an unusually long list.
In Messaging Server 6.x, when an administrator runs the IMAP list command, it displays only the explicitly shared folders.
To list all folders in the message store, use the mboxutil utility. For more information on the mboxutil utility, see the Sun Java System Messaging Server 6.3 Administration Guide.
The configuration program for the Delegated Administrator has changed. Install Delegated Administrator and run the configuration program. The current program is located at:
for Solaris and Linux, opt/sun/comms/da/bin/config-commda
Upgrade to the new Delegated Administrator when installing this version of Messaging Server.
Upgrading Messaging Server with Webmail over IMAP protocol change (6397425, 6397451, 2137362) The back-end server must be upgraded before upgrading the front-end server. Both the Webmail over IMAP protocol as well as the back-end message stores must be the same product version. See the Sun Java Communications Suite 5 Upgrade Guide for details. no additional comments
If you use Messaging Server with Access Manager Single Sign-on, it does not support Java Enterprise System 2004Q2 Access Manager Server. However, Access Manager 6.3 and later is supported. The specific versions of Messaging Server that do not support Java Enterprise System 2004Q2 Access Manager Server are:
  • Messaging Server 6.2-6.01 and later
  • Messaging Server 6.3
Upgrade Access Manager (JES 2004Q2) before upgrading Messaging Server.
Access Manager now has two installation types: Realm (version 7.x style) and Legacy (version 6.x style). If you are installing Access Manager with Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator, or Portal Server, you must select Legacy mode (version 6.x style). See: Sun Java System Access Manager 7 2005Q4 Release Notes If the wrong Access Manager is installed, you will not be able to run Delegated Administrator.
SNMP MADMAN mib support in Messaging Server 6.3 and later Running on Solaris 9 or earlier, Messaging Server SNMP support requires the Sun SEA SNMP master agent which comes with Solaris. There are issues with the SEA master agent. The preferred solution is to upgrade to Solaris 10 or later and use the Net-SNMP which comes with the OS. Running on Solaris 10 or later, Messaging Server SNMP support requires the Net-SNMP which comes with the OS.  

Problems Fixed in This Release of Messaging Server

6796347

The msgadm tool has a misleading name that conflicts with admin tools of other Comms products.

The msgadm command has been renamed to msgssh.

6840267

MMP can wedge due to back-end timeouts after Messaging Server 7 Update 2.

Known Issues and Limitations in Messaging Server

This section describes known issues in the Messaging Server product.

Red Hat Enterprise Linux 5 SNMP

Red Hat Enterprise Linux 5 only supports use of SNMP by 64-bit products. The current Messaging Server Linux build is 32-bit. Customers requiring SNMP support should continue using Red Hat Enterprise Linux 4.

Elimination of setuid binaries has potential behavior impact

The code works by having the job controller ask the watcher to start pipe_master and l_master. This has some potential impact:

  • If you have a large number of environment variables (approximately 16K), an upgrade to Messaging Server 7 Update 3 will cause l_master and pipe_master to stop working until the environment is reduced to a reasonable size. The job_controller log should have the phrase watch_newproc: buffer overflow if this happens.
  • The imsimta run pipe or imsimta run native commands now require root privilege (or a Solaris RBAC configuration granting pipe_master and l_master root privilege) to use.

32-Bit Plug-ins for 64-Bit Messaging Server Do Not Work

32-bit plug-ins from third-party vendors such as Brightmail or Cloudmark generally will not work with the 64-bit Messaging Server. There is very limited support for a single 32-bit Brightmail-interface compatible plugin through the use of a 64-to-32-bit shim. Use of this may result in reduced performance and limited functionality. Please contact your vendor for a 64-bit compatible plug-in for best results.

6860614

Advice for MMP default:NumThreads setting no longer correct, replace with default:MaxThreads setting

The MMP's default:NumThreads has been documented with the recommended setting equal to the number of CPUs and default setting of 1. This is no longer correct as of Messaging Server 7 Update 2 due to architecture changes necessary for IPv6 support.

To fix this, the MMP now ignores the default:NumThreads setting. It will instead look at a default:MaxThreads setting with semantics the same as the IMAP server's service.imap.maxthreads setting that defaults to 250.

SMS Gateway Server fails with assert in NSPR ptthreads.c on Red Hat Linux.

SMS Gateway Server does not work on Red Hat Linux.

6852929

Mail advance search does not work correctly if Messaging Server is configured with service.imap.indexer.enable

The results returned by an IMAP SEARCH will differ depending on whether or not the Messaging Server is configured with service.imap.indexer.enable to use the Indexing and Search Service. The IMAP specification states that a SEARCH operation should ignore white space. However, the search operation by the Indexing and Search Service is done as whole-word searches.

No Issue ID

Due to an upgrade to the Berkeley Database in Messaging Server 7 Update 1, after an upgrade from a version prior to Messaging Server 7 Update 1, when you restart the server, the Berkeley Database issues the following message: 'Skipping log file...historic log version.'

Redistributable Files for Messaging Server

The following redistributable files are provided with Messaging Server:

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

Sun Java System Instant Messaging Software 8 Update 2 Release Notes

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

About Instant Messaging

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

What's New in This Release of Instant Messaging

See the What's New in Instant Messaging 8 Update 2 document.

Deprecated and Removed Features for Instant Messaging 8 Update 2

The following features have been deprecated from Instant Messaging 8 Update 2:

  • IM Client - The Java client that is used to access the Instant Messaging server is deprecated. As a result, the following client features are deprecated:
    • VOIP Support - This feature enables you to convert a user's chat session into a live voice call over the internet by using Instant Messaging client
    • Poll - This feature helps you in surveying a group rapidly by conducting online polls
    • News - This feature enables you to access published information such as company announcements, project updates, or event notices on a subscription basis
    • Moderated Conferences - This feature enables the moderator to moderate private messages that are sent to conferences
    • Alerts - This feature enables you to notify users of time-sensitive information, either in individual messages or as broadcasts to multiple users. You can also specify routing of alerts received when offline
  • Redirect Server - This feature enables you to balance the load between different servers in a server pool
  • Communications Channel in Portal Server - This is the channel that is used to launch Instant Messaging in Portal Server
  • Portal Server Archiving - This feature enables you to archive chat content in the portal server

Requirements for Instant Messaging 8 Update 2

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

Instant Messaging Installation and Uninstallation Notes

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

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

Instant Messaging Compatibility Issues

The following table lists the compatibilities issues in Instant Messaging 8 Update 2.

Table 5-1 Instant Messaging 8 Update 2 Compatibility Issues

Incompatibility Impact Comments
Versions of Instant Messenger prior to Sun Java System Instant Messaging 7 2006Q1 do not support XMPP redirection.   If you use a third-party client, ensure that the client supports XMPP redirection before deploying the Instant Messaging redirect server.
The Instant Messaging SDK Java packages are renamed in Sun Java System Instant Messaging software 7 2005Q4 to match the open source community naming conventions. For example, org.netbeans.lib.collab. Instant Messaging will use the new naming scheme exclusively and deprecate the old scheme.  
Sun Java System Instant Messaging 8 is incompatible with Sun Java System Access Manager version 7 2005Q4. The supported version of Sun Java System Access Manager is version 7.1.  
Sun Java System Instant Messaging 8 is incompatible with the 2004Q2 versions of Portal Server and Messaging Server. The supported version of Sun Java System Portal Server are versions 7.1 and 7.1 update 1. The supported version of Sun Java System Messaging Server is version 7.0 Update 1.  
Due to a protocol change the Instant Messaging server 8 Update 2 cannot communicate with a server of a version older than 7.3 in federated deployments. Instant Messaging federated deployment sites should upgrade all the servers. The existing deployments who do not wish to upgrade the server should explicitly set the property of collaboration session factory object to use the legacy protocol implementation. Perform the upgrade to limit the length of time during which the servers cannot communicate with each other.
Client-Server Communication Due to a protocol change the older versions of the client and server (2004Q2 and earlier) cannot communicate with the new versions of client and server. Upgrade both the client and server at the same time.
Sun Java System Instant Messaging 7 2005Q4 and 2006Q1 are incompatible with the shared components that ship with Sun Java System Instant Messaging 8. Instant Messaging depends on the Instant Messaging SDK. The Instant Messaging SDK is installed with the shared components. Upgrade the shared components and then upgrade Instant Messaging. The Communication suite installer upgrades Instant Messaging SDK before installing Instant Messaging 8 Update 2.
The Instant Messaging SDK implementation of the legacy Instant Messaging Presence protocol is now co-packaged. By default, the Instant Messaging SDK APIs use the implementation based on the XMPP protocol. Applications should explicitly set the property of the collaboration session factory object to use the legacy Instant Messaging Presence protocol implementation.  
The SDK component includes additional JAR files. The Instant Messaging SDK uses the JSO (JABBER Stream Objects) libraries. To use the XMPP protocol effectively, modify the classpath parameter for older applications that use the Instant Messaging SDK.  
Sun Java System Instant Messaging 6 2004Q2 server is incompatible with the default behavior of the latest version of the SDK. To use the Instant Messaging 6 2004Q2 server with the current Instant Messaging SDK, set the property of the collaboration session factory object to use the legacy protocol implementation.  
Instant Messaging 8 Multiplexor might not work correctly with the older versions of the server.   Use Instant Messaging 8 for both the Multiplexor and server. Upgrade or patch systems on which the server is installed and then upgrade systems on which only the Multiplexor is enabled.
Instant Messaging 8 server might not work correctly with the previous versions of the Instant Messaging SDK.   Use the 8 version of the server and the SDK.
URL to the default codebase URL for Sun Java System Instant Messaging 8. The default URL for the codebase is http://server:port/im.  
Default port numbers for Sun Java System Instant Messaging 8 The default server port number is 45222 and the default Multiplexor port number is 5222.  
Instant Messaging 8 server might not work correctly with Multiplexor version 7.3.   Upgrade the Multiplexor to 8 Update 1.
Although the 7.3 client is supported on 8 server, all functionalities might not work.   Upgrade the client to version 8.

Problems Fixed in Instant Messaging 8 Update 2

This section contains a list of problems fixed in the Instant Messaging 8 Update 2 release.

6815949

Embryonic session closures occur in a server pool setup and single server.

6812926

When there is high load in a server pool setup, Null Pointer Exceptions are displayed.

6812928

Error messages received under load in the following format are only warn messages.

6831870

Improve performance of imadmin/adminrc scripts.

6831870

Refining the imadmin and adminrc shell scripts can improve the its responsiveness.

6848995

IM services fail to come up and displays a "Permission denied" error.

6863010

Error Loading native library when you set the usr/jdk/entsys-j2se to point to 64-bit jvm or set the jvm path in iim.conf file.

6849001

When IM service is deleted from SMF using svccfg, an incorrect message is displayed.

6863022

imadmin start does not display an error when the correct version of JDK is not found.

6777840

MSN gateway does not work on a 64-bit Linux machine.

6863005

MSN/Yahoo/AIM gateways fail to work on a Solaris machine when Python 2.3 is used.

6858621

MSN/AOL/Yahoo gateways fail to work on a Solaris machine.

6864236

Configuration fails with the following error when the JAVE_HOME is set to JDK 1.5.

6787948

In IM 8, gateway package fails to install on Redhat Linux 5.

6845798

JDK 1.6 should be supported for IM 8 Update 2 release.

6830607

Provide ACL/AM policy support to change the conference ownership from the owner to any user.

6853422

Server pool should support automatic discovery of new nodes.

6837382

Pidgin client cannot reconnect to a chat room after disconnecting.

6837841

Updating conference affiliations should accept http://jabber.org/protocol/muc#admin name space.

6845779

User with a mixed case uid can not enter a member-only conference room.

6847867

IM can not be deployed on Glassfish Enterprise Server v2.1 patch02.

6848348

Backup files display incorrect file names after upgrading IM to v8 Update 2.

6765540

Configurator should create the sym link for Yahoo gateway configuration file.

6850639

When logged in through httpbind, SASL auth failure error is displayed even though the authentication has passed.

6797269

Instant Messaging Server has a memory leak that impacts services and service availability.

6782734

Fix user caches. Problematic when there is not enough free memory to cache to tempfs.

6821743

Server hangs in a server pool setup when conferences are used.

Known Issues and Limitations in Instant Messaging 8 Update 2

This section contains a list of known issues at the time of release of Instant Messaging 8 Update 2 in the following categories:

Instant Messaging Agent Issues

6865601

MSN gateway fails to come up on Red Hat AS platform.

6886522

Login through Yahoo transport may not work since Yahoo transport is outdated.

6821946

Yahoo gateway can not connect to the server when TLS is mandated on the server.

6724472

Offline SMS messages are sent to user even after you block messages from a particular user.

6745138

Text formatting changes made in the AIM client do not appear in the Sun Instant Messaging client.

6646700

Sending an alert from the Instant Messaging client to a user in AIM, MSN, or Yahoo client results in an alert being delivered as a chat conversation. The delivery status of the alert is also not updated correctly.

6646702

The subject of the alert sent from the Instant Messaging client to an AIM, MSN, or Yahoo client is not displayed.

6646704

The Offline Alert functionality does not work when alerts are sent from the Sun Java System Instant Messaging client to users in the MSN, Yahoo, and AIM clients.

6646712

In the Instant Messenger client, the MSN, AIM, or Yahoo transport credentials that a user provides to log in are not displayed.

Instant Messaging Installation, Upgrade, and Uninstallation Issues

6878939

After upgrading from IM version 8 to IM 8 Update 2, IM fails to start, and the following error message is displayed even though Java 1.6 is installed:

6868625

For cal-agent to work when enabled, the configuration parameters have to be modified after upgrade.

6869042

Shoal parameters are missing and get replaced with old server pool or server-to-server parameters after upgrade.

6869109

The following parameters have to be modified if upgrading from versions earlier than IM 8.0.

Workaround: Modify the values to:

6824676

When you upgrade from Instant Messaging 7.2 or 7.3 to Instant Messaging 8 Update 1, Calendar agent parameters (jmq) are incorrect.

6818830

When you upgrade from Instant Messaging version 8 to Instant Messaging 8 Update 1, redeployment of client resources fails.
Workaround:
Before you redeploy the client resources, edit the imwebapp.properties file, and set the im_WAR_GENERATE_COMMAND parameter to a valid Java path.

6758197

If the server is reconfigured, the iim.conf file does not retain the previous configuration details.

6768193

The propstore_migraton.conf file does not exist when Instant Messaging is upgraded from version 7.2 to 8 Update 1.

6643628

The Configurator tool does not connect to the Sun Java System Directory Server SSL port number 636.
Workaround:
Manually add the SSL port number as 636 in the iim.conf file.

6672605

The Instant Messaging server takes the property store migration source from the iim.conf file even though the migration options are specified by using the command line.

6677138

The Configurator tool should be able to handle a scenario where Instant Messaging server and web server run as different users.
The Instant Messaging server defaults to running as inetuser and inetgroup. Web server defaults to running as webserverd. In this case, all the Instant Messaging configuration files that are generated by Configurator are readable only by inetuser. The Configurator tool must change the ownership of these files to the web server runtime user, so that they can be read by web applications.

6689151

The init-config utility should provide an option to perform Calendar Agent integration with JMQ, ENS, and None.
The Instant Messaging init-config utility provides the option to configure the Calendar Agent configuration settings. The Instant Messaging configure utility currently assumes that the integration with the Calendar Server uses the ENS (Event Notification Service) mechanism. As JMQ is also an option for notifications, it would be advantageous to provide the ability to configure JMQ during initial configuration.

Hence, the three options JMQ (preferred), ENS (legacy), and None with the defaults values for each mechanism should be provided during configuration.
Workaround:
Do not integrate the calendar agent during initial configuration. After the initial configuration process, manually configure the preferred mechanism, that is, ENS, JMQ, or None in the iim.conf file.

6709951

Deploying client resources fails if there are multiple http listeners.

6498428

The Configurator tool fails if you specify a user ID and a group ID other than root.
If you use any user ID or group ID other than root to install Instant Messaging, the user does not have permission to modify the iim.conf file. In this situation, when you invoke the Configurator tool after installing the Instant Messaging components, the tool fails.
Workaround:
After installing and before starting the Instant Messaging components, manually set permissions for imuser and imgroup. To do this, type the following command:

imuser and imgroup are the user and group that you use to install Instant Messaging.

6444431

The Configurator tool accepts values for Use Assess Manager for Policy and Use Assess Manager for SSO options and succeeds in configuration even when Sun Java System Access Manager is not installed.

6900056

Configuring an alternate (altroot) installation of Instant Messaging server fails.

Instant Messenger Issues

This section contains a list of known issues at the time of release of Instant Messenger 8 Update 2.

Instant Messenger General and Usability Issues

6739173

If the Alert if user status changes option is set for a MSN user, three alert messages are sent to other users when the status of the MSN user changes.

6815865

Status is not getting updated for Yahoo gateway users in the IM client.

6824201

If nick is not set, conference history displays messages from different domains as messages from local domain in a server-to-server setup in the IM client.

6831470

In MSN and Yahoo clients, chat functionality does not work properly with httpbind.

6770412

Status of the AIM users is not updated in the Sun Java System Instant Messaging client.

6766505

Conference history is not displayed in the Instant Messaging client if a user joins the conference before the owner of the conference.

6824299

Conference history does not display all the messages but only those messages from users who have currently joined the conference. This issue is with Sun IM Client only.

6751392

Transport name is not consistent.

6750943

MSN, AIM, and Yahoo Transport users are not shown in roster on a Red Hat Linux platform.

6750250

Entering a conference room with a multibyte nickname sometimes fails.

6649550

A Status Unknown message is displayed when offline users re-login in a server-to-server setup.

6626931

Users with self-JID (Jabber ID) encounter authorization issues in the Instant Messaging client.

6626943

Subscribe news channel displays an org.jabberstudio.jso.JIDFormatException error in a Schema2 hosted domain setup.

6486498

If you send an alert containing an image of a URL and a text message, the recipient receives only the text message.

6576575

The Authorize Contact message is not sent when a user is added from the Alert and Chat windows.

6727849

In a server-to-server installation, the File->Import Contacts option does not work.

Instant Messaging Server Issues

6873349

IM services fail to start after upgrading the OS from Solaris 9 to Solaris 10 Sparc.
Workaround: Perform the following steps to start the services:

  1. Check the status by typing the following command:
  2. If the SMF status is displayed as "maintenance", then execute the following command:

6777818

The following message is displayed when you register a duplicate user to blocked domains:

6869048

Cannot mandate TLS for specific servers when shoal peer discovery is enabled.

6869510

The agent-calendar.iim_server.port parameter gets replaced with iim_server.port after upgrading to IM 8 Update 2.

6821779

File transfer does not work in a public conference if the user rejoins the conference.

6805154

IM client settings window is not displayed in a profile with non-default privacy setting and jid.encoding.compat value set to 'false'.

6794173

Can not create conferences with restricted characters.

6744631

Subscription does not work in a server pool when identity is enabled.

6817064

Re-subscription does not happen as Yahoo users are not getting deleted from the gateway.
Workaround: Delete the users from the Yahoo gateway and then re-subscribe.

6742973

Only users who are recently added to the IM client are synchronized with the Sun Java System Instant Messaging client. Users who are removed from the AIM client are not synchronized.
Workaround:
If a user is deleted in the AIM client, manually delete the user in the Sun Java System Instant Messaging client.

6742857

SMS messages are not delivered if the SMS gateway is enabled on a single peer in a server pool.
Workaround:
Enable the SMS gateway on all peers. For more details about the SMS gateway, see SMS Gateway for Instant Messaging.

6740782

Private conference communication does not work between users who have the same user names but are on different domains.
Workaround:
Users should log in with a different resource and start a chat session.

6739134

Restarting the Instant Messaging services removes the MSN Transport from the Instant Messaging client compelling the user to register again.

6646034

The imadmin assign_services command fails if Instant Messaging interacts with the LDAP server in the SSL mode.
Workaround:
Ensure that the Instant Messaging interacts with the LDAP server in the non-SSL mode. Invoke the assign-services command and change the interaction back to the SSL mode.

6628423

In a server-to-server setup, users that log in through third-party messaging clients are unable to search conferences.

6632080

In a server-to-server setup, users are unable to join the conference rooms on a server that has the TLS (Transport Layer Security) enabled.

6620273

Data migration fails for user IDs that contain uppercase characters.

6724468

Propstore migration does not migrate the vcard-temp.xml file.

6752716

Null pointer exception is seen in the xmppd.log file when a MSN user is deleted from the Sun Java System Instant Messaging roster.

6599164

The Configurator tool should create the im.war and httpbind.war files if the web container used for Instant Messaging is not a supported web container.

Instant Messaging Voice Issues

6678951

Voice chat fails if users do a side chat in a conference.

6768190

If VoIP is enabled, the participant list option in the View menu of the Chat window does not work.

6730494

Voice call will not work if third user joins a voice conference of two users.

6727794

Inconsistent issues with voice chat.

6714770

If you use the Instant Messaging VoIP client to communicate with a remote peer that blocks the UDP (User Datagram Protocol) traffic due to a firewall, the VoIP connection is not established.

6689918

Voice chat does not work correctly on a Sun Ray machine.

6665839

Voice chat status displays as Connected even after the server has shut down.

6723424

User with admin privileges should be able to specify a default port range in the jnlp file.

6705989

In one-to-one conversation, the Voice Chat icon should be enabled by default.

Instant Messaging Administration Issues

6763462

The imadmin assign_services and migratepropstore commands do not work if the primary LDAP server is down.
Workaround:
Restart the primary LDAP server and rerun the imadmin assign_services and migratepropstore commands.

6719455

The ./iwadmin redeploy all command does not redeploy IMPS.
Workaround:
To redeploy IMPS, type the following command:
/opt/SUNWiim/sbin/iwadmin -v redeploy imps

6740272

ACL file behavior is different for identity and file-based policy management.
If the policy is identity, the Manage Conferences and Manage News Channel options are not enabled by default. However, these options are enables by default in file-based ACLs (Access Control List).

Instant Messaging Archive Issues

6738078

The Disabling Archive option does not work during a chat session.

Instant Messaging Interoperability Issues

6621474

Cannot kick the participants from a conference room.

Instant Messaging Performance Issues

6837866

Embryonic session closures are seen at a high load in the following circumstances:

  • When the following load is generated every ten seconds, and when the number of concurrent users is 60,000 or more:
    • 50 users log into server
    • 50 users logout
    • 1450 presence updates
    • 350 messages sent to offline destinations
    • 2400 messages sent to online destinations
    • 850 messages sent to random destinations
    • 50 roster additions
    • 50 roster rename
    • 50 roster removal
  • When there are more than ten chat messages per second across conference rooms
  • When there are too many messages sent to fewer conference rooms

6812313

Messages that are added to group chats or conferences are not deleted upon refreshing the setup.

6837307

Need to configure a separate thread pool for multiplexor to reduce the disk backup of files.
To reduce the number of files written to disk under high load, the following parameters must be added in the iim.conf file:

where
Maxthreads value is the number of multiplexers expected to connect to the server in a particular deployment.

Other Known Issues

6881141

(Inconsistent Issue) Manage Conference window is not displayed when connected through MSN gateway.

No ID

The new URL to download Java Web Start needs to be updated in the following documents.

6866196

Configuration fails when 64-bit JVM is used.
Workaround: Set the JVM value to 32-bit.

6742967

The status of AIM (AOL Instant Messaging) user is always shown as Offline in the Sun Java System Instant Messaging client.

6740263

In IMPS, response to a sent message is displayed as 'successfully completed' even when there is an error in the xmpp side.

6746794

In IMPS, a user in the virtual domain is not able to send messages to the user in the primary domain.

6738075

The Instant Messaging client does not display nicknames that have special characters.

6726738

In IMPS, an incorrect message is displayed when a user joins a conference with the duplicate nickname.

6673225

The imadmin start and imadmin stop commands do not invoke the SMF (Service Management Facility) command to start and stop the server or Multiplexor.
If you require the SMF, disable the SMF by typing the following command:

6671297

SMF does not support multiple Instant Messaging instances.

6641777

Selecting the Stop Moderating option in a conference room does not remove the moderate conference pane.

6635262

Configure parameters are not updated properly when httpbind option is enabled in the Configurator tool.

6726335

In IMPS, a null pointer exception is displayed when a user with a nickname that has a special character leaves a group.

6726347

In IMPS, a mobile phone user is listed twice in the member list when the user leaves and joins the group with different nicknames.

Redistributable Files for Instant Messaging

Sun Java System Instant Messaging software does not contain any files that you can redistribute.

Sun Java System Delegated Administrator 7 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Delegated Administrator 7 including:

About Delegated Administrator 7

Delegated Administrator 7 enables you to provision organizations (domains), users, groups, and resources in an LDAP directory used by Communications Suite applications such as Messaging Server, Calendar Server, and Instant Messaging.

The Delegated Administrator has two user interfaces:

  • A utility (a set of command-line tools) invoked with the commadmin command.
  • A console (a graphical user interface) accessible through a Web browser.

Online help in the Delegated Administrator console describes how administrators can use the GUI to provision users in an LDAP directory.

With Delegated Administrator 7, you can provision users in an LDAP Schema 1 and Schema 2 directories.

For information about configuring and managing Delegated Administrator, see the Sun Java System Delegated Administrator Administration Guide. For a description of the Delegated Administrator commadmin command-line tools, see Delegated Administrator Utility (commadmin) Reference.

What's New in This Release of Delegated Administrator

See the Communications Suite 7 What's New document.

Deprecated and Removed Features for Delegated Administrator 7

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.

Deprecated Platforms: Version 3 of Red Hat Linux (effective in Communications Suite 6)

Support for Communications Suite (including Delegated Administrator) on the following versions of Red Hat Linux has been deprecated and may be removed in a future release:

  • Red Hat Enterprise Linux Advanced Server (32– and 64–bit versions), version 3 (all updates)
  • Red Hat Enterprise Linux Enterprise Server (32– and 64–bit versions), version 3 (all updates)

For information on currently supported versions of Red Hat Linux, see CommSuite:Operating System Requirements.

iPlanet Delegated Administrator (effective in Communications Suite 5)

iPlanet Delegated Administrator has been deprecated in favor of the Communications Suite Delegated Administrator console and utility. Sun Microsystems, Inc. will announce an end-of-life time line for iPlanet Delegated Administrator at a future date.

Note
Although iPlanet Delegated Administrator has been deprecated, the iPlanet Delegated Administrator imadmin user purge command has been updated to be compatible with Messaging Server 6.3. For more information about the updated command, see Purging Users with iPlanet Delegated Administrator and Messaging Server 6.3.

Delegated Administrator Installation Notes

For a detailed steps required to install and configure Delegated Administrator, see “Chapter 2: Planning for Installation and Configuration” in the Sun Java System Delegated Administrator Administration Guide.

Top

ACI Consolidation

For large-scale installations with Access Manager, Messaging Server, and an LDAP Schema 2 directory, you might want to consolidate the Access Control Instructions (ACIs) in your directory.

When you install Access Manager with Messaging Server, a large number of ACIs initially are installed in the directory. Many default ACIs are not needed or used by Messaging Server. You can improve the performance of Directory Server and, consequently, of Messaging Server look-ups, by consolidating and reducing the number of default ACIs in the directory.

For information about how to consolidate and discard unused ACIs, see Consolidating ACIs for Directory Server Performance.

Delegated Administrator Documentation Updates

In this release of Delegated Administrator, Sun Java System Delegated Administrator Administration Guide describes how to enforce unique values for mail attributes when running Directory Server 5.x. This task appears as a “Post-Configuration Task” after you run the Delegated Administrator configuration program.

If you are running Directory Server 6.x, you must follow the procedure described here to enforce unique mail attribute values:

6579843 To enforce the uniqueness of mail attributes when running Directory Server 6.x

Messaging Server uses the following mail attributes to identify a user's email address and alternate email addresses:

  • mail
  • mailAlternateAddress
  • mailEquivalentAddress

Each user's mail attributes should be unique across the directory.

  1. Install the following Directory Server plug-in: 6.1_PR_6573440.

    To install the plug-in, follow the instructions in the plug-in README file.

    The plug-in is available with Directory Server 6.x patches on SunSolve.

    This plug-in provides a hotfix patch to Directory Server to enforce mail attribute uniqueness. Although the plug-in is labeled “6.1”, it applies to other Directory Server 6.x releases such as Directory Server 6.0.
  2. Create the plug-in for Delegated Administrator by using the Directory Server configuration utility, dsconf.

    For example:

    where

    host and port are the host name and port number of the machine where Directory Server is installed

    /opt/SUNWdsee/ds6/lib/uid-plugin.so is an example of the library path where uid-plugin.so is located on Solaris. (For Linux platforms, use the appropriate Linux library path.)

    ugldapbasedn is your root suffix. Uniqueness checking is performed on all entries underneath this suffix.

  3. Enable the plug-in for Delegated Administrator.

    For example:

    For more information about using the dsconf utility to enforce attribute value uniqueness, see the following chapter in the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide: Directory Server Attribute Value Uniqueness.

  4. Restart Directory Server.

Delegated Administrator Compatibility Issues

The following table lists the known incompatibilities between Communications Suite Delegated Administrator 7 and earlier versions.

Incompatibility Impact Comments
Access Manager in Realm Mode (version 7.x style)
Note: Access Manager has two install types: Realm Mode (version 7.x style) and Legacy Mode (version 6.x style). Legacy Mode is the default.
At installation, you must choose Legacy Mode as the install type on the following panel:

Access Manager: Administration (1 of 6)
If the Realm Mode install type of Access Manager is installed, you will not be able to run Delegated Administrator.
Directory Server releases 5.2.4 and earlier The Directory Server feature that enforces unique values for mail attributes is not available with versions earlier than 5.2.4. Solution: Upgrade to Directory Server 5.2.5 or later.

You also can install Directory Server 5.2.4, but you must apply patch 5.2_Patch_4_6313027. For detailed instructions, see Enforce Unique Values for Mail Attributes.

Problems Fixed in This Release of Delegated Administrator (since Communications Suite 5)

This list describes the issues fixed in Delegated Administrator:

6824794

The enabled and disabled values are not translated when you run an Advanced Search.

6825313

The text "App Server 8.x and up" is not translated for all locales.

6693227

Typo in prompt message displayed when you create an Organization by TLA without selecting a service package.

6540281

Missing space in the Organization Online Help page.

6825305

The configurator in French locale contains some doubled apostrophes.

6316832

Small typo in config-commda.

6862081

Default value for mailAutoReplyMode is "echo" instead of "reply" when using DL mode.

6868096

No post-upgrade notification regarding use of damerge command to keep customizations.

6837249

Update post-install instruction to enable IM service.

6825301

Delegated Administrator 7 Online Help is displayed in English even on French environment.

6784367

Cannot add OUA in Organization Properties when logged in as OUA in all locales.

6861629

Setting mail quota values as non-editable in Assign Service Package causes mail step to loop.

6862999

icsCalendar attribute isn't provisioned for new accounts.

6825320

The Help link from the Advanced Search page displays the main Online Help page.

6844640

DA Organization Admin Role ACI has unnecessary single quotes.

6851916

Organization administrator cannot apply user changes after fixing the ACI.

6862983

Missing da.sample.data-dl.ldif file causes config-commda deployment using DL to fail.

6824749

Delegated Administrator 7 Online Help is displayed in English even on Japanese environment.

6824813

In Delegated Administrator 7, some labels are displayed vertically and truncatedly.

6866244

In Delegated Administrator 7, both the 'Service Available' and 'Mail Quota' columns show services when SP for new users is

selected.

6868225

NullPointerException error message is displayed when you try to view or edit large groups.

6607925

Return failure occurs when config-commda fails.

6847020

The rpm --verify sun-commda fails.

6679372

Getting inconsistent results of organization searches for adding icsExtendedDomainPreds in DA console.

6587572

Delegated Administrator creates new mail groups with mgrpBroadcasterPolicy=NO_REQUIREMENTS

6587520

Delegated Administrator creates new users with mailAutoReplyMode=echo

6553328

There is no longer a Manager Field available in the Delegated Administrator tool like the one in iPlanet Delegated Administrator 1.2.

6525830

The Delegated Administrator online help for the Editing Group Properties page incorrectly documents the following UI fields: Add Header Field and Remove Header Field.

6525829

The Delegated Administrator online help incorrectly describes the Message Prefix Text field in the Create New Group wizard and Group Properties page.

6512161

The Delegated Administrator online help incorrectly defines the Attachment Quota value in the Create New Organization wizard and Organization Properties page.

6507859

Delegated Administrator online help erroneously states that you can use “>” and “<” signs when searching for organizations.

6483254

Delegated Administrator online help does not explain that the Login ID must be in ASCII characters.

6454001

Can not display icsExtendedDomainPrefs entry properly on Delegated Administrator console.

6431459

Although IMAPS is enabled for a service package, it shows "IMAP: disabled"

6317850

Attributes passed with the –A option of the commadmin command are ignored if the command also calls an input file containing attributes passed with –A.

6314711

An Organization Administrator (OA) can remove himself as an OA by modifying the organization Properties page.

6218713

Values in the resource.properties files are overwritten when Delegated Administrator is reconfigured with the config-commda program.

5107441

If the first part of the default organization name created in the Delegated Administrator configuration program (config-commda) matches the root suffix name, the organization cannot be created.

4934768

Cannot modify non-ASCII groups.

Known Issues and Limitations in Delegated Administrator

This section describes known issues in Communications Suite Delegated Administrator. The section includes the following topics:

Top

Delegated Administrator Installation, Upgrade, and Configuration Issues

6434047

You cannot upgrade Delegated Administrator from version 2004Q2 to version 7 (the current release) when Access Manager is deployed to an Application Server node agent.

This issue occurs when Delegated Administrator is deployed to Application Server and you upgrade Application Server from version 7 to version 8.x. The asupgrade utility migrates the Application Server 7 server1 instance into the Application Server 8.x server1 target running under a nodeagent. However, asupgrade changes the value of the virtual server from server1 in Application Server 7 to server in Application Server 8.x.

Workaround:

When you run the Delegated Administrator configuration program, config-commda , in the Application Server Preferences panel, specify these values for the target and virtual server:

  • Target: server1
  • Virtual Server: server

6376896, 6294603

Upgrading to Access Manager 7.0 without upgrading Delegated Administrator to version 7 (the current release) will cause user creation to fail.

Note
This issue occurs only if you are currently running Delegated Administrator 6 2005Q1 (Java ES Release 3) or earlier. If you have installed Delegated Administrator version 6 2005Q4 (Java ES Release 4) or have already upgraded Delegated Administrator to version 7, this issue does not occur.

When you upgrade to Java Enterprise System Release 5, if you upgrade Access Manager from version 6.x to 7.0 but do not upgrade Delegated Administrator to version 7, user creation with mail or calendar service will fail.

The recommended way to solve this issue is to upgrade Delegated Administrator to version 7. If you have a compelling reason not to upgrade Delegated Administrator, take the steps described in the following workaround.

Workaround:

  1. Update the UserCalendarService.xml file, located by default in the following directory:

    In the UserCalendarService.xml file, mark the mail, icssubscribed, and icsfirstday attributes as optional instead of required.

  2. In Access Manager, remove the existing xml file by running the amadmin command, as in the following example:
  3. In Access Manager, add the updated xml file, as in the following example:
  4. Restart the Web container.

6310711

The Delegated Administrator configuration program allows you to enter invalid values in the Domain Separator field.

In the configuration program, config-commda, you can enter invalid characters such as ^ in the Domain Separator field. You cannot log into the Delegated Administrator console using a login ID with the invalid domain-separator character.

Workaround: Edit the value of the commadminserver.domainseparator property in the daconfig.properties file, located in the following default path:

Use a valid value such as @, -, or _.

Redeploy the edited daconfig.properties file to the Web container used by the Delegated Administrator console.

Before the change can take effect, you must run the script that deploys the customized daconfig.properties file to your Web container.

For instructions on how to deploy a customized properties file to a particular Web container, see To Deploy a Customized Configuration File in Sun Java System Delegated Administrator Administration Guide.

Top

Delegated Administrator Console and Command-Line Utilities

6760564

In the Delegated Administrator console, the Calendar service Advanced Rights interface is missing the calendar group double-booking option.

When the group calendar account functionality was added in Calendar Server 6.3, a new bit was added to the icsAllowRights LDAP attribute:

bit 15 : allowGroupDoubleBook : "Double booking of group calendars"


The Delegated Administrator console is missing a field to "Allow double booking for new group calendars" by setting bit 15 of the icsAllowedRights attribute. (The Advanced Rights fields are in the Calendar Service section of the Organization Properties page in the Delegated Administrator console.)

Workaround:

Use the commadmin domain create -R or commadmin domain modify -R command to set the advanced rights properties (bits) in the icsAllowRights attribute.

6677194

Local Organization Administrators and Service Provider Administrators can change the disk space quota attribute of their domains when the service package assigned to the domains restricts the disk space quota.

An Organization Administrator can use the Delegated Administrator console to change the value of the Disk Space Quota option for the domain, overriding the service package restrictions.

Workaround: Edit the Security.properties file, as follows:

1. To prohibit an organization administrator from editing the disk space quota field, add the following line to the Security.properties file:

OrganizationAdminRole.UserProperties.MailQuotaValue=NONEDITABLE

For a Service Provider Administrator, add the following line:

ProviderAdminRole.UserProperties.MailQuotaValue=NONEDITABLE

Be sure to update the Security.properties file in the Delegated Administrator configuration directory. For example:

/var/opt/sun/com/da/WEB-INF/classes/com/sun/comm/da/resources/Security.properties

Note: If you are running Communications Suite 5 version of Delegated Administrator 7, the default path on Solaris would be:

/var/opt/SUNWcomm/da/WEB-INF/classes/com/sun/comm/da/resources/Security.properties

2. You also must deploy the updated Security.properties file to the web container's configuration directory. For example, if you have deployed Delegated Administrator to Web Server 7.x, the default path would be:

/var/opt/SUNWwbsvr7/<https-Host_name>/web-app/<Host_name> \
/da/WEB-INF/classes/com/sun/comm/da/resources/Security.properties


3. Restart the web container.

6430018

If service packages are displayed across multiple pages in the Delegated Administrator console, only changes to the last page are saved.

This issue affects three functions:

  • Allocating service packages to an organization.
  • Changing the quantities of service packages allocated to an organization.
  • Removing service packages from the list of service packages allocated to an organization.
    Workaround:

    If the services packages are displayed on multiple pages, click the icon that displays multiple pages pointing to a single page.

    This icon appears above and below the list of service packages. If you place your cursor over the icon, a message says: Show Data in a Single Page.

    You must display all service packages on a single page to save your all of your changes. If the service packages are displayed on multiple pages, only the changes made to service packages on the last page are saved.

6300923

When you add Dynamic members to a group In the Delegated Administrator console, you cannot test a manually constructed LDAP URL.

When you create a new group and add dynamic members to the group, you can either manually construct an LDAP URL or use the fields available in the drop-down menus to construct the LDAP URL. If you use the drop-down menus, you can click the Test LDAP URL button. If you manually construct the LDAP URL, this feature is disabled.

6292610

Using the browser or system controls in the Delegated Administrator console can generate unexpected results.

Workaround: Navigate only by using the built-in Delegated Administrator controls, such as the tabs, buttons, and navigation links provided on the page itself. Do not use browser or system controls, such as your browser's Back button or the Close icon on dialog windows.

6234660

No indication when a User, Organization, or Group list page has finished loading.

If you click a button while a list page is loading, an error occurs.

Workaround: While the page is loading, a message asks you to wait. Do not click any buttons or links until the page is ready.

5094680

The advanced search feature does not return correct results for organizations.

This issue occurs if you perform the following steps:

  1. Select the Advanced Search feature.
  2. Select “Organizations” from the drop-down list.
  3. Click the Match All or Match Any radio button.
  4. Select an organization name from the drop-down list.
  5. Enter valid values in the text field.
  6. Click Search.

Instead of returning only the organizations that match the search criteria, Delegated Administrator displays all organizations.

Workaround: None.

Top

Delegated Administrator Localization and Globalization Issues

This section describes Delegated Administrator localization problems. No localization issue exist for this release.

Top

Delegated Administrator Documentation

This section describes errors or incomplete information in the Delegated Administrator books and online help.

6760559

In the Delegated Administrator console, the Calendar service advanced rights (icsAllowRights) GUI interface can easily be misinterpreted.
This issue is described in the following page: Setting Calendar Server Advanced Rights with Delegated Administrator.

6693218

The Delegated Administrator online help displays the current version as Communications Suite 5 Delegated Administrator instead of Delegated Administrator 7 or Communications Suite 6 Delegated Administrator.

6824749

In Vista, the Delegated Administrator Online Help is displayed in English even when you have set the language to Japanese.

6825301

The Delegated Administrator Online Help is displayed in English even when you have set the language to French.
Workaround: You could modify the URL by changing \en to \fr.

6607494

The Delegated Administrator online help describes nested groups, although nested groups are not supported in Delegated Administrator.

For example, the online help describes how to add a nested group (add a group as a member of an existing group) by choosing from a drop-down menu and searching/selecting a group. These options do not exist in the UI. You cannot added nested groups.

651216

The Delegated Administrator online help incorrectly defines the Attachment Quota value in the Create New Organization wizard and Organization Properties page.

The online help describing the Mail Service Details panel in the Create New Organization wizard and the Mail Service section of the Organization Properties page states that the Attachment Quota field displays the “attachment size per message.” The online help tells the user to enter a maximum attachment quota size in kilobytes. This is incorrect.

The Attachment Quota sets the maximum number of attachments for each email message. For example, setting a value of 2 would allow users to attach no more than two files to a message. The size of each attachment is not affected by this attribute.

Top

Requirements for Delegated Administrator

See Requirements for Communications Suite 7 and Requirements for Delegated Administrator.

This section describes the following platform, client product, and additional software requirements for this release of Delegated Administrator:

Delegated Administrator Operating System Requirements

This release of the Communications Suite products, including Delegated Administrator, is supported on the following platforms:

  • Solaris 10 Operating System (SPARC™ and x86 Platform Editions) including Zones Support
  • Red Hat Enterprise Linux Advanced Server (32– and 64–bit versions), version 4 (all updates) and 5 (all updates)
  • Red Hat Enterprise Linux Enterprise Server (32– and 64–bit versions), version 4 (all updates) and 5 (all updates)
Note
Delegated Administrator is no longer supported on HP-UX or Windows platforms.

For detailed information about Solaris and Linux requirements, including required upgrade patches and kernel versions, see the Sun Java Communications Suite Installation Guide and Sun Java Communications Suite Release Notes .

Sun Java System Software

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

  • Directory Server 5.x or 6
    To enforce unique values for mail attributes, you must install one of these releases:
    • Directory Server 6
    • 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 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.x
  • Directory Server Preparation Tool (Setup script): comm_dssetup.pl version 6.4–4.01
    comm-dssetup.pl version 6.4–4.01 is provided in Communications Suite 6 Update 2.
  • LDAP Schema 1 and 2
    This release of Communications Suite Delegated Administrator is designed for provisioning users in an LDAP Schema 2 directory.

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 the Java Enterprise System components listed in this section, see the Sun Java Enterprise System Installation Guide.

Delegated Administrator Hardware Requirements

The memory and disk space 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.

Supported Browsers for Delegated Administrator

See Client Requirements for more information.

Sun Java System Connector for Microsoft Outlook 7.3 Update 1 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Connector for Microsoft Outlook 7.3 Update 1. 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 Connector for Microsoft Outlook 7.3 Update 1

Sun Java System Connector for Microsoft Outlook enables Outlook to be used as a desktop client with Sun Java Communications Suite.

Connector for Microsoft Outlook is an Outlook plug-in that must be installed on the end-user's desktop. Connector for Microsoft Outlook queries the Sun Java System Messaging Server for folder hierarchies and email messages. It converts the information into Messaging API (MAPI) properties that Outlook can display. Similarly, it uses WCAP to query the Sun Java System Calendar Server for events and tasks which are then converted into MAPI properties. With this model, Sun Java System Connector for Microsoft Outlook builds an end-user Outlook view from three separate information sources: mail from Messaging Server, calendar information from Calendar Server, and contacts from the address book server.

When users create and modify items through Outlook, Connector for Microsoft Outlook passes the new message along to the appropriate server depending on its message type. It sends new outgoing email to an SMTP mail server for delivery, and sends modified email messages back to the user's IMAP folder for storage. New calendar events and tasks are converted into a standard format to be stored in the Calendar Server database.

The address book service makes use of WABP and allows a user to have their personal address book accessible from Outlook, Sun Convergence, and Sun Java System Communications Express.

Note
Please note, the package that is Sun Java System Connector for Microsoft Outlook does not include any migration tools. You need those tools if you have users that are currently on Microsoft Exchange and would like to use Outlook with Sun Java Communications Suite. Sun provides a migration service to help move data and users from an existing Exchange deployment to Sun Java Communications Suite.

What's New in This Release of Connector for Microsoft Outlook

See the What's New document.

Deprecated and Removed Features for Connector for Microsoft Outlook 7.3 Update 1

The following features have been deprecated in Connector for Microsoft Outlook 7.3 Update 1:

  • Support for Microsoft Outlook 2000.
  • Support for Microsoft Outlook 2002/XP.

The following versions have been deprecated in Connector for Microsoft Outlook 7.3 Update 1:

  • Connector for Microsoft Outlook 7.1
  • Connector for Microsoft Outlook 7.2
    Going forward, no new features will be added to Connector for Microsoft Outlook versions 7.1 and 7.2. These versions have been deprecated in favor of Connector for Microsoft Outlook 7.3.

Requirements for Connector for Microsoft Outlook 7.3 Update 1

See Requirements for Communications Suite 6 and Requirements for Connector for Outlook.

Connector for Microsoft Outlook Installation Notes

Connector for Microsoft Outlook is an Outlook plug-in that requires installation on the end users' desktop. A deployment and configuration program is provided to aid the organization in deploying Connector for Microsoft Outlook.

Note
Before you install Sun Java System Connector for Microsoft Outlook, please check the SunSolve website (http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage) for the latest information about any required patches.

The installation and deployment is a three-step process.

Installing Connector for Microsoft Outlook
  1. Install the administrator package.
  2. Create an installation package for the end user.
  3. Deploy the installation package.

    The Connector for Microsoft Outlook packages ships an installer for the administrator package. The system administrator should prepare a special installation package called the Setup Wizard for the end user. The Setup Wizard installs and configures the Connector for Microsoft Outlook software on the end user's desktop. This installation package is designed to simplify and automate the installation process.
    For installation, configuration, and deployment instructions please see the following:

Converting Data

One of the optional steps that can be performed during setup and configuration of Connector for Microsoft Outlook is the conversion of data that resides on the desktop. This conversion process is invoked only if the administrator checks the Convert existing profile option during the creation of the end user installation package. Please note, this conversion process is not intended to, nor does it replace the need for server-based migration. Sun provides a migration service to help move data and users from an existing Exchange deployment to Sun Java Communications Suite.

LDAP Attributes

In order for Connector for Microsoft Outlook to function correctly, the following LDAP attributes in the Sun Java System Directory Server should be indexed for at least presence and equality to improve the overall performance:

  • icsCalendar
  • mail
  • mailalternateaddress

For more information on these attributes, see the Sun Java System Calendar Server 6.3 Administration Guide and the Sun Java System Messaging Server 6.3 Administration Guide.

Connector for Microsoft Outlook Compatibility Issues

Please refer to the following Technical Notes for information about compatibility issues with Connector for Microsoft Outlook and other products or applications:

Problems Fixed in This Release of Connector for Microsoft Outlook

From the README:

Fixed in most recent release

6551080 SERVER: Not able to add members of default contact folder into DL of shared non def contact folder
6777256 Outlook/Connector displays HTML enclosures as file type based on "Content-description:"
6780464 Yearly recurring events created thru  thunderbird, doesn't appear in Outlook
6785155 OC7.2.409: Buildup of backslashes in the CN(with special chars)of meeting attendees with each update
6785111 Unable to install OC 7.2.409 with Outlook 2007 after upgrading from Outlook 2003
6795339 Cannot add members from a shared addressbook into local DL
6815370 Incorrect behavior of radio buttons in Address Book tab in deployment program
6815407 Need to remove the ability to upload attachments in events

Fixed in -01

6189748 Multiple Junk Email folders created...
6430419 Default calendar's description not synced both ways.
6513268 product name should be in English
6535251 OL2k7:Events disappear on modifying one occurence of recurring appointment with attachments
6542799 Time zone mapping fails without explanation
6633416 Modification of appointment with attachment in OL is not synchronizing with SJCS
6635311 OL2K7:Modifying an appointment is not allowing to dismiss reminder when performing context switch
6646790 Outlook connector to use Sieve for Mail filters support, using IWC protocol
6646791 Outlook connector to implement its own UI for Out-of-Office functionality.
6647748 OC should sync all contacts folders
6649958 Pop ups unlocalized wrong message when try to create a Daily Recurrence Appointment in Outlook
6651684 For meeting,timings changed from uwc is reverted to orig time on opening orig OL invtn in attn inbox
6660487 Outlook Connector does not display imap quota warnings
6664699 IP: Bi-Weekly recurring appointment created in thunderbird is not showing in outlook
6675233 Meeting created for user with no invite perms when large number of attendees included in invitation
6675448 Service tag utility should be bundled with SJOC installer.
6676493 Popup reminders cannot be dismissed in Outlook 2003 SP3 for a recurrence appointment with attachment
6687213 OL2k7: Inconsistency during never ending recurring meeting.
6690282 Sun Java System Outlook Connector:  Adding Ownership of Shared Calendars
6692691 OL2K7:LDAP Group attendee cannot able to accept/decline meeting from inbox
6695468 l10n-de-Garbeled characters in Configurator and OL OLH's menu
6696126 OC7.3 - Incorrect link to next/previous in OLH page (French)
6698018 UI message not localised when selecting mail host server manually
6698672 OC: When accepting invitation, outlook sent an irritating response
6701410 param to configure "Expunge On Delete" via package.ini
6707394 Default Address books's description does not sync both ways
6708898 Outlook connector should display contact's photograph
6713167 Untranslated strings in Outlook Connector
6722312 Syntax error in line 30 of package.bat of OC Deployment Configuration Program
6725851 Changed time duration for "All Day Event" is getting reset after a context switch.
6730445 Subscribed default mail folder is not viewable.
6730989 Outlook crashes on uuencoded message with fix for bug 6575029
6731090 Vista: Performing empty/resync always displays wrong message
6732658 OutlookConnector: Resource is not present in Outlook
6733107 OL2k3:In attendee's calendar non ending recurring meeting will b created instead of reccurren bound
6738017 Default ABS settings URL should be changed to IWC
6744364 OC/able to send an invitation to user for whom you do not have permission to
6745139 wrongly sharing mail folders in a hosted domain setup
6750670 SERVER: Not able to delete Non default contact folder with contacts in it when using Convergence ABS
6750758 Problem with deletion of multiple emails from Outlook virtual folders
6751883 Timed event gets converted to an ALL day event on context switch
6759169 Recurring meeting request disappears from organizers calendar when attendee modifies each occurrance
6767202 IP:Unable to delete the non default calendar created in UWC from OL.
6768215 Doc: Release notes URL should be updated with the correct version in README .
6768555 Incorrect error message when trying to install OC on a machine that does not have Outlook installed
6773476 in attende's calendar , reply Time for an event is lost on doing empty -resync
6775539 After accepting meeting, info bar displays the meeting is accepted by organizer and not by attendee
6776138 IP: Monthly recurring event created in Thunderbird does not appear in OL

Known Limitations and Issues in Connector for Microsoft Outlook

This section describes the limitations and known issues that exist in this release of Sun Java System Connector for Microsoft Outlook.

Limitations in Connector for Microsoft Outlook

Some limitations exist in this release of Sun Java System Connector for Microsoft Outlook. The key limitations are:

  • Every distinct identity in the Directory Server (for example, users, resources, conference rooms) must have an email address.
  • Rich text in the appointment and meeting description field is lost once the same calendar event is modified in the Communications Express client.
  • Message recall functionality is not available.
  • Description of events is not available when checking availability.
  • Free/Busy lookup does not display TENTATIVE or OUT-OF-OFFICE color coding.
  • The properties for Sun Java System Connector for Microsoft Outlook cannot be modified using the Tools→Services option from the Outlook menu. To modify the properties:
    1. Exit Outlook.
    2. Right click the Outlook icon and select Properties.
      The Properties dialog appears.
    3. Select Folders - < your user name>from the list of services.
    4. Click Properties.
  • Free/busy lookup using SSL is not supported.
  • Installing Sun Java System Connector for Microsoft Outlook on Exchange servers is not supported.
  • Recurring tasks are not supported.
  • Offline limitations:
    • During an offline session, if any item in a Calendar, Task, mail, or Contact folder is modified using Outlook, and then another client on the server is used to modify the same item, the changes made offline are lost when the user returns to online mode in Outlook. The changes made by the other client on the server remain.
    • When creating a new event in offline mode, the invitation is saved to the user's Outbox. If, while still in offline mode, the user opens the invitation, the invitation disappears from the Outbox once it is closed.
  • Junk Mail Filter does not work for Outlook 2003 and Outlook 2007.
    The Junk Email feature available in Outlook 2003 and Outlook 2007 (select Tools→Option) does not function with Connector for Microsoft Outlook. Senders that are set to be filtered using this tool are not filtered.
    Because Outlook's Junk Email feature relies on the client to filter unwanted messages, Sun recommends using a server-side solution. In client filters, like the one Outlook utilizes, the messages arrive in the user's Inbox, which is then moved to the Junk folder. This could potentially create unnecessary network traffic and slower response time.
    Users may use the Tools→Mail Filter option, which utilizes the server-side filtering function. A more efficient solution would be to use a server-side virus or junk mail filter that is compatible with Sun Java System Messaging Server. Unsolicited email may be rejected at the MTA (message transfer agent) level and never arrive in the user's Inbox, saving resources and disk space. For a list of third-party partners, see http://www.sun.com/software/products/communications/partner&#95;library/index.xml

Known Issues in Connector for Microsoft Outlook

This section describes the known issues at the time of this release of Sun Java System Connector for Microsoft Outlook. If known, IDs are included in parentheses.
The categories of issues discussed in this section are:

General Issues in Connector for Microsoft Outlook

No ID

Mail Quota and Folder Size dialog and documentation are not localized.

6550994 and 6766033

Non Default Contacts Folder Not Getting Deleted in Communications Express and Convergence
Workaround: Delete the contacts folder from the Deleted Items list in addition to deleting it from Outlook.

6689448

Close button on Mail Filters Page Does Not Work in Mozilla Firefox
Workaround: If the Close button on Mail Filters page or on the Out of Office Message page does not work in Mozilla Firefox browser, go to the Program Files\Mozilla Firefox\greprefs folder. Edit the all.js file by setting the value of the dom.allow_scripts_to_close_windows preference to true.

6570441

Vista: Not able to create user profile using silent installation
Workaround: Able to proceed with silent installation after enabling hidden administrator. With Administrator account, this issue is not reproducible. This is Windows Vista specific. This behavior is not seen in other flavors of Windows.

Steps to enable default administrator account in Vista:

  1. Run the command compmgmt.msc.
  2. Select Local Users and Groups from Left side Tree View.
  3. Select Users. This will show all the users present on the machine.
  4. Right click on "Administrator".
  5. Click properties. Administrator Properties dialog box will be displayed.
  6. Clear the option "Account is Disabled".(By default, this option is selected so the administrator account is disabled).

6604704

Outlook 2007: Not able to create profile using installation package
When you run the installation package to create a new profile, you get the following error and the profile is not created.

"Outlook is not installed on this machine. Please install Outlook 2000 with the Office 2000 Service Pack 3 or Outlook 2002 with the Office XP Service Pack 2, and then run this program again."
Issue is because of the missing registry sub-key.
HKEY_CLASSES_ROOT\Outlook.Application

You may experience this issue if you install a Microsoft Office 2003 program after the 2007 Microsoft Office system is installed. For example, you experience this issue in the following scenario:

  1. You install the 2007 Office system.
  2. You modify the 2007 Office system installation to remove Microsoft Office Word 2007.
  3. You install Microsoft Office Word 2003.


Workaround:

  1. Exit all 2007 Office programs.
  2. Click Start, click Run, enter appwiz.cpl in the Open box, and then click OK.
  3. In the Add or Remove Programs dialog box, click Microsoft Office Version 2007, and then click Change.
  4. In the Microsoft Office Version 2007 dialog box, click Repair, and then click Continue.

For other details see:
http://support.microsoft.com/kb/930010

Note
Outlook 2000 and Outlook XP/2002 are not supported.

Installation and Upgrade Issues in Connector for Microsoft Outlook

4930092

Unauthenticated Shared Drive Path Displays Warning.
For fields requiring a shared drive path, or UNC (Universal Naming Convention) be entered (for example, the shared path to the location for Microsoft Web Publishing Wizard on the Processes Tab of the Deployment Configuration Program), a validation warning is displayed that states the path does not exist if the user is not authenticated for the specified shared drive.
Workaround: The specified shared drive should be accessible by anonymous authentication, allowing anybody to access the shared drive.

No ID

Upgrade defaults to previous servers and ports.
When upgrading from the Connector for Microsoft Outlook 6 2004Q2 version to the Connector for Microsoft Outlook 7.2 version, if the server names and port numbers have changed, the upgrade only takes into consideration the old server names and port numbers.
Workaround: None.

Calendar Issues in Connector for Microsoft Outlook

The following issues relate the calendar portion of Sun Java System Connector for Microsoft Outlook:

6589461

Outlook 2007 Cannot Open the Internet Calendar (.ics) File When a Nondefault Calendar Is Shared Through Email.
When you open an Internet Calendar email attachment in Outlook 2007, for example, Sample.ics, the following error message is displayed:

Workaround: Perform the following steps:

  1. Save the Sample.ics file from your email on your desktop.
  2. From Outlook Connector File menu, select Import and Export.
  3. Select the Import an iCalendar (.ics) or vCalendar file (.vcs) option from the actions list and click Next.
  4. Click the Sample.ics file that you have saved on your desktop.
    The Do you want to open this calendar as a new calendar or import its items into your calendar? dialog box appears.
  5. Click Import.
    The contents of the Internet Calendar file are imported to the default calendar folder.

6595737

When a Resource is Double Booked, Outlook Incorrectly Shows The Second Event as Created.
When a resource is booked for two recurring events in the same time slot, and the first instance of the recurring event is deleted, the event is not created in the Calendar Server. However, Outlook 2003 displays the event in the calendar.
The following error message is displayed:


Workaround: None.

6835766

Need to Specify Minimum Version of mapi32.dll.
When you try to install Outlook Connector on a machine that has Groupwise installed, the following error message is displayed:


Workaround: If you have Groupwise installed in your system prior to installing Outlook Connector, you must replace the existing mapi32.dll with the latest one from another machine that has the same Outlook version.

6823613

Attachment Icon is Not Displayed in Outlook 2003
When a calendar event with attachment is created in Outlook 2003, the attachment icon is not displayed.
Workaround: None.

5104189

Creating a new calendar profile brings up the old calendar reminders.
When logging in for the first time to a newly created calendar profile in Outlook that is set to your default Calendar Server, Outlook alarms pop up for old events as well as for future events. This applies only for recurring events where the entire series does not take place in the past.
Workaround: None.

6190293

Names of subscribed calendars not visible in Calendar view.
When you first subscribe to a calendar, the calendar name is labeled as "Calendar", not the name of the subscribed calendar.
Workaround:
To see the name of the subscribed calendar, log off Outlook and then log back into Outlook. The subscribed calendar's name should be displayed.

6292026

Opening a shared calendar link does not hook into subscription (Outlook 2003).
In Outlook 2003, clicking the calendar icon at the bottom of the left pane, displays the calendar view. Within that calendar view, clicking "Open a Shared Calendar" displays a dialog that allows the user to enter the user name of a shared calendar. When the user name of a known shared calendar is entered, the error "Unable to display the folder. Your profile is not configured to support this operation for this user." is displayed. This occurs also with contacts and tasks.
Workaround:
To view a shared calendar, select the shared calendar folder in the folders list.

6409671

Unable to remove attachment from an instance of a recurring event.
If a user creates a recurring event that includes an attachment, then attempts to remove the attachment from a single instance of the recurring event, the attachment is not deleted because an attachment usually gets created for a series and not for a single occurrence.
Workaround: None.

No ID

The following are additional issues related to the calendar portion of Connector for Microsoft Outlook that do not have IDs:

If delegate accepts or declines an invitation from the organizer's Shared Inbox, the calendar event is added to delegate's calendar, but not to the organizer's calendar.

  • Microsoft TNEF messages are sent when sending calendar attachments. iTIP and iMIP calendar attachments are not supported.
  • All Day events may become a non-All Day events (one event scheduled from 12:00am until 12:00pm) if the desktop time zone is different from the Calendar Server calendar time zone.
  • Changing permissions of a calendar requires restarting Outlook for the new permission setting to take effect for the Calendar folder in the Shared Calendar.
  • Tasks displayed in Shared Calendars are the login user's tasks, not the subscribed user's tasks. The calendar view always shows the login user's tasks.
  • If you create a recurring invitation in Outlook, but delete a single instance of that event, the recipients (attendees) will not see the deleted invitation if Calendar Server has not processed the initial recurring invitation before the deletion.

Mail Issues in Connector for Microsoft Outlook

The following issues relate the mail portion of Sun Java System Connector for Microsoft Outlook only:

2142968 and 6482360

Message recall does not work.
When a sender attempts to recall a message that was sent, the recall attempt fails. The recalled message is not deleted from the receiver's mailbox.
Workaround: None

Address Book Issues in Connector for Microsoft Outlook

The following issues relate to the Address Book portion of the Sun Java System Connector for Microsoft Outlook.

6225049

Deleting a contact from Communications Express does not delete it from Outlook.
The Communications Express configuration parameter delete_perm in the db_config.properties file needs to be set to false in order for Outlook to capture contact entries which have been deleted from Communications Express. The entry should be:
delete_perm=false
The default is true. The entry can be found at /var/opt/SUNWuwc/WEB-INF/config/ldapstore/db_config.properties .
Workaround: Manually fix the entry.

6752539

Cannot Delete a Contact Photo from Outlook Connector
When you right-click the contact photo and select Remove Picture, the photo is not deleted from the contact.
Workaround: None.

6228253

Login to Address Book Server Through Outlook Fails When Address Book is in SSL Mode.
Workaround:
Open Communications Express or Convergence (depending on which address book server you have configured your profile) in Internet Explorer and permanently accept the self-signed certificate.

6267180

Shared contact does not get removed from Address Book after you have unsubscribed.
After you have unsubscribed to a shared contact, it is not removed from the "Show Names from the" list of the Address Book.
Workaround: There are two workarounds:

  • If the subscribed contact has been added to the "Show Names from the" list of the Address Book," you should clear the "Show this folder as an email Address Book" option from the "Outlook Address Book" property page before you unsubscribe from the contact.
  • Remove the contact directly from the address book properties.
    In Outlook 2003:
    Select Tools > Email accounts.
    Choose "View or Change Existing Directories or Address Books" and select "Outlook Address Book" to change.
    Select the item to remove from your address book.
    In Outlook 2007:
    Select Select Tools > Account Settings.
    Click on Address Books.
    Select "Outlook Address Book" from the list of services set up in your profile.
    The Microsoft Outlook Address Book properties window is displayed.
    Select the item to remove from your address book and click Close.
    Note that user must logout and login again for the change to reflect.

Localization Issues for Connector for Microsoft Outlook

The following issues affect the localized versions of Sun Java System Connector for Microsoft Outlook:

6767897

Cancel Button in the Edit Filter Window Does Not Work in the French Locale
In the French locale, when you click Cancel in the Edit Filter window, the Cancel button does not work.
Workaround: Click the Close button to cancel the Edit operation.

6648138

English Names Are Displayed For IMAP Folders in French Locale
In the French locale, when you create a profile with Communications Express or Microsoft Outlook style folder mappings, folders such as Deleted Items, Sent Items, and Drafts are displayed in English. Only the Inbox folder name is displayed correctly.
Workaround: None.

6777127

Help Button Does Not Work in Korean Locale
In Korean locale, when you click the Help button from Out of Office Message or Mail Filters window, the Help page is not displayed.
Workaround: To view the Help, go to the following location and click the required topic from the contents:

6306873

Cannot Enter Non-ASCII Characters In The Full Name Field In The Install Wizard in Korean Locale
In the Korean Install wizard, when you enter non-ASCII characters in the Full Name field, the characters are displayed incorrectly.
Workaround: None.

6767893

Deplacer vers le haut (Move Up) Button in the Mail Filters Page is Not Displayed Correctly in French Locale
Workaround: None.

6672540

Multibyte Shared Calendar Name is Displayed as Question Marks
When you subscribe and query the multibyte shared calendar of another user, the calendar name is displayed as question marks.
Workaround: None.

6313321

Cannot convert IMAP profile name in Japanese.
If an IMAP profile already exists, and this profile has never been used by Outlook, the conversion fails.
Workaround: None.

6541324

After Deploying Outlook Connector in Traditional Chinese, Folder Names in Outlook 2007 Do Not Display Correctly
When you install Outlook Connector on a machine running Windows 2003 with Outlook 2007, the folder names are garbled.
Workaround: None.

6742345

Message Received in Simplified Chinese With HZ Encoding Is Garbled
When you send a message in Simplified Chinese with HZ encoding, the message is garbled on receipt.
Workaround: Choose from the following outgoing message encoding options:

  • Plain Text format – GB2312 or GB18030 combination
  • HTML or RTF format – any combination

Communications Express Interoperability Issues for Connector for Microsoft Outlook

The following issues relate to the interoperability between Sun Java System Connector for Microsoft Outlook and Sun Java System Communications Express:

6752413

Contact Folder Named "Calendar" Created in Communications Express Replaces the Default Calendar in Outlook Connector
When you create a contact folder named "Calendar" (case-sensitive) in Communications Express, it replaces the default calendar folder in Outlook Connector. Thus, all data in the calendar folder is lost.
Workaround: None.

4949659

Address Change in From: header
The name in the From: header changes if an attendee replies to an event invitation and attaches the winmail.dat calendar invitation. For example, Joe (using Outlook) sends an invitation to an event to Bob. Bob replies to Joe, using an email client that automatically sends the original winmail.dat calendar attachment back to Joe. When Joe opens the reply, the From: header is changed to Joe.
Workaround: None.

4969029

Email ID is a must for Outlook.
If a person with a calendar ID but no email ID is invited to an event in Communications Express, this person is not displayed as an attendee in Outlook. An email ID is required for Outlook.
Workaround: None.

5032872

When you unsubscribe, the calendar does not get removed from the folder list.
If you subscribe to or unsubscribe from a calendar in Communications Express, the information is updated in Outlook only after Outlook has been restarted. Additionally, if the LDAP configured for lookup is a replica, the subscription list is not updated until the replica is updated.
Workaround: None.

6175103

Error generated when Outlook synchronizes with server.
If a task is created (either in Outlook or Communications Express) while Outlook is synced with the server, then the task is deleted and the user attempts to switch to the Tasks folder in Outlook, an "Unable to display all cells due to low memory" error is generated.
Workaround: Switch to another folder and then back again to the Tasks folder.

6229276

Configuration parameter needs to be set in order for address book server contacts to be properly synchronized.
Workaround: The Communications Express configuration parameter delete_perm in the db_config.properties file needs to be set to false in order for Outlook to capture contact entries which have been deleted from Communications Express. The entry should be:
delete_perm=false
The default is true. The entry can be found at /var/opt/SUNWuwc/WEB-INF/config/ldapstore/db_config.properties .

6351914

Limitations in calendar alarms.
Because of the difference in how Outlook and Communications Express handle alarms and reminders, changes in one interface are not reflected in the other. Outlook utilizes pop-up windows as alarms, while Communications Express (Calendar Server) sends email reminders. In order to not replicate alarms when both interfaces are used (having both a pop-up and email reminder sent), Connector for Microsoft Outlook allows alarm synchronization upon creation of events in a single direction only. For example, when a new event is created using Communications Express, the alarm is copied to the Outlook event (as a pop-up). But when creating an Outlook event, the alarm is not set on the server.
Workaround: To allow the synchronization to work from Outlook to Communications Express, a registry value can be set in outlook: HKEY_CURRENT_USER\Software\Sun Microsystems\Outlook Connector\Sync Cal To turn this on, set the value to 1, and to turn it off, set the value to 0 (or remove the key. Note that setting the registry value will only have effect when creating new events. Modifying existing events only affects the alarm type associated with the client performing the modification.

No ID

The following are additional issues related to Communications Express interoperability that do not have IDs:

  • RTF formatting in Outlook is not preserved if the description text is edited using Communications Express.
  • Differences exist in privacy classes between Outlook and Communications Express.
    Outlook has two privacy classes (Private and Public), while Communications Express has three classes (private, Date and Time only, and Public). In Outlook, a private event is created as a "Date and Time only" event in Communications Express. A public event in Outlook maps to the public event in Communications Express. Similarly, a Communications Express "Date and Time Only" event maps as a private event in Outlook, and a public event maps as a public event in Outlook. A Communications Express private event also maps to Outlook as a private event. To create a private event in Outlook so it appears as a private event in Communications Express, select "Free" from the "Show time as:" field. The Communications Express private event cannot be seen in a shared Calendar folder by another user.
  • There are differences in the way free/busy is implemented in Outlook and Communications Express.
    The default private event is free in Communications Express. If the event is to be included for free/busy lookup, then it should manually be set to busy. In Outlook the default events are busy for both private and public events.
  • If you export an event from Communications Express to a file in Outlook format, you cannot import the event from the same file into Outlook.
  • Incompatibilities exist in how recurring tasks are implemented in Outlook and Communications Express.
    Recurring tasks in Outlook do not conform to RFC 2445 while Communications Express is specifically designed to work with RFC 2445-compliant information. This causes problems when recurring task information is passed between Outlook and Calendar Server.
    Information stored locally by Outlook does not always match information which is stored on the Calendar Server. Sun Java System Connector for Microsoft Outlook, for example, does not transfer any information dealing with the recurrence of a task to the Calendar Server. Any tasks created in Outlook (recurring or non-recurring) appears in Communications Express as single tasks. A task that is created in Communications Express only uses the recurring information from the Calendar Server when that task is written for the first time in the Outlook client and not during any modification of any existing task on Outlook.
    For these reasons, recurring tasks viewed in Outlook and tasks viewed in Communications Express appear different in many cases. We recommend that users who work with recurring tasks choose either Outlook or Communications Express and not attempt to work with recurring tasks in both clients interchangeably.
  • If a message is sent from Outlook in Rich Text format, the message contains a plain text body with no formatting and a WINMAIL.DAT attachment.
    The WINMAIL.DAT attachment contains the Rich Text message along with any other attachments that may have been added. Because the format is Microsoft proprietary, only Outlook can read the WINMAIL.DAT attachment. Communications Express (and any other client) sees only the unformatted text message and a WINMAIL.DAT attachment. It is recommended that HTML format be used instead of Rich Text format to send messages.
  • If contacts groups in Outlook contain external SMTP mail recipients or other contacts groups, they are not seen by Communications Express.
    Communications Express and Convergence cannot send mail to these recipients.
  • Communications Express and Convergence cannot decode and display Microsoft TNEF format.
    Outlook saves calendar events and tasks (any calendar folder not under the Calendar folder tree), contacts (any contacts folder not under the Contacts folder tree), notes, and journals in the Messaging Server. Because the data is saved as Microsoft TNEF format, Communications Express and Convergence cannot decode and correctly display them.

Microsoft Exchange Interoperability Issues

The following issues relate to the interoperability between Sun Java System Connector for Microsoft Outlook and Microsoft Exchange:

6174201

Free Busy Proxy for Exchange does not return complete Free/Busy information.
Workaround: None.

6255190

Cannot recover deleted items.
After selecting "Empty Deleted Items Folder," Connector for Microsoft Outlook does not allow for recovery of deleted items.
Workaround: None.

No ID

Receipt of a message with embedded OLE objects and HTML in RTF from Exchange (versions 5.5, 2000, and 2003) to Connector for Microsoft Outlook does not work.
Workaround: None.

Microsoft Outlook Issues

The following are issues with Microsoft Outlook:

Note
These issues are general issues with Microsoft Outlook, and are not specific issues with Connector for Microsoft Outlook.

6365369

Limitations for non-default calendars.
Limitations exist when attempting to perform operations on a non-default calendar with Outlook:

  • Free/Busy information is not displayed.
  • Reminders cannot be set on an event.
  • Attendee responses to invitations from non-default calendars are not tallied.
    Workaround: None.

Redistributable Files for Connector for Microsoft Outlook

Connector for Microsoft Outlook does not use any redistributable files.

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


Copyright © 2012, 2013 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/).

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.