test

Sun Java Communications Suite 5 Release Notes

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