Communications Suite Component Products Release Notes

Skip to end of metadata
Go to start of metadata

Common Release Information for Oracle Communications Unified Communications Suite Component Products
Version 7 Update 2

These release notes contain important release information that is common for all component products of Oracle Communications Unified Communications Suite 7 Update 2.

Topics:

Third-party URLs are referenced in this document and provide additional, related information.

Note
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

About Oracle Communications Unified Communications Suite 7 Update 2

The Oracle Communications Unified Communications Suite integrates a number of server and client products to support distributed communication and collaboration applications.

The Oracle Communications Unified Communications Suite 7 Update 2 release includes the following components:

Oracle Communications Unified Communications Suite Products and Components
Version 7 Update 2
Product Version
Oracle Communications Messaging Server 7 Update 4 (Patch 23)
Oracle Communications Instant Messaging Server 9
Convergence 2 (Patch 2)
Oracle Communications Calendar Server 7 Update 2
Delegated Administrator for Oracle Communications Unified Communications Suite 7 (Patch 4)
Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite 7.3 Update 1 (Patch 13)
Indexing and Search Service for Oracle Communications Unified Communications Suite 1 Update 3
Messaging Server HA Agent (MS_SCHA) 7
Instant Messaging HA Agent (IM_SCHA) 7.3
Dssetup for Oracle Communications Unified Communications Suite (comm_dssetup) 6.4 (Patch 23)

Check Communications Suite Component Patches for current patches that have shipped since the initial Communications Suite 7 Update 2 release.

For release notes on individual component products, see the following links:

What's New in This Release of Communications Suite

See the What's New document.

Deprecated and Removed Features for Communications Suite

Support for the following features may have been removed in this or a previous release, or may be eliminated in a future release:

Calendar Server 6.3

In this release (Communications Suite 7 Update 2), Calendar Server 6.3 has been removed from the installation bundle. Refer to the Oracle Lifetime Support Policy for information on product support dates.

For information on Calendar Server 6.3, refer to Calendar Server Release Notes Version 6.3 (in Communications Suite 7 Update 1).

Communications Express 6.3

Communications Express has been removed from the installation bundle. For an Ajax-based user interface with integrated email, calendar, address book, and instant messaging, use Convergence.

No patches will be issued for Communications Express versions prior to 6.3.

If you need to install Communications Express 6.3, use the Communications Suite 6 Update 2 media to get the software.

Delegated Administrator 6.4

Going forward, no new features will be added to Delegated Administrator 6.4. It has been deprecated in favor of Delegated Administrator 7.

Connector for Microsoft Outlook 7.1 , 7.2, and 7.2 Update 1

Going forward, no new features will be added to the Connector for Microsoft Outlook 7.1, 7.2, and 7.2 Update 1. They have been deprecated in favor of Connector for Microsoft Outlook for Oracle Communications Unified Communications Suite 7 Update 3.

Communications Sync

Going forward, no new features will be added to Communications Sync. All versions of Communications Sync have been deprecated. If you are using Communications Sync, consider moving to Oracle Communications Mobile Synchronization Server (formerly known as Sun Java Mobile Communications).

Support for Access Manager and Sun OpenSSO

Support for Access Manager 7.x and Sun OpenSSO 8.x has been deprecated. Convergence, Instant Messaging, and Delegated Administrator optionally utilize Access Manager and/or Sun OpenSSO for single sign-on, authentication, and policy options.

The following table describes available options for impacted products:

Communications Suite Product
Access Manager and OpenSSO Features Used by Communications Suite Product
Impact of Access Manager and OpenSSO Deprecation of Support
Current Alternatives and Solutions to Mitigate Impact
Convergence
Authentication, SSO (legacy and realm modes)
For new customers: no supported identity product for authentication and SSO
See: Create a Custom Convergence SSO Authentication Plug-in and Create a Custom Authentication Convergence Module
Instant Messaging
Authentication, SSO (legacy mode), Policy (legacy mode) No out-of-the-box OpenSSO solution
Delegated Administrator
Authentication, LDAP Access (legacy mode)
Access Manager Mode of LDAP access is no longer available
Switch to Direct LDAP mode

Support for OpenSSO will continue for existing customers while they migrate to other SSO and authentication solutions.

Note
OpenSSO Single Sign only works with Sun Enterprise GlassFish Server 2.1.1 Patch 7 and earlier patches. It does not work with Sun GlassFish Enterprise Server 2.1.1 Patch 12, the GlassFish version that is supported in this release.

Requirements for Communications Suite 7 Update 2

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:

  • To install a particular Communications Suite product, which other components do I need? The Communications Suite 7 Update 2 Component Dependencies table lists the individual Communications Suite products and shows the components on which they depend, including other Communications Suite components.

The following table shows the other products required by Communications Suite 7 Update 2. For information about requirements for these products, refer to the individual product's release notes.

Product Version Compatibility Requirements for Communications Suite 7 Update 2
Product Version Required or Optional?
Oracle Directory Server Enterprise Edition (formerly Sun Java System Directory Server) 5.x, 6.x, 7, 11gR1 Required. Use 6.3 or later. If doing a fresh installation, 11gR1 is recommended.
Oracle GlassFish Message Queue 4.4 Update 1 Optional. Communications Suite installer automatically installs Message Queue as a shared component for Messaging Server as well as for Indexing and Search Service.
Sun Java System Access Manager

See: Deprecated Support for Access Manager and Sun OpenSSO
7.1 Optional.
Sun GlassFish Enterprise Server 2.1.1 Required as the web container for Communications Suite 7 Update 2 components.

The following table shows the web container support by component product in this release.

Web Containers Supported in Oracle Communications Unified Communications Suite
Version 7 Update 2
Component Product GlassFish Server 2.1.1 Application Server 9.1 Update 2 Application Server 8 Application Server 7
Oracle iPlanet Web Server 7.0 Update 2
Web Server 6.1
Calendar Server 7 Update 2 Supported Not supported
Not supported
Not supported
Not supported
Not supported
Convergence 2 Supported Not supported Not supported Not supported Not supported Not supported
Delegated Administrator 7 Supported Supported
Supported
Supported
Supported
Supported
Indexing and Search Service 1 Update 3 Supported Not supported Not supported Not supported Not supported Not supported
Instant Messaging Server 9 Supported
Not supported
Not supported
Not supported
Not supported
Not supported

Notes:

The default installation paths for GlassFish Server 2.1.1. and Application Server 9 are the following:

Base installation directory: /opt/SUNWappserver
Domain directory: /opt/SUNWappserver/domains/domain1
Document root directory: /opt/SUNWappserver/domains/domain1/docroot

The default installation paths for Application Server 8 are the following:

Base installation directory: /opt/SUNWappserver/appserver
Domain directory: /var/opt/SUNWappserver/domains/domain1
Document root directory: /var/opt/SUNWappserver/domains/domain1/docroot

The following table lists the individual Communications Suite products and shows the components on which they depend.

Communications Suite 7 Update 2 Component Dependencies
Product Component Dependencies Required or Optional? Must Be on Local Host?
Calendar Server 7 Update 2
Directory Server 5.x, 6.x, 7, 11gR1
Recommended: 11gR1
Required. To store user/group and domain information for authentication, authorization, and email delivery. Not required.
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 7 Update 2 installer.
Required. To prepare the LDAP directory for Messaging Server. Not required. Must be on the same host as Directory Server.
  Oracle Database 11g Release 2 or MySQL Server 5.5.8 Required. To store Calendar Server database information. Not required.
  GlassFish Enterprise Server 2.1.1 Required. To act as the web container. Same host on which you install Calendar Server 7 Update 2 front end. You can use GlassFish Enterprise Server for Message Queue functions.
  Messaging Server Optional but an SMTP server is required. Not required.
  Delegated Administrator 7 Optional. To provision users of calendar services; to manage the directory schema. Not required.
Indexing and Search Service 1 Directory Server 5.x, 6.x, 7, 11gR1
Recommended: 11gR1
Required. To store user/group and domain information for authentication, authorization, and email delivery. Not required.
  Messaging Server 7 Update 4 Required. Not required.
  GlassFish Enterprise Server 2.1.1 To act as the web container. Same host on which you install front-end ISS components.
  GlassFish Message Queue 4.4 Update 1 To generate notifications. Not required.
Messaging Server 7 Update 4 Directory Server 5.x, 6.x, 7, 11gR1
Recommended: 11gR1
Required. To store user/group and domain information for authentication, authorization, and email delivery. Not required.
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 7 Update 2 installer.
Required. To prepare the LDAP directory for Messaging Server. Not required. Must be on the same host as Directory Server.
  Delegated Administrator 7 Optional. To manage user and group data; to manage the directory schema. Not required.
  Access Manager 7.1 (for SSO).

See: Deprecated Support for Access Manager and Sun OpenSSO.
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). Not required.
Instant Messaging 9 Directory Server 5.x, 6.x, 7, 11gR1
Recommended: 11gR1
Required. To store user, conference room, and news channel data. Not required.
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 7 Update 2 installer.
Required. To prepare the LDAP directory for Instant Messaging. Not required. Must be on the same host as Directory Server.
  Messaging Server 6 through 6.3, 7.0, 7 Update 1, 7 Update 2, 7 Update 3, 7 Update 4
Recommended: 7 Update 4
Optional. To support offline delivery of instant messaging alerts and chat archives as email messages. Not required.
  Calendar Server 7 Update 2
Recommended: Calendar Server 7 Update 2
Optional. To support Calendar Server event reminder notifications. See: Configuring Instant Messaging 9.0.1.4.0 Calendar Agent with Calendar Server 7. Not required.
  GlassFish Enterprise Server 2.1.1 web container
Optional. To provide IMPS Gateway and HTTP Gateway functionality. Must be on local host.

See: Deprecated Support for Access Manager and Sun OpenSSO.
Directory Server Setup Script (comm_dssetup.pl)
(Version bundled with Communications Suite 7 Update 2 installer)
Directory Server 5.x, 6.x, 7, 11gR1
Recommended: 11gR1
Required. To set up the LDAP directory, which the comm_dssetup.pl script updates with Communications Suite components' schema. Must be on local host.
Delegated Administrator 7 Directory Server 5.x, 6.x, 7, 11gR1
Recommended: 11gR1
To enforce unique values for mail attributes, you must install one of these releases:
Oracle Directory Server Enterprise Edition 11gR1
Oracle Directory Server Enterprise Edition 7
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. Not required.
  Directory Server Setup Script (comm_dssetup.pl)
You must use the version that is bundled with the Communications Suite 7 Update 2 installer.
Required. To prepare the LDAP directory for Delegated Administrator. Not required. Must be on the same host as Directory Server.
  Access Manager 7.1

See: Deprecated Support for Access Manager and Sun OpenSSO.
Optional. To provide authentication and authorization services when Delegated Administrator accesses the LDAP directory data. Must be on local host.
  Web container, one of:
Oracle iPlanet Web Server (at least Versions 6.1 or 7)
Application Server (at least Versions 7, 8, or 9)
Sun GlassFish Enterprise Server 2.1.1
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. Must be on local host.
  Messaging Server 6 through 6.3, 7.0, 7 Update 1, 7 Update 2, 7 Update 3, 7 Update 4
Recommended: 7 Update 4
Required to provide mail service for users and groups provisioned by Delegated Administrator. Not required if you do not provision mail users. Not required.
  Calendar Server 7 Update 2
(If you are deciding between Calendar Server 7 Update 2 and Calendar Server 6, Calendar Server 7 Update 2 is recommended.)
Required to provide calendar service for users and groups provisioned by Delegated Administrator 7. Not required if you do not provision calendar users. Not required.
  Calendar Server 6.x Required to provide calendar service for users and groups provisioned by Delegated Administrator 6.4 or greater. Not required if you do not provision calendar users. Not required.
Convergence 2 Patch 2
Convergence 2 Patch 3
Convergence 2 Patch 4

  For details about Convergence dependencies, see Convergence 2: Product Version Compatibility Requirements.  
Connector for Microsoft Outlook 7.3 Update 1
Messaging Server 6.3, 7
Required to provide mail service.  
  Calendar Server 7 Update 2, Calendar Server 6.3, 6.3.1
Required to provide calendar service.  
  Convergence 2 Patch 2
Convergence 2 Patch 3
Convergence 2 Patch 4

Optional (recommended). Convergence can be used to provide address book service, mail filters, and out-of-office message features.  
  Directory Server 5.2, 6.0 or higher
Required for Global Address List (GAL), a corporate address book service.  

Java Requirements

The following products require that you have Java 1.6 installed: GlassFish Enterprise Server 2.1.1, Calendar Server 7 Update 2, Indexing and Search Service 1 Update 3, Convergence, and Instant Messaging 9. The Communications Suite Installer installs Java 1.6 as a shared component.

If you switch to another Java version, download and install the latest JDK (not JRE) onto your system. For more information, refer to the GlassFish Enterprise Server 2.1.1 Release Notes.

Note
If you are enabling S/MIME, be sure to install the most recent Java plug-in patch, beginning with 1.6.0_29. For more details, see: http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html.

Network Security Services Requirements

Communications Suite 7 Update 2 requires the use of the shared security component. While the minimum version of Network Security Services (NSS) is 3.12.3 (patch rev -08), you should install the latest NSS patch 3.12.6 (patch rev -11), which improves security.

If you are using Directory Server 5, and you upgrade to NSS 3.11.7 on the Directory Server host, you need at least Directory Server 5.2 patch 6 due to an NSS incompatibility. See the IMPORTANT NOTE in the NSS patch.

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

Time Synchronization Requirements

Configure Network Time Protocol (NTP) to ensure that time is synchronized across your deployment.

Convergence 2: Product Version Compatibility Requirements (for Patch 2, Patch 3, and Patch 4)

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 7 Update 2 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:

Note that some of this information repeats the information shown in the Product Version Compatibility Requirements for Communications Suite 7 Update 2 table.

Additional Product Requirements for Convergence 2 (Patch 2, Patch 3, and Patch 4)
Product Version Required or Optional? Must Be on Local Host?
Oracle Directory Server Enterprise Edition Release 5.x, Release 6.x, Release 7.0, 11g Release 1 (11.1.1) or later

Note
VLV indexing causes crashes in Oracle Directory Server Enterprise Edition 7.0. This issue does not occur in Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1) or Oracle Directory Server Enterprise Edition 5.x or 6.x.
Required. For fresh installations, use Directory Server 11g Release 1 (11.1.1). For the recommended version to download, see Get the Software. Not required
Web Container Sun GlassFish Enterprise Server 2.1.1 Required. For the recommended version to download, see Get the Software. Required
Sun Java System Access Manager

See: Deprecated Support for Access Manager and Sun OpenSSO
7.1 Optional. Required only if you want to use Access Manager for authentication, SSO, or both.
Convergence supports both Access Manager Realm mode (the default) and Legacy mode for providing authentication and SSO.
Not required
Sun OpenSSO Enterprise

See: Deprecated Support for Access Manager and Sun OpenSSO
8.0
Optional. Required only if you want to use Sun OpenSSO Enterprise for authentication, SSO, or both. Not required
Indexing and Search Service
1 Update 3
Required to provide Attachment search in Convergence.
Not required

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

Communications Suite Component Requirements for Convergence 2 (Patch 2, Patch 3, and Patch 4)
Product Version Communications Suite Release Required or Optional? Must Be on Local Host?
Messaging Server – Webmail Server 7 Update 4 7 Update 2 (for MS 7 Update 4) Required to provide mail service in Convergence. Not required, but you should deploy Webmail Server on the same host as Convergence for scalability and performance.
Messaging Server – all other messaging components 6.3, 7, 7 Update 1, 7 Update 2, 7 Update 3, 7 Update 4

Note
If you enable flagged message sort in Convergence, ensure that wmap_version is equal to or greater than 9. This is available after the Messaging Server 7 Update 3 release in patch 137203-11 (Red Hat Linux), 137204-11 (SPARC 64-bit), and 137205-11 (Solaris x86 64-bit) or greater.

In addition, the imapd version (Messaging Server back-end host) must have the same patch or greater. Otherwise, flag sorting does not work.


5 (for MS 6.3)
6 (for MS 7.0)
6 Update 1 (for MS 7 Update 1)
6 Update 2 (for MS 7 Update 2)
7 (for MS 7 Update 3)
7 Update 1 (for MS 7 Update 4)
7 Update 2 (for MS 7 Update 4, latest patch)
Required to provide mail service in Convergence. Not required.
Calendar Server 6
(formerly Oracle Communications Calendar Server)

See: Calendar Server 6.3 Deprecation
6.3, patch level -44 or higher
5 + apply patch level -35
6 + apply patch level -35
6 Update 1 + apply patch level -35
6 Update 2
7
7 Update 1
Required to provide calendar service in Convergence if Calendar Server 7 is not installed.
Not required.
Oracle Communications Calendar Server (also known as Calendar Server 7, formerly Oracle Communications Calendar Server for CALDAV Clients) 7 Update 2 Patch 5

Note
(Beginning with Convergence 2 Patch 3)


7 Update 2 + apply minimum patch level 5
Required to provide calendar service beginning with Convergence 2 Patch 3.
Not required.
Oracle Communications Calendar Server (also known as Calendar Server 7, formerly Oracle Communications Calendar Server for CALDAV Clients)
7, 7 Update 1, 7 Update 2

Note
(Only applicable up to Convergence 2 Patch 2)


7 Update 2 (for Calendar Server 7 Update 2)
Required to provide calendar service up to Convergence 2 patch 2. Not required.
Instant Messaging 8, 9 7 Update 2 (for Instant Messaging 9) Required to provide Instant Messaging service in Convergence. No.
Directory Server Setup script, comm_dssetup.pl You must use the version that is bundled with the Communications Suite 7 Update 2 installer. 7 Update 2
Required. You must run comm_dssetup.pl on the hosts where Directory Server is installed. No.
Delegated Administrator 6.4, 7.0-0.00
You must use Delegated Administrator 7 with Calendar Server 7.
5, 6, or 6 Update 1, or 6 Update 2, 7, 7 Update 1, 7 Update 2 Optional. Not required.

Convergence 2 (Patch 2, Patch 3, and Patch 4) Compatibility with Connector for Microsoft Outlook, Address Book Store, and LDAP Schema
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 Instant Messaging service, you do not need Instant Messaging.
Product Version Communications Suite Release Required or Optional?
Connector for Microsoft Outlook 7.3, 7.3 Update 1 6 (for 7.3)
7 Update 1 (for 7.3 Update 1)
7 Update 2
Optional. You can deploy Connector for Microsoft Outlook with the same Communications Suite products and Directory Server as Convergence 2 (Patch 2, Patch 3, and Patch 4). End users of Outlook (configured using the Connector for Microsoft Outlook) can access the same Communications Suite services as those accessed through Convergence.
Personal Address Book store Can be configured by Convergence 2 Patch 2,
Convergence 2 Patch 3, or
Convergence 2 Patch 4
Not applicable. The Address Book store resides in an LDAP directory. You can configure Convergence 2 (Patch 2, Patch 3, and Patch 4) and Connector for Microsoft Outlook 7.3 to use the same Address Book store.
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 the now deprecated Communications Express.
Corporate Address Books:
Convergence can be configured to support one Corporate Address Book for each hosted domain.
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.
Not applicable. If you use Access Manager (Realm Mode or Legacy Mode) to provide 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.

See: Deprecated Support for Access Manager and Sun OpenSSO.

Memory and Disk Space Requirements


The following table shows the memory and disk space requirements for Communications Suite 7 Update 2 component products.

Memory and Disk Space Requirements for Communications Suite 7 Update 2
Product Disk Space RAM Other
Indexing and Search Service1 Update 3
Approximately 20 Mbytes must be free in /opt for /opt/sun/comms/jiss.
Roughly 20 percent of the Messaging Server store size will be required for the /var/opt/sun/comms/jiss directory. 1
4 Gbytes  
Calendar Server 7 Update 2 Approximately 20 Mbytes.    
Convergence Approximately 100 Mbytes of disk space for initial installation. 1 Gbyte minimum.  
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.  
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.
 
MySQL Server Approximately 650 Mbytes.    
JDK Approximately 450 Mbytes.    


1 In Indexing and Search Service, the /var/opt/sun/comms/jiss directory is divided into three subdirectories:

  • /var/opt/sun/comms/jiss/attach - Stores generated thumbnail images from attachments, which tends to consume 2 to 3 percent of the size of the mail store. Turning off the attachment store is a configurable option. Compared to the index store, this directory could probably reside on a slower disk.
  • /var/opt/sun/comms/jiss/logs - Stores log files.
  • /var/opt/sun/comms/jiss/index - Stores index files. This tends to take up about 15 percent of the size of the mail store and needs to be on a fast disk because it is frequently accessed.

Operating System Requirements

The following table shows the recommended platforms for Communications Suite 7 Update 2:

Operating System and Platform Support (Recommended for Communications Suite 7 Update 2)
Operating System CPU Comments
Solaris OS 10 SPARC, x64 Minimum recommended version: Solaris OS 10 9/10 (Update 9)
See Solaris 10 9/10 documentation for more information.
Oracle Linux 5.5 x64 See Oracle Linux Documentation for more information.
Red Hat Enterprise Linux 5 64-bit x64 See Red Hat Enterprise Linux documentation for more information.

The following table shows all the supported platforms for Communications Suite products.

Operating System and Platform Support (by Communications Suite Component)
Component Solaris OS 10 SPARC Solaris OS 10 x86
32-bit
Solaris OS 10 x86
64-bit
Red Hat Linux 4
32-bit
Red Hat Linux 4
64-bit
Red Hat Linux 5 Server (Update 3)
32-bit
Red Hat Linux 5 Server (Update 3)
64-bit
Oracle Linux 5.5
64-bit
XP (SP1 or higher) 2003
Terminal Server
Windows Vista Windows 7
Messaging Server  7 Update 4 32-bit
Not supported
Not supported
Not supported
Supported
Supported
Not supported
Supported
Supported
Not applicable
Not applicable
Not applicable
Messaging Server 7 Update 4 64-bit
Supported
Not supported
Supported
Not supported
Not supported
Not supported
Supported
Supported Not applicable
Not applicable
Not applicable
Calendar Server 7 Update 2
Supported
Not supported
Supported
Not supported
Not supported
Not supported
Supported
Supported Not applicable
Not applicable
Not applicable
Instant Messaging 9
Supported
Not supported
Supported
Not supported
Not supported
Not supported
Supported
Supported Not applicable
Not applicable
Not applicable
Convergence 2 (Patch 2, Patch 3, and Patch 4)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported Not applicable
Not applicable
Not applicable
Delegated Administrator 7
Supported
Supported
Supported
Supported
Supported
Not supported
Supported
Supported Not applicable
Not applicable
Not applicable
Connector for Outlook 7.3 Update 1
Not applicable
Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not
applicable
Supported
Supported
Supported
Indexing and Search Service 1 Update 3
Supported
Not supported
Supported
Not supported
Not supported
Not supported
Supported
Supported Not applicable
Not applicable
Not applicable
Dssetup 6.4
Supported
Supported
Supported
Supported Supported Not supported Supported
Supported Not applicable
Not applicable
Not applicable
Note
  • Recommended platforms are Solaris OS 10, Red Hat 5 64-bit, and Oracle Linux 5.5 64-bit.
  • No upgrade from previous major version forces a simultaneous upgrade of both the operating system and component.
  • An upgrade of a component does not force an upgrade of the operating system. An upgrade of the operating system forces an upgrade of the component.
  • Messaging Server, Calendar Server, Instant Messaging, and Delegated Administrator are no longer supported on HP-UX or Windows platforms.
  • Instant Messaging is not supported on Solaris OS 32-bit and Red Hat Linux 32-bit OS platforms.
  • The Communications Suite installer checks for required platform patches.
  • 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 Communications Suite representative.
Minimal Solaris OS Install Requirements for Indexing and Search Service

The following Solaris OS packages are required for Indexing and Search Service: SUNWgcmn, SUNWgtar, SUNWxcu4, SUNWj5rt. If remote installs are needed, SUNWwgetr and SUNWwgetu are also required. Confirm that they are installed by using pkginfo. Multi-machine deployments require SUNWapch2d, SUNWapch2r, and SUNWapch2u to be installed on indexing nodes. If they are not installed, install them from Solaris OS media before installing Indexing and Search Service.

The following Solaris JumpStart profile represents the minimal set of packages required for Indexing and Search Service.

##
## Minimum Required Software for Reduced Networking Support
## http://blogs.sun.com/gbrunett/entry/foundation_for_minimal_solaris_10
##
cluster SUNWCrnet

##
## Additional basic system services
##
# SSH Daemon, Tools and Dependencies
package SUNWgss add
package SUNWgssc add
package SUNWsshcu add
package SUNWsshdr add
package SUNWsshdu add
package SUNWsshr add
package SUNWsshu add
# NTP
package SUNWntpr add
package SUNWntpu add
# System Admin Tools (showrev)
package SUNWadmfw add
package SUNWadmfr add

##
## Indexing and Search Service Requirements
##
# GNU tar and Dependencies
package SUNWgcmn add
package SUNWgtar add
# XCU4 Utilities - ISS requires for awk and id
package SUNWxcu4 add
# Java 5 Run Time
package SUNWj5rt add
# wget - required only for remote ISS installs
package SUNWwgetr add
package SUNWwgetu add
Minimal Linux (Red Hat Linux and Oracle Linux) Installation Requirements for Indexing and Search Service

The Red Hat Linux and Oracle Linux installations can run on top of the install group @Base in your kickstart.cfg file. The following RPMs must be installed on Red Hat Enterprise Linux 5:

  • rpm-build
  • elfutils
  • elfutils-libs
  • compat-libstdc++-33
  • ntp
  • sharutils
  • compat-libstdc++-296
  • libxml2
  • xinetd

Multi-machine deployments require that the httpd RPM be installed on indexing nodes.

High Availability Support

Supported High-Availability Products
Product Supported Versions
Instant Messaging 9
  • Sun Cluster
    • SPARC: 3.1 Update 4, 3.2, 3.3
    • x86: 3.1 Update 4, 3.2, 3.3
    • Red Hat Linux: Not supported
    • Oracle Linux: Not supported
  • Veritas
    • SPARC: Not supported
    • x86: Not supported
    • Red Hat Linux: Not supported
    • Oracle Linux: Not supported
Messaging Server 7 Update 4
  • Sun Cluster
    • SPARC: 3.0, 3.1 Update 4, 3.2, 3.3
    • x86: 3.1 Update 4, 3.2 U1, 3.3
    • Red Hat Linux: Not supported
    • Oracle Linux: Not supported
  • Veritas
    • SPARC: 3.5, 4.0, 4.1, 5.0
    • x86: 3.5, 4.0. 4.1, 5.0
    • Red Hat Linux: 4.1, 5.0
    • Oracle Linux: 4.1, 5.5

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 does 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 table shows which browsers are supported for Communications Suite clients.

Supported Browser Versions for Convergence 2 Clients

Convergence 2 Patch 2 and Convergence 2 Patch 3

Browser Windows XP Windows 2000 Windows Vista Windows 7 Solaris Red Hat Linux Oracle Linux
Mac OS 10.x
Microsoft Internet Explorer 8.x
Not applicable 8.x, 9.x 8.x, 9.x Not applicable Not applicable Not applicable
Not applicable
Firefox 5, 6
5, 6 5, 6
5, 6
Not applicable Not applicable Not applicable
Not applicable
Safari Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable
5.x

Convergence 2 Patch 4

Browser Windows XP Windows 2000 Windows Vista Windows 7 Solaris Red Hat Linux Oracle Linux
Mac OS 10.x
Microsoft Internet Explorer 8.x
Not applicable 8.x, 9.x 8.x, 9.x Not applicable Not applicable Not applicable
Not applicable
Firefox 5, 6
5, 6 5, 6, 9
5, 6, 9
Not applicable Not applicable Not applicable
Not applicable
Safari Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable
5.x
Supported Browser Versions for Delegated Administrator Clients
Browser Windows XP Windows 2000 Solaris
Microsoft Internet Explorer 6.0 SP1 and 7.x 6.0 SP1 and 7.x Not applicable
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

Calendar Server 7 Update 2

Supported Clients for Calendar Server 7 Update 2
Client Version Notes
Apple iCal At least version 3 iCal 3 comes bundled with Mac OS 10.5.
Apple iPhone OS calendar client 3.x and 4.x Support for scheduling in iOS 4.x on iPhone, iPod touch, and iPad.
Lightning 0.8, 0.9, and 1 Lightning 0.8 supports basic CalDAV but does not support invitations so cannot be used for scheduling. Lightning 0.9, which does support CalDAV scheduling, is also supported by Calendar Server. Note that Thunderbird version 3 is the latest version.
Convergence 2
 
Connector for Microsoft Outlook 7.3 Patch 13  
eM   Desktop client for Windows (.NET) that supports CalDAV access. 1
Symbian   Symbian OS (mobile devices) support for CalDAV access. 1
Enterprise Tasks   eTask is a business application for the iPhone and iPod touch that uses the CalDAV protocol to view, edit, create, delete, and sync your tasks on the CalDAV server. 1


1 These clients have not officially been tested by Oracle. In general, any CalDAV compliant client should work.
Note: Communications Express is not a supported client in the Calendar Server 7 Update 2 release.

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 Messaging Server Administration Guide for more information. In addition, NFS can be supported on BSD-style mailboxes (/var/mail/) as well as for message stores. 
  • ZFS. Starting with Messaging Server 6.3, Messaging Server supports the ZFS file system. See Messaging Server ZFS Support for more information.
DNS Server and Messaging Server

Production deployments of Messaging Server require a high-quality caching DNS server on the local network. Messaging Server depends heavily on the responsiveness and scalability of the DNS server.

Additionally, your DNS configuration must clearly specify routes 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 must exist and contain the proper entries for reachable DNS servers and domain suffixes.
  • In the /etc/nsswitch.conf file, the hosts: line must have the files, dns, and nis keywords added. The keyword files must precede the keywords dns and nis. For example, the lines should look like this:
hosts:  files nis dns
ipnodes:  files nis dns

not like this:

hosts:  nis dns files
ipnodes:  nis dns files
  • The Internet host table in the /etc/hosts file should include only one line for the IP address of the host. The first host name must be a fully qualified domain name.

For example, the table should look like this:

123.45.67.89 budgie.west.sesta.com budgie loghost mailhost

not like this:

123.45.67.89 budgie.west.sesta.com
123.45.67.89 budgie loghost mailhost
Note
For releases up to Solaris OS 10 U3, you must add the fully qualified domain name not only to the /etc/hosts file, but also to the /etc/inet/ipnodes file. Otherwise, you receive an error indicating that your host name is not a fully qualified domain name. For Solaris OS 10 U4 and later releases, the contents of the /etc/inet/ipnodes and /etc/hosts files have been merged together into the /etc/hosts file. Applying kernel patch 120011-14 on any Solaris 10 system also performs this merge and removes the /etc/inet/ipnodes file.

Delegated Administrator

The following components, tools, and LDAP schema version are required for this release of Delegated Administrator:

  • Directory Server 5.x, 6.x, 7, or 11gR1. To enforce unique values for mail attributes, you must install one of these releases:
    • Oracle Directory Server Enterprise Edition 11gR1
    • Oracle Directory Server Enterprise Edition 7
    • 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:
    • Oracle iPlanet Web Server (at least Versions 6.1 or 7)
    • Application Server (at least Versions 7, 8, or 9)
    • Sun GlassFish Enterprise Server 2.1.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 Operating System Requirements

The Instant Messaging client has been removed from Instant Messaging 9.

Pidgin is the tested supported XMPP client. Ideally any XMPP-compliant client should work with Instant Messaging server.

The following table lists the supported server platforms:
Instant Messaging Support Server Platforms

Operating System Supported Platforms
Solaris Solaris OS 10 64-bit
Red Hat Linux Red Hat Linux 5, 64-bit
Oracle Linux Oracle Linux 5.5, 64-bit
Note:
Instant Messaging 9 requires Java version 1.6 or later.

Connector for Outlook

This section describes the requirements and recommendations for Connector for Microsoft Outlook.

The following operating systems are supported:

  • Microsoft Windows 7
  • Microsoft Windows 2000 (Service Pack 3 or later)
  • Microsoft Windows XP
  • Microsoft Windows 2003 Terminal Server
  • Microsoft Vista

The following versions of Microsoft Outlook are supported:

  • Outlook 2007
  • Outlook 2003
Note
Calendar Server customers who have deployed previous versions of Sun Java System Calendar Server need to engage with Oracle Consulting. A migration offering is available that enables data to be converted and migrated to the new format. This migration is required for Outlook because of changes in the storage and management of recurring events. No migration service is required for new customers of Calendar Server 6 2004Q2 and later.

Locating Patches for Communications Suite Products

Communications Suite Patches

For the most current list of required patches for Oracle Communications Unified Communications Suite, refer to Unified Communications Suite Component Patches. When operating system patch requirements change and patches to Communications Suite and other Oracle components become available, you can find updates in the My Oracle Support (MOS) database, initially as recommended patch clusters.

Communications Suite Installation and Upgrade Notes

Default Installation Directories and Ports

The Communications Suite installer installs product components under a single umbrella installation directory (INSTALLROOT). The default value for INSTALLROOT is /opt/sun/comms. Individual product components are installed in subdirectories under INSTALLROOT. For example, Calendar Server 7 is installed in a subdirectory called "davserver". There is no option to change the subdirectory, you can only change the INSTALLROOT. The subdirectory for each product can be found by running the "commpkg info --listPackages" command. A sample session for the "commpkg info --listPackages" command by platform can be found here.

  • The following table lists the default installation directories for other product components not installed by the Communications Suite installer.
Default Installation Directories
Product Default Directory Comment
Access Manager Solaris OS: /opt/SUNWam
Red Hat and Oracle Linux: /opt/sun/identity
 
Application Server Solaris OS and Red Hat Linux: /opt/SUNWappserver Contains Application Server utilities, executables, and libraries.
Application Server Domains Solaris OS and Red Hat Linux: /opt/SUNWappserver/domains Default area under which administrative domains are created.
Directory Server Core Solaris OS: /opt/SUNWdsee/ds6
Red Hat and Oracle 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 Solaris OS: /opt/SUNWdsee/dscc
Red Hat and Oracle Linux: /opt/sun/dscc
 
Directory Proxy Server
Solaris OS: /opt/SUNWdsee/dps
Red Hat and Oracle Linux: /opt/sun/dps
 
Directory Server Instance Directory
Solaris OS: /var/opt/SUNWdsee/dsins1
Red Hat and Oracle Linux: /var/opt/sun/dsins1
 
HADB Solaris OS: /opt/SUNWhadb
Red Hat and Oracle Linux: /opt/SUNWhadb
HADB install locations are not relocatable in Communications Suite installation.
  Solaris OS: /var/opt/SUNWhadb
Red Hat and Oracle Linux: /var/opt/SUNWhadb
HADB Repository Data and Log location.
  Solaris OS: /etc/opt/SUNWhadb
Red Hat and Oracle Linux: /etc/opt/SUNWhadb
HADB Management Agent config file.
  Solaris OS: /etc/init.d/ma-initd
Red Hat and Oracle Linux: /etc/init.d/ma-initd
HADB Management Agent startup script.
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
Red Hat and Oracle Linux:
/opt/sun/mq /etc/opt/sun/mq /var/opt/sun/mq
Monitoring Console Solaris OS: /opt/SUNWjesmc
Red Hat and Oracle 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 Solaris OS: /opt/SUNWwbsvr7
Red Hat and Oracle Linux: /opt/sun/webserver7
 
Web Server Instance Directory Solaris OS: /var/opt/SUNWwbsvr7
Red Hat and Oracle 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, 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 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 7 Uses the GlassFish Server ports  
MySQL Server 5.5.8
3306 Calendar Server 7 port
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
GlassFish Server 80 HTTP
  443 HTTPS
HADB 1862 Management Agent Port (JMX)
  15200 Default Portbase
Indexing and Search Service 52222 Util Service port (used over localhost only) for product internal communication
Instant Messaging 5222 Multiplexer port
  5269 Instant Messaging server-to-server port
  45222 Server port used for multiplexer communication
  55222
Gateway Connector Service For Facebook
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 and 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 Messaging Server 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, Communications Suite Compatibility Issues.

Problems Fixed in This Release of Communications Suite

This section lists problems fixed in this release of Communications Suite.

13491787

Add New Attributes and Object Classes for NAB

This bug was fixed in the DSsetup 6.4 Patch 24 release.

13946660

Define New Attributes for External Auth

This bug was fixed in the DSsetup 6.4 Patch 24 release.

12289905

comm_dssetup.pl pre-patch script - backup of files does not work

12303781

comm_dssetup.pl failed to find DS install directory

12303307

Need to add new attribute for calendar ACLs at domain level

12240710

comm_dssetup.pl may create duplicate or bad configuration in Directory Server 5.2x

12235005

deleted attribute not indexed

12235123

comm_dssetup.pl failed to modify comms-config for configuration only setup

Known Issues in Communications Suite

This section describes the known issues that exist in this release of Communications Suite. Specifically, this section describes installation and upgrade issues.

15964936

Upgrading to Instant Messaging Server 9 Patch 1 on Oracle Enterprise Linux fails because of an incorrect ksh path in the preupgrade and postupgrade scripts. The upgrade uses /usr/bin/ksh whereas the default ksh location is /bin/ksh.

Workaround
Create a symbolic link before you run the upgrade. For example:

12301307

MySQL cannot be installed in a sparse zone

MySQL can not be installed into a sparse zone. Workaround: install it on a whole root zone.

12290017

Access Manager 7.1 install fails if sun-ldapcsdk-libs 6.0.8 rpm is already installed on Red Hat 5
Access Manager 7.1 requires LDAPCSDK version 6.0.6, but the Comms 7 Update 2 installer installs version 6.0.8, causing the Access Manager installation to fail. First, manually remove LDAPCSDK 6.0.8 rpm, then install Access Manager 7.1.

JDK Upgrade Can Affect Other Products' Upgrade

The JDK upgrade can affect the upgrade of other products. For details, see Compatibility Issues.

12226371

The Communications Installer fails when a directory contains a space.
The commpkg utility fails when the current directory includes a space in its name.

Workaround: Do not use commpkg in a path that contains a space in its name.

No Oracle Bug DB ID, Bugster ID 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 7 Compatibility Issues.

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 enter 3.

You must upgrade and run comm_dssetup.pl before upgrading the other component products that require it. Otherwise the commpkg upgrade of component products might fail (for example, Delegated Administrator and Messaging Server).

Directory Server 5.2 Issues with NSS 3.12

With the NSS 3.12 patch, you must run Directory Server 5.2 Patch 6 or later. For more information, see: http://download.oracle.com/docs/cd/E19199-01/820-3003/.

Labels:
releasenotes releasenotes Delete
prerequisites prerequisites Delete
deprecatedam/opensso deprecatedam/opensso Delete
guide guide Delete
commsuite commsuite Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Oct 12, 2011

    Hi,

    The Whats New document mentions "Support for Oracle Database" for Calendar Server 7u2 but only MySQL is listed in the release notes.

    Is Calendar Server 7u2 supported with Oracle DB in a standalone and RAC configuration? RAC is important for high-availability but has potential performance implications.

    Thanks, Shane.

    1. Oct 12, 2011

      sar

      Hi Shane,

      Yes, 7u2 can use mysql 5.5.8 or Oracle DB 11gr2 as the database part of the backend.

      Have not tested RAC, but do not know of a reason it should not work.

      Scott

  2. Jan 30, 2013

    Hi Shane,

    Convergence 2 patch5 is not included in this document. Support for Google chrome browser may be added in this page.

    Thanks,

    Adi.

  3. Feb 01, 2013

    Hi Eric,

    12291560 SUNBT6940556 RFE : SUPPORT FOR GOOGLE CHROME BROWSER
    Chrome is now a supported browser. It may be added in this page in convergence patch 5 section.

    Thanks,
    Adi.

    1. Mar 02, 2013

      Added Chrome as supported browser in Patch 5.

      Regards,

      Joe

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


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