| Oracle® Beehive Deployment Guide Release 2 (2.0.1.8) Part Number E16645-06 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Deployment Guide Release 2 (2.0.1.8) Part Number E16645-06 |
|
|
PDF · Mobi · ePub |
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 Team Collaboration
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
How Oracle Beehive Extensions for Outlook Communicates with Oracle Beehive
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).
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>
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.
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.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.
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 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 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/
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 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:
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.
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 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 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 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.
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
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".
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
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.
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 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".
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
