| Oracle® Beehive Release Notes Release 1 (1.4) Part Number E13790-07 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.4) Part Number E13790-07 |
|
|
View PDF |
This module contains the following types of information related to Oracle Beehive installation and configuration:
This section contains general information about the installation and configuration of Oracle Beehive. It contains the following topic:
Patch 7459672 Required for Deployments Upgrading to Oracle Beehive Release 1 (1.4.1.0.0) for Linux
Configuring Oracle Beehive Integration for Zimbra in Same Oracle Home as Oracle Beehive
Verifying Maximum Number of Open File Descriptors Recommended
If you plan to upgrade your deployment to Oracle Beehive Release 1 (1.4.1.0.0) for Linux, you must download and install Patch 7459672 immediately after the upgrade process. Patch 7459672 resolves an issue (Bug 7454534) that prevents Oracle Beehive Integration for Outlook users from loading server-side rules.
You can access and download Patch 7459672 at Oracle MetaLink:
If your installation of Oracle Beehive Release 1 (1.4.1.0.0) for Linux is not an upgrade from a previous version, you do not need to apply this patch. Also, using Oracle Enterprise Manager Grid Control to apply Patch 7459672 is not supported.
If you install Oracle Beehive on a computer with at least 3 gigabytes (GBs) of memory, Oracle Beehive Integration for Zimbra will be automatically configured in the same Oracle home.
To install Oracle Beehive, the maximum number of open file descriptors must be no less than 4096. Oracle recommends verifying that your system meets this requirement prior to installing Oracle Beehive and, if it does not, increasing the maximum number of open file descriptors to at least this amount, if not higher.
If you plan to deploy Oracle Beehive for Linux on a 64-bit system, you must use 32-bit shell emulation. To do this, use the following command before running the Oracle Beehive Install Wizard or any other Oracle Beehive commands:
$ linux32 bash
This section contains information about known limitations and workarounds related to the installation and configuration of Oracle Beehive. It contains the following topics:
Multiple Cloned Instances From Same Clone Tree Not Recommended
Spaces in Shiphome Image Directory Path Prevent Installer from Launching
Oracle Beehive Prerequisite Checks Will Fail for Third-Party Sun Solaris Patches
Installing Oracle Beehive on Sun Solaris May Fail During Core Configuration
Conflicts with Oracle Beekeeper and Oracle Database ONS Ports Result in Large OPMN Log Files
A clone tree consists of an Oracle Beehive instance (the source instance), instances cloned from the source instance, and instances cloned from clones of the source instance. Oracle does not recommend deploying more than one Oracle Beehive instance from the same clone tree. However, if you think this might be the best option for you, contact your Oracle Support representative.
Note:
This know limitation affects Oracle Beehive Release 1 (1.3.2.0.0) and later for the Microsoft Windows (32-bit) only.If your shiphome image resides in a directory path containing spaces, you will not be able to launch the installer by double-clicking the setup.exe icon within the Disk1 directory. Please either run setup.exe from a command shell or move your shiphome image to a path that does not contain spaces.
Bug 7326046. Attempts to install Oracle Beehive Integration for Zimbra on an Application Tier computer configured for TLS with test certificates may fail. Administrators can avoid this issue by ensuring that the specified Oracle Wallet contains real certificates. For more information, please contact Oracle Support.
Note:
This known limitation affects Oracle Beehive Release 1 (1.3.2.0.0) and later for the Solaris Operating System (SPARC 64-bit) only.Bug 6628667. The automatic prerequisite checks provided by the Oracle Beehive installation program will fail if you install Oracle Beehive on a Solaris operating system that contains third-party patches with non-numerical patch numbers. If you intend to deploy Oracle Beehive in such an environment, Oracle strongly recommends that you manually verify that your deployment environment meets the system's prerequisites prior to installation. In addition to the risk of an installation failure, failing to verify the prerequisites may result in an unsupported deployment. For the prerequisites for the Solaris operating system, please refer to the Oracle Beehive Installation Guide for Solaris Operating System (SPARC 64-Bit).
Note:
This known limitation affects Oracle Beehive Release 1 (1.3.2.0.0) and later for Solaris Operating System (SPARC 64-bit) only.Bug 7332530. Installing Oracle Beehive on the Sun Solaris operating system may fail during the Core Configuration CA step. To avoid this issue, Oracle recommends installing Sun Solaris patch 127127-11.
Note:
This issue only affects deployments that use Oracle Enterprise Manager Grid Control 10.2.0.4 to install and configure Oracle Beehive.Bug 7362094. Attempts to install Oracle Beehive with Oracle Enterprise Manager Grid Control 10.2.0.4 using non-ASCII characters in either the enterprise or organization name field will fail. To avoid this issue, do not use non-ASCII characters in either of these fields.
Bug 7365175. Conflicts with Oracle Beekeeper and Oracle Database ONS ports will result in large OPMN log files. These files, in turn, may consume a significant amount of available memory. To avoid this situation, Oracle recommends that you change the ONS localport setting for Oracle Database to a value that doesn't conflict with OPMN port value for Oracle Beekeeper.
To change the local port setting for Oracle Database, complete the following steps:
Stop the Oracle Database listener.
Open the Oracle Database ONS configuration file at the following location:
$OH/opmn/conf/ons.config
Change the localport setting to a value that doesn't conflict with the OPMN port value for Oracle Beekeeper. For example, set the localport value to 6150.
Save the Oracle Database ONS configuration file.
Restart the Oracle Database listener.
Bug 7489313. If you use Oracle Enterprise Manager Grid Control to install Oracle Beehive, the automatic memory prerequisite check may return an incorrect value for available physical memory. This is due to an issue with Oracle Universal Installer that rounds down the actual value.
In some cases, the incorrect value may appear to be too low to successfully install certain components, such as Oracle Beehive Integration for Zimbra. Oracle Enterprise Manager Grid Control may even reflect this incorrect assessment in its log files. However, if there is enough actual physical memory available, you will receive a message that states the memory check passed (despite the log file entry to the contrary) and all components will install correctly.
Note:
This issue and the related workaround only affect deployments that are upgrading from Oracle Beehive Release 1 (1.4.1) to Release 1 (1.4.3).Bug 7582794. The file secure-web-site.xml contains, among other settings, the root URL for Oracle Beekeeper. During the upgrade to Oracle Beehive Release 1 (1.4.3), the installation program does not update the root URL setting to the latest value. Therefore, you must do so manually.
To update the root URL value in secure-web-site.xml:
Open secure-web-site.xml, which is located in the following directory:
<BKPR_OH>/j2ee/home/config/
Where <BKPR_OH> is the Oracle home for your Oracle Beekeeper instance.
In the web-app application element, change the value of root from "/beehivecontrol" to "/bkpr", as follows:
Old setting:
<web-app application="beehivecontrol" name="bkpr-web" load-on-startup="true" root="/beehivecontrol" />
New setting:
<web-app application="beehivecontrol" name="bkpr-web" load-on-startup="true" root="/bkpr" />
Save secure-web-site.xml.
Restart the Oracle Beekeeper OC4J instance.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
