Skip Headers
Oracle® Beehive Installation Guide
Release 1 (1.5) for Linux x86

Part Number E14830-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

31 Installing Oracle Beehive Conferencing Client

This module describes how to install the Oracle Beehive Conferencing client.

Oracle recommends that you install the Oracle Beehive Conferencing client using Oracle Beehive's Device Management Service (DMS). This installation method is recommended for all desktops with standard environments. Currently a desktop based, non-DMS installation method is not available for custom installation.

The following topics are covered:

System Requirements

This section describes the software and hardware requirements for the Oracle Beehive Conferencing client.

Operating System

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. This framework is included in Microsoft Windows XP and later versions of Microsoft Windows.

Disk Space

Device Management Service (DMS) Based Installation

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 Client Using Remote Downloader

You may install the Oracle Beehive Conferencing 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.

Obtaining Remote Downloader

Obtain the Oracle Beehive Conferencing client remote downloader, BeehiveConferencingSetup.exe, from the directory <Oracle Beehive home>/beehive/bootstrap/confclient/downloader.

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.

DMS Connection Settings

You may specify the address and port of the DMS in the name of the downloader executable or through the command line.

Specifying Connection Parameters in Executable Name

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
Specifying Connection Parameters Through Command Line

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 31-1 Oracle Beehive Conferencing Downloader Options

Option Description

/server

Oracle Beehive server address

/dm_port

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

Additional Command Line Options

The Oracle Beehive Conferencing client downloader version 1.5.1.2 and later supports the following additional command line options:

Table 31-2 Oracle Beehive Conferencing Downloader Options

Option Description

/nolaunch

Stops the downloader from launching Oracle Beehive Conferencing after installation.

By default, the application is launched after installation.

/user

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

Remote Downloader Return Values

The Oracle Beehive Conferencing client downloader returns 0 for a successful installation and a non-zero value to indicate that an error occurred. If the error occurred during the installation phase, the msiexec.exe error code is returned.

Updating Oracle Beehive Conferencing in DMS Repository

Follow these steps to update the version of the Oracle Beehive Conferencing client in the DMS repository:

  1. Make sure the application package for the updated version of the Oracle Beehive Conferencing client is accessible to the Oracle Beehive server.

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

Updating Oracle Beehive Conferencing Through DMS

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.

Uninstalling and Downgrading Oracle Beehive Conferencing Client

Use the following methods to uninstall or downgrade the Oracle Beehive Conferencing client.

Uninstalling Oracle Beehive Conferencing Client

End users may uninstall the Oracle Beehive Conferencing client from their computers by selecting Add/Remove Programs from the Control Panel, selecting Oracle Beehive Conferencing from the list, and clicking Remove.

Downgrading Oracle Beehive Conferencing Client

End users are always forced to upgrade or downgrade the Oracle Beehive Conferencing client depending on the version in the DMS repository.