h1. Communications Suite 6 Update 1 Compatibility Issues
This page describes compatibility issues affecting Communications Suite products and the products and shared components used by Communications Suite.
{anchor:6782178}
h4. The latest Common Agent Container (cacao) patch is not compatible with the JavaES 5 Update1 Installer. (*6782178*)
||Incompatibility||Solution||Comments||
|*Issue:* If you install the latest cacao patch (123893-05 or 123896-05), the Java ES 5 Update 1 installer reports that the installation is completed. However, the log files indicate that the installer did not start cacao (bad lib path).\\
*Note:* The Java ES installer is needed to install Access Manager and Web Server, two products optionally used with Communications Suite products.\\
*Cause:* Patch 123893-05 or 123896-05 installs release 2.2.0.1 of cacao. The Java ES 5 Update 1 installer tries to downgrade to cacao release 2.1.0. But the release downgrade is not supported by cacao. The result is that cacao never starts. | In general, we recommend that you run the Communications Suite installer _after_ running the Java ES installer to ensure that the latest versions of the Communications Suite shared components are installed. However, the Communications Suite installer does not install cacao; so this issue does not directly affect the installation of Communications Suite products. | This issue can affect the use of Communications Suite products if they are monitored with the Java Enterprise System Monitoring Framework (JESMF).\\
Note also that this is not a compatibility issue with Communications Suite products. It is an incompatibility between the cacao patches and the Java ES installer. |
{anchor:6743356}
h4. On Linux systems, upgrading to Java 6 (JDK 1.6u7) may affect dependent products that use earlier versions of Java. (*6743356*)
||Incompatibility||Solution||Comments||
|*Issue 1:* On Linux systems, when installing or upgrading to Communications Suite 6 Update 1, the Comms Suite installer checks if there is an existing version of Java on the machine and upgrades it to Java 6 (JDK 1.6u7). Some Sun Java products used by Communications Suite products, such as Access Manager, Web Server, Directory Server, and Application Server, may not be compatible with Java 6.\\
On Linux, the Communications Suite installer replaces any previous Java version with Java 6. This is not an issue on Solaris; on Solaris, the Comms Suite installer upgrades Java side-by-side with the previous version. That is, the installer installs Java 6 and leaves the previous Java version on the system.\\
This issue only affects dependent Sun Java products running on the same machine as the Communications Suite products.\\
*Cause:* On Linux systems, packages are not used to manage product versions. Without the version-management facility available with Solaris packages, the Comms Suite installer can only replace any existing Java version with the upgraded version.\\
\\
*Issue 2:* Under some conditions, there is the potential for Sun Java products used by Communications Suite products to be unable to access the Java shared component. In most cases, the Comms Suite installer addresses and resolves this issue. \\
This issue might occur only if the Comms Suite installer upgrades the Java shared component to Java 6 under these conditions: on Linux systems, in silent mode, and when the dependent Sun Java product such as Access Manager, Web Server, Directory Server, or Application Server was installed with the Java ES 5 Update 1 installer.\\
*Cause:* When the Java ES installer installs the Java shared component, it creates a Sun Java Enterprise System (JES) {{entsys symlink}} to the Java files. The symlink is in the following location: {{/usr/jdk/entsys-j2se}}. On Linux, when the Comms Installer replaces the previous Java version with Java 6, the symlink to the old files is temporarily broken. However, the Comms Installer prompts you to fix this problem. See the *Solution for Issue 2*. \\
In silent mode, the Comms Installer cannot prompt you to fix the broken symlink. Instead, you must use the {{--fixEntsys y}} option in the command line when you run the {{commpkg}} command. | *Solution for Issue 1:* Install or upgrade to a later version of the affected Sun Java product, which is compatible with Java 6. \\
However, this approach does not apply to Access Manager 7.1, installed with the Java Enterprise 5 Update 1 installer, which is required for Delegated Administrator 6.4 and tested for compatibility with other Communications Suite products. See the *Note for Access Manager 7.1*, below.\\
*Note:* You could choose not to upgrade to Java 6 when you run {{commpkg upgrade}}, but in general we do not recommend this approach. Java 6 is recommended for Communications Suite 6 Update 1 products such as Convergence 1 Update 1. If Convergence is configured to use S/MIME, Java 6 is required on end users' client machines.\\
*Note for Access Manager 7.1:* The Java Enterprise 5 Update 1 (JES5u1) installer cannot successfully deploy Access Manager 7.1 if Java Development Kit (JDK) 1.6 or above is installed. Therefore, on a Linux machine where you are installing Access Manager 7.1, you need to downgrade to JDK 1.5. For instructions, see [Verifying the Correct JDK Version to Support Access Manager]. \\
*Solution for Issue 2:* During interactive installations or upgrades, if the Comms Installer detects a broken sym link, it asks if you want to fix the broken link. Choose {{y}} to fix the link. The Comms Installer then changes the link to point to the upgraded Java 6 files. \\
Alternatively, use the {{--fixEntsys y}} option with the {{commpkg install}} or {{commpkg upgrade}} command. If you run {{commpkg}} in silent mode, you must enter this option in the command line with the {{commpkg}} command. | On Linux, during an interactive install or upgrade, if the Comms Suite installer detects any existing Java version on the machine, it prompts you to choose whether to upgrade the Java component or not. Choose {{y}} to perform the upgrade. \\
If you are performing a silent installation or upgrade, the default behavior is _not_ to upgrade shared components, including Java. However, you can override the default setting, even in a silent installation or upgrade. For more information, see [_About Upgrading Shared Components_|Installing Communications Suite in Silent Mode#aboutupgradingsharedcomponents]. |
{excerpt:hidden=true}
{anchor:6653773}
h4. Access Manager 7.1 fails to start if it is deployed to a non-enterprise (non-HADB) version of Application Server 9.1 Update 2.(*6653773*)
||Incompatibility||Solution||Comments||
|*Issue:* On Solaris and Linux, if you install Access Manager 7.1 and deploy it to a version of Application Server 9.1 Update 2 that is not the enterprise version or is not bundled with HADB, Access Manager fails to start. \\
*Cause:* Access Manager requires that {{libjss4.so}} is installed in the Application Server lib path. For example, on Solaris: {{/opt/SUNWappserver/lib}} |*Solution 1:* Add the location of {{libjss4.so}} to the Application Server configuration file, {{asenv.conf}}. For example, on Solaris: {{AS_NSS="/usr/lib/mps/secv1:/opt/SUNWappserver/lib"}}. \\
*Solution 2:* Download and install an enterprise (EE) version of Application Server 9.1 U2; this may be a version bundled with HADB. | |
{excerpt}
This page describes compatibility issues affecting Communications Suite products and the products and shared components used by Communications Suite.
{anchor:6782178}
h4. The latest Common Agent Container (cacao) patch is not compatible with the JavaES 5 Update1 Installer. (*6782178*)
||Incompatibility||Solution||Comments||
|*Issue:* If you install the latest cacao patch (123893-05 or 123896-05), the Java ES 5 Update 1 installer reports that the installation is completed. However, the log files indicate that the installer did not start cacao (bad lib path).\\
*Note:* The Java ES installer is needed to install Access Manager and Web Server, two products optionally used with Communications Suite products.\\
*Cause:* Patch 123893-05 or 123896-05 installs release 2.2.0.1 of cacao. The Java ES 5 Update 1 installer tries to downgrade to cacao release 2.1.0. But the release downgrade is not supported by cacao. The result is that cacao never starts. | In general, we recommend that you run the Communications Suite installer _after_ running the Java ES installer to ensure that the latest versions of the Communications Suite shared components are installed. However, the Communications Suite installer does not install cacao; so this issue does not directly affect the installation of Communications Suite products. | This issue can affect the use of Communications Suite products if they are monitored with the Java Enterprise System Monitoring Framework (JESMF).\\
Note also that this is not a compatibility issue with Communications Suite products. It is an incompatibility between the cacao patches and the Java ES installer. |
{anchor:6743356}
h4. On Linux systems, upgrading to Java 6 (JDK 1.6u7) may affect dependent products that use earlier versions of Java. (*6743356*)
||Incompatibility||Solution||Comments||
|*Issue 1:* On Linux systems, when installing or upgrading to Communications Suite 6 Update 1, the Comms Suite installer checks if there is an existing version of Java on the machine and upgrades it to Java 6 (JDK 1.6u7). Some Sun Java products used by Communications Suite products, such as Access Manager, Web Server, Directory Server, and Application Server, may not be compatible with Java 6.\\
On Linux, the Communications Suite installer replaces any previous Java version with Java 6. This is not an issue on Solaris; on Solaris, the Comms Suite installer upgrades Java side-by-side with the previous version. That is, the installer installs Java 6 and leaves the previous Java version on the system.\\
This issue only affects dependent Sun Java products running on the same machine as the Communications Suite products.\\
*Cause:* On Linux systems, packages are not used to manage product versions. Without the version-management facility available with Solaris packages, the Comms Suite installer can only replace any existing Java version with the upgraded version.\\
\\
*Issue 2:* Under some conditions, there is the potential for Sun Java products used by Communications Suite products to be unable to access the Java shared component. In most cases, the Comms Suite installer addresses and resolves this issue. \\
This issue might occur only if the Comms Suite installer upgrades the Java shared component to Java 6 under these conditions: on Linux systems, in silent mode, and when the dependent Sun Java product such as Access Manager, Web Server, Directory Server, or Application Server was installed with the Java ES 5 Update 1 installer.\\
*Cause:* When the Java ES installer installs the Java shared component, it creates a Sun Java Enterprise System (JES) {{entsys symlink}} to the Java files. The symlink is in the following location: {{/usr/jdk/entsys-j2se}}. On Linux, when the Comms Installer replaces the previous Java version with Java 6, the symlink to the old files is temporarily broken. However, the Comms Installer prompts you to fix this problem. See the *Solution for Issue 2*. \\
In silent mode, the Comms Installer cannot prompt you to fix the broken symlink. Instead, you must use the {{--fixEntsys y}} option in the command line when you run the {{commpkg}} command. | *Solution for Issue 1:* Install or upgrade to a later version of the affected Sun Java product, which is compatible with Java 6. \\
However, this approach does not apply to Access Manager 7.1, installed with the Java Enterprise 5 Update 1 installer, which is required for Delegated Administrator 6.4 and tested for compatibility with other Communications Suite products. See the *Note for Access Manager 7.1*, below.\\
*Note:* You could choose not to upgrade to Java 6 when you run {{commpkg upgrade}}, but in general we do not recommend this approach. Java 6 is recommended for Communications Suite 6 Update 1 products such as Convergence 1 Update 1. If Convergence is configured to use S/MIME, Java 6 is required on end users' client machines.\\
*Note for Access Manager 7.1:* The Java Enterprise 5 Update 1 (JES5u1) installer cannot successfully deploy Access Manager 7.1 if Java Development Kit (JDK) 1.6 or above is installed. Therefore, on a Linux machine where you are installing Access Manager 7.1, you need to downgrade to JDK 1.5. For instructions, see [Verifying the Correct JDK Version to Support Access Manager]. \\
*Solution for Issue 2:* During interactive installations or upgrades, if the Comms Installer detects a broken sym link, it asks if you want to fix the broken link. Choose {{y}} to fix the link. The Comms Installer then changes the link to point to the upgraded Java 6 files. \\
Alternatively, use the {{--fixEntsys y}} option with the {{commpkg install}} or {{commpkg upgrade}} command. If you run {{commpkg}} in silent mode, you must enter this option in the command line with the {{commpkg}} command. | On Linux, during an interactive install or upgrade, if the Comms Suite installer detects any existing Java version on the machine, it prompts you to choose whether to upgrade the Java component or not. Choose {{y}} to perform the upgrade. \\
If you are performing a silent installation or upgrade, the default behavior is _not_ to upgrade shared components, including Java. However, you can override the default setting, even in a silent installation or upgrade. For more information, see [_About Upgrading Shared Components_|Installing Communications Suite in Silent Mode#aboutupgradingsharedcomponents]. |
{excerpt:hidden=true}
{anchor:6653773}
h4. Access Manager 7.1 fails to start if it is deployed to a non-enterprise (non-HADB) version of Application Server 9.1 Update 2.(*6653773*)
||Incompatibility||Solution||Comments||
|*Issue:* On Solaris and Linux, if you install Access Manager 7.1 and deploy it to a version of Application Server 9.1 Update 2 that is not the enterprise version or is not bundled with HADB, Access Manager fails to start. \\
*Cause:* Access Manager requires that {{libjss4.so}} is installed in the Application Server lib path. For example, on Solaris: {{/opt/SUNWappserver/lib}} |*Solution 1:* Add the location of {{libjss4.so}} to the Application Server configuration file, {{asenv.conf}}. For example, on Solaris: {{AS_NSS="/usr/lib/mps/secv1:/opt/SUNWappserver/lib"}}. \\
*Solution 2:* Download and install an enterprise (EE) version of Application Server 9.1 U2; this may be a version bundled with HADB. | |
{excerpt}