Oracle® Beehive Installation Guide Release 2 (2.0.1.8) for Oracle Solaris on SPARC (64-Bit) Part Number E16643-07 |
|
|
PDF · Mobi · ePub |
This chapter describes how to install Oracle Beehive Extensions for Explorer.
Oracle recommends that you install Oracle Beehive Extensions for Explorer using Oracle Beehive's Device Management Service (DMS). This installation method is recommended for almost all desktops with standard environments and administrative privileges. A desktop based, non-DMS installation method is available for custom environments with limited administrative privileges.
It covers the following topics:
This section describes the software and hardware requirements for Oracle Beehive Extensions for Explorer. 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:
Microsoft Windows XP: Home or Professional
Microsoft Windows 7 (32-bit and 64-bit edition) - Home Premium, Professional, Ultimate or Enterprise
Microsoft Windows Server 2003
Microsoft Windows Server 2008
Microsoft Windows Server 2008 R2
Note:
You need administrative privileges to install Oracle Beehive Extensions for Explorer on Windows XP, Windows Server 2003, and Windows Server 2008.You must install Windows XP Service Pack 2 on Windows XP computers if you intend to use non-English locales with Oracle Beehive Extensions for Explorer. Attempting to run Oracle Beehive Extensions for Explorer with a non-English locale on a computer with Windows XP Service Pack 1 (or earlier) may result in the computer failing to operate normally.
100 MB minimum
Hard disk usage varies according to configuration. Custom installation options may require more or less hard disk space. The amount of online data the user accesses may also affect the disk space requirement.
Oracle recommends that you install and deploy Oracle Beehive Extensions for Explorer using Oracle Beehive's Device Management Service (DMS). This installation method is recommended for almost all desktops with standard environments and administrative privileges. It is designed for centralized installation and management of auto-updates.
This section covers the following topics:
Installing Oracle Beehive Extensions for Explorer Using Remote Downloader
Uninstalling and Downgrading Oracle Beehive Extensions for Explorer (DMS Process)
You may install Oracle Beehive Extensions for Explorer by distributing a remote downloader to end users. The remote downloader enables end users to download and install the provisioned Oracle Beehive Extensions for Explorer application from the Device Management Service (DMS) repository. By default, the DMS contains a pre-seeded Oracle Beehive Extensions for Explorer application that is provisioned for all end users.
For more information on how to provision applications for specific users or groups of users, refer to "Managing the Device Management Service" in Oracle Beehive Administrator's Guide.
Obtain the Oracle Beehive Extensions for Explorer remote downloader, explorer_extensions_downloader.exe
in the directory <Oracle Beehive home>
/beehive/bootstrap/obee/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.
Pre-Seeding Server Name in Remote Downloader
The remote downloader prompts the end user to provide a server name, account name, and password to initiate download and installation. If you want to pre-seed a server name to prevent end users from having to specify a server name on their own, rename the remote downloader to <fully qualified server name>
.exe
. For example, if your server name is faulkner.oracle.com
, your remote downloader name would be faulkner.oracle.com.exe
.
You may pre-seed the port number that Oracle Beehive Extensions for Outlook uses to connect to the server.
For example, if your remote downloader name is faulkner.oracle.com.exe
and you want to pre-seed the port number in the downloader, rename the file to faulkner.oracle.com,443.exe
, where 443
is your port number.
Note:
The pre-seeded port number is the port number of the DMS on the server that is used to obtain the settings for direct and HTTPS connections.This option is available for Oracle Beehive Release 1 (1.5.1.2) and later.
You may also use the Oracle Beehive Extensions for Explorer downloader to provide a full, non-interactive deployment option. To do so, use the silent switch, /s
.
Specify the required connection parameters through the command line or in an initialization file.
The following is an example of specifying connection parameters through the command line (line breaks have been added for clarity):
explorer_extensions_downloader.exe /server example.com /user OracleBeehiveUserName /direct port=5224 secure=true /https port=443 secure=true /s UI=1
The following table describes the Oracle Beehive Extensions for Explorer downloader's command line options:
Table 26-1 Oracle Beehive Extensions for Explorer Downloader Options
Option | Description |
---|---|
|
Oracle Beehive server address |
|
Oracle Beehive user account |
|
User's password Note: It is recommended that you use the option |
|
Specifies the following for direct connection:
|
|
Specifies the following for HTTPS connection:
|
|
Determines if an Oracle Beehive Extensions for Explorer profile should be created on the user's computer during installation. This parameter may be assigned one of the following values:
|
|
Specifies the port number of the DMS on the server to obtain the settings for direct and HTTPS connections.By using this option, you do not need to specify either the |
|
Changes the name of the profile created during installation of Oracle Beehive Extensions for Outlook. The default profile name is |
|
Downloads and reinstalls the MSI package from the DMS if the installed version on the user's computer is the same version as the MSI package. If |
|
Determines if Windows Explorer is launched after Oracle Beehive Extensions for Explorer is installed. This parameter may be assigned one of the following values:
|
|
Use silent mode |
Specify the full path of the initialization file you want to use as follows. In this example, C:\testSilentDownloader.ini
is the full path of the initialization file:
explorer_extensions_downloader.exe /s C:\testSilentDownloader.ini
If you use the silent switch with a UI=1
parameter, the connection dialog will be presented in which all the controls are disabled and only the password field is enabled:
explorer_extensions_downloader.exe /s UI=1 C:\testSilentDownloader.ini
The downloader will return a value of 1
or 0
, which indicates whether the operations performed by it failed (1
) or were successful (0
). You may use this returned value in a script to determine whether or not the remote downloader was successful.
Use the following template to create a silent initialization file:
Example 26-1 Template for Silent Initialization File
[General] Account_Name= Server= User= Password= Direct_Port= Direct_Secure= Direct_Enable= Discovert_Port= HTTPS_PORT= HTTPS_Secure= HTTPS_Enable=TRUE Proxy= Proxy_Type=0 Proxy_URL= Use_Existing= Default= Remember_Pwd= Timeout=120000
The following table describes the silent initialization file's parameters:
Table 26-2 Initialization File Parameters
Initialization File Parameter | Description |
---|---|
|
Changes the name of the profile created during installation of Oracle Beehive Extensions for Outlook. The default profile name is |
|
Oracle Beehive server address |
|
Oracle Beehive user account |
|
User's password Note: It is recommended that you use the option |
|
Valid port number to be used to establish a direct connection |
|
Boolean value; specifies whether to use a direct connection ( |
|
Boolean value; specifies whether to enable the direct connection ( |
|
Valid port number used to connect to the DMS on the server to obtain the settings for direct and HTTPS connections By using this parameter, you do not need to specify any of the following parameters: |
|
Valid port number to be used to establish an HTTPS connection |
|
Boolean value; specifies whether to use an HTTPS connection ( |
|
Manual proxy configuration (for example, |
|
Specifies the proxy type. It may have a value of
|
|
Manual proxy configuration (for example, |
|
Boolean value:
|
|
Boolean value: Specifies whether the created profile should be the default profile ( |
|
Timeout duration, in milliseconds, before reporting failure to connect |
You may update the version of Oracle Beehive Extensions for Explorer in the DMS repository. Afterwards, if Oracle Beehive Extensions for Explorer is running on an end user's computer, it will automatically prompt the end user to download and install updates from the DMS repository.
In addition, end users may also manually search for updates by selecting About Oracle Beehive Extensions for Explorer from the Beehive menu and clicking Check for Updates.
The following topics are covered in this section:
Updating Oracle Beehive Extensions for Explorer in DMS Repository
Updating Language Pack for Oracle Beehive Extensions for Explorer
Follow these steps to update the version of Oracle Beehive Extensions for Explorer in the DMS repository:
Ensure the application package for the updated version of Oracle Beehive Extensions for Explorer is accessible to the Oracle Beehive server.
Upload the updated version of Oracle Beehive Extensions for Explorer to the DMS repository by running the following command:
beectl upload_client_application
--file <Path to Oracle Beehive Extensions for Explorer zip file>
Note:
This command will upload the new version of the Oracle Beehive Extensions for Explorer application to the DMS repository and will make it available for those who are already provisioned to it.If you have not provisioned Oracle Beehive Extensions for Explorer, 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.
If Oracle Beehive Extensions for Explorer is running on an end user's computer, it will automatically prompt the end user to download and install updates from the DMS repository. End users may also manually search for updates by selecting About Oracle Beehive Extensions for Explorer from the Beehive menu and clicking Check for Updates.
You may localize the user interface of Oracle Beehive Extensions for Explorer to match Windows Explorer languages by updating the language pack with the one found at <Oracle Beehive home>
/beehive/bootstrap/obee/languagepack
. The following languages are currently supported in the language pack:
French
German
Italian
Spanish
Brazilian Portuguese
Japanese
Korean
Simplified Chinese
Traditional Chinese
To update the language pack for Oracle Beehive Extensions for Explorer, upload it to the DMS repository using the beectl upload_client_application
command. By default, the language pack is uploaded and provisioned to all users. Follow these steps to update the language pack:
Ensure the language pack for Oracle Beehive Extensions for Explorer is accessible to the Oracle Beehive server.
Upload the language pack for Oracle Beehive Extensions for Explorer to the DMS repository by running the following command:
beectl upload_client_application
--file <Path to Oracle Beehive Extensions for Explorer language pack>
If Oracle Beehive Extensions for Explorer is running on an end user's computer, it will automatically prompt the end user to download and install updates (including language packs) from the DMS repository. End users also may manually search for updates by selecting About Oracle Beehive Extensions for Explorer from the Beehive menu and clicking Check for Updates.
Note:
The language installed by the Oracle Beehive Extensions for Explorer language pack will automatically match Windows Explorer, provided that Oracle Beehive Extensions for Explorer supports the language. If the end user has Windows Explorer in an unsupported language, Oracle Beehive Extensions for Explorer will default to English.Use the following methods to uninstall or downgrade Oracle Beehive Extensions for Explorer.
End users may remove Oracle Beehive Extensions for Explorer from their computers by selecting Add/Remove Programs from the Control Panel, selecting Oracle Beehive Extensions for Explorer from the list, and clicking Remove.
By default, Oracle Beehive Extensions for Explorer will only detect updates if the server version is newer than the currently installed version. If you want to allow end users to install downgraded versions of Oracle Beehive Extensions for Explorer as updates, set the value of the INSTALL:AllowDowngrade
Property node to TRUE
in your provisioning file.
This option is available for Oracle Beehive Release 1 (1.5.1.2) and later.
The following table describes the public properties you may specify:
Table 26-3 MSI Package Public Properties
Property | Description |
---|---|
|
Determines if an Oracle Beehive Extensions for Explorer profile should be created on the user's computer during installation. This parameter may be assigned one of the following values:
|
|
Boolean value:
If |
|
Changes the name of the profile created during installation of Oracle Beehive Extensions for Outlook. The default profile name is |
|
Determines if Windows Explorer is launched after Oracle Beehive Extensions for Explorer is installed. This parameter may be assigned one of the following values:
|
It is recommended to install Oracle Beehive Extensions for Explorer using Oracle's Device Management Service (DMS). However, custom environments with limited administrative privileges may require a desktop based method of installation that is non-DMS based.
This section covers the following topics:
Installing Oracle Beehive Extensions for Explorer Using Executable File
Configuring Oracle Beehive Extensions for Explorer Using MSI Package
Upgrading Oracle Beehive Extensions for Explorer Installation
Updating Language Pack for Oracle Beehive Extensions for Explorer (Non-DMS)
Uninstalling and Downgrading Oracle Beehive Extensions for Explorer (Non-DMS Process)
You may give end users direct access to the Oracle Beehive Extensions for Explorer installer. End users install the product by double-clicking the installer and following the on-screen instructions.
Retrieve the installer explorer_extensions_setup.exe
from <Oracle Beehive home>
/beehive/bootstrap/obee/setup
.
This option is available for Oracle Beehive Release 1 (1.5.1.2) and later.
The following table describes the public properties you may specify:
Table 26-4 MSI Package Public Properties
Property | Description |
---|---|
|
Determines if an Oracle Beehive Extensions for Explorer profile should be created on the user's computer during installation. This parameter may be assigned one of the following values:
|
|
Boolean value:
If |
|
Changes the name of the profile created during installation of Oracle Beehive Extensions for Outlook. The default profile name is |
|
Determines if Windows Explorer is launched after Oracle Beehive Extensions for Explorer is installed. This parameter may be assigned one of the following values:
|
This section describes how to deploy custom OBEE MSI package.Create a silent obeeconfig.ini
file and specify the required connection parameters in the initialization file.
Use the following template to create a silent initialization file:
Example 26-2 Template for Silent Initialization File
[General]Account_Name=BeehiveServer=yourservername.comUser=username@yourcompany.comPassword=Direct_Port=5224Direct_Secure=TRUEDirect_Enable=TRUEHTTPS_PORT=443HTTPS_Secure=TRUEHTTPS_Enable=TRUEProxy=Proxy_Type=0Proxy_URL=Use_Existing=TRUEDiscover_Port=443Discover_Enable=TRUEDefault=Remember_Pwd=Timeout=60000
For information on the description of initialization file's parameters, refer Table 26-2, "Initialization File Parameters".
To configure OBEE, after installing as an admin user, follow the below mentioned steps:
Install Oracle Beehive Extensions for Explorer by running the following command. This requires admin privilege.
msiexec.exe -i "C:\testObeeMsi\explorer_extensions_application.msi"
Place the obeeconfig.ini
file in the installation directory, or in a network location where users have access. You do not need to make the ini
file read-only.
Configure the OBEE profile according to the settings in the ini
file. This step does not require admin privilege and will repeat for each user.
Copy the obeeconfig.ini
file to a temp location of the logged in user (You do not need to make the ini
file read-only).
Add a new String value called ConfigPath
and populate it with the full path to the obeeconfig.ini
file under the following registry path:
HKEY_CURRENT_USER\Software\Oracle\Explorer Extensions
For example:
ConfigPath C:\testObeeMsi\obeeconfig.ini
Insert the username in the ini
file from the temp location.
Note:
As part of the post installation/setup cleanup process, the deployedini
file will be consumed and removed when OBEE is first launched on your machines. As the process works with a copy from the temp location, the ini
file does not have to be read-only and can be invoked for the user name insertion process and configuration.When you provision a new version of Oracle Beehive Extensions for Explorer in the DMS repository, end users will be notified about the new update and will be able to download and install it.
If administrators prefer to upgrade to a newer version of Oracle Beehive Extensions for Explorer on end users' systems without relying on the DMS upgrade process, then they need to deploy the new version of Oracle Beehive Extensions for Explorer before performing any server updates.
Alternatively, you may remove any Oracle Beehive Extensions for Explorer packages from the DMS repository so that end users are never prompted to upgrade to newer versions. Perform the following steps to remove Oracle Beehive Extensions for Explorer packages:
Run the following command:
beectl list_client_applications
The previous command will return a list of the applications installed in the DMS repository and their identifiers. Find the listings pertaining to OBEE, you may see any of the following Oracle Beehive Extensions for Explorer application packages and their identifiers:
Oracle Beehive Extensions for Explorer
Oracle Beehive Extensions for Explorer Downloader
Oracle Beehive Extensions for Explorer Language Pack
Remove any of these client applications found by running the following command (for each application):
beectl delete_client_application
--application <identifier of client application>
The default localization of the user interface of OBEE can be changed according to the user preference. This can be done by supplying newer xliff files for the preferred languages that would contain the required changes. If the default language pack is satisfactory, however, then no change will be required and hence no updating of the language pack will be necessary.
Follow the steps below to update the modified language packs:
Obtain the default language pack from the following location:
<Oracle Beehivehome>/beehive/bootstrap/obee/languagepack
Unzip the package.
Find the corresponding xliff file of the language that needs to be modified and make the changes.
Place the changed file in a folder.
For example: c:\lab\Updates (This would be the path to xliff chm files)
These modified files can be deployed on the users' machines using one of the following commands:
explorer_extension_setup.exe /package_langpack {path_to_a_folder_of_xliff_chm_files}
This command generates a newer installation package with the updated xliff files packaged inside it. This full installation package is generated in the same folder of the original installation package. It can then be executed normally by the users to install and update their deployed language pack in the deployed location (usually C:\Program Files\Oracle\Explorer Extensions\languages\Updates).
explorer_extension_setup.exe /install_langpack {path_to_a_folder_of_xliff_chm_files}
This command does not generate a new installation package. Instead, it copies the modified files directly to its deployed location. It can be used by the user to update the deployed language pack, provided that the user running the installation has access to the folder where the updated files are located (this can be a network location) during the installation time.
Use the following methods to uninstall or downgrade Oracle Beehive Extensions for Explorer.