| 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 several concepts related to deploying Oracle Beehive, and contains the following topics:
This section provides an overview of several fundamental terms related to deploying Oracle Beehive, including:
A site is a collection of hardware in a specific geographic location and on which Oracle Beehive runs. A site can support multiple instances of a variety of components including Oracle Beehive servers and Oracle Database instances. Oracle Beehive currently supports only one site per deployment.
An instance is an Oracle Beehive server that is running on a computer in an Oracle home (ORACLE_HOME). An instance may respond to requests from a specific enterprise. Oracle Beehive supports one server instance on each computer.
An enterprise is a container for all of the users, groups, and resources that are a part of a single Oracle Beehive deployment. Typically, an enterprise includes all of the users, groups, and resources within a company. Oracle Beehive supports one enterprise for each deployment.
Enterprises are the containers for organizations, which are groups defined by a department, line of business, project, or other criteria.
The hierarchical relationship between enterprises and organizations in Oracle Beehive provides a logical structure for organizing users, groups, and resources. This structure also allows system administrators to more easily manage users, groups, and resources through their organizational associations.
Through the Coexistence Service, enterprises can integrate Oracle Beehive with other supported systems (or applications) so that certain data or functionality can be viewed or leveraged by users of both systems. This capability, referred to as Oracle Beehive collaboration coexistence, enables users to perform actions in one system, such as send e-mail messages or schedule meetings, and then view or receive the results of those actions in both systems. Currently, Oracle Beehive supports collaboration coexistence for Microsoft Exchange Server 2003, Microsoft Exchange Server 2007, and IBM Lotus Domino Server.
Through collaboration coexistence, Oracle Beehive provides enterprises a non-intrusive deployment approach that gives users a choice in how they access their data, either from Oracle Beehive or other clients, such as Microsoft Outlook (with Oracle Beehive Extensions for Outlook and connected to Microsoft Exchange). With this approach, users can be introduced to Oracle Beehive and its contextual environment without needing to immediately adopt and adapt to it. This approach also enables users of third-party systems to leverage Oracle Beehive functionality through their existing applications.
Oracle Beehive provides collaboration coexistence through the Oracle Collaboration Coexistence Gateway, which is a logical part of the Coexistence Service. The Oracle Collaboration Coexistence Gateway is an Oracle proprietary solution that provides the connection between Oracle Beehive and supported enterprise messaging solutions. For more information, refer to the following topics:
Oracle Beehive provides a flexible system deployment model that supports several distinct scenarios, including:
Oracle Beehive can be deployed on a single computer. In this case, the system can leverage a single Oracle Database instance that may be located on the same computer or on a different computer, although the latter is recommended. The system can also leverage a database cluster, located among several other computers, using Oracle Real Application Clusters (Oracle RAC).
Out of the box, Oracle Beehive provides all required user directory components so it can function as an independent system. It can also integrate with external corporate directories, if preferred or required.
Deploying Oracle Beehive on a single computer is suitable for test environments, development environments, and small production environments. Due to the lack of its failover capabilities, this deployment scenario is unsuitable in cases where very high levels of guaranteed services are required.
For more information on these scenarios and the considerations that each entail, see "Oracle Beehive Deployment Configurations" in the Oracle Beehive Deployment Guide.
Oracle Beehive supports deployments where multiple Oracle Beehive server instances are distributed across multiple computers. In this scenario, each computer hosts one Oracle Beehive server instance, which can be accessed through a load balancing router (LBR).
In this scenario, each instance runs all available services provided with Oracle Beehive. For example, if you have 5 computers, each with a Oracle Beehive server instance, you will 5 instances of the User Directory Service, the E-mail Service, and so forth. However, each service is instantiated as a single instance, or as a collection of all of the available instances.
This deployment scenario requires either a single database instance or an Oracle RAC cluster. From the user directory standpoint, you can integrate Oracle Beehive with an external corporate directory, or you can deploy it as a standalone system that leverages its own user directory capabilities and features.
Typically, a deployment with multiple Oracle Beehive instances across multiple computers is used in test environments, large production environments, or in situations where a higher level of service (high availability) is required. Test environments in this scenario can either be replicas of their associated production environments (recommended) or they may be scaled-down versions that mimic production environment topologies but with less hardware. Cloning of Oracle Beehive instances is supported to facilitate this process.
For more information on these scenarios and the considerations that each entail, see "Oracle Beehive Deployment Configurations" in the Oracle Beehive Deployment Guide.
Oracle Beehive supports deployments across networks zones, which are used to logically split the different layers of Oracle Beehive into the following areas:
Client Access Zone
Application Zone
Data Zone
Firewalls and multiple network zones are supported in this deployment scenario, providing increased security measures where user access to the system is required from corporate networks and the Internet. Network zones such as corporate intranets or demilitarized zones (DMZs) are also supported. Oracle Beehive services may have a dedicated system on which they run so that only the required services are exposed in the DMZ.
In this scenario, the Client Access Zone is separated from the other zones and their services, and resides in a separate network layer such as a DMZ. Firewalls may exist between the different zones, and a reverse proxy may also be present in the Client Access Zone. To provide higher levels of service (high availability), this deployment scenario may also consist of multiple computers each running an Oracle Beehive server instance. For more information, see "Deployments with Multiple Oracle Beehive Instances on Multiple Computers".
Typically, organizations deploy Oracle Beehive in this scenario for the increased security that it provides. This scenario protects core data (in the Data Zone) behind several layers (zones) and barriers. Similarly, this scenarios also protects application logic while seamlessly providing users needed access and functionality. Network connectivity layers are thin but, upon successful authentication, allow full access to available services.
For more information on these scenarios and the considerations that each entail, see "Oracle Beehive Deployment Configurations" in the Oracle Beehive Deployment Guide.
The Oracle Beehive platform provides a unified client implementation model that supports the following end-user client and device deployments:
Oracle Beehive Deployments with Oracle Beehive Extensions for Explorer
Oracle Beehive Deployments with Oracle Beehive Extensions for Outlook
Oracle Beehive Deployments with Oracle Beehive Team Collaboration
Oracle Beehive Deployments with Standards-based and Open Source Clients
Oracle Beehive Central is a Web-based client that is automatically deployed during the Oracle Beehive installation process. To access Oracle Beehive Central, users need only to launch a supported Web browser and enter the URL designated for Oracle Beehive Central for their deployment. Typically, this URL appears in the following format:
http://<Your-Server-Name>:<Port-Number>/bcentral/
Oracle Beehive Conferencing requires a client installation on the computers of individual users. Administrators can make the Oracle Beehive Conferencing client installation package available to users through Oracle Beehive Central, internal websites, or traditional desktop software delivery tools. Users can then download and install the Oracle Beehive Conferencing client on their computers.
The Oracle Beehive Web Conferencing Center is automatically deployed during the Oracle Beehive installation process. The Oracle Beehive Web Conferencing Center is an interface for users to join or start Oracle Beehive conferences. However, to join or start a conference, users need to first install the Oracle Beehive Conferencing client.
For more information on deploying Oracle Beehive Conferencing and Oracle Beehive Web Conferencing Center, see "Oracle Beehive Deployments with Oracle Beehive Conferencing" in the Oracle Beehive Deployment Guide.
Oracle Beehive Extensions for Explorer requires installation on the computers of individual users. To access, download, and install on users' computers, Oracle Beehive provides a download agent that administrators can make available to users on internal websites. Upon execution, the download agent connects users to Oracle Beehive, challenges them for their credentials, and enables them to download and install Oracle Beehive Extensions for Explorer. Users can delete the download agent once they complete the installation.
By default, Oracle Beehive provides the Oracle Beehive Extensions for Explorer installation package as a zip file (.zip) in the Device Management Application Repository. The contents of the zip file include a Windows executable installation program (.msi) and an Extensible Markup Language (XML) file that describes the installation program.
Oracle Beehive Extensions for Outlook requires installation on the computers of individual users. To access, download, and install on users' computers, Oracle Beehive provides a download agent that administrators can make available to users on internal websites. Upon execution, the download agent connects users to Oracle Beehive, challenges them for their credentials, and enables them to download and install Oracle Beehive Extensions for Outlook. Users can delete the download agent once they complete the installation.
Note:
In addition to the download agent distribution model, administrators can manage and distribute the Oracle Beehive Extensions for Outlook installation package through Microsoft Windows Server 2003 SP 2 for Windows Terminal Services. Oracle Beehive Extensions for Outlook can also leverage Windows Terminal Services once it is installed.By default, Oracle Beehive provides the Oracle Beehive Extensions for Outlook installation package as a zip file (.zip) in the Device Management Application Repository. The contents of the zip file include a Windows executable installation program (.msi) and an Extensible Markup Language (XML) file that describes the installation program.
Oracle Beehive also provides a language pack application module for Oracle Beehive Extensions for Outlook as well as a profile migration tool that enables users to migrate certain preferences and settings, such as LDAP settings and personal folders files (.pst), from previous Microsoft Outlook installations.
Oracle Beehive Team Collaboration is a Web-based client that is installed by default during the Oracle Beehive installation. No separate installation on users' computers or Oracle Beehive servers is required.
After Oracle Beehive is installed and configured, users can access and leverage Oracle Beehive Team Collaboration simply by launching a supported Web browser and entering the URL configured for the client. Typically, this URL appears in the following format:
http://<Your-Server-Name>:<Port-Number>/teamcollab/
Note:
As of Oracle Beehive Release 1.5, Oracle Beehive Webmail no longer needs to be installed in a separate Oracle home.Oracle Beehive Webmail is a Web-based client that requires installation on an Oracle Beehive server instance. The Oracle Beehive Webmail installation is bundled with the Oracle Beehive installation and can be performed as part of the latter's installation procedure. Once installed and configured on an Oracle Beehive server instance, users can access and leverage Beehive Webmail simply by launching a supported Web browser and entering the URL configured for the client. Typically, this URL appears in the following format:
http://<Your-Server-Name>:<Port-Number>/zimbra/
Oracle Beehive enables users of supported mobile devices to receive and send collaborative data. For administrators managing these users and their devices, Oracle Beehive provides many useful functions including the ability to create configuration files for client application installations, provision client applications, and upload device logs, among others.
Before being able to access their collaborative data from mobile devices, users must register their devices with the Oracle Beehive Device Management Service, and then download, install, and configure one or more supported clients based on their settings for their deployments.
For more information, refer to one or more of the following topics:
For information on the types of mobile clients and related features that Oracle Beehive supports, see "Mobile Device Families Supported by Oracle Beehive".
For information on the administrative tasks required to deploy mobile devices with Oracle Beehive, see "Oracle Beehive Deployments with Mobile Devices" in the Oracle Beehive Deployment Guide.
For the complete list of mobile devices that Oracle Beehive supports and for details on how to configure them, see Oracle Beehive Mobile Client Help at the following location:
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm
Oracle Beehive supports several standards-based protocols, enabling users to access Oracle Beehive information with commonly available clients. Typically, standards-based and open source clients require installation on the computers or devices of individual users. For details on how to install a particular client, please refer to the documentation provided with the client that you want to install.
For the complete list of standards-based and open source clients that Oracle Beehive supports, and for details on how to configure them, see Oracle Beehive Standards-based Client Help at the following location:
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/standards.htm
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
