9 Coexistence Notes

This module contains the following types of information regarding Oracle Beehive coexistence, which includes the Oracle Collaboration Coexistence Gateway:

• General Coexistence Notes

• Known Limitations and Workarounds with Coexistence

• Known Issues with Coexistence

General Coexistence Notes

This section contains general information about Oracle Beehive coexistence, and includes the following topic:

• Cloning Oracle Beehive Instances with Oracle Collaboration Coexistence Gateway

• Oracle Beehive Clients that Provide Time Management Functionality not Intended for Coexisting Third-Party Users

• Oracle Beehive No Longer Supports Team Collaboration-enabled Coexistence

Cloning Oracle Beehive Instances with Oracle Collaboration Coexistence Gateway

Bug 6729291. If you want to clone an Oracle Beehive instance that is configured with the Oracle Collaboration Coexistence Gateway, contact Oracle Support Services or your organization's Oracle representative.

Oracle Beehive Clients that Provide Time Management Functionality not Intended for Coexisting Third-Party Users

Oracle Beehive clients that support time management functionality, such as Oracle Beehive Extensions for Outlook, Oracle Beehive Webmail, and Oracle Beehive Team Collaboration, are not intended for coexisting third-party users. When used by coexisting third-party users, the time management functionality that these clients provide may not work as designed. For example, meetings created by third-party coexisting users may not appear in the calendars of users with accounts on Microsoft Exchange Server. Therefore, Oracle recommends that you do not deploy these clients for coexisting third-party users.

Oracle Beehive No Longer Supports Team Collaboration-enabled Coexistence

Oracle Beehive Release 1 (1.5.1.2) and later do not support the team collaboration-enabled coexistence configuration option and team collaboration-enabled users.

Known Limitations and Workarounds with Coexistence

This section contains information on known limitations and workarounds related to Oracle Beehive coexistence, and includes the following topics:

• Support for Microsoft Exchange Server 2003 Only

• Support for Microsoft Outlook 2003 Only

• Recurring Task Coexistence Not Supported

• Microsoft Exchange Server Subfolders Not Supported

Support for Microsoft Exchange Server 2003 Only

In Oracle Beehive, coexistence is supported for Microsoft Exchange Server 2003 (and all related service packs) only.

Support for Microsoft Outlook 2003 Only

In Oracle Beehive, coexistence is supported for Microsoft Outlook 2003 as the Microsoft Exchange Server client. Service packs 1 and 2, and Microsoft Outlook Web Access 2003, are also supported. No other Microsoft Exchange Server clients are supported.

Recurring Task Coexistence Not Supported

Recurring task coexistence is not supported in Oracle Beehive.

Microsoft Exchange Server Subfolders Not Supported

Oracle Beehive supports only the Microsoft Exchange Server Inbox, the main Calendar, and the Contacts folders. Subfolders are not supported.

Known Issues with Coexistence

This section contains information about issues with Oracle Beehive coexistence, and includes the following topics:

• Oracle Beehive Extensions for Outlook Meeting Categories Not Propagated

• Issues May Occur if Administrative Group and Routing Group Differ for Microsoft Exchange Server Host Computer

• Other Known Issues with Oracle Beehive Coexistence

Oracle Beehive Extensions for Outlook Meeting Categories Not Propagated

Bug 6376126. For multi-system coexistence users, Oracle Beehive Extensions for Outlook meeting categories are not shared with Microsoft Exchange Server.

Issues May Occur if Administrative Group and Routing Group Differ for Microsoft Exchange Server Host Computer

Bug 8880141. Oracle does not recommend installing the Oracle Coexistence Connector on any Microsoft Exchange Server host computer that belongs to a different administrative group and routing group. On such computers, the Oracle Collaboration Coexistence Gateway might not function correctly and Microsoft Exchange Server might not correctly route messages intended for Oracle Beehive users.

Note:

The issue described here does not apply to the Oracle Change Notification Service. Installing the Oracle Change Notification Service on such computers is fully supported.

Other Known Issues with Oracle Beehive Coexistence

The following table contains brief descriptions of other known issues with Oracle Beehive coexistence:

Table 9-1 Other Known Issues with Oracle Beehive Coexistence

Bug Number	Description
9259180	Recurring meeting rules do not synchronize with Oracle Beehive when modified by coexisting remote users
9282639	Notifications to coexisting remote users are not disabled
8872115	Status of coexisting Beehive users will not appear to coexisting remote users as being "reset" when the latter reschedule meetings
9310177	Coexisting Beehive users receive invitations to individual meeting instances if coexisting remote users invite them to existing recurring meetings
8856090	Coexisting Domino users receive two invitations when invited by coexisting Beehive users to existing meetings