| Oracle® Beehive Installation Guide Release 2 (2.0.1.8) for Microsoft Windows x86 Part Number E16642-07 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Installation Guide Release 2 (2.0.1.8) for Microsoft Windows x86 Part Number E16642-07 |
|
|
PDF · Mobi · ePub |
This chapter describes how to install Oracle Beehive Conferencing clients.
There are two clients supported by Beehive Conferencing:
Oracle Beehive Java-based (JavaFX) Conferencing Client
The Oracle Beehive Java-based Conferencing client (also referred to as JavaFX client), by default, is the primary client used to participate in Beehive conferences. However, a user can customize the primary client through Oracle Beehive Central.
When a user joins a conference from a calendar event, e-mail notification, or directly from the Oracle Beehive Conferencing Web Center, the user will be brought to the Oracle Beehive Conferencing Web Center where they will automatically launch into Java-based conferencing application. Being Java-based, the installation of the client is done automatically, with all the necessary Java and JavaFX components. End users are not required to install or deploy any components directly on their machines themselves.
Oracle Beehive Conferencing Desktop Client
The Oracle Beehive Conferencing Desktop Client is a desktop-based application that requires a local installation on each machine. It is only recommended for users using platforms not supported by the JavaFX client.
This section describes how to deploy the JavaFX Conferencing client and the Oracle Beehive Conferencing desktop client using Oracle Beehive's Device Management Service (DMS). This deployment method is recommended for all desktops with standard environments. Currently a desktop based, non-DMS installation method is not available for custom installation.
This chapter covers the following topics:
This section describes the software and hardware requirements for the JavaFX Conferencing and the Oracle Beehive Conferencing client. For updated list of certified hardware platforms and operating system version, review the certification matrix on the My Oracle Support Web site at the following URL:
JavaFX Conferencing Client Operating System
Microsoft Windows Vista: Home, Business, or Ultimate
Microsoft Windows XP: Home or Professional
Microsoft Windows 7 (32-bit and 64-bit edition) - Home Premium, Professional, Ultimate or Enterprise
Note:
Write privileges are required for the destination folder of the installation path of Oracle Beehive Conferencing.Microsoft Installer framework version 2.0 or above is required for Windows installations. This framework is included in Microsoft Windows XP and later versions of Microsoft Windows.
Apple Mac OS X 10.6 (Snow Leopard) and 10.7 (Lion)
Note:
The Java-based Conferencing Client for the Macintosh only supports Intel processors; PowerPC processors are not supported.Linux Ubuntu 10.x
Other Components for JavaFX Conferencing Client
Java Runtime Environment 1.6.0.23 or later. The end user will be prompted to upgrade if the Java version in their machine does not match the requirements.
Mac and Linux users may need to set the Web proxy in the Java Control Panel to an explicit proxy.
Oracle Beehive Conferencing Client Operating System
Microsoft Windows Vista: Home, Business, or Ultimate
Microsoft Windows XP: Home or Professional
Microsoft Windows 7: Home Premium, Professional, Ultimate or Enterprise
Note:
Write privileges are required for the destination folder of the installation path of Oracle Beehive Conferencing.Microsoft Installer framework version 2.0 or above is required for Windows installations. This framework is included in Microsoft Windows XP and later versions of Microsoft Windows.
Apple Mac OS X 10.5 (Leopard), 10.6 (Snow Leopard), and 10.7 (Lion)
Note:
The Desktop Conferencing Client for the Macintosh is supported on machines with either Intel or PowerPC (minimum 1GHz G4) processors.100 MB minimum
Hard disk usage varies according to configuration. Custom installation options may require more or less hard disk space.
Oracle recommends that you install and deploy the Oracle Beehive Conferencing client using Oracle Beehive's Device Management Service (DMS). This installation method is recommended for all desktops with standard environments. It is designed for centralized installation and management of auto-updates.
This section covers the following topics:
Installing Oracle Beehive Conferencing Desktop Client Using Remote Downloader
Uninstalling and Downgrading Oracle Beehive Conferencing Client
The Java-based architecture JavaFX Conferencing Client can be used by users without requiring any Operating System specific desktop installation. The advantages of this new architecture is the ability to leverage Java to auto-detect, auto-install, and auto-update all the necessary components required by Beehive Conferencing to run. Therefore, for a user to join a conference, the Beehive Conferencing application needs to access:
JavaScript code (deployJava.js) for launching Java applications and detecting JRE versions
Beehive Conferencing uses the Java resources by accessing the files through java.com site over the Web. This may be a cause for concern if you do not have access to the internet, or cannot access the java.com site (because it is unavailable at that time), and/or do not have proxy settings configured correctly.
To avoid this issue, Oracle recommends that users distribute the resources through the Beehive Desktop Management Service as a DMS package.
Configure the Web Conferencing Center to use deployJava.js from DMS:
beectl modify_property--component _BeehiveConferencingService--name ConfJavaDeployJavaURL--value DMS://deployJava.js
Activate the changes:
beectl activate_configuration
You may install the Oracle Beehive Conferencing Desktop client by distributing a remote downloader to end users. The remote downloader enables end users to download and install the provisioned Oracle Beehive Conferencing client application from the Device Management Service (DMS) repository. By default, the DMS contains a pre-seeded Oracle Beehive Conferencing client application that is provisioned for all end users.
Obtain the Oracle Beehive Conferencing client remote downloader, BeehiveConferencingSetup.exe, from the directory <Oracle Beehivehome>/beehive/seed/dm/confclient_win_bootstrapper.zip.
You may also obtain the remote downloader from Oracle Beehive Central, a Web-based client that provides users a central location to download supported clients and set their preferences for Oracle Beehive functionality.
To download and install Oracle Beehive Conferencing:
Access Oracle Beehive Central and click Downloads.
On the Oracle Beehive Central Downloads page, click the button next to Oracle Beehive Conferencing. (Whether you use a Windows machine or a Mac, the button will read either "Windows" or "Mac").
Oracle Beehive Conferencing download page appears displaying product details and installation information.
Verify your system requirements, then click Download for [Windows or Mac].
You may specify the address and port of the DMS in the name of the downloader executable or through the command line.
The Oracle Beehive Conferencing client downloader requires only the address and port of the DMS to function correctly. The port is always the normal HTTP(s) port that the Oracle Beehive server is using.
To specify DMS settings in the file name of the downloader, rename it using the following form:
<downloader name>,<DMS address>,<DMS port>.exe
<downloader name>: This is the name given to the downloader. You may use any name.
<DMS address>: This is the address of the DMS.
<DMS port>: This is the port number of the DMS. It is always the normal HTTP(s) port that the Oracle Beehive server is using.
Note that you must use a comma (,) to separate DMS settings in the name of the downloader. The following is a valid example of a file name of the downloader:
BeehiveConferencingSetup,beehive.oracle.com,443.exe
You may specify DMS connection settings through the command line. The following table describes the command line options that the Oracle Beehive Conferencing client downloader currently supports:
Table 29-1 Oracle Beehive Conferencing Downloader Options
| Option | Description |
|---|---|
|
|
Oracle Beehive server address |
|
|
Specifies the port used by the DMS for communication. Note: Specify the normal HTTP(s) port that the Oracle Beehive server is using. |
The following is an example of specifying connection parameters through command line options:
BeehiveConferencingSetup.exe /server beehive.oracle.com /dm_port 443
The Oracle Beehive Conferencing client downloader version 1.5.1.2 and later supports the following additional command line options:
Table 29-2 Oracle Beehive Conferencing Downloader Options
| Option | Description |
|---|---|
|
|
Stops the downloader from launching Oracle Beehive Conferencing after installation. By default, the application is launched after installation. |
|
|
Specifies the Oracle Beehive user account that is seeded in the Oracle Beehive Conferencing configuration file. Note: User names that contain spaces must be enclosed within quotation marks ( |
The following are examples of specifying these downloader options:
BeehiveConferencingSetup.exe /server beehive.oracle.com /dm_port 443 /user John.Doe@oracle.com
BeehiveConferencingSetup.exe /server beehive.oracle.com /dm_port 443 /nolaunch
BeehiveConferencingSetup,beehive.oracle.com,443.exe /user John.Doe@oracle.com /nolaunch
Follow these steps to update the version of the Oracle Beehive Conferencing client in the DMS repository:
Ensure the application package for the updated version of the Oracle Beehive Conferencing client is accessible to the Oracle Beehive server.
Upload the updated version of the Oracle Beehive Conferencing client to the DMS repository by running the following command:
beectl upload_client_application --file <path to Oracle Beehive Conferencing zip file>
Note:
This command uploads the new version of the Oracle Beehive Conferencing client application to the DMS repository and makes it available for those who are already provisioned to it.If you have not provisioned the Oracle Beehive Conferencing client, run the provisioning commands (such as beectl add_client_application_provisioning). Refer to "Managing the Device Management Service" in Oracle Beehive Administrator's Guide for more information.
Note:
End users may also re-run the remote downloader to install any updated version uploaded to the DMS repository. If the version of the Oracle Beehive Conferencing client in the DMS repository is the same as the one installed in an end user's computer, re-running the remote downloader simply reinstalls the application.After you update the version of the Oracle Beehive Conferencing client in the DMS repository, when an end user starts the client, Oracle Beehive will automatically check, download, and install any updates from the DMS repository. Oracle Beehive always checks for a newer version when the Oracle Beehive Conferencing client is started.
Use the following methods to uninstall or downgrade the Oracle Beehive Conferencing client.
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|