| Oracle® Beehive Concepts Release 2 (2.0.1.8) Part Number E16644-06 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Concepts Release 2 (2.0.1.8) Part Number E16644-06 |
|
|
PDF · Mobi · ePub |
This module provides an overview of the various Oracle and third-party software components that organizations can integrate with Oracle Beehive. This module includes the following topics:
Calendar Integration Between Oracle Beehive Deployments with iSchedule
Oracle Beehive Integration with Third-Party Single Sign-On Providers
Oracle Beehive Integration with Oracle Information Rights Management (Oracle IRM)
Oracle Beehive Integration with Oracle Real Application Clusters (Oracle RAC)
Oracle Beehive Integration with Oracle Secure Enterprise Search 10g
Oracle Beehive Integration with OracleAS Single Sign-On (OSSO)
Oracle Beehive Integration with Oracle Universal Content Management (Oracle UCM)
Oracle Beehive Integration with Oracle Universal Records Management (URM)
Oracle Beehive Integration with Microsoft Exchange Server 2003 or 2007
Oracle Beehive supports the Internet Calendar Scheduling Protocol (iSchedule). iSchedule enables interoperability between different calendaring and scheduling systems. With iSchedule, users in connected systems can perform common calendaring and scheduling tasks, such as scheduling and rescheduling meetings, responding to meeting requests, and searching for free-busy time of other users, regardless of which system a user resides.
Oracle Beehive 2.0 supports iSchedule interoperability between Oracle Beehive deployments only. For more information on integrating calendaring and scheduling between Oracle Beehive deployments, see "Enabling Cross-Scheduling Between Oracle Beehive Deployments with iSchedule" in Oracle Beehive Deployment Guide.
Oracle Beehive provides flexible user account management and provisioning by supporting both native and system-external user directory options. With Oracle Beehive, administrators can manage user account data either natively in Oracle Beehive itself or externally through integration with a supported LDAP-based user directory server. Oracle Beehive, which provides this flexibility for user account management through the User Directory Service (UDS), supports the following user directory servers:
In addition to configuring UDS for integration with these supported external user directory servers, administrators have the option to configure the Authentication Service to leverage the same external users directories for authentication attributes such as user names and passwords.
To learn more about how Oracle Beehive integrates with external user directories, see the following topics:
When you integrate Oracle Beehive with an external user directory server, the external directory becomes the master source for user account attributes. In other words, the external directory is the point of reference or source of truth for those attributes. All external user directory servers that integrate with Oracle Beehive are considered master sources.
Oracle Beehive supports user account mastering on a field by field basis. Mastering user accounts refers to managing account attributes in a specific location, such as an external user directory. However, even when an external user directory is present and is used as a master source, it is possible to master certain user account attributes in UDS. In fact, this is a requirement for certain Oracle Beehive-based attributes, such as voicemail passwords and instant messaging user names.
Prior to integrating Oracle Beehive with an external user directory, administrators must import user account data from the external user directory to UDS. This is a straightforward process that involves creating two XML files. The first file contains the mappings between the user account attributes in the external user directory and UDS. The second file contains the list of user accounts that will be synchronized between the external user directory and UDS.
For more information, including the steps to integrate an external user directory with Oracle Beehive, see "Integrating an External User Directory with Oracle Beehive" in the Oracle Beehive Integration Guide.
To maintain data consistency between Oracle Beehive and an external user directory, UDS synchronizes with the external user directory server at regular intervals. The default interval period is 30 seconds, although Oracle Beehive administrators can change this setting to suit their organizations' needs. Every time UDS synchronizes with an external user directory server, it obtains only the records that changed during the previous interval. UDS then updates its records accordingly.
Note:
The directory synchronization process is unidirectional, that is, changes in an external user directory are imported into UDS only. User account data in UDS is never promoted to external user directories.Out of the box, Oracle Beehive is configured with the Java Single Sign-On Service (JSSO), which provides a single sign-on experience for users across all Oracle Beehive Web-based applications. Oracle Beehive also supports integration with OracleAS Single Sign On, and provides a Pluggable Authentication Framework for custom integration with third-party single sign-on providers.
To integrate Oracle Beehive with a third-party single sign-on provider, such as IBM Tivoli Access Manager WebSEAL, you must create and deploy a Java plug-in through the Oracle Beehive Pluggable Authentication Framework. For more information, see "Oracle Beehive Pluggable Authentication" on the Oracle Beehive page on Oracle Technology Network. This page provides a sample plug-in for redirect-style single sign-on providers and another sample plug-in for IBM Tivoli Access Manager WebSEAL, which is a reverse proxy-style single sign-on provider.
Oracle Beehive stores all of its data such as collaborative, configuration, and audit data, as well as its log archives in Oracle Database. Every Oracle Beehive deployment must have at least one Oracle Database instance installed and available prior to installing Oracle Beehive.
Oracle Beehive supports the following Oracle Database 11g releases:
Oracle Database 11g Release 1 (11.1.0.7)
Oracle Database 11g Release 1 (11.2.0.1)
Note:
Oracle Beehive supports the option to deploy a secondary database instance dedicated to the system's search functions. This option should be considered in large deployments as it may provide significant performance improvements for search-related features. For more information on this option, please contact Oracle Support.Oracle Information Rights Management (Oracle IRM) is an information security solution that uses encryption to seal content. Through the Information Rights Management (IRM) Service, Oracle IRM, and policies created by administrators, Oracle Beehive controls access to sealed content, ensuring that only authorized users can open and use it. This control pertains not only to content saved locally on users' computers, but also extends to content distributed outside the firewall through e-mail and other means.
For more information on integrating Oracle Beehive with Oracle IRM, see "Integrating Oracle Information Rights Management with Oracle Beehive" in the Oracle Beehive Integration Guide.
Oracle Beehive supports Oracle Real Application Clusters (Oracle RAC). With Oracle RAC, you can deploy Oracle Database across multiple computers so that they each share a single physical database. This is useful for deployments that need to achieve high availability and scalability, especially on low cost hardware. With Oracle RAC, the number of computers across which Oracle Database is distributed is invisible to Oracle Beehive and its users.
Oracle Beehive supports affinity toward Oracle RAC database instances, providing more efficient user sessions and balanced database workloads. Currently, database instance affinity is supported by the E-mail Service and the Event Framework only. With the E-mail Service, affinity is based on the instance associated with a user's Internet Message Access Protocol (IMAP) session. Support for other Oracle Beehive services and affinity types will be provided in later releases.
For more information on integrating Oracle Beehive with Oracle RAC, see Oracle Beehive Deployment Guide.
Oracle Beehive maintains its own optimized search index enabling users to perform comprehensive searches across all Oracle Beehive artifacts. At the enterprise level, however, other information repositories might exist and contain information that users need. For example, depending on their roles, knowledge workers might need to find expense reports or purchase requisitions stored outside of Oracle Beehive. This level of search across all enterprise information repositories is provided by Oracle Secure Enterprise Search 10g.
Oracle Secure Enterprise Search has been designed as a stand-alone enterprise search solution. It incorporates best-in-class indexing, crawling, and security capabilities to create a reliable and comprehensive search solution for any organization. To leverage this powerful option, organizations can integrate Oracle Beehive with Oracle Secure Enterprise Search 10g. With this integration, Oracle Beehive becomes a federated data source of Oracle Secure Enterprise Search 10g.
For more information on integrating Oracle Beehive with Oracle Secure Enterprise Search 10g, see "Integrating Oracle Secure Enterprise Search 10g with Oracle Beehive" in the Oracle Beehive Integration Guide.
Out of the box, Oracle Beehive is configured with the Java Single Sign-On Service (JSSO), which provides a single sign-on experience for users across all Oracle Beehive Web-based applications. In addition, you may register Oracle Beehive as a partner application with OracleAS Single Sign-On (OSSO), which means that you may delegate the authentication function to the single sign-on server. For more information on this option, see "Configuring Single Sign-On with Oracle Beehive" in the installation guide for your operating system.
Oracle Universal Content Management (Oracle UCM) enables users to view and collaborate on content through its document management, Web content management, digital asset management, and records retention capabilities. Through integration with Oracle UCM, Oracle Beehive enables users to leverage these powerful capabilities. Oracle Beehive supports Oracle UCM 10g Release 3 or later.
For more information on how to integrate Oracle Beehive with Oracle UCM, see "Integrating Oracle Universal Content Management with Oracle Beehive" in the Oracle Beehive Integration Guide.
Oracle Universal Records Management (Oracle URM) enables organizations to manage their records and retention policies, disposition processes, and litigation holds or freezes in a central repository known as a Universal Records Management (URM) server. Organizations can then apply those policies, dispositions, and holds to content stored in other systems, such as Oracle Beehive. Oracle Collaboration Suite provides integration with Oracle URM through the Records Management Service.
For more information on integrating Oracle Beehive with Oracle URM, refer to "Integrating Oracle Universal Records Management with Oracle Beehive" in the Oracle Beehive Integration Guide.
Oracle Wallet is a component of Oracle Application Server 10g that provides important authentication capabilities. A wallet is a password-protected container that stores authentication and signing credentials, including private keys, certificates, and trusted certificates, all of which are used by Secure Sockets Layer (SSL) for strong authentication.
Oracle Wallet provides an encrypted Transport Layer Security (TLS) communication channel that some Oracle Beehive services require, such as the XMPP Service. Oracle Wallet is also required when configuring Oracle Beehive Web Services for Security Assertions Markup Language (SAML) authentication.
For more information on integrating Oracle Beehive with Oracle Wallet, see Oracle Beehive Deployment Guide.
Oracle Beehive provides its voicemail and fax functionality through integration with Cisco Voice Gateway. This includes enabling users to access and manage voice messages from a telephone or as audio files in their e-mail inboxes.
For more information, including the steps to deploy Oracle Beehive Voicemail with Cisco Voice Gateway, see "Integrating Cisco Voice Gateway with Oracle Beehive" in the Oracle Beehive Integration Guide.
Oracle Beehive supports integration with IBM Lotus Domino Server through the Oracle Collaboration Coexistence Gateway. The Oracle Collaboration Coexistence Gateway is an Oracle proprietary solution that allows Oracle Beehive users to schedule meetings with IBM Lotus Domino Server users, and vice versa. Additionally, this solution allows IBM Lotus Domino Server users to leverage Oracle Beehive features without being migrated from IBM Lotus Domino Server.
This section includes the following topics:
Types of Users Supported by the Oracle Collaboration Coexistence Gateway for IBM Lotus Domino Server
Oracle Collaboration Coexistence Gateway Concepts for IBM Lotus Domino Server
For details on how to integrate IBM Lotus Domino Server with Oracle Beehive, refer to "Integrating IBM Lotus Domino Server with Oracle Beehive" in the Oracle Beehive Integration Guide.
This section provides details on the types of users that Oracle Collaboration Coexistence Gateway supports for IBM Lotus Domino Server, including:
A Lotus Notes Foreign User is a user who does not have a mailbox in the Lotus Domino environment, free/busy information on the Lotus Domino environment, and does not belong to the Domino server domain (in other words, the user comes from a different domain). This user is defined in the Lotus Domino server directory or as part of a contact list of Lotus Notes users.
The only way to distinguish a Foreign User from other users is through the e-mail address domain. For example, a Lotus Notes Foreign User could be an Oracle Beehive user.
A Coexisting Domino user is a user who resides on IBM Lotus Domino Server. Similar to Oracle Beehive users, a Coexisting Domino user can collaborate with and view free/busy information of coexisting Oracle Beehive users.
Additionally, coexisting Domino users can also perform the following tasks:
Collaborate with other users on the same system.
View free/busy information of Oracle Beehive users.
Collaborate with Oracle Beehive users as though they were users native to Lotus Domino.
Use Oracle Beehive clients, such as Oracle Beehive Team Collaboration and Oracle Beehive Conferencing, and supported instant messaging clients.
A non-coexisting Domino user resides solely on an existing third-party system. A non-coexisting Domino user is not aware of the existence of Oracle Beehive. No coexistence solution is provided to this group of users. Although these users may exist in the Oracle Beehive Global Address List, an Oracle Beehive user cannot view the free/busy information of these users or schedule these users. All communication between Oracle Beehive users and non-coexisting Domino user on third-party systems is accomplished using e-mail.
A non-coexisting Domino user can perform the following tasks:
Collaborate with other users on the same system.
View the free/busy information of Oracle Beehive users.
Collaborate with Oracle Beehive users by e-mail.
Coexisting Beehive users have Oracle Beehive as messaging and scheduling system. Coexisting Beehive users can perform the following tasks:
Use all available Oracle Beehive services.
Collaborate with other Oracle Beehive users.
Collaborate with coexisting third-party users as if they were Oracle Beehive users.
This section defines Oracle Collaboration Coexistence Gateway concepts that are specific to IBM Lotus Domino Server.
This section includes the following topics:
The Coexistence Connector requires that the following five databases be created within the IBM Lotus Domino Server system:
The first database is called Coex Mail Box and is derived from a Domino Mail Router Mailbox template. This database is used by Domino because it routes all outgoing messages destined to coexisting Oracle Beehive users.
The second database is called Coex Import Box and is derived from a Domino Mail Router Mailbox template. This database is used by Domino as it routes all outgoing import request messages destined to coexisting Oracle Beehive users.
The third database is called Oracle Free/Busy database and is derived from a Domino Local free time info template. This database is used by the Coexistence Connector to cache all the free/busy information of the coexisting Oracle Beehive user so that the Domino server task can retrieve the free/busy information of the Oracle Beehive user and return it to the Lotus Notes clients.
The fourth database is called Oracle Coexistence Storage database and is used to store all coexistence-related configuration information.
The fifth database is the Coex Bad Mailbox and it contains failed messages destined to Oracle Beehive that will no longer be retried.
Lotus Domino is a message-based system. Both e-mail and calendaring information are classified as messages and get routed through the same components in the system. The only noticeable difference between calendaring messages and e-mail messages is in the way they are interpreted by the Lotus Notes client.
Figure 9-1 outlines how e-mail and calendaring messages are routed in the Lotus Domino system.
Figure 9-1 Lotus Domino System: Handling E-mail and Calendar Information
When a Lotus Notes user invites a foreign user (a coexisting Oracle Beehive user) to a meeting, the Lotus Domino server redirects the message to the database referenced in the foreign domain document (which is represented in the Figure by CoexCMail.box). The Coexistence Connector gets notified when new messages arrive in that database and it then processes them and sends them to the Oracle Beehive user.
If the message in question is a calendar invitation, then the Coexistence Connector will send it to Beehive by CoexML. If the message is an e-mail message, then the Coexistence Connector will re-route it back to the Lotus Domino server by the Mail.box database and have the Domino server send it by SMTP.
Figure 9-2 shows how the Collaboration Coexistence Connector handles e-mail and calendar information.
Figure 9-2 Collaboration Coexistence Connector: Handling E-mail and Calendar Information
Oracle Beehive supports integration with Microsoft Exchange Server 2003 or 2007 through the Oracle Collaboration Coexistence Gateway. The Oracle Collaboration Coexistence Gateway is an Oracle proprietary solution that allows Oracle Beehive users to schedule meetings with Microsoft Exchange Server users, and vice versa. Additionally, this solution allows Microsoft Exchange Server users to leverage Oracle Beehive features without being migrated from Microsoft Exchange Server.
This section discusses Oracle Beehive coexistence as it relates to Microsoft Exchange Server, and includes the following topics:
Features Provided by Oracle Beehive Collaboration Coexistence
Overview of the Oracle Collaboration Coexistence Gateway for Microsoft Exchange Server
For details on how to integrate Microsoft Exchange Server 2003 or 2007 with Oracle Beehive, see "Integrating Microsoft Exchange Server 2003 or 2007 with Oracle Beehive" in the Oracle Beehive Integration Guide.
Oracle Beehive collaboration coexistence with Microsoft Exchange Server enables users of both systems to collaborate transparently with each other beyond the limited capabilities of e-mail. This includes the ability to leverage the following features through clients of both Oracle Beehive and Microsoft Exchange Server:
Time management: Users can create, view, and manage meeting entries through Oracle Beehive or Microsoft Exchange Server. This includes inviting (to meetings) users hosted by either system.
Task management: Users can create, assign, view, and manage tasks in both Oracle Beehive and Microsoft Exchange Server. This includes assigning tasks to users hosted by either system.
E-mail management: Users can create, view, and manage e-mail messages through Oracle Beehive or Microsoft Exchange Server.
Contact management: Users can create, view, and manage contacts through Oracle Beehive or Microsoft Exchange Server.
Oracle Beehive coexistence provides a non-intrusive configuration approach, giving users a choice in how they access their data, either natively from Oracle Beehive or from Microsoft Exchange Server. With this approach, users can be introduced to Oracle Beehive and its contextual environment without needing to immediately adopt and adapt to it. It is also possible to configure Oracle Beehive coexistence so that users of Oracle Beehive and Microsoft Exchange Server can collaboratively schedule meetings, view free/busy information, and receive post-invitation event updates without being aware of each other's systems.
Enterprises can leverage Oracle Beehive collaboration coexistence with Microsoft Exchange Server by configuring their users in the following manner:
Note:
This collaboration coexistence option requires the installation of the Oracle Collaboration Coexistence Gateway on Microsoft Exchange Server. For more information, see "Overview of the Oracle Collaboration Coexistence Gateway for Microsoft Exchange Server".Cross-scheduling coexistence with Microsoft Exchange Server enables two distinct user sets to schedule meetings with one leveraging Microsoft Exchange Server through Microsoft Outlook, and the other leveraging Oracle Beehive through a supported client. This includes cross-scheduling with visibility of free/busy information for users of both systems.
Oracle Beehive coexistence with Microsoft Exchange Server supports the following user types:
A Microsoft Active Directory contact is a user who does not have a Microsoft Exchange Server mailbox, and who resides on a different system. For example, an Active Directory contact could be an Oracle Beehive user.
A Microsoft Active Directory user resides on Microsoft Exchange Server and has an Exchange mailbox. The Exchange mailbox can contain e-mail, calendar, and task items, among other objects.
A coexisting third-party user resides on a third-party system, such as Microsoft Exchange Server, but has the ability to schedule meetings with and view free/busy information of Oracle Beehive users. Conversely, Oracle Beehive users are able to schedule meetings with and view free/busy information of coexisting third-party users. These users can perform the following tasks:
Collaborate with other users on the same system
View Oracle Beehive users as users native to Microsoft Exchange Server
Collaborate with Oracle Beehive users as if they are users native to Microsoft Exchange Server
A non-coexisting third-party user resides solely on an existing third-party system. These users are not aware of the existence of Oracle Beehive. No coexistence solution has been provided to this group of users. Although these users may exist in the Oracle Beehive Global Address List, an Oracle Beehive user cannot view the free/busy information or cross-schedule with these users. All communication between Oracle Beehive users and non-coexisting third-party users is accomplished using e-mail. Non-coexisting third-party users can perform the following tasks:
Collaborate with other users on their systems
View Oracle Beehive users as external users
Collaborate with Oracle Beehive users through e-mail
An Oracle Beehive user leverages Oracle Beehive for all content types and can perform the following tasks:
Use all available Oracle Beehive services
Collaborate with other Oracle Beehive users
Collaborate with coexisting third-party users as if they are Oracle Beehive users
The Oracle Collaboration Coexistence Gateway is an Oracle proprietary solution that enables Oracle Beehive collaboration coexistence by providing the connection between Oracle Beehive and Microsoft Exchange Server. Oracle Collaboration Coexistence Gateway contains the following components:
These components update and propagate data between Oracle Beehive and Microsoft Exchange Server, which may include meeting entries, contacts, e-mail messages, and folders. Figure 9-3 depicts these components as they relate to the Oracle Collaboration Coexistence Gateway architecture, which includes Microsoft Exchange Server, third-party software, and related information flows.
Figure 9-3 Oracle Collaboration Coexistence Gateway Architecture
The Oracle Beehive Coexistence Service runs in an OC4J container that is installed with Oracle Beehive. The service is automatically enabled when Oracle Beehive is installed and it is required in order to implement the Oracle Collaboration Coexistence Gateway. The Oracle Beehive Coexistence Service relays data between the Oracle Connector for Exchange and Oracle Beehive.
The Oracle Connector for Exchange is an Oracle Collaboration Coexistence Gateway service that is responsible for the following tasks:
Converting outgoing messages to an accepted Oracle Beehive format and dispatching the delivery to the Oracle Communication Service
Delivering Oracle Beehive meeting requests, responses, and cancellations to Microsoft Exchange users
Updating free/busy information
The Oracle Communication Service plays a vital role in facilitating the exchange of information between Oracle Beehive and Microsoft Exchange Server. The Oracle Communication Service is responsible for the transmission of all messages between the two systems and distinguishes between different message types, including e-mail messages, calendar entries, and contacts.
The Oracle Change Notification Service for Exchange is the Oracle Collaboration Coexistence Gateway service that is responsible for the following tasks:
Detecting changes to the personal data (e-mail, contacts, and calendar events) of team collaboration-enabled users
Detecting changes to free/busy information for third-party coexisting users
Dispatching changes to Oracle Connector for Exchange
Oracle Beehive supports integration with Symantec Scan Engine. This provides another option for organizations that want to leverage existing Symantec Scan Engine instances or that want anti-virus features beyond what the Oracle Beehive Virus Scanner provides. Through this integration, organizations can leverage the scan types and modes that Symantec Scan Engine provides, as well as its artifact and message filtering capabilities. Oracle Beehive supports Symantec Scan Engine version 5.1.2 and later.
For more information on the anti-virus capabilities of the Oracle Beehive Virus Scanner, see "Anti-virus Support in Oracle Beehive". For more information on integrating Oracle Beehive with Symantec Scan Engine, see "Integrating Symantec Scan Engine with Oracle Beehive" in the Oracle Beehive Integration Guide.
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
