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:
Sun Java Communications Suite Release Notes Revision History
Sun Java Communications Suite Installation and Upgrade Notes
Third-party URLs are referenced in this document and provide additional, related information.
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.
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) |
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:
Sun Java System Calendar Server 6.3
Sun Java System Messaging Server 6.3
Sun Java System Instant Messaging 7.2
Sun Java System Communications Express 6.3
Sun Java System Connector for Microsoft Outlook 7.2
Sun Java System Delegated Administrator 6.4
Sun Java System Communications Sync 3
The Release Notes for Sun Java System Communications Sync can be found at Sun Java System Communications Sync 2006Q2 Release Notes
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” |
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.
This section describes new features and changes to Sun Java Communications Suite 5.
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:
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 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.
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.
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.
The server component products of Sun Java Communications Suite are no longer supported on HP-UX or Windows platforms.
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.
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:
If you have not installed JES, remove the SUNWldapcsdk-tools package, prior to installing the released version of JES5. To check the SUNWldapcsdk-tools version, run the command pkgparam -v SUNWldapcsdk-tools VERSION.
You must have a version that is 6.00,REV=2006.12.11.00.08 or later. Otherwise, you will get an error message that the LDAP search utility is not found.
Use the pkgrm SUNWldapcsdk-tools command, to remove the SUNWldapcsdk-tools package.
If you have already run the JES5 installer, you can manually remove the SUNWldapcsdk-tools package, and install it using the command:
cd <jes5_distro>/Solaris_sparc/Product/shared_components/Packages pkgadd -d . SUNWldapcsdk-tools |
This section lists the product component installation directories and port numbers that the Sun JavaSystem Communications Suite 5 installer uses by default.
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.
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
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.
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.
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 |
This section describes the known issues that exist in this release of Sun Java Communications Suite.
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
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.
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:
cd to the package location.
Enter:
pkgrm pkg
Enter:
pkgadd —d . pkg
pkg is the package that is causing the problem.
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:
cd to the package location.
Enter:
pkgadd -d . SUNWjcapi
Enter:
pkgadd -d . SUNWiimdv
Unable to install Access Manager in sparse zone, if Sun Cluster was installed multi-lingual=no in global zone, but yes in sparse.
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.
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.
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.
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).
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