Oracle Beehive Deployment Guide, Release 2 (2.0.1.8)

Release 2 (2.0.1.8)

E16645-06

Contents

List of Figures

List of Tables

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Overview of Deploying Oracle Beehive

- Overview of Oracle Beehive

- How to Use This Guide to Deploy Oracle Beehive

- Prerequisites for Deploying Oracle Beehive

- Deploying Oracle Beehive in Stages

- Oracle Beehive Deployment Stage #1: Create a Deployment Plan

- Oracle Beehive Deployment Stage #2: Research and Knowledge Gathering

- Oracle Beehive Deployment Stage #3: Requirements Gathering

- Oracle Beehive Deployment Stage #4: Install and Configure the System

- Oracle Beehive Deployment Stage #5: Customize the System

- Oracle Beehive Deployment Stage #6: Evaluate and Test the System

- Oracle Beehive Deployment Stage #7: Training for Developers, Administrators, and End Users

- Oracle Beehive Deployment Stage #8: Launch the System into Production

- Oracle Beehive Deployment Stage #9: On-going Maintenance and Administration

- Key Terms and Concepts for Deploying Oracle Beehive

- Servers and Nodes

- Network Zones

- Demilitarized Zones (DMZs)

- Installations

- Services

- Instances

- Sites

- Enterprises and Organizations

2 Oracle Beehive Architecture

- Overview of the Oracle Beehive Tiers

- Overview of the Client Tier

- Overview of the Application Tier

- Overview of the Data Tier

- Overview of the Ancillary Tier

- Connections Between Oracle Beehive Tiers

- Overview of the Database Access Framework

- Overview of the Beehive Transport Infrastructure

- Overview of the Event Framework

- Overview of Oracle Beehive Schemas

- Code Schema

- Data Schema

3 Tools for Deploying Oracle Beehive

- The Oracle Beehive Install Wizard

- The Oracle Beehive Config Wizard

- Oracle Beekeeper

- The Oracle Beehive beectl Utility

- Oracle Enterprise Manager Grid Control

4 Deploying Oracle Beehive with Other Software Components

- Enabling Cross-Scheduling Between Oracle Beehive Deployments with iSchedule

- Deploying Oracle Beehive with an External User Directory

- Deploying Oracle Beehive with a Third-Party Single Sign-On Provider

- Deploying Oracle Beehive with Oracle Database

- Deploying Oracle Beehive with Oracle Real Application Clusters (Oracle RAC)

- Preparing to Deploy Oracle Beehive with Oracle RAC

- Post installation Steps for Deploying Oracle Beehive with 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 Oracle Wallet

- Deploying Oracle Beehive with Cisco Voice Gateway

- Deploying Oracle Beehive with IBM Lotus Domino Server

- Deploying Oracle Beehive with Microsoft Exchange Server 2003 or 2007

- Deploying Oracle Beehive with Symantec Scan Engine

5 Network Considerations for Oracle Beehive

- Basic Network Considerations

- Network Considerations for Small Deployments

- Access and Security Considerations

- Traffic Considerations

- Internal Traffic

- External Traffic

- Other Network Considerations for Deploying Oracle Beehive

6 Architectural Considerations for Oracle Beehive

- Basic Architectural Considerations

- Access Considerations

- Capacity Considerations

- Recovery Considerations

- Availability Considerations

- Scalability Considerations

- Workload Considerations

- Security Considerations

- Organization-specific Architecture Considerations

7 Oracle Beehive Deployment Configurations

- Deploying Oracle Beehive on a Single Computer

- Deploying Oracle Beehive on Multiple Computers

- Deploying Oracle Beehive Across Network Zones

- How the Beehive Transport Infrastructure (BTI) Supports Multiple Network Zones

8 Deploying Oracle Beehive with Supported Clients and Devices

- Oracle Beehive Deployments with Oracle Beehive Extensions for Outlook

- Considerations for Deploying Oracle Beehive Extensions for Outlook

- Populating User's Global Address Lists (GAL) Incrementally

- Migrating Users' Microsoft Outlook Settings and Profiles

- Upgrading Oracle Beehive Extensions for Outlook

- How Oracle Beehive Extensions for Outlook Communicates with Oracle Beehive

- Oracle Beehive Deployments with Oracle Beehive Extensions for Explorer

- Oracle Beehive Deployments with Oracle Beehive Central

- Security Considerations for Oracle Beehive Central

- Oracle Beehive Deployments with Oracle Beehive Conferencing

- Deploying the Voice Conferencing Media Server

- Deploying Oracle Beehive Conferencing on Users' Computers

- Oracle Beehive Deployments with Oracle Beehive Team Collaboration

- Oracle Beehive Deployments with Oracle Beehive Webmail

- Oracle Beehive Deployments with Mobile Devices

- Recommended Ports for Mobile Device-related Services and Protocols

- Mobile Device Clients Provided by Oracle Beehive

- Deploying Oracle Beehive Mobile Clients on Apple iPhone

- Deploying Mobile Clients on Microsoft Windows and RIM BlackBerry Mobile Devices

- Enabling the Oracle Beehive Short Message Service (SMS) Delivery Channel

- Oracle Beehive Deployments with Standards-based Clients

Index

List of Figures

- 2-1 Oracle Beehive Logical Architecture

- 7-1 Oracle Beehive and Oracle Database Deployed on a Single Computer

- 7-2 Oracle Beehive and Oracle Database Deployed on Different Computers

- 7-3 Multiple Oracle Beehive Instances on Multiple Computers

- 7-4 Oracle Beehive Deployed Across Multiple Network Zones

List of Tables

- 8-1 Recommended Ports for Mobile Device-related Services and Protocols

Oracle® Beehive

Deployment Guide

Release 2 (2.0.1.8)

E16645-06

August 2013

Documentation that describes the concepts, considerations, and options associated with deploying Oracle Beehive.

Oracle Beehive Deployment Guide, Release 2 (2.0.1.8)

E16645-06

Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author: Jean Rao

Contributing Authors: Raymond Gallardo, Pat Huey, Kristina Jensen, Roza Leyderman, Andrew Mitchell, Valarie Moore, Jay Rajiva, Josh Stanley, Sheela Vasudevan, Sujata Nimbalkar

Contributors: Henrik Blixt, Vimal Chopra, Jeff Doering, Ramesh Dommeti, Brennan Gaunce, Bikash Ghosh, Richard Hall, Marc-Andre Houle, Daniel Kapaya, Duane Jensen, Tait McCarthy, Andrew Mitchell, Paul Nock, Mark Paterson, Francois Perrault, Jay Rajiva, Jamie Rancourt, Reza Rokni, Sudip Roy, Costa Siourbas, Josh Stanley

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware 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.

Preface

This guide describes the concepts, considerations, and options associated with deploying Oracle Beehive.

Note:
This guide has not undergone any content change for this release. Only the version number and date have changed. As and when this guide is revised, it will be updated on the Beehive 2.0 documentation library.

This preface contains the following topics:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This guide is intended for anyone who is involved with deploying Oracle Beehive. This guide is particularly useful to administrators and other resources who plan to deploy and manage Oracle Beehive.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle Beehive Release 2 (2.0) documentation library:

Administration Guides

- Oracle® Beehive Administrator's Guide

- Oracle® Beehive Administrator's Reference Guide

- Oracle® Beekeeper Online Help (Integrated UA)

- Oracle® Beehive Integration Guide

Application Development

- Oracle® Beehive Application Developer's Guide

- Oracle® Beehive Business Views

- Oracle® Beehive Java Content Repository Java API Reference

- Oracle® Beehive RESTful Web Services API Reference

- Oracle® Beehive SOAP Web Services API Reference

Installation Guides

- Oracle® Beehive Installation Guide for Linux

- Oracle® Beehive Installation Guide for Microsoft Windows

- Oracle® Beehive Installation Guide for Solaris Operating System

- Oracle® Beehive Installation Help (Integrated UA)

Online Helps

- Oracle® Beehive Central

- Oracle® Beehive Webmail

- Oracle® Beehive Standards-based Clients

- Oracle® Beehive Team Collaboration

- Oracle® Beehive Conferencing

- OBEE Supplemental Help & Release Notes

- OBEO Supplemental Help & Release Notes

- Oracle® Beehive Extensions for Explorer (OBEE) (Integrated UA)

- Oracle® Beehive Extensions for Outlook (OBEO) (Integrated UA)

Mobile Devices

- Oracle® Beehive Mobile Client for Windows

- Oracle® Beehive Mobile Communicator for Windows

- Oracle® Beehive Mobile Communicator for iPhone

- Oracle® Beehive Mobile Communicator for BlackBerry

- Oracle® Beehive Configuring Mobile Devices

Planning Guides

- Oracle® Beehive Concepts

- Oracle® Beehive Licensing Information

Release Notes

- Oracle® Beehive Release Notes

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Overview of Deploying Oracle Beehive

This module provides an introduction to Oracle Beehive and an overview of the deployment process, and includes the following topics:

- Overview of Oracle Beehive

- How to Use This Guide to Deploy Oracle Beehive

- Prerequisites for Deploying Oracle Beehive

- Deploying Oracle Beehive in Stages

- Key Terms and Concepts for Deploying Oracle Beehive

Overview of Oracle Beehive

Oracle Beehive is the next generation of Oracle's enterprise collaboration technologies. Oracle Beehive provides a unified collaboration application and platform comprised of a comprehensive set of integrated, Java-based services, offering a new paradigm for enterprise collaboration solutions.

Oracle Beehive unifies common yet typically disjointed collaborative services, such as e-mail, time management, instant messaging, and content management, among others, and delivers them through standard protocol clients, integrated Web services, and familiar desktop tools such as Microsoft Outlook. This unified offering enables teams, individuals, and organizations to more easily collaborate, generate new information, make timely decisions, and, take action.

Oracle Beehive allows IT departments to consolidate their collaboration-enabling infrastructures and implement people-centric, rather than tool-centric, applications in a centrally managed, secure, and compliant environment. The Oracle Beehive platform is built on proven and cost-effective Oracle technologies, such as Oracle Database and Oracle Application Server, which provide reliability, manageability, scalability, and performance.

How to Use This Guide to Deploy Oracle Beehive

Oracle Beehive is a comprehensive enterprise collaboration platform that provides a wide range of functionality for deployments both small and large. As with any complex software technology that is designed to support the needs of an entire enterprise, there any many options to consider related to its deployment. Deploying Oracle Beehive can be complex from the standpoint that the system can leverage and interoperate with many hardware and software components. However, with proper planning as well as the right tools and resources in place, deploying Oracle Beehive can be straightforward and easily achieved.

This guide provides details on the things you will need to consider when planning to deploy Oracle Beehive. This guide will also help you evaluate many aspects of your organization's deployment needs, and will enable you to choose and plan the most appropriate path for successfully and optimally deploying Oracle Beehive. For reference purposes, examples of common deployment scenarios are provided. References and links to more in-depth details on certain options and components, especially those provided by other Oracle products, are also provided where appropriate.

Note:
To gain a comprehensive, high-level understanding of the features, options, and benefits that Oracle Beehive provides, see Oracle Beehive Concepts.

This guide provides details on the various aspects for consideration when deploying Oracle Beehive, including:

- Network considerations

- Architectural considerations

- Integration with other supported Oracle and third-party products

- High availability

- Coexistence with third-party components

- Installation and upgrades

Note:
No install or upgrade-related procedural information is provided in this guide. For that type of information, see Oracle Beehive Installation Guide for your operating system.

- Deploying supported clients

- Supported deployment scenarios

Prerequisites for Deploying Oracle Beehive

To successfully deploy Oracle Beehive you should know or understand the following:

- Oracle Beehive architecture

- Available Oracle Beehive features and options

- Your organization's deployment needs

- The resources that are available for deployment, including software and hardware components as well as technical personnel

You should read this and other related chapters before installing Oracle Beehive and allowing users to access the system.

Deploying Oracle Beehive in Stages

Before deploying Oracle Beehive, Oracle strongly recommends that you consider a framework and methodology to follow through the various deployment stages. Doing so will help you and your organization prepare for, plan and execute a successful deployment of Oracle Beehive.

For your convenience, a sample framework to follow is provided in this section. However, following this framework is not mandatory for a successful deployment of Oracle Beehive. You should use whatever approach or methodology that best meets the needs, standards, and obligations of your organization based on the available resources and other factors.

The framework provided here is divided into several stages that follow each other in order. This framework also integrates the use of three successive deployment environments:

1. Development or customization

2. Testing

3. Production

Following this or a similar framework will help ensure a successful initial deployment of Oracle Beehive. It will also enable your organization to successfully maintain, administer, and upgrade the system in future.

The proposed framework for deploying Oracle Beehive includes the following stages, in order:

- Oracle Beehive Deployment Stage #1: Create a Deployment Plan

- Oracle Beehive Deployment Stage #2: Research and Knowledge Gathering

- Oracle Beehive Deployment Stage #3: Requirements Gathering

- Oracle Beehive Deployment Stage #4: Install and Configure the System

- Oracle Beehive Deployment Stage #6: Evaluate and Test the System

- Oracle Beehive Deployment Stage #7: Training for Developers, Administrators, and End Users

- Oracle Beehive Deployment Stage #8: Launch the System into Production

- Oracle Beehive Deployment Stage #9: On-going Maintenance and Administration

Oracle Beehive Deployment Stage #1: Create a Deployment Plan

The first thing that you and others in your organization should do is to choose an approach or methodology for deploying Oracle Beehive. The second thing that you should do is put that approach in writing and begin to create a plan based on it. The initial plan that you create should contain the general or high-level tasks that you expect will be required to deploy your Oracle Beehive instance. This can include major stages such as those listed here. The addition of specific, low-level tasks and their details should be added to the plan only as they become known, which often occurs in the following stages of the deployment process.

You should also begin to identify key resources that will be involved in the deployment process. These resources may include system administrators and technical staff members as well as senior-level members in your organization who possess decision-making and signoff authority.

Oracle Beehive Deployment Stage #2: Research and Knowledge Gathering

The research and knowledge gathering stage includes gaining a solid understanding of what Oracle Beehive is as well as what related options are available to you and your organization. To gain a comprehensive, high-level understanding of the features, options, and benefits that Oracle Beehive provides, see Oracle Beehive Concepts.

During this stage, you should gain an understanding of how your organization plans to deploy and use Oracle Beehive. You should understand your organization's goals for deploying Oracle Beehive, and what the motivators and constraints are for achieving those goals, including any time frames or deadlines. This should also include confirming whether or not your organization plans to migrate users and data from existing systems. Remember to consider your organization's current and future needs, whether actual or potential, as you gather this information.

Oracle Beehive Deployment Stage #3: Requirements Gathering

Once you have a better understanding of the various available Oracle Beehive options and components, determine which ones will apply to your deployment and then gather the information related to their requirements. This includes obtaining hardware and software requirements, server and host names, and port numbers, among other important information. This may also include identifying users and data sets that will be migrated from existing systems to Oracle Beehive, and how your organization plans to migrate them.

Tip:
To ease the transition from a development environment to a production environment and beyond, it is best to use virtual host names from the beginning. With this approach, you can transition and grow the system without having to significantly modify existing integrations of servers, services, and other components.

This guide provide general deployment considerations and recommendations as they pertain to system requirements. For specific hardware and software requirements as well as other installation-specific information, see Oracle BeehiveInstallation Guide for your operating system.

Oracle Beehive Deployment Stage #4: Install and Configure the System

The installation stage includes all installation-related steps, including pre- and post installation steps. Pre-installation steps include, among others, mapping out and planning for the installation process, preparing your operating system, and verifying that Oracle Database is already installed. Another pre-installation step is obtaining the Oracle Beehive installation package.

Oracle provides the Oracle Beehive installation package through an installation medium (CD, DVD, and so on) or through a download process from a supported Oracle website. For more information, see Oracle Beehive Installation Guide for your operating system.

Post installation steps include verifying that the installation was successful, configuring fundamental aspects of the system, and, optionally, beginning to migrate data from existing systems.

Oracle Beehive Deployment Stage #5: Customize the System

This stage includes customizing Oracle Beehive in one or more ways such as by integrating the system with other supported Oracle and third-party applications. This stage may also include deploying Oracle Beehive into a development environment to customize the system programmatically. This can include extending Oracle Beehive services or leveraging the platform's Application Programming Interface (API). The Oracle Beehive API enables organizations to retrieve and manipulate Oracle Beehive data as well as integrate the system with custom and third-party applications. For more information, see Oracle Beehive Application Developer's Guide.

Oracle Beehive Deployment Stage #6: Evaluate and Test the System

After installing and customizing Oracle Beehive, but before launching the system, it is critical that you or your organization rigorously test the system to ensure that it functions as expected. This includes testing various server configurations and custom development, tuning the system, verifying that data from existing systems has migrated successfully, and conducting functional tests on all end-user clients that will be deployed into production. This stage also includes making any necessary changes if issues are discovered.

Note:
For more information on configuring and tuning the system, see Oracle Beehive Administrator's Guide.

Test environments 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.

Oracle Beehive Deployment Stage #7: Training for Developers, Administrators, and End Users

An often-overlooked, but fundamentally important aspect of deploying a new system or application is training. In this stage, developers, administrators, and end users receive the information and instructions that they will need to begin customizing, managing, and collaborating with Oracle Beehive. This can include in-class training, online tutorials and demos, or other formats that are appropriate for your organization and the resources that are available. Oracle Beehive supports a variety of clients and users of all levels, so it might make sense to consider a different training strategy and delivery medium for each client or user type.

Including this stage in your overall deployment strategy will benefit your organization on many levels. For example, providing adequate training will likely reduce end-user issues and support costs. Conversely, it will also likely boost end-user adoption and productivity, ensuring that your organization receives the maximum return on the benefits provided by Oracle Beehive.

Oracle Beehive Deployment Stage #8: Launch the System into Production

After testing Oracle Beehive and training end users, the next stage is to launch system into a production environment, or go live. This is the stage where all of the work and preparations from the previous stages come to fruition. Steps such as using virtual host names are of particular importance and can greatly simplify the process of launching the system. Depending on the protocols and needs of your organization, launching the system into production might include rolling out to one or more selected user groups at first and then, after confirming system stability, to the remainder of the enterprise. This stage may also include migrating users and data from existing systems.

Oracle Beehive Deployment Stage #9: On-going Maintenance and Administration

After launching the system, you will enter the on-going maintenance and administration stage. This stage includes monitoring Oracle Beehive, changing configuration settings as needed, and managing users and groups, among other administrative tasks. This may also include coordinating regular updates and upgrades for the deployment of additional features, services, or hardware. For more information, see Oracle Beehive Administrator's Guide.

Key Terms and Concepts for Deploying Oracle Beehive

Before beginning the deployment process for Oracle Beehive, it is important to understand several fundamental deployment terms and concepts, including:

- Servers and Nodes

- Network Zones

- Demilitarized Zones (DMZs)

- Installations

- Services

- Instances

- Sites

- Enterprises and Organizations

Servers and Nodes

A server is a computer on which an Oracle Beehive instance runs. A node is a server in a network deployment of Oracle Beehive. Oracle Beehive supports deployments with multiple nodes.

Network Zones

A network zone is a defined and segregated area of a network that hosts one or more Oracle Beehive components.

Demilitarized Zones (DMZs)

A demilitarized zone (DMZ) is a computer host or small network that an enterprise inserts as a neutral zone between its internal, private network and the Internet. A DMZ prevents unauthorized users from accessing systems that contain confidential or proprietary data. In effect, DMZs act as proxy servers and provide another layer of network security, especially when used with firewalls.

Installations

An installation is the set of bits that comprise Oracle Beehive. Although multiple installations may exist on the same server, typically there is only one installation for each server.

Services

An Oracle Beehive service is a discrete implementation of specific functionality that users and other services can leverage to accomplish a task. The capabilities and interactions of services enable the full scope of functionality that Oracle Beehive provides.

Oracle Beehive services can be installed and deployed on a single computer or among several computers distributed across multiple network zones. In the latter case, when multiple instances of service are deployed, the collection is referred to and represented as a single implementation of that service. By default, all services are deployed during the Oracle Beehive installation process.

Instances

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.

Sites

A site is a collection of physical hardware in the same geographic location used to run Oracle Beehive. Each Oracle Beehive site requires a minimum set of components to support a fully-functioning system. However, within each site, multiple instances of a variety of supported components, including services and servers, can be implemented. This can be useful for the purposes of availability and performance. Oracle Beehive currently supports only one site per deployment.

Enterprises and Organizations

An enterprise is a container for all of the users, groups, and resources that leverage or that are a part of a single Oracle Beehive instance. 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.

2 Oracle Beehive Architecture

Built on Java 2 Platform Enterprise Edition (J2EE), Oracle Beehive provides a multitier architecture that leverages proven Oracle technologies, such as Oracle Database and Oracle Application Server, as well as other key Oracle and third-party components.

This module provides a high-level overview of the Oracle Beehive architecture and its supported components, and includes the following topics:

- Overview of the Oracle Beehive Tiers

- Connections Between Oracle Beehive Tiers

Overview of the Oracle Beehive Tiers

The Oracle Beehive architecture is divided into the following logical tiers:

- The Client Tier, which contains Oracle Beehive clients, as well as other supported clients and devices. For more information, see "Overview of the Client Tier".

- The Application Tier, which contains Oracle Beehive services and application server components. For more information, see "Overview of the Application Tier".

- The Data Tier, which contains Oracle Database to store system configuration and collaboration data. For more information, see "Overview of the Data Tier".

- The Ancillary Tier, which contains optional Oracle and third-party components that enhance or coexist with certain aspects of the system. For more information, see "Overview of the Ancillary Tier".

Figure 2-1 Oracle Beehive Logical Architecture

Description of "Figure 2-1 Oracle Beehive Logical Architecture"

Overview of the Client Tier

The Client Tier is the face of the system and includes all supported clients and devices, including integration with Microsoft Outlook and a command-line tool for system administration. Oracle Beehive also supports clients and devices that leverage the following standardized protocols:

- Calendaring Extensions for WebDAV (CalDAV)

- Extensible Messaging and Presence Protocol (XMPP)

- File Transfer Protocol (FTP)

- Internet Message Access Protocol (IMAP)

- Push Internet Message Access Protocol (P-IMAP)

- Open Mobile Alliance Data Synchronization (OMA-DS)

- Simple Mail Transfer Protocol (SMTP)

- Web-based Distributed Authoring and Versioning (WebDAV)

The open nature of the Oracle Beehive platform also enables developers to build and implement custom clients in the Client Tier using Oracle Beehive Web services.

For more information about the deployment options and considerations related to components in the Client Tier, see "Deploying Oracle Beehive with Supported Clients and Devices".

Overview of the Application Tier

The Application Tier is the core of the system and includes all Oracle Beehive server components, including interoperable, function-specific services that provide the system's enterprise collaboration features.

The Application Tier supports multiple Oracle Beehive server instances. Each Oracle Beehive server instance includes required components of Oracle Application Server 10g, which itself hosts the Oracle Beehive services, including:

- Oracle HTTP Server: The Web server component of Oracle Application Server 10g. Enables connections between supported clients over HyperText Transport Protocol (HTTP) and Secure HyperText Transport Protocol (HTTPS).

- Oracle Application Server Containers for J2EE (OC4J): J2EE v1.4 -compliant containers that provides an infrastructure for deploying, undeploying, and redeploying J2EE-compliant applications and modules. Oracle Beehive services are deployed in OC4J containers.

When you install Oracle Beehive, the required Oracle Application Server 10g components are pre-bundled and installed by default.

Each Oracle Beehive server instance also includes the Beehive Transport Infrastructure (BTI), which enables connectivity between supported clients and Oracle Beehive through its proprietary multiplexor protocol (MX). For more information, see "Overview of the Beehive Transport Infrastructure".

Overview of the Data Tier

The Data Tier is the information store for Oracle Beehive and contains Oracle Database, either as a single, standalone database instance or an Oracle Real Application Cluster (Oracle RAC). All system configuration and collaborative data for Oracle Beehive is stored in Oracle Database.

The Data Tier provides Oracle Database a layer of separation from the other tiers, ensuring, among other things, optimized security and system performance. Only the Database Access Framework (provided by Oracle Beehive) can access the Data Tier. Oracle Beehive services cannot access the Data Tier directly and must make all connections through the schemas provided by the Database Access Framework. For more information on the Database Access Framework, see "Overview of the Database Access Framework".

Overview of the Ancillary Tier

The Ancillary Tier contains any optional servers and applications that are external to the Oracle Beehive server. Typically, components in this tier are optional because Oracle Beehive already provides many of these capabilities, such as user directories, e-mail, and time management.

Oracle Beehive supports Ancillary Tier components to provide enterprises flexibility in their deployment choices, especially for those that want to leverage existing or specialized component investments. In either case, enterprises can choose to implement the components of this tier to coexist with or access key aspects of Oracle Beehive.

Examples of Oracle and third-party components in the Ancillary Tier include:

- Oracle Internet Directory

- Oracle Secure Enterprise Search

- Oracle Single Sign-On

- IBM Tivoli Directory Server

- IBM Tivoli Access Manager WebSEAL

- Microsoft Active Directory Server

- Microsoft Exchange Server

- Sun Java Directory Server

- OpenLDAP Directory Server

- Symantec Anti-Virus Scan Engine

Connections Between Oracle Beehive Tiers

Components in the Oracle Beehive tiers connect through the following system frameworks and components:

- The Database Access Framework, which supports connections between the Application and Data Tiers. For more information, refer to "Overview of the Database Access Framework".

- The Beehive Transport Infrastructure (BTI), which supports client connectivity between the Client and Application Tiers. For more information, refer to "Overview of the Beehive Transport Infrastructure".

- The Event Framework, manages all system events, as well as notification logic that they initiate. For more information, refer to "Overview of the Event Framework".

- Oracle Beehive schemas, which segregate system, configuration, and collaborative data, and application code. For more information, refer to "Overview of Oracle Beehive Schemas".

Overview of the Database Access Framework

The Application and Data Tiers connect through the Database Access Framework, which provides a logical data structure and an optimized data management resource for Oracle Beehive. The Database Access Framework improves system performance and scaling capabilities, while reducing overall system complexity.

The Database Access Framework controls all access to the database through a connection pool that it manages. Services request connections to the database through the connection pool. Once a service receives the requested information, it returns the connection back to the connection pool. The Database Access Framework leverages Java Database Connectivity (JDBC) for these connections.

The Database Access Framework enables centralized management of data store resources and utilizations. It also simplifies database administration tasks that are external, yet related, to Oracle Beehive, including:

- Changing database connection information, such as database host names and Oracle RAC nodes

- Managing database connection pool sizes

- Gathering database usage metrics

Overview of the Beehive Transport Infrastructure

The Beehive Transport Infrastructure (BTI) enables connectivity between the Client and Application Tiers by providing the network-level infrastructure for both client-to-server and server-to-server communications. Specifically, the BTIprovides port and connection management for Microsoft Outlook (with Oracle Beehive Extensions for Outlook) and non-HTTP, standard-based clients through its proprietary multiplexor protocol (MX).

In a typical enterprise client/server deployment, clients connect through a series of networks to a known port on a known server. However, in many cases, the communication channels must traverse firewalls, load balancing routers, forward and reverse proxies, and demilitarized zones (DMZs). The BTI is designed for deployment in these complex network infrastructures, while providing optimal port and connection management.

The BTI is a bundled component of the Oracle Beehive server so it is always provided whether you deploy Oracle Beehive in the Application Tier or in a DMZ. The latter case provides another layer of security between clients connecting to the system and internal components such as Oracle Database. This increased level of security and control over client connections is particularly beneficial when client connections are expected to originate from points outside of your network, such as from the Internet or from other private networks.

Oracle Beehive also provides Oracle HTTP Server, which enables client connectivity over HTTP/HTTPS. This can be leveraged in cases where HTTP/HTTPS is the preferred method of enabling client connections that originate from external locations.

Overview of the Event Framework

Oracle Beehive is an event-driven platform. Many aspects of system functionality and service interoperability stem from the event-based design of the platform. To manage this complex and powerful design implementation, Oracle Beehive provides the Event Framework. The Event Framework manages all events that occur in the system, which includes initiating any notification logic and policies that may apply.

Oracle Beehive supports business events, which are events that trigger business logic. Business events provide a unique integration point for Oracle Beehive that allows customers to customize business processes or initiate external processes based on specific activities or occurrences. An example of a business event is when a user creates a document and it initiates a specific approval and notification process.

The open design of Oracle Beehive enables organizations to customize and extend the Event Framework. For example, developers can write and integrate custom business logic that executes when corresponding events are triggered in the system. Oracle Beehive administrators can also customize Oracle Beehive business logic to suit their specific requirements.

Overview of Oracle Beehive Schemas

Oracle Beehive schemas logically segregate system, configuration, and collaborative data, and application code. In addition to organizing system, data, and configuration management, Oracle Beehive schemas also provide a significant security benefit by isolating each of the major data components that drive the system. Each Oracle Database in an Oracle Beehive deployment must contain one Oracle Beehive schema set.

An Oracle Beehive schema set consists of the following schema types:

- Code Schema

- Data Schema

Code Schema

The Code Schema contains all Procedural Language/Structured Query Language (PL/SQL) code used by Oracle Beehive. The Code Schema enables application-level cloning and code updates separate from system data. Benefits of these capabilities include easier and seamless patches and upgrades, since these tasks can be performed without any system downtime. The separation of PL/SQL code from system data also reduces the amount of time required for system backups, as code backups are required less frequently.

The Code Schema also controls the access requests made by Oracle Beehive services to data residing in the Data Tier, as well as the connections from services to other Oracle Beehive schemas, which the services cannot connect to directly. Connections between Oracle Beehive services and the Code Schema are managed by the Database Access Framework.

Data Schema

The Data Schema is the primary repository of collaborative data for Oracle Beehive. In Oracle Beehive, each service owns specific tables and views for the data that it manages. However, a service can request data from the tables or views owned by another service. For example, the Calendar Service may request data from a table belonging to the E-mail Service, which, in turn, may refer to and request information from tables owned by the User Directory Service.

3 Tools for Deploying Oracle Beehive

This module provides a high-level overview on the tools that can be used to deploy Oracle Beehive. This module contains the following topics:

- The Oracle Beehive Install Wizard

- The Oracle Beehive Config Wizard

- Oracle Beekeeper

- The Oracle Beehive beectl Utility

- Oracle Enterprise Manager Grid Control

The Oracle Beehive Install Wizard

The Oracle Beehive Install Wizard is a GUI-based wizard that guides you through the installation process. The Install Wizard is provided with your Oracle Beehive media and can be used to install, upgrade, and uninstall Oracle Beehive in either interactive mode or silent mode. In interactive mode, the Install Wizard prompts you for information and settings specific to your Oracle Beehive deployment and the supporting infrastructure. In silent mode, you supply a response file that contains all of the same information and settings normally requested during the Oracle Beehive installation process.

Note:
Upgrades are supported for the following scenario only:

- Oracle Beehive Release 1.5.1 to Oracle Beehive Release 2.0

For more information on the Oracle Beehive Install Wizard, refer to the Oracle Beehive Installation Guide for your operating system.

The Oracle Beehive Config Wizard

The Oracle Beehive Config Wizard is a GUI-based wizard that guides you through the configuration segment of the installation process for software-only installations. Similar to the Oracle Beehive Install Wizard, it can be used in either interactive mode or silent mode. With the latter, you supply a response file that contains all of the same information and settings normally requested during the Oracle Beehive configuration process.

For more information on the Oracle Beehive Config Wizard, refer to the Oracle Beehive Installation Guide for your operating system.

Oracle Beekeeper

The Oracle Beehive administration client, Oracle Beekeeper, is a secure, browser-based client built on Oracle ADF Faces technology. Oracle Beekeeper provides Oracle Beehive administrators centralized and role-based access to system configuration and management, user and group administration, monitoring, and reporting functions.

Oracle Beekeeper requires a server-based installation that is separate from the Oracle Beehive installation. The Oracle Beekeeper installation program is provided with the Oracle Beehive installation kit. Once installed and configured, administrators simply need to access the configured URL to launch Oracle Beekeeper, log on to the system, and access the administrative features and information that it provides. Oracle Beekeeper supports the Hypertext Transfer Protocol Over Secure Socket Layer (HTTPS) for secure communications.

Note:
For security reasons, Oracle strongly recommends enabling SSL encryption for your Oracle Beekeeper installation.

For more information on how you can use Oracle Beekeeper to manage your Oracle Beehive deployment, refer to Oracle Beekeeper Online Help.

The Oracle Beehive beectl Utility

The Oracle Beehive beectl utility is a command-line tool provided with Oracle Beehive. Administrators can use beectl to manage their Oracle Beehive deployments by executing commands in a supported operating system shell. Some of the deployment-related tasks for which administrators can use the utility include:

- Cloning Oracle Beehive instances and OC4Js

- Creating and managing client application configuration files

- Provisioning client applications

For more information on how you can use beectl to manage your Oracle Beehive deployment, refer to the Oracle Beehive Administrator's Guide.

Oracle Enterprise Manager Grid Control

Oracle Enterprise Manager Grid Control includes a Web-based administration tool that provides both installation and monitoring capabilities for Oracle Beehive. Oracle Enterprise Manager Grid Control offers a centralized environment with which you can manage the complete Oracle IT infrastructure, including systems running Oracle and non-Oracle technologies. It provides a broad set of administration, configuration management, provisioning, end-to-end monitoring, and security capabilities. Due to these capabilities and others, Oracle Enterprise Manager Grid Control is recommended for use with Oracle Beehive. Oracle Beehive supports Oracle Enterprise Manager 10g Release 5 Grid Control (10.2.0.5) or later.

Installing Oracle Beehive through Oracle Enterprise Manager Grid Control requires the Oracle Beehive Provisioning Application, which is provided with Oracle Beehive. However, Oracle Enterprise Manager Grid Control is not provided with the Oracle Beehive media package and must be installed separately. For details, contact your Oracle representative.

For more information on how you can use Oracle Enterprise Manager Grid Control to install Oracle Beehive, see "Integrating Oracle Enterprise Manager Grid Control with Oracle Beehive" in the Oracle Beehive Integration Guide. For more information on how you can use Oracle Enterprise Manager Grid Control to manage your Oracle Beehive deployment, see "Oracle Beehive Management" in Oracle Enterprise Manager Concepts.

4 Deploying Oracle Beehive with Other Software Components

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 an External User Directory

- Deploying Oracle Beehive with a Third-Party Single Sign-On Provider

- Deploying Oracle Beehive with Oracle Database

- 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 Oracle Wallet

- Deploying Oracle Beehive with Cisco Voice Gateway

- Deploying Oracle Beehive with IBM Lotus Domino Server

- Deploying Oracle Beehive with Microsoft Exchange Server 2003 or 2007

- Deploying Oracle Beehive with Symantec Scan Engine

Enabling Cross-Scheduling Between Oracle Beehive Deployments with iSchedule

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:

1. 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.

2. 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.

Deploying Oracle Beehive with an External User Directory

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.

Deploying Oracle Beehive with a Third-Party Single Sign-On Provider

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.

Deploying Oracle Beehive with Oracle Database

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.

Deploying Oracle Beehive with Oracle Real Application Clusters (Oracle RAC)

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:

- Preparing to Deploy Oracle Beehive with Oracle RAC

- Post installation Steps for Deploying Oracle Beehive with Oracle RAC

Preparing to Deploy Oracle Beehive with Oracle RAC

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.

Post installation Steps for Deploying Oracle Beehive with Oracle RAC

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.

Deploying Oracle Beehive with Oracle Secure Enterprise Search 10g

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.

Deploying Oracle Beehive with OracleAS Single Sign-On (OSSO)

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.

Deploying Oracle Beehive with Oracle Universal Content Management (Oracle UCM)

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.

Deploying Oracle Beehive with Oracle Information Rights Management (Oracle IRM)

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.

Deploying Oracle Beehive with Oracle Universal Records Management (Oracle URM)

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.

Deploying Oracle Beehive with Oracle Wallet

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.

Deploying Oracle Beehive with Cisco Voice Gateway

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.

Deploying Oracle Beehive with IBM Lotus Domino Server

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.

Deploying Oracle Beehive with Microsoft Exchange Server 2003 or 2007

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.

Deploying Oracle Beehive with Symantec Scan Engine

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.

5 Network Considerations for Oracle Beehive

This module discusses the following network considerations when planning for an Oracle Beehive deployment:

- Basic Network Considerations

- Network Considerations for Small Deployments

- Access and Security Considerations

- Traffic Considerations

- Other Network Considerations for Deploying Oracle Beehive

Note:
Because network configuration varies according to the unique requirements of each organization, this module does not provide specific network setup instructions. Rather, it discusses the general network considerations that organizations must address when deploying Oracle Beehive.

Basic Network Considerations

The basic goal of network planning is to make optimal use of Oracle Beehive and your existing network services and components. To accomplish this, you must determine a number of factors including the amount of access permitted to external sources, the capacity needed to meet user requirements, and network availability. You must also consider business factors such as budget constraints and the strategic reasons behind each of your network planning goals.

Network Considerations for Small Deployments

In small deployments of Oracle Beehive, network and architectural planning are intertwined since smaller pools of available servers result in fewer deployment options. When planning an architecture with only one or two servers, you will often have to choose between component accessibility and server location. The location of servers is often based on security requirements and, as a result, access to the servers must be planned accordingly.

Access and Security Considerations

When deploying Oracle Beehive, access and security must be planned simultaneously since each aspect has a direct impact on the other, especially with smaller deployments.

Access is arguably the more complex of these two considerations. In virtually any deployment, you must account for several access methods (or levels) within a single environment. These depend on factors such as the locations from which users will access the network, the types of clients users will leverage, and the components to which users will need access.

Because access is a network-dependent element, much of its setup depends on the surrounding network environment. Therefore, Domain Name Services (DNS), mail relays, reverse proxies, firewalls, network routing, and other network services must interact very closely with the components of Oracle Beehive. Understanding this interaction is the key to understanding Oracle Beehive network access in a production environment.

Security is a subset of access in many ways, as many security issues are solved simply by denying access to certain services or networks. For example, an organization might choose to deny access from outside its network across all protocols except for HyperText Transfer Protocol (HTTP) and Secure HyperText Transfer Protocol (HTTPS). HTTPS is the HTTP protocol implemented over Secure Sockets Layer (SSL) or Transport Layer Security (TLS). It is more secure than HTTP because it provides authentication and data encryption. Users typically access Oracle Beehive from outside the network with supported clients over HTTPS. So, you can proxy HTTPS as each user requires.

The other element to consider is how to secure the traffic that you allow to flow, and this is where encryption plays an important role. This is especially true for external traffic.

Traffic Considerations

A typical Oracle Beehive deployment may separate traffic in the following ways:

- Internal Traffic

- External Traffic

Internal Traffic

Internally, all protocols are allowed and all clients may be used. In this case, a typical deployment could leverage the BTI for all client connections. This policy can be modified to be more granular, either by configuring access rules or by separating the networks with firewalls.

External Traffic

Externally, only a few encrypted, hardened, and monitored services are exposed. For example, some organizations choose to make external client access available only over HTTP and HTTPS. In this case, a typical deployment could leverage Oracle HTTP Server (installed with Oracle Beehive) deployed in a DMZ.

Other Network Considerations for Deploying Oracle Beehive

This section provides a list of questions that you should ask before deploying Oracle Beehive. The answers to these questions will help you to evaluate which Oracle Beehive and network components need to be deployed, where they need to be deployed, and how they need to be configured:

- What kind of network and security policies does your organization have?

- Does your organization have a DMZ and if so, what kind?

- Does your organization use NAT to abstract its network?

- Has your organization implemented load balancing and reverse proxy?

- Does your organization use hardware encryption acceleration?

- Does your organization have an SMTP mail relay?

- Does your organization want to expose IMAP externally?

- Is filtering installed for spam and viruses?

- What components might your organization want to deploy initially or later?

- Which Oracle Beehive services and network services will be used?

- From where should Oracle Beehive be accessible?

- Do your plans fit into your organization's security model?

- What are the existing network services on which you will rely?

- What is the configurability of your network services? Can they be easily changed to suit Oracle Beehive?

- What is the size of the current network?

- How many users will there be?

- What is your budget?

What kind of network and security policies does your organization have?

Unless your organization is willing to revise its policies, you'll need to adhere to existing network and security policies when deploying Oracle Beehive. This is likely to affect where you deploy Oracle Beehive, such as in or behind a DMZ, and what components you'll use to enable client connections, such as Oracle HTTP Server or the BTI.

Does your organization have a DMZ and if so, what kind?

This is crucial to the design and planning of your architecture, as it determines where components need to be placed, depending on how they are to be accessed. DMZ is a part of the network, which is in between an intranet and the Internet, and is often referred as the neutral zone. It enables only certain services of the hosts in an intranet to be accessible to the hosts on the Internet. This sub-network is especially used for public access servers such as Web servers.

If there is a DMZ:

- How is it used for external access?

- How is it used for internal access?

- Are DNS servers used? If so, consider the following issues.

- Sometimes, two DNS servers (split DNS) are used to help separate deployments by reserving server names for separate internal and external computers.

- DNS servers can be separated onto separate networks; for example, one in the DMZ and one in the internal network.

- You can configure any DNS server, such as Berkeley Internet Name Domain (BIND), to respond to DNS requests differently, depending on where the request originates.

- DNS services can be further fortified when combined with Network Address Translation (NAT).

Using two DNS servers provides more flexibility than using just one. In either case, clients connect to either an external or internal IP address for the same host name, depending on where the connection originates, and client access is properly routed by DNS connectivity.

Does your organization use NAT to abstract its network?

NAT is the process of translating an IP address used within one network to a different IP address of another network. Generally, organizations set up NAT to translate internal addresses into public routable addresses. The translation takes place at the firewall and protects internal addresses from external tracing or routing.

NAT has a large and beneficial impact on naming services. External IP addresses in DNS can be mapped to virtual addresses as configured in Oracle Beehive.

Note:
When you install Oracle Beehive, each Oracle Beehive server instance assumes the name of the server on which it is installed. You must configure external IPs on your DNS server, then configure Oracle Beehive to use the appropriate virtual addresses instead of the original server name.

Has your organization implemented load balancing and reverse proxy?

Load balancing is the process of managing the distribution of inbound traffic among multiple servers. The use of load balancers and reverse proxy is an important strategy in securing your Oracle Beehive deployment. With load balancing and reverse proxy, you can abstract the routing and addressing of HTTP/HTTPS traffic so that Oracle Beehive servers are not directly exposed to external users.

If your organization uses existing hardware and a switching strategy, consider whether Oracle Beehive can be integrated into it.

Using content switches as load balancers is recommended. Content switches can host virtual IP addresses and spread the load over multiple servers, particularly for Application Tier services. Traffic can be redirected based on protocols such as HTTP, HTTPS, SMTP, and so forth.

If your organization has host names for its current services running on virtual devices, migration will be much easier. In fact, it is always a good idea to identify virtual services names early in the process. Embed them in documentation and get SSL certificates early if they are needed. It is also a good idea to start setting up DNS and Mail Exchange records early on, to map domain names to mail servers.

Does your organization use hardware encryption acceleration?

If you plan to use the SSL protocol to encrypt communications, it is a good idea to make use of SSL accelerators to optimize performance. SSL processing is a CPU-intensive task that can reduce performance. This is best off-loaded to hardware devices designed for this purpose.

Consider using SSL to encrypt external access to Oracle Beehive.

Does your organization have an SMTP mail relay?

Relay services are important for filtering, limiting, and routing SMTP traffic. They can be used to protect Oracle Beehive instances from external abuse and unnecessary load.

Most organizations have an existing SMTP mail relay (or Mail Transport Agent), ideally with spam services implemented on it. However, note the limitations of mail relays, such as:

- Attachment size

- Throughput throttling

- Retry count

Evaluate whether or not these limitations are realistic for your organization, and keep them in mind as you deploy Oracle Beehive.

It is a good strategy for many deployments to use programs such as these to handle and filter e-mail before forwarding it to the Oracle Beehive mail relay, which can reside behind a firewall or in a DMZ.

Does your organization want to expose IMAP externally?

IMAP is used to access e-mail messages from the mail server. Using IMAP, you can retrieve e-mail messages and manipulate them on the server itself. Many organizations choose not to provide IMAP access directly over the Internet, as they feel it overly exposes them from a security standpoint. If you decide to provide IMAP access across the Internet (without the additional security of a VPN infrastructure, for instance), Oracle Corporation strongly recommends implementing SSL for those IMAP services.

Is filtering installed for spam and viruses?

For the judicious use of valuable database storage, avoid saving unnecessary information such as e-mail spam. To protect the integrity of the network, viruses (often linked directly to spam) must also be blocked. There are several methods of filtering out these unwanted communications.

What components might your organization want to deploy initially or later?

It is possible that in the process of deploying Oracle Beehive, your organization may want to either implement components for the first time (such as a load balancer, for example) or upgrade existing ones (such as a mail relay).

Which Oracle Beehive services and network services will be used?

Determine which Oracle Beehive services your organization will use and consider which network services are necessary to support them. For example, if your organization plans to leverage the E-mail Service, you may want it to be accessible from anywhere in the world through HTTPS. Generally, the most important Oracle Beehive network components are as follows:

- Routing Equipment: Routing equipment can include routers, load balancers, and firewalls.

- Domain Name System (DNS): This network service resolves domain names or host names into Internet Protocol (IP) addresses. DNS maintains a database of all the host names and their respective IP address information.

- Mail relay: This network service is a server that routes e-mail messages to their destinations, mostly within local networks.

From where should Oracle Beehive be accessible?

For example, will it be accessible to users externally, internally, or both?

Do your plans fit into your organization's security model?

Before creating an elaborate deployment plan for Oracle Beehive, make sure you know your organization's security model, if there is one. For instance, some organizations may not allow DMZs or external access to e-mail.

What are the existing network services on which you will rely?

It may be practical to make use of existing network services.

What is the configurability of your network services? Can they be easily changed to suit Oracle Beehive?

Check how flexible your existing network implementation is.

What is the size of the current network?

Find out what sort of upgrades and additions, if any, will have to be made to the network to accommodate Oracle Beehive.

How many users will there be?

This is a primary concern in determining the type of deployment you need but it also affects (or may be affected by) the capacity of your network. If supporting a specified number of users is the highest priority, you'll need to determine whether or not your network has the speed, bandwidth, and latency to support those users, and what network improvements might be needed to support them. Or, if your network is a fixed and known quantity that cannot be changed, you'll need to determine how many users it can realistically support and then plan accordingly.

What is your budget?

Cost is always an important consideration in any network installation.

6 Architectural Considerations for Oracle Beehive

This module includes information on the following topics, which are related to the architectural considerations when planning for an Oracle Beehive deployment:

- Basic Architectural Considerations

- Access Considerations

- Capacity Considerations

- Recovery Considerations

- Availability Considerations

- Scalability Considerations

- Workload Considerations

- Security Considerations

- Organization-specific Architecture Considerations

Basic Architectural Considerations

Oracle Beehive can work in many different permutations, with exact placement and integration of components and servers varying greatly. Configuration depends on the needs of the organization and the existing architecture that can be leveraged.

The choice of architecture has a definite impact on performance and stability. Some organizations may require high availability, and may have moved to Oracle Beehive for this purpose. Others may not need high availability throughout an architecture, and can save time and resources initially.

Access Considerations

Access to Oracle Beehive is determined by your network setup and security strategies. Part of your planning involves determining where components need to be accessed from, whether internally, externally, or both. You can deploy multiple Oracle Beehive server instances in the Application Tier, depending on where your users are, perhaps with one in a DMZ and another on the internal network.

Capacity Considerations

To provide the appropriate capacity for the number of users in your deployment, you must start by evaluating how many servers you will need. Keep in mind not just the number of users, but also the frequency and concurrency of use.

Properly deployed Application Tier components can back up each other in cases of failures among them. This style of duplication and redundancy provides deployment flexibility and enables the load to be spread across all the components of the Application Tier.

Recovery Considerations

Ensure you plan for the ability to restore deleted or corrupt data to its last known good state. This is a part of your backup strategy.

Availability Considerations

Availability encompasses strategies you put into place to keep things running in case of system failures. Strategies can range from backing up data in-house to maintaining high levels of redundancy for Oracle Beehive system components. One example is to ensure you have network redundancy, so that in the event that one of your network paths fails, network traffic can be routed along a secondary or backup network route.

Scalability Considerations

With any deployment, it is important to plan for growth. You must be prepared to expand your deployment along with the size or needs of your user base. The use of virtual host names is recommended, even if you are installing on a single host or in a non-high availability environment. This will allow you to abstract Oracle Beehive server instances across multiple servers later on, without having to rename servers.

Ensure you have hardware that allows for growth and memory expansion. See the "Capacity Considerations" section for more information.

Workload Considerations

You can deploy Oracle Beehive on a single computer. However, such a deployment architecture may not be able to meet all the availability, security, and scalability requirements of your organization. Distribution of Oracle Beehive on multiple computers makes it easier to meet these requirements.

To optimize resource utilization on a particular computer, you should not mix different types of workloads on the computer. Typically, architectures for relatively large systems feature the distribution of these tiers on different computers.

The Application Tier, where Oracle Beehive server instances reside, and the Data Tier, where Oracle Database resides, handle different types of workloads. The Application Tier is CPU- and memory-intensive with fewer disk input/output (I/O) operations. Conversely, the Data Tier is I/O intensive.

In Oracle Beehive, the demand for Application Tier resources increases at a rate that is different from the rate at which the demand for Data Tier resources increases. This is another factor that justifies a distributed architecture. With a distributed architecture, you can scale up the Application and Data Tiers independently.

Security Considerations

If you want to provide access to Oracle Beehive components from public networks, you must take measures to secure this type of access. You can enhance the security of the system by distributing the tiers and deploying the system behind a DMZ. Standard security practices and Oracle Beehive prevent, for example, network traffic from passing directly from the Internet to the database. Instead, such traffic would be routed through a DMZ and a server in the Application Tier.

If you choose to deploy Oracle Beehive in a DMZ, the DMZ must contain the hardware and software required to relay traffic securely between the public network and private network.

Organization-specific Architecture Considerations

This section discusses deployment configuration considerations that may vary according to the specific requirements of each organization. For this reason, this and other Oracle Beehive deployment modules provide general, and not specific, guidance for these aspects of the system:

- How many servers is your organization willing to manage?

- What type of platform is your organization comfortable with?

- Is your organization prepared to deploy Oracle Beehive in stages?

- Does your organization need high availability?

- What is your organization's existing backup solution?

How many servers is your organization willing to manage?

This largely depends on the size of your IT staff and availability of system management tools.

What type of platform is your organization comfortable with?

Oracle Beehive supports several chip architectures and operating systems including heterogeneous and homogeneous platforms.

Is your organization prepared to deploy Oracle Beehive in stages?

It is strongly recommended that you consider deploying Oracle Beehive in stages, as described in the section "Deploying Oracle Beehive in Stages" from Chapter 1, "Overview of Deploying Oracle Beehive". At minimum, you should plan to deploy the system in the following stages:

- Development: Map out host names, servers, components, services, and access on a small scale.

- Staging: Expand your initial deployment for use by a test group, to expose configuration issue flaws and also to test the capacity and performance.

- Production: Official live deployment for use by the entire organization.

To ease the transition from a development environment to a production environment, it is best to use virtual host names from the start, as described in the "Scalability Considerations" section. With this strategy, you can grow your deployment without having to greatly modify the integration of your services and components.

Does your organization need high availability?

Keep in mind that implementing a high availability deployment generally doubles the need for hardware. As such, you should consider implementing cold failover strategies and becoming familiar with Oracle 10g Real Application Clusters (Oracle RAC).

Storage strategies in a high availability deployment are much different than in a standard deployment. If shared storage is needed, consider external Small Computer System Interface (SCSI) storage or a storage area network (SAN), a high-speed specialized network that interconnects different kinds of data storage devices with associated data servers or network attached storage (NAS).

The increased complexity of a high availability environment means that installation and configuration involves significantly more planning and effort than does a non-high availability environment. Management of a high availability environment is also more complex and should be allocated the appropriate amount of time.

What is your organization's existing backup solution?

Recommended backup strategies for most organizations include standing policies for regular, scheduled data backups, file system backups, and tape backups. Also, your organization might have mandated recovery times and granularity for data recovery that you'll need to consider.

7 Oracle Beehive Deployment Configurations

Oracle Beehive provides a flexible system deployment model that supports a variety of configurations. This section provides high-level details on the following main deployment configurations:

- Deploying Oracle Beehive on a Single Computer

- Deploying Oracle Beehive on Multiple Computers

- Deploying Oracle Beehive Across Network Zones

Deploying Oracle Beehive on a Single Computer

Oracle Beehive can be deployed on a single computer. In this case, the system can leverage a single Oracle Database instance located on the same computer, as illustrated by Figure 7-1, "Oracle Beehive and Oracle Database Deployed on a Single Computer", or it may leverage an Oracle Database instance that resides on another computer, as illustrated by Figure 7-2, "Oracle Beehive and Oracle Database Deployed on Different Computers". However, the latter case is more likely and, in fact, strongly recommended. The system can also leverage a database cluster, residing among several other computers, using Oracle Real Application Clusters (Oracle RAC).

Figure 7-1 Oracle Beehive and Oracle Database Deployed on a Single Computer

Description of "Figure 7-1 Oracle Beehive and Oracle Database Deployed on a Single Computer"

Additionally, Oracle Beehive provides all required user directory components so it can function as an independent system. It can also integrate with one or more external LDAP- based corporate directories such as Oracle Internet Directory or Microsoft Active Directory Server.

Figure 7-2 Oracle Beehive and Oracle Database Deployed on Different Computers

Description of "Figure 7-2 Oracle Beehive and Oracle Database Deployed on Different Computers"

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 high levels of guaranteed services are required.

Deploying Oracle Beehive on Multiple Computers

Oracle Beehive supports deployments where multiple Oracle Beehive server instances are distributed across multiple computers. In this scenario, each computer hosts one Oracle Beehive instance, which can be accessed through load balancing routers (LBRs).

Each instance runs all available services provided with Oracle Beehive. For example, if you have five computers, each with an Oracle Beehive server instance, you will five instances each of the User Directory Service, the E-mail Service, and so forth. However, each service is instantiated as a single deployment of the service, or as a single 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 a supported 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 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.

Figure 7-3 Multiple Oracle Beehive Instances on Multiple Computers

Description of "Figure 7-3 Multiple Oracle Beehive Instances on Multiple Computers"

During the Oracle Beehive installation process, you provide the names for your Enterprise, Organization, Site, and Instance. To successfully deploy multiple Oracle Beehive instances, you must provide the same names for Enterprise, Organization, and Site for all instances. You must also specify the same Oracle Database instance for all Oracle Beehive server instances.

Deploying Oracle Beehive Across Network Zones

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 a corporate intranet or a demilitarized zone (DMZ) 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, refer to "Deploying Oracle Beehive 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.

Figure 7-4 Oracle Beehive Deployed Across Multiple Network Zones

Description of "Figure 7-4 Oracle Beehive Deployed Across Multiple Network Zones"

How the Beehive Transport Infrastructure (BTI) Supports Multiple Network Zones

Deployments that leverage segregated network zones with limited connectivity between these zones is common. These requirements are an evolution of continually improving security policies and best practices. The BTI provides the flexibility to integrate well with this configuration scenario and almost any other topology requirements.

The BTI enables Oracle Beehive to accommodate any number of network buffer zones while still providing client access. This maintains open access to the system but limits the possibility of system compromise.

The BTI provides a plug-in (mod_bti) to Oracle HTTP Server, which allows enterprises to expose only one or two standard open ports to the Internet without limiting client access. The mod_bti does so by recognizing Oracle Beehive MX protocol traffic and transparently redirecting those requests to the appropriate Oracle Beehive services.

The BTI allows enterprises to place very thin network services in the DMZ and minimize exposure of the Application and Data Tiers, while providing secure client access to Oracle Beehive services.

8 Deploying Oracle Beehive with Supported Clients and Devices

The Oracle Beehive platform provides a unified client implementation model that supports deployments with a variety of end-user clients and devices. This chapter discusses the considerations related to deploying supported clients and devices, and includes the following topics:

- Oracle Beehive Deployments with Oracle Beehive Extensions for Outlook

- Oracle Beehive Deployments with Oracle Beehive Extensions for Explorer

- Oracle Beehive Deployments with Oracle Beehive Central

- Oracle Beehive Deployments with Oracle Beehive Conferencing

- Oracle Beehive Deployments with Oracle Beehive Team Collaboration

- Oracle Beehive Deployments with Oracle Beehive Webmail

- Oracle Beehive Deployments with Mobile Devices

- Oracle Beehive Deployments with Standards-based Clients

Oracle Beehive Deployments with Oracle Beehive Extensions for Outlook

Note:
As of Oracle Beehive Release 1 (1.5), the product name Oracle Beehive Integration for Outlook has been changed to Oracle Beehive Extensions for Outlook.

Oracle Beehive Extensions for Outlook is a Messaging Application Programming Interface (MAPI) service provider for Microsoft Outlook. Oracle Beehive Extensions for Outlook extends the functionality of Microsoft Outlook by providing Outlook users with unified access to Oracle Beehive-based collaborative features and data in a familiar environment. Oracle Beehive Extensions for Outlook requires installation on the computers of individual users.

This section provides the following topics:

- Considerations for Deploying Oracle Beehive Extensions for Outlook

- Populating User's Global Address Lists (GAL) Incrementally

- Migrating Users' Microsoft Outlook Settings and Profiles

- Upgrading Oracle Beehive Extensions for Outlook

- How Oracle Beehive Extensions for Outlook Communicates with Oracle Beehive

Considerations for Deploying Oracle Beehive Extensions for Outlook

To access, download, and install Oracle Beehive Extensions for Outlook on your system, Oracle Beehive provides a download agent, which is accessible from the following location:

$ORACLE_HOME/beehive/bootstrap/obeo/setup

Administrators can make the download agent available to users from 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.

Oracle Beehive also provides a language pack application module for Oracle Beehive Extensions for Outlook, which can be accessed by administrators in the same location as the Oracle Beehive Extensions for Outlook download agent. Administrators can modify the application module by adding or removing one or more languages. The module can be deployed to users through the Device Management Application Repository or another preferred method, such as by download from an intranet.

By default, Oracle Beehive provides Oracle Beehive Extensions for Outlook 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. The structure of the file follows the XML-based metadata schema mandated by the Device Management Service (DMS).

Populating User's Global Address Lists (GAL) Incrementally

By default, new installations of Oracle Beehive Extensions for Outlook that are deployed using the Device Management Service (DMS) method will initially construct the Global Address List (GAL) by downloading only the manager, peers, direct reports, and groups of the authenticated user. Additional contacts will be downloaded and added to the local cache on an ad-hoc basis whenever the user performs an action that requires a server lookup. Whenever the user performs an action like creating or receiving e-mail and creating or receiving meeting invites with contacts that are not in the local GAL, that contact or the list of contacts will then be added to the local GAL. This is referred as the Smart GAL mode.

The Smart GAL approach substantially reduces the load on the User Directory Service (UDS) after an upgrade or patch that affects the structure of UDS entries. Furthermore, some users might prefer this approach, as it makes their GALs more manageable by populating only those contacts with whom they are most likely to communicate.

You can disable this behavior by editing the following section of the Client Application metadata.xml file, and then uploading the file to Oracle Beehive using the beectl upload_client_application command:

<configuration>
<param name="FILE:profile.ini:GENERAL:GAL-DOWNLOAD-UDS-ON-DEMAND-CACHING-ONLY" value="FALSE"></param>
</configuration>

Advantages of Smart GAL mode

- Users do not have to wait till the entire GAL is downloaded.

- The initial GAL size is small and it does not take long to download and construct the initial list.

- The GAL grows dynamically and adds entries in the local list incrementally as the user communicates with other users and groups.

- Adding new contacts and groups is easy and automatic.

Limitations of GAL Smart GAL mode

- The initial local GAL does not contain the full list as on the server.

- If needed, users have to initiate the download of the full GAL manually from the menu options.

- Server lookup for new contacts and groups is necessary when they are not in the local GAL.

For more information, refer the chapter "Installing Oracle Beehive Extensions for Outlook" in the Oracle Beehive Installation Guide for your platform.

Migrating Users' Microsoft Outlook Settings and Profiles

To ease the transition to Oracle Beehive Extensions for Outlook, Oracle Beehive provides a migration tool in the download agent. The Oracle Beehive Extensions for Outlook migration tool enables users to:

- Migrate existing personal folder data files (*.pst) from previous profiles

- Migrate LDAP settings from previous profiles

- Add new LDAP settings

- Add new personal folder data files

To present users these options requires administrators to enable the migration tool with the /migrate option. Administrators must also configure and specify the migration .ini file (migrateinifile.ini) provided with Oracle Beehive. If the migration tool initialization file is not specified, then the download agent will only allow users to migrate personal folder data files and LDAP settings from previous profiles. For more information, see Oracle Beehive Installation Guide for Microsoft Windows.

Note:
Using the profile migration tool is an advanced deployment option. If you intend to use this tool, then Oracle recommends that you plan for and test it accordingly.

Upgrading Oracle Beehive Extensions for Outlook

Administrators can upgrade existing Oracle Beehive Extensions for Outlook versions simply by deploying newer packages to the Device Management Application Repository using beectl. Administrators can also remove existing packages and replace them with newer ones, as needed. After installation on user computers, Oracle Beehive Extensions for Outlook automatically detects newer versions that are made available through the Device Management Service. Users can receive updates automatically upon Outlook startup or manually by clicking the update option in the About Oracle Beehive Extensions for Outlook dialog window.

How Oracle Beehive Extensions for Outlook Communicates with Oracle Beehive

Oracle Beehive Extensions for Outlook communicates with Oracle Beehive through the Beehive Transport Infrastructure (BTI) and the proprietary MX protocol that the BTI provides. Thus, Oracle Beehive Extensions for Outlook users can either connect directly to an Oracle Beehive deployment or they can be tunneled through standard HTTPS ports.

Oracle Beehive Deployments with Oracle Beehive Extensions for Explorer

Oracle Beehive Extensions for Explorer is an extension to Microsoft® Windows® Explorer that provides Oracle Beehive users direct access to their workspaces and workspace content. Oracle Beehive Extensions for Explorer is supported on the Microsoft Windows XP and Vista operating systems.

Oracle Beehive Extensions for Explorer requires a client installation on the computers of individual users. Administrators can make the Oracle Beehive Extensions for Explorer client installation package available to users through internal websites or Oracle Beehive Central. Users can then download and install Oracle Beehive Extensions for Explorer on their computers.

To access, download, and install Oracle Beehive Extensions for Explorer on users' computers, Oracle Beehive provides a download agent, which is accessible from the following location:

$ORACLE_HOME/beehive/bootstrap/obee/setup

Administrators can make the download agent available to users from 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 Oracle Beehive Extensions for Explorer installation.

Note:
In addition to the download agent distribution model, administrators can manage and distribute the Oracle Beehive Extensions for Explorer installation package through Microsoft Windows Server 2003 SP 2 for Windows Terminal Services. Oracle Beehive Extensions for Explorer can also leverage Windows Terminal Services once it is installed.

Oracle Beehive also provides a language pack application module for Oracle Beehive Extensions for Explorer, which can be accessed by administrators in the same location as the Oracle Beehive Extensions for Explorer download agent. Administrators can modify the application module by adding or removing one or more languages. The module can be deployed to users through the Device Management Application Repository or another preferred method, such as by download from an intranet.

By default, Oracle Beehive provides Oracle Beehive Extensions for Explorer 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. The structure of the file follows the XML-based metadata schema mandated by the Device Management Service.

Oracle Beehive Deployments with Oracle Beehive Central

Oracle Beehive Central is a Web-based client that provides users a central location to download supported clients and set their preferences for Oracle Beehive functionality. This includes the ability to delegate privileges for users' e-mail, calendars, tasks, notes, journals, and contacts.

Oracle Beehive Central provides both a public and private home page. The public home page is accessible to all users and does not require them to provide authentication credentials. Typically, the public home page is used to allow users to download supported clients. The private home page is accessible only to users that provide their authentication credentials. The private home page is where users can set their preferences for Oracle Beehive functionality, in addition to downloading supported clients.

Oracle Beehive Central 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/

Security Considerations for Oracle Beehive Central

When deployed with the user directory provided by Oracle Beehive, Oracle Beehive Central enables users to change their passwords through the Change Password tab. In this scenario, Oracle strongly recommends that you enable SSL for your deployment to ensure that only encrypted password data is transmitted.

When deployed with an external user directory, that is, a user directory other than the one provided by Oracle Beehive, Oracle Beehive Central does not allow users to change their passwords. In fact, Oracle Beehive Central does not display the Change Password tab in this scenario as a security measure against the possible transmission of password data over less secure networks.

For more information about enabling SSL for your deployment, see "Configuring SSL for LDAP Integration" in the Oracle Beehive Installation Guide for your operating system.

Oracle Beehive Deployments with Oracle Beehive Conferencing

Oracle Beehive Conferencing is a feature-rich desktop client that enables Oracle Beehive users to conduct Web-based meetings and presentations. Deploying Oracle Beehive Conferencing includes server-side and client-side considerations, which are discussed in the following topics:

- Deploying the Voice Conferencing Media Server

- Deploying Oracle Beehive Conferencing on Users' Computers

Deploying the Voice Conferencing Media Server

Oracle Beehive comes with the Voice Conferencing Media Server, which provides voice conferencing functionality for Oracle Beehive Conferencing. To ensure overall system performance and the quality of voice conferences, Oracle recommends that you deploy the Voice Conferencing Media Server on its own dedicated computer and then configure your Oracle Beehive instance to use the remote Voice Conferencing Media Server instance. Furthermore, since the Voice Conferencing Media Server is supported on Linux x86 computers only, this recommendation applies to all Oracle Beehive deployments, including those on the Sun Solaris and Microsoft Windows operating systems.

For more information on how to install and configure the Voice Conferencing Media Server on its own computer, see "Configuring Remote Media Server for Oracle Beehive Conferencing" in the Oracle Beehive Installation Guide for your operating system.

Deploying Oracle Beehive Conferencing on Users' Computers

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 Conferencing client is supported on both Windows and Macintosh operating systems.

Oracle Beehive also provides the Oracle Beehive Web Conferencing Center, which enables users to view, start, join, filter, delete, and refresh their scheduled conferences through supported Web browsers. After Oracle Beehive and Oracle Beehive Conferencing are installed and configured, users can access and leverage the Oracle Beehive Web Conferencing Center 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>/bconf/

The Oracle Beehive Web Conferencing Center supports Mozilla Firefox 3.0 in the Windows, Linux, Mac OS X, and Solaris operating systems, and Microsoft Internet Explorer 7.0 in the Windows operating system only.

Oracle Beehive Deployments with Oracle Beehive Team Collaboration

Oracle Beehive Team Collaboration is a Web-based client that leverages dynamic, wiki page technology to support team collaboration activities in Oracle Beehive workspaces.

Oracle Beehive Team Collaboration 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>/workspaces/

Oracle Beehive Team Collaboration supports the following Web browsers on the Microsoft Windows XP, Microsoft Vista, Mac OS X, and Linux operating systems:

- Apple Safari 4

- Microsoft Internet Explorer 7

- Mozilla Firefox 3.x

Oracle Beehive Deployments with Oracle Beehive Webmail

Oracle Beehive Webmail is a powerful online messaging and collaboration tool providing instant anytime access to your Beehive mail, calendar, contacts, tasks, and workspace content. In addition, Oracle Beehive Webmail extends calendar management features by allowing you to schedule and join Beehive conferences. You can also organize, search, and tag content, view and manage your personal and team workspaces, build multiple address book hierarchies, and share and delegate address books, mail folders, calendars, and tasks lists.As you travel, Oracle Beehive Webmail offers easy access through your Web browser (from your computer or mobile device), allowing you to retrieve and send mails, schedule meetings, and access team workspace activity, from anywhere you have Web access.

Deploying Oracle Beehive Webmail 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, or it can occur separately.

Note:
As of Oracle Beehive Release 1.5, Beehive Webmail no longer needs to be installed in a separate Oracle home.

After Oracle Beehive Webmail is installed and configured on an Oracle Beehive server instance, users can access and leverage it 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 Webmail is based on the open source Zimbra Web client and supports the following Web browsers in the Windows (Vista and XP) and Mac OS X operating systems:

- Apple Safari 3

- Mozilla Firefox 2.0

- Mozilla Firefox 3.0

- Microsoft Internet Explorer 6.0

- Microsoft Internet Explorer 7.0

Oracle Beehive Deployments with Mobile Devices

Oracle Beehive enables users of supported mobile devices to send and receive collaborative data, such as e-mail, calendar synchronization, and instant messages. Deploying mobile devices with Oracle Beehive typically requires completion of the following tasks:

- Deciding on which mobile devices your organization wants to deploy. For the complete list of mobile devices that Oracle Beehive supports, see Oracle Beehive Mobile Devices Help at the following location:
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm

- Deciding on which client applications your organization wants to deploy on users' mobile devices.
For information on deploying Oracle Beehive mobile clients, see "Mobile Device Clients Provided by Oracle Beehive".

For information on deploying mobile clients on Apple iPhone devices, see "Deploying Oracle Beehive Mobile Clients on Apple iPhone".

For information on deploying mobile clients on Microsoft Windows Mobile and RIM BlackBerry devices, see "Deploying Mobile Clients on Microsoft Windows and RIM BlackBerry Mobile Devices".

For the list of client applications that Oracle Beehive supports for a particular mobile device, see the section for that device in Oracle Beehive Mobile Devices Help at the following location:

http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm

- Uploading the selected client applications to the Device Management Application Repository. You perform this step using the upload_client_application command in the beectl utility.
For more information, see "Uploading and Provisioning a New Application" in the Oracle Beehive Administrator's Guide.

- Opening firewall ports for any services and protocols required by the devices and clients that you plan to deploy.
For more information, see "Recommended Ports for Mobile Device-related Services and Protocols".

- Registering the selected mobile devices with Oracle Beehive and configuring them based on the settings of your deployment.
For details on how to register and configure supported devices for Oracle Beehive, see the Oracle Beehive Mobile Devices Help at the following location:

http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm

- Install the selected clients on users' devices and configure them based on the settings of your Oracle Beehive deployment.
For more information, see Oracle Beehive Mobile Devices Help at the following location:

http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm

- Enabling the Oracle Beehive SMS Delivery Channel, if your organization wants to leverage the network of a Short Message Service (SMS) service provider or if you want to leverage the mobile device registration functionality provided by Oracle Beehive Centrall.
For more information, see "Enabling the Oracle Beehive Short Message Service (SMS) Delivery Channel".

For information on other administrative tasks related to mobile devices and services, see "Managing Oracle Beehive Mobility Services" in the Oracle Beehive Administrator's Guide.

Recommended Ports for Mobile Device-related Services and Protocols

Oracle recommends that you open the following firewall ports for any services and protocols required by the mobile devices and clients that you plan to deploy:

Table 8-1 Recommended Ports for Mobile Device-related Services and Protocols

Service

Purpose

Recommended Port

Mobile Data Sync Service (using Open Mobile Alliance Data Synchronization, or OMA-DS)

Provides for automatic synchronization of e-mail, calendar, task, and address book data for any mobile device with an OMA-DS compliant client

Use the same port as designated for HTTPS (port 443). HTTP (port 80) is also supported although not recommended.

Mobile Device Management Service

Manages the communications and configuration settings for the Mobile Device Management Server, which enables connections between the Device Management Service and supported device-resident Mobile Device Management clients.

Use the same port as designated for HTTPS (port 443). HTTP (port 80) is also supported although not recommended.

Mobile Mail Service (over Push Internet Message Access Protocol, or P-IMAP)

Provides a complete P-IMAP v0.6 implementation for real-time delivery of e-mail to users' mobile devices.

Use the same port as designated for Secure Beehive Transport Protocol (BTPS). Beehive Transport Protocol (BTP) is also supported although not recommended.

Mobile Push Service

Responsible for delivering notifications to push clients running on end users' mobile devices.

Use the same port as designated for Secure Beehive Transport Protocol (BTPS) or HTTPS (port 443). Beehive Transport Protocol (BTP) and HTTP (port 80) are also supported, although neither is recommended.

Mobile Device Clients Provided by Oracle Beehive

Oracle Beehive provides the following mobile device clients:

- Oracle Beehive Mobile Communicator, which provides mobile instant messaging capabilities. Oracle Beehive Mobile Communicator is supported on Microsoft Windows Mobile, RIM BlackBerry, and iPhone mobile devices.

- Oracle Beehive Mobile Messaging, which enables real-time push mail also updates to calendar entries, tasks, and contacts for the Blackberry devices.

- A plug-in for Microsoft Windows Mobile Outlook, which enables real-time push mail also updates to calendar entries, tasks, and contacts. The Microsoft Windows Mobile Outlook plug-in is supported on Microsoft Windows Mobile devices only.

For more information on deploying Oracle Beehive mobile clients on supported Apple iPhone devices, see "Deploying Oracle Beehive Mobile Clients on Apple iPhone".

For more information on deploying Oracle Beehive mobile clients on supported Microsoft Windows Mobile and RIM BlackBerry devices, see "Deploying Mobile Clients on Microsoft Windows and RIM BlackBerry Mobile Devices".

Deploying Oracle Beehive Mobile Clients on Apple iPhone

Users can visit the Apple Store to download and install Oracle Beehive Mobile Communicator on supported Apple iPhone devices. For more information, see the Oracle Beehive Mobile Devices Help at the following location:

http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm

Deploying Mobile Clients on Microsoft Windows and RIM BlackBerry Mobile Devices

To install, provision, and manage mobile clients on supported Microsoft Windows Mobile and RIM BlackBerry devices, Oracle Beehive provides the Mobile Management Console. Before downloading and installing supported mobile clients, users must first install the Mobile Management Console on their mobile devices. Oracle provides the Mobile Management Console as a .cab file for Microsoft Windows Mobile devices and as a .jad file for RIM BlackBerry devices.

Oracle Beehive supports the following methods for downloading and installing the Mobile Management Console:

- Over-the-air (OTA): Supported for Microsoft Windows Mobile and RIM BlackBerry devices. Users register their mobile devices using Oracle Beehive Central or by connecting to the following URL in a Web browser on their mobile devices:
https://<Your-Server-Name>:<Port-Number>/mobiledm

After registering, Oracle Beehive provides users a link so that they can download and install the Mobile Management Console.

For more information on the server-side requirements and considerations for the OTA deployment option, see "Enabling the Oracle Beehive Short Message Service (SMS) Delivery Channel".

For more information on the mobile device requirements and considerations for the OTA deployment option, see "Over-the-Air Configuration Using SMS" and "Over-the-Air Configuration Without SMS" in Oracle Beehive Mobile Devices Help at the following location:

http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm

- Active synchronization (ActiveSync): Supported for Microsoft Windows Mobile only. Users download the .cab file to their computers through a Windows-based utility provided with Oracle Beehive. Users then synchronize their mobile devices with their computers to install the .cab file.
For more information on the ActiveSync deployment option, see "Configuration Using ActiveSync" in Oracle Beehive Mobile Devices Help at the following location:

http://www.oracle.com/technology/products/beehive/beehive_users/2_0/mobile.htm

- Storage card: Supported for Microsoft Windows Mobile only. Administrators or support personnel download the .cab file to their computers through a Windows-based utility provided with Oracle Beehive. Then, they run the utility from the command line to install the .cab file on storage cards. Users can then insert the storage cards into their devices.

After the Mobile Device Management Console is installed, it automatically starts, connects to the Oracle Beehive Mobile Device Management Service, and requests a list of all available mobile software for the user, including Oracle Beehive Mobile Communicator and the Mobile Outlook plug-in (for Microsoft Windows Mobile devices only). The list can also contain other third-party mobile software managed by Oracle Beehive. Users may then choose which software to install on their mobile devices.

To upgrade Oracle Beehive Mobile Communicator, the Mobile Outlook plug-in, or other third-party mobile software managed by Oracle Beehive, users can periodically check for updates on their mobile devices or they can wait for their Oracle Beehive administrators to provide alerts informing them of available updates.

Enabling the Oracle Beehive Short Message Service (SMS) Delivery Channel

The Oracle Beehive SMS Delivery Channel is the component of the SMS Service that enables delivery of SMS messages. The SMS Delivery Channel supports the Short Message Peer-to-Peer (SMPP) protocol, which is a telecommunications industry standard supported by most SMS service providers.

By default, the Oracle Beehive SMS Delivery Channel is configured to use the Verisign Intelligent Messaging Network. However, organizations may choose to leverage the network of any SMS service provider that supports SMPP, such as Clickatell. Organizations may also leverage the Oracle iAS Wireless XMS interface, which was the default interface for Oracle Collaboration Suite 10g and is also supported by Oracle Beehive.

The steps required to configure and enable the SMS Delivery Channel depend on which SMS service provider you choose. For example, if you choose the Verisign Intelligent Messaging Network, you must first subscribe to it (to request a free trial, contact Verisign). After you activate your Verisign subscription, you will need to configure and enable the Oracle Beehive SMS Delivery Channel for it. This includes configuring your SMPP settings, setting your SMS mode to SMPP, and enabling the SMS Delivery Channel. To perform these tasks, you use the beectl utility.

For more information on the specific steps required to configure the SMS Delivery Channel for your chosen SMS provider, see the section entitled "Configuring SMS using SMPP" in the Oracle Beehive Administrator's Guide.

Oracle Beehive Deployments with Standards-based Clients

Oracle Beehive supports several standards-based protocols, enabling organizations to deploy commonly-available and custom clients with the platform. Standards-based clients can provide a wide array of Oracle Beehive functionality, such as e-mail, time management, and instant messaging.

Deploying standards-based clients typically requires the following steps:

- Deciding on which standards-based clients your organization wants to deploy. For the complete list of standards-based clients that Oracle Beehive supports, see Oracle Beehive Standards-based Client Help at the following location:
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/standards.htm

- Making available for download the installation packages of the standards-based clients that your organization wants to deploy. Typically, this can be accomplished by posting the installation packages on your organization's intranet or from another internally accessible location.

- Opening firewall ports for any standards-based services required by the clients that you plan to deploy, such as SMTP (for e-mail clients) or XMPP (for instant messaging clients). This step should be completed if you expect to support remote users, although it might not be required in cases where remote users access Oracle Beehive through virtual private networks (VPNs).

- Installing the selected clients on users' computers and devices. For details on how to install a particular standards-based client, refer to the documentation provided with the client that you want to install.

- Configuring the installed client applications based on the settings of your Oracle Beehive deployment. For details on how to configure supported standards-based clients, see Oracle Beehive Standards-based Client Help at the following location:
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/standards.htm

Note:

- For additional considerations related to deploying standards-based clients on mobile devices, see "Oracle Beehive Deployments with Mobile Devices".

Index

A  B  C  D  E  F  H  I  J  L  M  N  O  P  R  S  T  V  W  Z

A

access, 5.3, 5.5

administration, 1.4.9

tools

Oracle Beekeeper, 3.3, 3.3

Ancillary Tier, 2.1, 2.1.4 Application Tier, 2.1, 2.1.2, 2.2.1 Application Zone, 7.3 availability, 6.5

B

backup, 6.9

beectl, 8.1.4

Beehive Transport Infrastructure (BTI), 2.2, 2.2.2, 5.4.1, 5.5, 7.3.1, 7.3.1, 8.1.5

Beehive Webmail, 8.6

Berkeley Internet Name Domain (BIND), 5.5

BIND

See Berkeley Internet Name Domain (BIND)

BTI

See Beehive Transport Infrastructure

See Beehive Transport Infrastructure (BTI)

business events, 2.2.3

C

CalDAV

See Calendaring Extensions to WebDAV (CalDAV)

Calendaring Extensions to WebDAV (CalDAV), 2.1.1 client

standard protocol, 8.8

Client Access Zone, 7.3 Client Tier, 2.1, 2.1.1 clients

mobile devices, 8.7

Oracle Beehive Extensions for Outlook, 8.1

cloning, 7.2 Code Schema

about, 2.2.4.1

configuration, 1.4.4 content switches, 5.5 customization, 1.4.5

D

Data Schema

about, 2.2.4.2

Data Tier, 2.1, 2.1.3, 2.2.1 Data Zone, 7.3 Database Access Framework, 2.1.3, 2.2

about, 2.2.1

demilitarized zones (DMZs), 1.5.3, 2.2.2, 5.4.2, 5.5, 5.5, 5.5, 5.5, 6.2, 6.8, 7.3.1 deploying

across network zones, 7.3

in stages, 6.9

on a single computer, 7.1

on multiple computers, 7.2

deployment

prerequisites, 1.3

stages, 1.4

Device Management Repository, 8.1.1, 8.1.4, 8.2 DMZ

See demilitarized zones (DMZs)

DNS

See Domain Name System (DNS)

Domain Name System (DNS), 5.3, 5.5, 5.5

servers, 5.5, 5.5

E

enterprises, 1.5.8

Event Framework, 2.2

about, 2.2.3

extending, 2.2.3

events

business events, 2.2.3

Extensible Messaging and Presence Protocol (XMPP), 2.1.1

F

File Transfer Protocol (FTP), 2.1.1

firewalls, 5.3, 5.5, 5.5

H

high availability, 6.1, 6.9, 7.3

HTTP

See HyperText Transfer Protocol (HTTP)

HTTPS

See Hypertext Transfer Protocol Over Secure Socket Layer

See Secure HyperText Transfer Protocol (HTTPS)

HyperText Transfer Protocol (HTTP), 5.3, 5.4.2, 5.5 Hypertext Transfer Protocol Over Secure Socket Layer (HTTPS), 3.3

I

IBM Tivoli Access Manager WebSEAL, 2.1.4

IBM Tivoli Directory Server, 2.1.4

installation, 1.4.4, 7.2

instances, 1.5.6

Internet Message Access Protocol (IMAP), 2.1.1, 5.5

J

J2EE

See Java 2 Platform Enterprise Edition (J2EE)

Java 2 Platform Enterprise Edition (J2EE), 2 Java Database Connectivity (JDBC), 2.2.1 JDBC

See Java Database Connectivity (JDBC)

L

launching the system, 1.4.7

load balancers, 5.5, 5.5, 5.5, 7.2

M

mail relays, 5.3, 5.5, 5.5, 5.5

maintenance, 1.4.9

Microsoft Active Directory, 2.1.4

Microsoft Exchange Server, 2.1.4

Microsoft Outlook, 1.1, 2.1.1, 2.2.2

Microsoft Windows, 8.7.4

Microsoft Windows Explorer, 8.2

Microsoft Windows Mobile Outlook, 8.7.2

plug-in for, 8.7.2

Mobile Device Management Console, 8.7.4 Mobile Device Management Service, 8.7.4 mobile devices

deploying, 8.7

Microsoft Windows-based, 8.7.4

mod_bti, 7.3.1 multiple computer deployments, 7.2 multiplexor protocol (MX), 2.1.2, 7.3.1, 8.1.5 MX

See multiplexor protocol (MX)

N

NAS

See network attached storage (NAS)

NAT

See Network Address Translation (NAT)

Network Address Translation (NAT), 5.5, 5.5 network attached storage (NAS), 6.9 network capacity, 5.5, 6.3 network services, 5.5, 5.5 network traffic

external, 5.4.2

internal, 5.4.1

network zone deployments, 7.3 network zones, 1.5.2, 7.3

Application Zone, 7.3

Client Access Zone, 7.3

Data Zone, 7.3

nodes, 1.5.1

O

OID

See Oracle Internet Directory (OID)

OMA-DS

See Open Mobile Alliance Data Synchronization

Open Mobile Alliance Data Synchronization (OMA-DS), 2.1.1, 8.7.1 OpenLDAP Directory Server, 2.1.4 Oracle Application Server, 2, 2.1.2 Oracle Beehive

schemas, 2.2

about, 2.2.4

Code Schema, 2.2.4.1

Data Schema, 2.2.4.2

tiers

Ancillary Tier, 2.1.4

Application Tier, 2.1.2

Client Tier, 2.1.1

Data Tier, 2.1.3

Oracle Beehive Central, 8.3 Oracle Beehive Extensions for Explorer, 8.2 Oracle Beehive Extensions for Outlook, 2.2.2, 8.1

deploying, 8.1, 8.1.1, 8.2

download agent, 8.1.1, 8.2

upgrading, 8.1.4

Oracle Beehive Team Collaboration, 8.5 Oracle Beekeeper, 3.3, 3.3 Oracle Database, 2, 2.1.3, 6.7, 7.1, 7.2 Oracle HTTP Server, 5.4.2, 5.5, 7.3.1 Oracle Internet Directory (OID), 2.1.4 Oracle Real Application Clusters (Oracle RAC), 2.1.3, 7.1

nodes

adding, 2.2.1

removing, 2.2.1

Oracle Secure Enterprise Search, 2.1.4 Oracle Single Sign-On (OSSO), 2.1.4 organizations, 1.5.8 OSSO

See Oracle Single Sign-On

P

P-IMAP

See Push Internet Message Access Protocol

policies

network, 5.5

security, 5.5

Push Internet Message Access Protocol (P-IMAP), 2.1.1, 8.7.1

R

RAC

See Oracle Real Application Clusters (Oracle RAC)

recovery, 6.4 reverse proxies, 5.3, 5.5 routers, 5.5

S

SAN

See storage area network (SAN)

scalability, 6.6 schemas

about, 2.2.4

Oracle Beehive, 2.2

SCSI

See Small Computer System Interface (SCSI)

Secure HyperText Transfer Protocol (HTTPS), 5.3, 5.4.2, 5.5, 5.5 Secure Sockets Layer (SSL), 5.3, 5.5, 5.5 security, 5.3, 6.8

policies, 5.5

spam and virus filters, 5.5

servers, 1.5.1 services, 1.5.5, 5.5 Simple Mail Transfer Protocol (SMTP), 2.1.1, 5.5, 5.5, 5.5 single computer deployments, 7.1 sites, 1.5.7 Small Computer System Interface (SCSI), 6.9 SMTP

See Simple Mail Transfer Protocol (SMTP)

spam, 5.5

services, 5.5

SSL

See Secure Sockets Layer (SSL)

standard protocol clients

deploying, 8.8

storage

network attached storage (NAS), 6.9, 6.9

Small Computer System Interface (SCSI), 6.9, 6.9

storage area network (SAN), 6.9, 6.9

storage area network (SAN), 6.9 Sun Java Directory Server, 2.1.4 Symantec Anti-Virus Scan Engine, 2.1.4 system administration, 1.4.9 system configuration, 1.4.4

T

testing, 1.4.6

tiers

Ancillary Tier, 2.1.4

Application Tier, 2.1.2, 2.2.1

Client Tier, 2.1.1

Data Tier, 2.1.3, 2.2.1

TLS

See Transport Layer Security (TLS)

training, 1.4.7 Transport Layer Security (TLS), 5.3

V

Virtual Private Networks (VPNs), 5.5

viruses, 5.5

VPN

See Virtual Private Networks (VPNs)

W

Web-based Distributed Authoring and Versioning (WebDAV), 2.1.1

workload, 6.7

Z

zones

network, 1.5.2

Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved.