| Oracle® Beehive Release Notes Release 2 (2.0) for Linux, Windows, and Solaris Operating System (SPARC 64-Bit) Part Number E16640-11 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Release Notes Release 2 (2.0) for Linux, Windows, and Solaris Operating System (SPARC 64-Bit) Part Number E16640-11 |
|
|
PDF · Mobi · ePub |
This module contains the following types of information regarding Oracle Beehive administration:
This section contains general information that is useful to Oracle Beehive administrators, and includes the following topics:
Modifying the Disclaimer Text on the Java Single Sign-On Page
Using the beectl add_search_recovery_scope Command to Index Old Data
Oracle Beehive No Longer Supports Local Updates of JVM Start and Stop Parameters
Deprecation Planned for User Memberships Supported in Organizations
New and Updated beectl Commands for Managing Workspace Templates
New and Deleted beectl Commands in Oracle Beehive Release 2 (2.0.1.x)
Beginning with Oracle Beehive 2.0.1.4, you can modify the disclaimer text that is shown on the Java single-sign-on login page.
To modify this text, perform the following procedure:
In your Oracle Beehive Oracle_Home, create the following directory:
$ORACLE_HOME/langpack/xliff/custom/
In that directory, use a text editor to create a file named oracle.ocs.authentication.service.AuthServiceEndUserResourceBundle.xlf and copy and paste in the following content:
<?xml version="1.0" encoding="UTF-8"?>
<xliff version='1.1' xmlns='urn:oasis:names:tc:xliff:document:1.1'>
<file original='oracle.ocs.authentication.service.AuthServiceEndUserResourceBundle' source-language='en-us' datatype='beehive'>
<header>
<prop-group name="ora_reconstruction">
<prop prop-type="beehive-version">0.0.0.0</prop>
<prop prop-type="beehive-filetype">custom</prop>
<prop prop-type="beehive-scope">enduser-webui</prop>
</prop-group>
</header>
<body>
<trans-unit id='OCSSSO-00003'>
<source>Insert new disclaimer or privacy statement here</source>
</trans-unit>
</body>
</file>
</xliff>
Be sure to edit the content of the source element with the new text you want to display on the single sign-on page.
If you have created translations for additional languages you can also add them to the directory you created, and then use the following commands to create and upload your custom language pack:
Run the following command:
jar cvf javasso-disclaimer.jar langpack
Run the following commands to upload the laguage pack:
$ORACLE_HOME/beehive/bin/beectl upload_language_pack --source /var/tmp/javasso-disclaimer.jar $ORACLE_HOME/beehive/bin/beectl activate_configuration
On every Oracle Beehive server running javasso, run the following command:
$ORACLE_HOME/beehive/bin/beectl modify_local_configuration_files --restart_needed false
Restart the BEEMGMT component.
Beginning in Oracle Beehive 2.0.1.2.1, a new beectl command, add_search_recovery_scope, enables you to run a search index recovery crawler to process and index old (uncrawled) data.
Note:
While theadd_search_recover_scope command can take as input an enterprise or organization scope, Oracle recommends using Workspace-level scopes, and limiting the number of items that are queued to be indexed at a single time to a medium size (~50,000 items). While monitoring the load on the server, you can then gradually add to the queue as it is processed.
More information on how to monitor the load is detailed in the Search readme available at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info (Doc ID 1135054.1).
The beectl add_search_recovery_scope command adds a list of items to be indexed to the SS_FEEDS table, where it will then be queued to process just like any other new or updated indexable content in your Oracle Beehive deployment.
See Also:
The SS_FEEDS table is discussed in the Search Service Architecture section of the Search readme available athttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=info (Doc ID 1135054.1).You should monitor the accumulation of data in the SS_FEEDS table as you run add_search_recovery_scope to ensure the queue is not increasing beyond the capacity of the system to process it.
Caution:
On many deployments, theadd_search_recovery_scope command is capable of overwhelming the system's capacity to process the SS_FEEDS table in a timely manner, potentially degrading performance of the entire server. Oracle recommends using the following careful approach to adding to the queue to avoid a service outage.Oracle recommends that you create a batch file to run this command for a few workspaces (personal or team) at a time. For very large workspaces, you can also limit the number of items based on date (age of the item).
To create the batch file, run beectl list_workspaces --type p (or t) to get a list of all personal (or team) workspaces, and then create a file which runs add_search_recovery_scope with the --scope option for each workspace. Oracle recommends starting with five workspaces and monitoring the load of the SS_FEEDS table. If your system appears to be adequately handling the load (the number of items waiting to be indexed decreases), run a batch file with another five or ten workspaces.
When attempting to troubleshoot or diagnose issues related to Oracle Beehive, refer to the infrastructure (core) log file of the OC4J instance where Oracle Beehive is deployed. This log file provides the most useful information if issues occur, especially workspace-related issues. Also, Oracle recommends referring to this file whenever you communicate with Oracle Support Services to diagnose and resolve issues.
Typically, you can access this log file in the following location:
$ORACLE_HOME/beehive/logs/oc4j/BEECORE/log.txt
For connectivity issues, refer to the log files in the following location:
$ORACLE_HOME/beehive/logs/bti/
The main application log file is in the following location:
$ORACLE_HOME/beehive/logs/oc4j/BEEAPP/log.txt
Command-line events are captured in log files in the following location:
$ORACLE_HOME/beehive/logs/beectl/
Management events are captured in log files in the following location:
$ORACLE_HOME/beehive/logs/oc4j/BEEMGMT
For documentation on Enterprise Manager Grid Control, including release notes that are specific to that product, refer to the following link:
http://download.oracle.com/docs/cd/B16240_01/doc/nav/portal_booklist.htm
Oracle recommends that administrators use Oracle Beekeeper to configure E-mail Service rules. If you prefer to use beectl for this purpose, contact Oracle Support for assistance.
Each release of Oracle Beekeeper is only compatible with its associated release of Oracle Beehive. For example, Oracle Beekeeper 1.3.1.0.0 is only compatible with Oracle Beehive 1.3.1.0.0, and so on.
For the releases before Oracle Beehive 1 (1.4), Oracle Beehive required administrators to update JVM start and stop parameters for OC4Js and the Oracle Beehive BTI in local copies of the opmn.xml file. However, in Oracle Beehive Release 1 (1.4) and later this method is no longer supported.
To update JVM start and stop parameters, administrators must now enter changes in the Oracle Beehive Central Configuration Repository using the beectl command line tool. Also, after updating any parameters, administrators should execute the modify_local_configuration_files command and restart any OPMN or OC4J instances as necessary. The modify_local_configuration_files command culls updates from the Oracle Beehive Central Configuration Repository and pushes them to local copies of the opmn.xml file.
All Oracle Beehive property and preference set names are case sensitive. When using the beectl command-line tool to set the value for a property or preference set, ensure that you use the correct case for the property or preference set name.
Oracle recommends that you do not use this feature. The ability to scope (contain) users within organizations will not be affected by this change.
beectl Commands for Managing Workspace TemplatesThe follow commands for managing workspace templates have been added or modified as of the Oracle Beehive Release 2 (2.0.1.1.0):
| Command | Status | Description |
|---|---|---|
| list_applied_workspace_templates | New | Lists the workspace templates that have been applied to this workspace. For each applied template it indicates whether this workspace is a template evolution target. |
| list_template_evolution_target_workspaces | New | Lists the workspaces to which the latest version of the given workspace template must be applied to make the workspaces conform to the latest version of the template. |
| add_team_workspace_template_evolution | Modified | Added the --limit option. |
beectl Commands in Oracle Beehive Release 2 (2.0.1.x)The following tables list new and removed commands in the Oracle Beehive 2.0.1.x patch releases, compared to Oracle Beehive 2.0:
Table 6-1 New beectl Commands in Oracle Beehive 2.0.1.1
| Utility | Function |
|---|---|
|
list_template_evolution_target_workspaces |
Lists the workspaces to which the latest version of the given workspace template must be applied to make the workspaces conform to the latest version of the template. |
|
list_applied_workspace_templates |
Lists the workspace templates that have been applied to this workspace. For each applied template it indicates whether this workspace is a template evolution target. |
Table 6-2 New beectl Commands in Oracle Beehive 2.0.1.3
| Utility | Function |
|---|---|
|
validate_midtier |
It validates midtier for various conditions. For example, it reports the issues of database connectivity with each individual rac node. |
|
add_search_recovery_scope |
Recover the search index for entities of the specified types, in the specified Scope, and which were last modified between the specified dates. |
|
list_operation_statuses |
Lists the Operation Statuses. |
|
export_workspace |
Exports workspace contents into an external directory. |
|
import_workspace |
Imports contents of an external directory into a new team workspace. |
Table 6-3 Removed beectl Commands in Oracle Beehive 2.0.1.3
| Utility | Function |
|---|---|
|
modify_search |
Create system model objects for Search and configure them. |
|
modify_search_engine |
Starts or stops the search crawl process for a specific source type. |
|
list_search_recovery_status |
Lists the status and reports on how many containers need to be recovered. |
|
add_search_recovery_container |
Adds/updates the recovery_id for the specified container. |
If there is a problem with the e-mail delivery process (for example VMS configuration), the number of messages in the queue may increase into many when the server is stopped and these messages are then placed in a delivery queue. To delete such unwanted messages from the delivery queue, run the following commands:
SQL> INSERT INTO es_gc_queue (partition_id, message_eid) select ORA_HASH(message_eid, 15), message_eid from es_queue q where exists (select 1 from es_messages m where m.eid = q.message_eid and m.sender like 'XYZ' and m.subject like 'ABC' and m.received_on between 'XXX' and 'YYY');
SQL> delete from es_queue q where exists (select 1 from es_messages m where m.eid = q.message_eid and m.sender like 'XYZ' and m.subject like 'ABC' and m.received_on between 'XXX' and 'YYY');
SQL> INSERT INTO es_gc_queue (partition_id, message_eid) select ORA_HASH(message_eid, 15), message_eid from es_retry_queue q where exists (select 1 from es_messages m where m.eid = q.message_eid and m.sender like 'XYZ' and m.subject like 'ABC' and m.received_on between 'XXX' and 'YYY');
SQL> delete from es_retry_queue q where exists (select 1 from es_messages m where m.eid = q.message_eid and m.sender like 'XYZ' and m.subject like 'ABC' and m.received_on between 'XXX' and 'YYY');
SQL> INSERT INTO es_gc_queue (partition_id, message_eid) select ORA_HASH(message_eid, 15), message_eid from es_balk_queue q where exists (select 1 from es_messages m where m.eid = q.message_eid and m.sender like 'XYZ' and m.subject like 'ABC' and m.received_on between 'XXX' and 'YYY');
SQL> delete from es_balk_queue q where exists (select 1 from es_messages m where m.eid = q.message_eid and m.sender like 'XYZ' and m.subject like 'ABC' and m.received_on between 'XXX' and 'YYY');
where 'XYZ' is sender's name,
'ABC' is subject of the mail,
'XXX' and 'YYY' is date/time range between which the mail was received.
This section contains information on known limitations and workarounds related to Oracle Beehive administration, and includes the following topics:
Password Change May Result in LDAP Synchronization Account Getting Locked Out
Running beectl Commands in Oracle_Home as Root User Causes Issues
OPMN Required for Controlling Oracle Beekeeper's OC4J Instances
Oracle Beekeeper Does Not Return Users to Login Page After Session Timeouts
Oracle Beehive Does Not Provide Statistics for External Components
Sensitive Information Entered Through beectl May Be Visible to Others
Oracle Beekeeper Does Not Save Changes to LDAP Profile of External User Directories
Setting the Log Level for a Service Does Not Override the Log Level for a Site
Search Indexes Do Not Include Certain File Types Due to Oracle Text Filtering Issue
Note:
This known limitation only affects deployments that leverage an external user directory, such as Oracle Internet Directory, Microsoft Active Directory, and Sun Java Directory Server.In cases where an external user directory is used, changing the password of the LDAP account used for synchronization (not the password of a regular user account) may result in that account getting locked out. This will occur if Oracle Beehive attempts to authenticate multiple times using the stored (old) password.
To avoid this situation, complete the following steps whenever you change the password of the LDAP account used for synchronization:
Disable the synchronization directory profile by issuing the following command:
$ beectl modify_property --component <profile_name> --name ProfileState --value DISABLE
For example:
$ beectl modify_property --component oidldapdirectoryprofile --name ProfileState --value DISABLE
Activate the configuration by issuing the following command:
$ beectl activate_configuration
In the external user directory, change the password of the LDAP account used for synchronization.
Update the Oracle Beehive LDAP configuration file with the account's new password.
Enable the synchronization directory profile by issuing the following command:
$ beectl modify_property --component <profile_name> --name ProfileState --value ENABLE
For example:
$ beectl modify_property --component oidldapdirectoryprofile --name ProfileState --value ENABLE
Activate the configuration by issuing the following command:
$ beectl activate_configuration
Issue the modify_local_configuration_files command.
For more information on this and other commands issued in this procedure, refer to Oracle Beehive Administrator's Reference Guide.
beectl Commands in Oracle_Home as Root User Causes IssuesFor Oracle Beehive instances in the UNIX and LINUX operating systems, running any beectl commands in your Oracle_Home as the root user may cause issues. Oracle strongly recommends that you do not run any beectl commands in your Oracle_Home as the root user. Instead, you should always run commands as the user who installed your Oracle Beehive instance.
Bug 6751859. Shutting down an Oracle Database instance associated with your Oracle Beehive deployment may result in the following error:
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []
Ignore this error as it indicates that some items remain in the library cache when closing down the instance. The error itself occurs after the database close and dismount stages so it only affects the instance shutdown itself. All datafiles have been closed cleanly and no additional steps are required.
Bug 7316433. To control Oracle Beekeeper OC4J instances, administrators need to leverage OPMN. The method for controlling OC4J instances depends on your operating system, as follows:
Table 6-6 Supported Methods for Controlling Oracle Beehive OC4J Instances
| Release | Method |
|---|---|
|
Oracle Beehive Release 2 (2.0) for Linux |
Run |
|
Oracle Beehive Release 2 (2.0) for Microsoft Windows (32-bit) |
Use one of the following methods:
Note: Logging out of the Microsoft Windows computer where Oracle Beekeeper resides will terminate the administration tool. |
|
Oracle Beehive Release 2 (2.0) for Solaris Operating System (SPARC 64-bit) |
Run |
Bug 6835314 and 7023557. Oracle Beekeeper does not return users to the Login page after session timeouts. To minimize the risk of experiencing this issue, Oracle recommends that you set the session timeout value for your Oracle Beekeeper instance to 3600 seconds or higher.
Bug 7519613. Through supported administration clients, Oracle Beehive provides administrators with data for a variety of statistical measures, such as counts for login successes and failures. However, Oracle Beehive does not provide statistical data for external components that might be deployed with the system. For example, counts for login successes and failures are not provided for Oracle Enterprise Single Sign-On.
Bug 9206658. All information entered in the beectl command-line utility may be visible to other users while the associated commands execute. Therefore, if you need to run a command that contains sensitive information, such as setting VM GUI command push user names and passwords, Oracle strongly recommends that you do so in shell mode only. This will prevent the information from being visible to others while the associated commands execute.
Specifically, Oracle recommends you use shell mode to run any commands that contain the following properties and associated information:
AxlConfigA
AxlConfigB
FaxReceiverPassword
IpPhonePassword
IpPhonePasswordSeed
RTPServerPassword
Bug 8980619. If you use Oracle Beekeeper to modify certain attributes in the LDAP synchronization profile, such as the LDAP server hostname, the changes will not be saved.
To avoid this issue, use beectl to modify attributes in your LDAP synchronization profile.
Bug 9080336. Setting the log level for a Service does not override the log level for a Site. To avoid this issue, set the log level for the Service's module to the desired level.
For example, if the Base Log Level for a Site is “WARNING”, and you want to set the log level for the Beehive Central Service to “TRACE”, set the log level for the Beehive Central Service's module to “TRACE”, as follows:
beectl modify_property --component _current_site:LoggingProperties –name ModuleLogLevel --value oracle.ocs.web.bcentral:TRACE --activate_configuration
Note:
This issue applies to Oracle Beehive Release 2 (2.0) and later for Solaris Operating System (SPARC 64-Bit) only.Bug 9237090. Due to an issue with Oracle Text filtering on Sun Solaris, Oracle Beehive search indexes do not include the following file types:
Adobe PDF (.pdf)
Microsoft Word (.doc)
XLS (.xls)
As a result of this issue, Oracle Beehive will not return documents of these file types in search results.
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|