| Oracle® Beehive Deployment Guide Release 2 (2.0.1.8) Part Number E16645-06 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Deployment Guide Release 2 (2.0.1.8) Part Number E16645-06 |
|
|
PDF · Mobi · ePub |
This module provides overviews of the various Oracle and third-party components supported by Oracle Beehive and the related considerations for deploying them with the system.
This module contains the following topics:
Enabling Cross-Scheduling Between Oracle Beehive Deployments with iSchedule
Deploying Oracle Beehive with a Third-Party Single Sign-On Provider
Deploying Oracle Beehive with Oracle Real Application Clusters (Oracle RAC)
Deploying Oracle Beehive with Oracle Secure Enterprise Search 10g
Deploying Oracle Beehive with OracleAS Single Sign-On (OSSO)
Deploying Oracle Beehive with Oracle Universal Content Management (Oracle UCM)
Deploying Oracle Beehive with Oracle Information Rights Management (Oracle IRM)
Deploying Oracle Beehive with Oracle Universal Records Management (Oracle URM)
Deploying Oracle Beehive 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 regardless of which system a user resides. These tasks include scheduling and rescheduling meetings, responding to meeting requests, and searching for free/busy time of other users. Oracle Beehive 2.0 supports iSchedule interoperability between Oracle Beehive deployments only.
Enabling cross-scheduling between two different Oracle Beehive deployments includes the following steps:
Verify that the Oracle Beehive deployments are capable of sending and receiving HTTPS requests to and from each other. In some cases, Oracle Beehive is deployed behind a firewall that prevents HTTPS requests to be sent or received.
Use beectl to configure the iSchedule server for each Oracle Beehive deployment.
For complete details on the steps to enable cross-scheduling between Oracle Beehive deployments, see "Enabling Cross-Scheduling Between Oracle Beehive Deployments with iSchedule" in the Oracle Beehive Administrator's 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 or externally through integration with a supported LDAP-based user directory server. Oracle Beehive provides this flexibility for user account management through the User Directory Service (UDS).
For more information, including the steps to deploy Oracle Beehive with an external user directory, see "Integrating an External User Directory 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. 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 deploy 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—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 before 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)
Before installing Oracle Beehive and deploying it with Oracle Database, there are several required steps that you must take and a few recommended configuration steps you should consider. These steps will prepare your database environment for certain Oracle Beehive installation prerequisites and other requirements, and include:
Installing any patches required for your version of Oracle Database.
Setting the minimum values for certain Oracle Database initialization parameters, including java_pool_size, job_queue_processes, and processes.
Enabling the system's archiving capabilities.
If you plan to use a database that uses raw storage, then customizing Oracle Beehive's custom tablespaces script (beehive_custom_ts.sql).
For more information on these and other database-related steps, including details on how to perform these steps, refer to the Oracle Beehive Installation Guide for your operating system.
Notes:
For high availability deployments with a shared file system (or that leverage the filesystem_reference object within workspaces), all computers on which Oracle Beehive Application Tier instances and Oracle Database instances reside must have access to the file system reference paths at the same logical location. This shared access may be accomplished using a Network File System (NFS) server, symbolic links (symlinks), or another supported method. Typically, organizations will experience optimal performance if their file systems reside on computers other than those on which Oracle Beehive and Oracle Database reside. For information on managing file system directories deployed with Oracle Beehive, see "Managing File System Directories" in the Oracle Beehive Administrator's Guide.
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, contact your Oracle Support representative.
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.
If you plan to deploy Oracle Beehive with Oracle RAC, you should consider the pre- and post installation steps necessary to prepare your deployment for this option. These topics are covered in the following sections:
Before installing Oracle Beehive and deploying it with Oracle RAC, there are several required configuration steps that you must take and a few recommended steps that you should consider. These steps, which will prepare your high availability environment for certain Oracle Beehive installation prerequisites and other requirements, include:
Creating multiple logical database services.
Starting all of the logical database services that you created.
For deployments that require communications over Secure Sockets Layer (SSL), enabling Secure Oracle Notification Services (ONS) notification.
For more information on these and other pre-installation steps related to Oracle RAC, including details on how to perform these steps, refer to the Oracle Beehive Installation Guide for your operating system.
After installing Oracle Beehive, you must complete several post installation steps, including:
Retrieving your site and database object system identifiers (you'll need these for the post installation steps that follow).
Changing the value of the connect_string property by substituting the database service name with the global service name.
Updating the database system object and the local bootstrap file with the updated connect string value.
Modifying the database system object's configuration by specifying the database services you created and the ONS remote ports that are listening on your Oracle RAC nodes.
Creating an affinity service instance for each Oracle RAC node and adding the names of the affinity service instances to your Oracle Beehive configuration.
Committing (activating) the changes listed above to all Oracle Beehive instances.
Configuring your Oracle RAC nodes to receive secure ONS notifications (if they haven't been configured already).
For more information on these and other post installation steps related to Oracle RAC, including details on how to perform these steps, refer to the Oracle Beehive Installation Guide for your operating system.
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.
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 requires the completion of tasks (post installation) that are specific to Oracle Beehive and others that are specific to Oracle Secure Enterprise Search 10g. For example, your Oracle Beehive instance must be configured in Oracle Secure Enterprise Search 10g as a federated data source.
You use to the beectl utility to complete the tasks that are specific to Oracle Beehive, which include:
Creating a special user account that has administrator rights to the content managed by Oracle Beehive.
Configuring the Secure Enterprise Search service by entering the host and port number of your Oracle Beehive Application Tier instance, and by enabling the service.
Activating these changes using the activate_configuration command.
You use the Oracle Secure Enterprise Search Administration Tool to complete the tasks that are specific to Oracle Secure Enterprise Search 10g, which include:
Activating the identity plug-in on the Global Settings - Identity Management Setup page.
Specifying your Oracle Beehive database instance as a federated source.
Specifying the Uniform Resource Identifier (URI) of the Oracle Beehive Search Service.
Entering the credentials of the special user account that you created in Oracle Beehive.
For more information on deploying 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.
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 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 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 Beehive provides integration with Oracle URM through the Records Management Service.
Deploying Oracle Beehive with Oracle URM requires that you have an Oracle URM instance installed and configured before installing Oracle Beehive. After you install Oracle Beehive, you must complete several tasks, some of which you perform in Oracle Beehive and others in Oracle URM.
For more information, including the steps to deploy Oracle Beehive with an Oracle URM, see "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.
After installing Oracle Beehive, you should configure Oracle Beehive to use Oracle Wallet so that clients may access the system with a TLS connection. These steps include:
Enabling auto-login for Oracle Wallet.
Enabling Oracle Remote Method Invocation over SSL (ORMIS) for Oracle Wallet.
Configuring your Oracle Beehive server instance to use Oracle Wallet. If your deployment contains multiple instances, you will need to configure each instance separately.
For more information on the specific steps required to deploy Oracle Beehive with Oracle Wallet, refer to the Oracle Beehive Installation Guide for your operating system.
Oracle Beehive provides 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 users, and vice versa. Additionally, this solution allows IBM Lotus Domino users to leverage Oracle Beehive features without being migrated from IBM Lotus Domino.
For full details on deploying Oracle Beehive with IBM Lotus Domino Server, see "Integrating IBM Lotus Domino Server with Oracle Beehive" in the Oracle Beehive Integration Guide.
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 collaborate with Microsoft Exchange users beyond the limited capabilities of e-mail. Additionally, this solution allows Microsoft Exchange users to leverage Oracle Beehive features without being migrated from Microsoft Exchange.
For full details on deploying Oracle Beehive with Microsoft Exchange Server, see "Integrating Microsoft Exchange Server 2003 or 2007 with Oracle Beehive" in the Oracle Beehive Integration Guide.
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 or later.
Administrators manage the Oracle Beehive Virus Scanner through beectl. To manage Symantec Scan Engine, administrators should leverage the tools provided with that product.
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 |
|
