Sun Java Communications Suite 5 Release Notes

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

Version 5

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

The most up-to-date version of these release notes can be found at http://docs.sun.com/coll/1634.1. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.

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.


Sun Java Communications Suite Release Notes Revision History

Table 1–1 Sun Java Communications Suite Revision History

Date 

Description of Changes 

August 2007 

Updated Messaging Server Release Notes with announcement of Sun Cluster 3.2 support with Messaging Server. 

July 2007 

Updated supported browser version requirements in Communications Express and Delegated Administrator Release Notes. 

April 27, 2007 

Updated Calendar Server and Communications Express Release Notes. 

April 2007 

Calendar Server release notes added one bug, 6542989. 

March 2007 

Revenue Release of Sun Java Communications Suite, Version 5 

September 2006 

Initial draft of these release notes (Version 5) 

About Sun Java Communications Suite, Version 5

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

Locating Patches for Sun Java Communications Suite Products

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

Table 1–2 Patch Keywords for Communications Suite Products

Product 

Keyword 

Calendar Server 

“Calendar Server” 

Communications Express 

“communications express” 

Delegated Administrator 

commcli 

Dssetup 

comm_dssetup 

Instant Messaging 

“Instant Messaging” 

Messaging Server 

“Messaging Server” 

Connector for Microsoft Outlook 

“Outlook Connector” 


Note –

The double quotes should be used in order to search for the string including the space.


To search for patches for all the Java Enterprise System products, use the keyword Java_ES.

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

This section describes new features and changes to Sun Java Communications Suite 5.

Support For Red Hat Linux

Support for Sun Java Communications Suite on the following versions of Red Hat Linux has been deprecated and may be removed in a future release:

For information on currently supported versions of Red Hat Linux, see Calendar Server Operating System Requirements, Messaging Server Operating System Requirements, Requirements for Instant Messaging, Delegated Administrator Operating System Requirements, and Communications Express Operating System Requirements for the specific Sun Java Communications Suite component product.

Change in Availability of Sun Java Communications Suite Products

Beginning with this release of Sun Java Communications Suite 5, communications products are being removed from the Sun Java Enterprise System entitlement. Communications products are available as part of the Sun Java Communications Suite or as individual products. Communications products will no longer be installed through the Java Enterprise System installer. Communications product components continue to interoperate with Java Enterprise System components.

This change in entitlement does not affect the communications products in Java Enterprise System 2005Q4. If you have communication products installed, no change will occur to your entitlement.

Sun JavaTM Enterprise System Monitoring Framework

This release of Sun Java Communications Suite supports version 2.0 of the monitoring framework. This monitoring framework provides information on the length of time for authentication, message delivery, the number of instant messages sent through the service, and other statistics.

For information on the Sun JavaTM Enterprise System Monitoring Framework, see: Sun Java Enterprise System 5 Monitoring Guide.

Platform Support for Sun Java Communications Suite Server Products

The server component products of Sun Java Communications Suite are no longer supported on HP-UX or Windows platforms.

Sun Java Communications Suite Installation and Upgrade Notes

Sun Java System Portal Server Installation

Sun Java System Portal Server is not installed with Sun Java System Sun Java Communications Suite 5. To install Portal Server, please refer to Sun Java Enterprise System 5 Installation Guide for UNIX.

Java Enterprise System 5 Beta Installation

If you have installed the earlier (Beta) version of Java Enterprise System, you need to remove the SUNWldapcsdk-tools package prior to installing the released (RR) version of JES 5. This is due to the change in location of the SUNWldapcsdk-tools package in the released version. If you do not remove this package and try to start up Calendar Server or Messaging server after installing the released version, you will get the error message:


Could not find .../bin/ldapsearch utility
Please install the ldapcsdk-tools package

This error message is due to the change in the location of LDAP tools.

Two workarounds exist:

Default Installation Directories and Ports

This section lists the product component installation directories and port numbers that the Sun JavaSystem Communications Suite 5 installer uses by default.

Default Installation Directories

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:


Note –

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


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

Table 1–3 Default Installation Directories

Label and State File Parameter 

Default Directory 

Comment 

Access Manager 

CMN_IS_INSTALLDIR

Solaris OS: /opt/SUNWam

Linux: /opt/sun/identity

 

Application Server 

CMN_AS_INSTALLDIR

Solaris OS: /opt/SUNWappserver/appserver

Linux: /opt/sun/appserver

Contains Application Server utilities, executables, and libraries. 

Application Server Domains 

CMN_AS_DOMAINSDIR

Solaris OS: 

/var/opt/SUNWappserver/domains

Linux: 

/var/opt/sun/appserver/domains

Default area under which administrative domains are created. 

Calendar Server 

CMN_CS_INSTALLDIR

Solaris OS: /opt/SUNWics5

Linux: /opt/sun/calendar

 

Communications Express 

CMN_UWC_INSTALLDIR

Solaris OS: /opt/SUNWuwc

Linux: /opt/sun/uwc

 

Delegated Administrator

CMN_COMMDA_INSTALLDIR

Solaris OS: /opt/SUNWcomm

Linux: /opt/sun/comms/commcli

 

Directory Preparation Tool

CMN_DSSETUP_INSTALLDIR

Solaris OS: /opt/SUNWcomds

Linux: /opt/sun/comms/dssetup

 

Directory Server Core 

DSEE_BASE

Solaris OS: /opt/SUNWdsee/ds6

Linux: /opt/sun/ds6

Separately located subcomponents of Directory Server EE include Directory Server Core, Directory Service Control Center, and Directory Proxy Server. 

Directory Service Control Center

DSEE_BASE

Solaris OS: /opt/SUNWdsee/dscc

Linux: /opt/sun/dscc

 

Directory Proxy Server 

DSEE_BASE

Solaris OS: /opt/SUNWdsee/dps

Linux and HP-UX: /opt/sun/dps

 

Directory Server Instance Directory 

DSEE_INSTANCE_DIR

Solaris OS: /var/opt/SUNWdsee/dsins1

Linux: /var/opt/sun/dsins1

 

HADB

CMN_HADB_INSTALLDIR

Solaris OS: /opt/SUNWhadb

Linux: /opt/SUNWhadb

HADB install locations are not relocatable in Communications Suite installation. 

Solaris OS: /var/opt/SUNWhadb

Linux: /var/opt/SUNWhadb

HADB Repository Data and Log location. 

Solaris OS: /etc/opt/SUNWhadb

Linux: /etc/opt/SUNWhadb

HADB Management Agent Config File 

Solaris OS: /etc/init.d/ma-initd

Linux: /etc/init.d/ma-initd

HADB Management Agent Startup Script 

Instant Messaging

CMN_IIM_INSTALLDIR

Solaris OS: /opt

Linux: /opt/sun

 

Instant Messaging Resource Directory 

CMN_IIM_DOCSDIR

Solaris OS: /opt/SUNWiim/html

Linux: /opt/sun/im/html

 

Instant Messaging Online Help Directory 

CMN_IIM_DOCSHELPDIR

Solaris OS: /opt/SUNWiim/html/en/imhelp

Linux: /opt/sun/im/html/en/imhelp

 

Message Queue 

You cannot change the installation directories, so there is no field 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

Linux: 

/opt/sun/mq

/etc/opt/sun/mq

/var/opt/sun/mq

Messaging Server 

CMN_MS_INSTALLDIR

Solaris OS: /opt/SUNWmsgsr

Linux: /opt/sun/messaging

 

Monitoring Console

CMN_MC_INSTALLDIR

Solaris OS: /opt/SUNWjesmc

Linux: /opt/sun/jesmc

 

Sun Cluster 

You cannot change the installation directories, so there is no field in the installer or parameter in the state file. 

Not applicable 

Sun Cluster software is installed in the following locations on Solaris OS: 

/

/usr/opt

/usr/cluster

Web Server 

CMN_WS_INSTALLDIR

Solaris OS: /opt/SUNWwbsvr7

Linux: /opt/sun/webserver7

 

Web Server Instance Directory 

CMN_WS_INSTANCEDIR

Solaris OS: /var/opt/SUNWwbsvr7

Linux: /var/opt/sun/webserver7

 

Web Proxy Server

CMN_WPS_INSTALLDIR

Solaris OS: /opt/SUNWproxy

Linux: /opt/sun/webproxyserver

 

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 –

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


Table 1–4 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 

4849 

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 

Multiplexor port 

5269 

Instant Messaging server-to-server port 

45222 

Server port used for multiplexor communication 

Message Queue 

80 

Standard HTTP port 

7676 

Port Mapper 

7674 

HTTPS Tunnelling Servlet Port 

7675 

HTTP Tunneling Servlet Port 

Messaging Server 

25 

Standard SMTP port 

80 

Messaging Express (HTTP) port 

110 

Standard POP3 port / MMP POP3 Proxy 

143 

Standard IMAP4 port / MMP IMAP Proxy 

995 

POP3 over SSL or MMP POP Proxy over SSL 

993 

IMAP over SSL or MMP IMAP Proxy over SSL 

7997 

Event Notification Service 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 

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 

Web Proxy Server 

8888 

Administration Port 

8080 

Proxy Instance Port 

Known Issues in Sun Java Communications Suite

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

Installation and Upgrade Issues

2137103

If you are performing an upgrade of any Java Enterprise System or Communications Suite component to the Java Enterprise System 5 or Communications Suite 5 level on a system that is running Application Server 8.1, you need to apply the following patch (or newer) to Application Server 8.1 first:

  • 119166–17 Solaris SPARC

  • 119167–17 Solaris x86

  • 119168–17 Linux RHEL2.1 RHEL3.0

6527879

Cannot install Communications Express in a local, sparse root non-global zone using the Communications Suite installer.

Instead, you need to manually add the Communications Express and Access Manager packages using pkgadd.

6531802

SUNWldkx not reinstalled.

Java Enterprise System 5 does not reinstall SUNWldkx. This was installed using the -G option with Java Enterprise System 2005Q4. You may get the following error message installing in a sparse zone, even after installing all Shared Components in the Global Zone:


Unsupported components in zone

Following components required by the selected components, are not supported in non-global zone and they can not be installed directly into the non-global zone. Please install these components from the global zone before proceeding this installation.

SharedComponent

The installer can not proceed without resolving the problem. {”<” goes back, “!“exits}!

Consult the Java Enterprise System installer log (the most recent file under /var/sadm/install/logs) to see which Shared Component is missing. It may indicate one or more of these shared components as missing: LDAPCSDKX, JCAPI, and IMAPI.

  • LDAPCSDKX is package SUNWldkx

  • JCAPI is package SUNWjcapi

  • IMAPI is package SUNWldkx

Check to see if the packages are installed in the global zone. If the packages are not present then it is a different bug, perhaps 6531833 or 6531809. If they are present, then check if the packages are listed under /var/sadm/install/gz-only-packages . If they are present in gz-only-packages, then this workaround below applies.

Workaround: manually reinstall the package in the global zone The location of these packages are in the distribution under .../Product/shared_components/Packages

To install:

  1. cd to the package location.

  2. Enter:

    pkgrm pkg

  3. Enter:

    pkgadd —d . pkg

    pkg is the package that is causing the problem.

6531809

Cannot install Communications Express or Instant Messaging in a sparse zone.

You may receive the following error message while installing Communications Express or Instant Messaging in a sparse zone, even after installing all Shared Components in the Global Zone:


Unsupported components in zone

Following components required by the selected components, are not supported in
non-global zone and they can not be installed directly into the non-global
zone. Please install these components from the global zone before proceeding
this installation.

SharedComponent

   The installer can not proceed without resolving the problem. {"<" goes back,
   "!" exits} !

Check to see the SUNWjcapi and the SUNWiimdv packages are installed in the global zone. If they are not, apply the workaround below. If they are present, then check if the packages are listed under /var/sadm/install/gz-only-packages . If they are present in gz-only-packages, then this is a different issue.

Workaround: manually install SUNWjcapi and SUNWiimdv in the global zone. The location of these packages are in the distribution under .../Product/shared_components/Packages. To install:

  1. cd to the package location.

  2. Enter:

    pkgadd -d . SUNWjcapi

  3. Enter:

    pkgadd -d . SUNWiimdv

6531833

Unable to install Access Manager in sparse zone, if Sun Cluster was installed multi-lingual=no in global zone, but yes in sparse.

6535582

Running viewlog with the –help option doesn't display help.

If you run the viewlog command with the -help option, it launches the log viewer instead of displaying the help.

6535583

The uninstaller –help option doesn't include information about obtaining the version.

If you run the uninstaller command with the -help option, it displays a list of options you can use with uninstaller . However, the -version option is not listed as it should be.

No ID

User's Sieve scripts may stop working after the upgrade.

This is relevant for sites running Messaging Server 2005Q4 patch 29 or later, and upgrading to the current Messaging Server 6.3 release and users who make any use of date-based filtering via the mail filters from Communications Express.

For Sieve filters, the setdate action, implemented for Messaging Server 2005Q4 (issue 6236243), has been removed in Messaging Server 6.3. In place of that now-obsolete approach, the more recently proposed date Sieve extension (and in particular its currentdate test) has been implemented.

End users are quite unlikely to have attempted to explicitly, knowingly used setdate. However, the Communications Express mail filter generator in Messaging Server 2005Q4 did use setdate when users requested any filtering of their messages by date. Therefore, many users likely have, without knowing it, personal Sieve filters making use of the now-obsolete setdate action. If a user edits their Sieve filter in any way, any such obsolete usages will be corrected to use the newer currentdate approach. But in the meantime, their Sieve filter will be considered syntactically incorrect and generate an error; each message to the user with such an incorrect Sieve filter will simply be delivered without filtering, plus the MTA will send a notification message to the user owning the Sieve filter warning of the syntax problem in his/her Sieve filter.

Documentation Issues

6524806, 6514424

The Communications Suite Schema Migration Guide incorrectly defines the authentication user and password options for the commdirmig utility.

The -D option of the commdirmig utility should be specified with AuthenticationDN, the DN of Directory Manager, the user authorized to run and manage the Directory Server. The -w option should be specified with password , the password of the Directory Manager.

The Schema Migration Guide incorrectly states that the -D option should be specified with login ID of the user authorized to manage Directory Server. It also incorrectly states that the -w option should be specified with a password file (instead of a password string entered at the command line).

6523606

The Communications Suite Schema Migration Guide incorrectly describes the locations of the audit files generated by the commdirmig utility.

By default, the AuditLDIFFile generated by the commdirmig utility is written to the /tmp directory.

Chapter 3, “Using the Migration Utility” of the Schema Migration Guide incorrectly states that the default paths for the AuditLDIFFile are as follows:

  • Solaris: /var/opt/SUNWComm/log/commdirmig.audit.ldif

  • Linux: /var/opt/sun/comms/commcli/log/commdirmig.audit.ldif