Communications Suite 6 Update 1 Component Products Release Notes

Added by joesciallo, last edited by AnjanaK on May 13, 2009  (view change)
Searching CommSuite6 U1 Release Specific Documentation

Finding Info

This image is for the Communications Suite Wiki logo.
Home
Why Use This Wiki?
Contact Wiki Administrators

Return to Comms Suite Home
Comms Suite Home

Comms Suite 6 U1 Product Docs

Convergence 1 Update 1
Messaging Server 7 Update 1
Calendar Server 6.3
Instant Messaging 8
Delegated Administrator 6.4
Connector for Outlook 7.3
Communications Express 6.3
Printable Docs

Release Specific Docs

Communications Suite 6 Docs
Communications Suite 6 U1 RR Snapshot
Communications Suite Snapshot Updates
Communications Suite 6 RR Snapshot
Communications Suite 5
Java ES 2005Q4
Java ES 2005Q1
Java ES 2004Q2
Java ES 2003Q4
Sun ONE Messaging Server 6
iPlanet Messaging Server 5.2

Common Release Information for Sun Java Communications Suite 6 Update 1 Component Products

These release notes contain important release information that is common for all component products of Sun Java Communications Suite 6 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 Sun Java Communications Suite, Version 6 Update 1

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

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 6 Update 1 What's New document.

Requirements for Communications Suite 6 Update 1

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:

  • Which Sun Java System products are required to support the Communications Suite 6 Update 1 products? Table 1-1 lists the Sun Java System product versions that are compatible with the Communications Suite 6 Update 1 products.
  • To install a particular Communications Suite product, which other components do I need? Table 1-2 lists the individual Communications Suite products and shows the components on which they depend, including other Communications Suite components.


Table 1-1 Sun Java System Product Version Compatibility Requirements for Communications Suite 6 Update 1

Product Version Required or Optional?
Sun Java System Directory Server 5.x, 6.x Required. 6.3 or later recommended.
Sun Java System Message Queue 3.7, 4.1p1 Optional. Communications Suite installer automatically installs Message Queue as a shared component.
Sun Java System Access Manager 7.1 Optional.
Sun Java System Application Server 9.1 Update 2 9.1 Update 2 is required as the web container for Sun Convergence 1 Update 1.
Sun Java System Web Server 7.0 Update 1 Instant Messaging, Communications Express, and Delegated Administrator require a web container. Use either Web Server 7.0 Update 1, Application 8.2P2, or Application Server 9.1 Update 2 (recommended).

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 Application Server 9.1 Update 2, see the Sun Java System Application Server 9.1 Installation Guide.

For installation instructions for Directory Server Enterprise Edition 6.3, see the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

For installation instructions for the other components, see the Sun Java Enterprise System 5 Update 1 Installation Guide.


Table 1-2 Communications Suite 6 Update 1 Component Dependencies

Product Component Dependencies Required or Optional? Must Be on Local Host?
Messaging Server 7 Update 1

(64-bit or 32-bit)		 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 6 Update 1 installer. 		Required. To prepare the LDAP directory for Messaging Server. No. Must be on the same host as Directory Server.
  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. No
  Delegated Administrator 6.4 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 6 Update 1 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


Recommended: 7 Update 1 		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 6.4 Optional. To provision users of calendar services; to manage the directory schema. No
Instant Messaging 8 (Server) Directory Server 5.x, 6.x


Recommended: 6.3 or later 		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 6 Update 1 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


Recommended: 7 Update 1 		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:



Application Server 9.1 U2

Application Server 8.x

Recommended: AS 9.1 U2


Web Server 7 or higher 		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 6 Update 1 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 6.4 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.x
Directory 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 6 Update 1 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.x

Recommended: AS 9.1 U2


Web Server 7 or higher

Web Server 6 (compatible with Delegated Administrator 6.4, 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


Recommended: 7 Update 1 		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 1   For details about Convergence dependencies, see Convergence 1 Update 1: Product Version Compatibility Requirements.  
Communications Express 6.3 Directory Server 5.x, 6.x


Recommended: 6.3 or later 		Required. To store user/group data in the LDAP directory; to store address book data in the LDAP directory. No
  Directory Server Setup Script (comm_dssetup.pl)


You must use the version that is bundled with the Communications Suite 6 Update 1 installer. 		Required. To prepare the LDAP directory for Communications Express. No. Must be on the same host as Directory Server.
  Access Manager 7.1 Optional. To provide single sign-on (SSO) authentication and authorization services for Communications Express users. No
  Web container, one of:


Application Server 9.1 U2

Application Server 8.x

Recommended: AS 9.1 U2


Web Server 7 or higher 		Required. Communications Express must be deployed to one of these web containers. Yes
  Messaging Server 6.3, 7.0, 7 Update 1


Recommended: 7 Update 1 		Required to provide mail service for Communications Express users. No. However, we recommend deploying the Webmail Server component of Messaging Server on the same host as Convergence for scalability and performance.
  Calendar Server 6.3


Recommended: 6.3 		Required to provide calendar service for Communications Express users. No

NSS Requirements

Communications Suite 6 Update 1 requires the use of the shared security component NSS version 3.11.7.

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

Convergence 1 Update 1: 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 6 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 Table 1-1.

Table 1-3 Sun Java System Product Requirements for Convergence 1 Update 1

Product Version Required or Optional? Must Be on Local Host?
Sun Java System Directory Server Enterprise Edition 5.x, 6.x Required. 6.3 or later recommended. For the recommended version to download, see Get the Software. No
Sun Java System Application Server 9.1 Update 2 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

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

Table 1-4 Communications Suite Component Requirements for Convergence 1 Update 1

Product Version Communications Suite Release Required or Optional? Must Be on Local Host?
Messaging Server - Webmail Server 7.0, 7 Update 1 6 (for MS 7.0)
6 Update 1 (for MS 7 Update 1) 		Required to provide mail service in Convergence. No, but we recommend deploying 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 5 (for MS 6.3)

6 (for MS 7.0)

6 Update 1 (for MS 7 Update 1)		 Required to provide mail service in Convergence. No
Calendar Server 6.3, patch level -28 or higher 5 + apply patch level -28

6
6 Update 1 		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 7.3, 8 6 (for IM 7.3)
6 Update 1 (for IM 8) 		Required to provide IM service in Convergence. No
Directory Server Setup script, comm_dssetup.pl You must use the version that is bundled with the Communications Suite 6 Update 1 installer. 6 Update 1 Required. You must run comm_dssetup.pl on the hosts where Directory Server is installed. No
Delegated Administrator 6.4 5, 6, or 6 Update 1 Optional. No

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.


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

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


Table 1-6 Memory and Disk Space Requirements for Communications Suite 6

Product Disk Space RAM Other
Sun Java System Calendar Server 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. 		 
Communications Express Approximately the same as Messaging Server/Calender Server. 1 Gbyte minimum.  

Operating System Requirements

This release supports the following platforms:


Table 1-7 Operating System and Platform Support

Operating System CPU Comments
Solaris OS 10 SPARC, x86, x64  
Solaris OS 9 SPARC, x86  
Red Hat Enterprise Linux 4

Advanced Server (32-bit and 64-bit versions)

Enterprise Server (32-bit and 64-bit versions) 		x86, x64
  • Distinct 32-bit x86 and 64-bit AMD64/Intel EM64T distributions exist.
  • Advanced Server and Enterprise Server provide identical functionality. Essentially ES limits CPU/memory support.
Red Hat Enterprise Linux 3

Advanced Server (32-bit and 64-bit versions)

Enterprise Server (32-bit and 64-bit versions) 		x86, x64
  • Distinct 32-bit x86 and 64-bit AMD64/Intel EM64T distributions exist.
  • Advanced Server and Enterprise Server provide identical functionality. Essentially ES limits CPU/memory support.
Windows 2000 (SP 3 or higher); XP (SP 1 or higher); 2003 Terminal Server; Vista x86 For Sun Java System Connector for Outlook only.

Notes:

  • Messaging Server, Calendar Server, Instant Messaging, Communications Express, and Delegated Administrator are no longer supported on HP-UX or Windows platforms.
  • The Communications Suite installer checks for required platform patches. You must install all required patches or the installation process does not continue.
  • 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.

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.

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.

At the time of general release of the Sun Java Communications Suite 6 Update 1, the following patches are available:

Table 1-8 Sun Java Communications Suite 6 Component Patches

Component Platform Patch Number (English) Patch Number (Localized Languages)
Calendar Server 6.3 Solaris SPARC 121657 Incorporated into the English patch
  x86 121658 Incorporated into the English patch
  Linux 121659 Incorporated into the English patch
Communications Express 6.3 Solaris SPARC 122793  
  x86 122794  
  Linux 122795  
Delegated Administrator 6.4 Solaris SPARC 121581 Part of the English patch
  x86 121582 Part of the English patch
  Linux 121583 Part of the English patch

A fresh installation of Calendar Server 6.3, Communications Express 6.3, and Delegated Administrator 6.4, through the Communications Installer, puts you at the above patch levels for those products.

To deploy Calendar Server 6.3 with Convergence, Calendar Server must be at least at the -28 patch level.

High Availability Support

Table 1-9 Supported High-Availablity Products

Product Supported Versions
Calendar Server 6.3
  • Sun Cluster
    • SPARC: 3.0, 3.1 Update 4, 3.2
    • x86: 3.1 Update 4, 3.2
    • Linux: Not Supported
  • Veritas
    • SPARC: Not Supported
    • x86: Not Supported
    • Linux: Not Supported
Instant Messaging 8
  • Sun Cluster
    • SPARC: 3.1 Update 4, 3.2
    • x86: 3.1 Update 4, 3.2
    • Linux: Not Supported
  • Veritas
    • SPARC: Not Supported
    • x86: Not Supported
    • Linux: Not Supported
Messaging Server 7 Update 1
  • Sun Cluster
    • SPARC: 3.0, 3.1 Update 4, 3.2
    • x86: 3.1 Update 4, 3.2 U1
    • Linux: Not Supported
  • Veritas
    • SPARC: 3.5, 4.0, 4.1, 5.0
    • x86: 3.5, 4.0. 4.1, 5.0
    • Linux: 4.1,5.0


Table 1-9a 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 browsers are supported for Communications Suite clients.

Table 1-10 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 N/A 7.x N/A N/A N/A
Firefox 2.0.0.11 minimum
3.0.x 		2.0.0.11 minimum
3.0.x 		2.0.0.11 minimum
3.0.x 		2.0.0.11 minimum
3.0.x 		2.0.0.11 minimum
3.0.x 		2.0.0.11 minimum
3.0.x
Safari N/A N/A N/A N/A N/A 3.1.x


Table 1-11 Supported Browser Versions for Communications Express Clients

Browser Windows XP Windows 2000 Solaris Red Hat Linux Mac OS 10.x
Microsoft Internet Explorer 7.0 6.0 SP1 N/A N/A N/A
Safari N/A N/A N/A N/A 3.0
Firefox 2.0 2.0 2.0 2.0 2.0

Table 1-12 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

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. The Sun StorEdge 53xx NAS have been certified for use with Messaging Server. See Using Sun StorageTek 53xx NAS with Messaging Server Message Store for more information.
  • ZFS. As of Messaging Server 6.3, Messaging Server supports the ZFS file system. See Messaging Server ZFS Support for more information.
Non-Supported Files Systems for Messaging Server Deployments

Messaging Server must not be used on the EXT4 file system. Use on EXT4 file system will cause critical data loss.

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

This release supports the following client platforms:

  • Solaris OS 9, and 10
  • Microsoft Windows 98, ME, NT (SP 6a), 2000, XP
  • Mac OS X, minimum 10.1
  • Red Hat Linux, minimum 7.2

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

Table 1-13 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

Table 1-14: 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

To locate patches for the Sun Java Communications Suite products, check the following table, which lists the keywords used for each Communications Suite product. You can use the specific keyword to search for relevant patches in the SunSolve database.

Table 1-15 Patch Keywords for Communications Suite Products

Product Keyword
Calendar Server "Calendar Server"
Convergence TBD
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 to search for the text string and word space.

Sun Java Communications Suite Installation and Upgrade Notes

Default Installation Directories and Ports

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.

Table 1-16 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 and Linux: /opt/SUNWappserver Contains Application Server utilities, executables, and libraries.
Application Server Domains

CMN_AS_DOMAINSDIR 		Solaris OS and Linux: /opt/SUNWappserver/domains Default area under which administrative domains are created.
Calendar Server

CMN_CS_INSTALLDIR 		Solaris OS and Linux: /opt/sun/comms/calendar  
Convergence

CMN_IWC_INSTALLDIR 		Solaris OS and Linux: /opt/sun/comms/iwc  
Communications Express

CMN_UWC_INSTALLDIR 		Solaris OS and Linux: /opt/sun/comms/ce  
Delegated Administrator

CMN_COMMDA_INSTALLDIR 		Solaris OS and Linux: /opt/sun/comms/commcli  
Directory Preparation Tool

CMN_DSSETUP_INSTALLDIR 		Solaris OS and 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 and Linux: /opt/sun/comms/im  
Instant Messaging Resource Directory

CMN_IIM_DOCSDIR 		Solaris OS and Linux: /opt/sun/comms/im/html  
Instant Messaging Online Help Directory

CMN_IIM_DOCSHELPDIR 		Solaris OS and 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

Linux:

/opt/sun/mq

/etc/opt/sun/mq

/var/opt/sun/mq
Messaging Server

CMN_MS_INSTALLDIR 		Solaris OS & 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


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


Linux: /opt/sun/webserver7 		 
Web Server Instance Directory

CMN_WS_INSTANCEDIR 		Solaris OS: /var/opt/SUNWwbsvr7


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.

Table 1-17 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 Sun Java System Messaging Server 6.3 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, see

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 Linux) the Calendar Server installation fails.

6669238

The Communications Express configuration process results in an error when you configure the Webmail host and port settings.
You get the warning, "Unable to connect to the Webmail Server" while configuring Communications Express against Messaging Server 7.0.

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 6 Update 1 Compatibility Issues.

6785668

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

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.

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 6 Update 1 Compatibility Issues.

No Localization Files for Communications Express

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 upgrade and select 3. If you are upgrading comm_dssetup only, see issue 6785668, above.

Labels

prerequisites prerequisites Delete
guide guide Delete
communicationssuite communicationssuite Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (24)

 

  1. May 07, 2008

    Thiru says:

    Remove below bug from Known Issues in Sun Java Communications Suite Bug 6668349 ...

    Remove below bug from Known Issues in Sun Java Communications Suite
    Bug 6668349 (CI 6.0-0.02 only)
    The /opt/sun/comms/CommsInstaller/bin/commpkg uninstall fails.
    Workaround: Use the commpkg command that comes in the zip file.

    1. May 08, 2008

      joesciallo says:

      Thanks Thiru. I removed that fixed bug.

      Thanks Thiru. I removed that fixed bug.

  2. May 11, 2008

    DNReddy says:

    1) Table 1-6 Supported Browser Versions for Convergence Clients IE row =>...

    1) Table 1-6 Supported Browser Versions for Convergence Clients IE row => no changes
    Firefox row => change all to 2.0 (1.5 is not supported)
    Safari row => 3.0 on Mac OS 10.x

    2) Table 1-11 Default Installation Directories

    • Missing Convergence entry in the table, default location is /opt/sun/comms/iwc
    • Appserver default installation for AS9.1Update1 is /opt/SUNWappserver (Solaris and Linux) not
      /opt/SUNWappserver/appserver
    • Application Server Domains for AS9.1Update1 is /opt/SUNWappserver/domains(Solaris and Linux)

    3) Table 1-12 Product Component Default Port Numbers

    • 4848 is the default Application Server's Administration Server port

    1. May 12, 2008

      The_Tech_Writer says:

      Thanks, Reddy. I have made these changes. For the missing Convergence entry, I...

      Thanks, Reddy. I have made these changes. For the missing Convergence entry, I added the the label and state file parameter CMN_IWC_INSTALLDIR.

  3. May 14, 2008

    Sarma.Vempati@Sun.COM says:

    Will be good to capture the minimum required patch versions for interoperability...

    Will be good to capture the minimum required patch versions for interoperability/compatibility with R6. Populating table 1-4 can
    help.

    Thanks.

    1. May 14, 2008

      joesciallo says:

      Sarma, Yes, we will be populating Table 1-4 with this info before Revenue Relea...

      Sarma,

      Yes, we will be populating Table 1-4 with this info before Revenue Release.

      Thanks,

      Joe

  4. May 14, 2008

    mchametzky says:

    Under "Table 1-11 Default Installation Directories", we should probably also lis...

    Under "Table 1-11 Default Installation Directories", we should probably also list the /var/opt/sun/comms/messaging (and I guess /var/opt/sun/comms/messaging64) directories that are used as the read-write area including configuration, queue, log, store, and other miscellaneous data used and updated by the Messaging Server.

    1. May 14, 2008

      joesciallo says:

      Marc, Added this info to Table 1-11. Thanks, Joe

      Marc,

      Added this info to Table 1-11.

      Thanks,

      Joe

  5. May 28, 2008

    NarenLahoti says:

    Table 1-9 Supported Browser Versions for Convergence Clients   Remove MS I...

    Table 1-9 Supported Browser Versions for Convergence Clients
     

    Remove MS Internet Explorer 6.0  Under Windows XP
    Remove MS Internet Explorer 6.0 SP1  Under Windows 2000
    remove the last row Mozilla (TBD)

    1. May 28, 2008

      joesciallo says:

      Done. However, is MS Internet Explorer 7 supported for Windows 2000? Please clar...

      Done. However, is MS Internet Explorer 7 supported for Windows 2000? Please clarify.

      Thanks,

      Joe

      1. May 28, 2008

        NarenLahoti says:

        IE7 is not available for the windows 2000

        IE7 is not available for the windows 2000

        1. May 28, 2008

          joesciallo says:

          Thanks.

          Thanks.

  6. Jun 15, 2008

    p4l4n1s0ng says:

    Is there communication sync "3.1"? The link for release note is for 3.0.

    Is there communication sync "3.1"?
    The link for release note is for 3.0.

    1. Jun 17, 2008

      joesciallo says:

      Trying to get an answer for you from our Prod Mkt group. Joe

      Trying to get an answer for you from our Prod Mkt group.

      • Joe

  7. Jun 17, 2008

    Merat says:

    The link of the Documentation for Sun Java System Communications Sync 3.0 http...

    The link of the Documentation for Sun Java System Communications Sync 3.0
    http://docs.sun.com/db/coll/S1_Sync_11
    is broken in http://docs.sun.com/source/819-4706/index.html#doc

    Where can we find this documentation ?

    What about Communications Sync 3.1 ?

    1. Jun 17, 2008

      joesciallo says:

      Looks like http://docs.sun.com/db/coll/S1_Sync_11 should be: http://docs.sun.co...

      Looks like http://docs.sun.com/db/coll/S1_Sync_11

      should be: http://docs.sun.com/app/docs/coll/1313.2

      but it still just brings you to: http://docs.sun.com/source/819-4706/index.html (last updated Oct 2006, per the doc).

      re: Sync 3.1, see comment above (trying to find out from Prod Mkt).

      • Joe

  8. Nov 17, 2008

    benc2 says:

    "Table 1-12 Supported Browser Versions for Delegated Administrator Clients" Nav...

    "Table 1-12 Supported Browser Versions for Delegated Administrator Clients"

    Navigator "2.0" should probably be "7.2"

    Take look at:

    http://docs.sun.com/app/docs/doc/819-4432/fvzmz?a=view

    1. Nov 17, 2008

      The_Tech_Writer says:

      I have made the change. Thanks for catching this.

      I have made the change. Thanks for catching this.

  9. Dec 11, 2008

    gangadharcm says:

    Under Browser Versions for Communications Express Clients Change FireFox Browse...

    Under Browser Versions for Communications Express Clients

    Change FireFox Browser Version 1.0.7 to 2.0 for Windows 2000,Solaris,Red Hat Linux

    1. Dec 12, 2008

      joesciallo says:

      Made these changes. Joe

      Made these changes.

      Joe

  10. Apr 17

    bn126029 says:

    Table 1-1 (Sun Java System Product Version Compatibility Requirements....) shows...

    Table 1-1 (Sun Java System Product Version Compatibility Requirements....) shows version 3.7 of SJS Message Queue. But the Comms Installer (commpkg) installs SJS Message Queue 4.1. This is also documented at http://wikis.sun.com/display/CommSuite6U1/SharedComponents

    So, this table must be modified to add 'SJS Message Queue 4.1' as well.

    Thanks,
    Brijesh

    1. Apr 17

      The_Tech_Writer says:

      I replaced 3.7 with 4.1p1. Michael

      I replaced 3.7 with 4.1p1.

      Michael

  11. Apr 22

    bn126029 says:

    Thanks Michael! Shouldn't the table show both 3.7 and 4.1p1 as compatible ? As...

    Thanks Michael!

    Shouldn't the table show both 3.7 and 4.1p1 as compatible ?

    As you have replaced 3.7 with 4.1p1, does it mean Message Queue 3.7 is not compatible with Comms6 Update 1 ?

    Regards,
    Brijesh

    1. Apr 22

      The_Tech_Writer says:

      Thanks, Brijesh. I added 3.7 back along with 4.1p1 for the Message Queue versio...

      Thanks, Brijesh. I added 3.7 back along with 4.1p1 for the Message Queue versions since they are both compatible with Communications Suite 6 Update 1.

      Michael

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact