| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
This module contains the following types of information related to Oracle Beehive installation and configuration:
This section contains general information related to Oracle Beehive installation and configuration, and includes the following topics:
Note:
As of Release 1 (1.3), it is no longer possible to enter trailing spaces in enterprise and organization names during the Oracle Beehive installation.During the Oracle Beehive installation, you will be asked to enter the name of your enterprise and the name of one organization within your enterprise. Although spaces are allowed in enterprise and organization names, do not enter any trailing spaces in either as this may cause configuration issues.
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
Oracle Enterprise Manager Grid Control Does Not Automatically Register Oracle Beehive
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
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 issue is resolved in Release 1 (1.3) and later.Bug 6962295. Oracle Enterprise Manager Grid Control does not automatically register Oracle Beehive as a target, even when it is used to install Oracle Beehive. To overcome this limitation, you must manually add Oracle Beehive as a target in Oracle Enterprise Manager Grid Control.
To add Oracle Beehive as a target in Oracle Enterprise Manager Grid Control:
In Oracle Enterprise Manager Grid Control, navigate to the Admin page.
Click All Targets.
From the drop-down list box, select Oracle Application Server and click Go.
Select the computer on which Oracle Beehive is installed, click Continue, and then click OK.
Bug 6981952. If your organization deploys one or more Oracle Beehive DMZ instances and Oracle Beehive Integration for Outlook, you must complete the following additional configuration steps (post-installation) on each Oracle Beehive DMZ instance to enable the HTTP-based client/server connections:
Open the oracle_apache.conf file, located in the following directory:
$ORACLE_HOME/Apache/Apache/conf/
Add the following line in the oracle_apache.conf file:
include "<Oracle Home>/beehive/conf/modbti.conf"
where <Oracle Home> is the Oracle home for your Oracle Beehive DMZ instance.
Save the oracle_apache.conf file.
Create a file called "modbti.conf" in the following directory:
$ORACLE_HOME/beehive/conf
In the modbti.conf file, enter the following:
LoadModule bti_module <Oracle Home>/beehive/lib/mod_bti.so<IfModule mod_bti.c> <Location /beehive/redirect> SetHandler bti-handler BtiEnableDebugging "no" BtiWorkingDirectory "<Oracle Home>/beehive/bin" #BtiEnableStatistics <Enable Option> </Location></IfModule>
where <Oracle Home> is the Oracle home for your Oracle Beehive DMZ instance and <Enable Option> determines whether or not BTI Statistics are enabled. Enter "yes" (with quotation marks) to enable; "no" to disable.
Save the modbti.conf file.
Restart the HTTP_Server by issuing the following command:
$ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server
If your shiphome image resides in a directory path containing spaces, you will not be able to launch the installer by double-clicking on 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) for 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) 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.
This section contains information about issues related to the installation and configuration of Oracle Beehive, and includes the following topic:
Bug 6154119. Workflows in Oracle Beehive may not function if the BPEL process deployment to either Oracle BPEL Process Manager for SerialWorkflow or ParallelVoteWorkflow failed during installation. You can confirm that the installation failed by looking for a file called bpel_Xxx.jar.failed in $ORACLE_HOME/bpel/domains/default/deploy.
If the installation failed, perform the following steps to correct the problem:
Delete the bpel_Xxx.jar.failed file.
Copy the workflow JAR file for the missing workflow from $ORACLE_HOME/beehive/seed/workflows and paste it in the deploy directory. For example, if the failed file was bpel_SerialWorkflow.jar, copy that file and paste it in the $ORACLE_HOME/bpel/domains/default/deploy directory.
Wait for a few minutes and the JAR file will disappear from the deploy directory. This happens because Oracle BPEL Process Manager is in auto-deploy mode and will immediately attempt to deploy this new JAR file.
Once the file disappears, restart Oracle Beehive using the beectl stop --all and beectl start --all commands.
