| Oracle® Beekeeper Online Help Release 1 (1.4) Part Number E13799-02 |
|
|
View PDF |
| Oracle® Beekeeper Online Help Release 1 (1.4) Part Number E13799-02 |
|
|
View PDF |
This module describes how to manage your Oracle Beehive system using Oracle Beekeeper, and includes the following sections:
The Topology module allows you to stop and start individual Oracle Beehive services, while providing you with a broad view of your deployment topology.
The Configuration module allows you to verify, activate, and clear changes made to system objects such as sites, servers, services, and Oracle Application Server Containers for J2EE (OC4J) instances.
The currently running Oracle Beehive configuration is known as the active configuration.
To view the active configuration version:
In the System panel, select Configuration. The Configuration pane appears in the right-side of the screen. The version number is displayed in the Active Configuration section.
A saved Oracle Beehive configuration that has not yet been activated is known as the proposed configuration. You can view the proposed configuration version number in the Proposed Configuration section of the Configuration pane.
Before activating a proposed configuration, you must validate it to ensure that there are no errors.
To validate a proposed configuration:
In the System panel, select Configuration.
In the Proposed Configuration section, click Validate.
If your proposed configuration is validated, click OK. If the proposed configuration is not successfully validated, any management or configuration errors are displayed in a message box. You cannot activate a proposed configuration until you correct your validation errors.
To activate a proposed configuration:
In the System panel, select Configuration.
In the Proposed Configuration section, click Activate. The system will confirm that the proposed configuration was successfully activated.
Click OK.
After you have deleted all proposed configurations, the proposed configuration becomes identical to the currently running configuration.
To delete a proposed configuration:
In the System panel, select Configuration.
In the Proposed Configuration section, click Clear. The system will confirm that all proposed configurations have been deleted.
Click OK.
Using the Metrics Dashboard module, you can monitor Oracle Beehive availability, performance, and usage, for one or more services.
To add metrics to your dashboard:
Click New.
From the Services pull-down menu, select an Oracle Beehive service to be monitored.
Select one or more metrics using the check boxes in the Metrics list. Alternatively, select the All check box to add every metric for the Oracle Beehive service you have chosen.
In the Scope section, select a scope for the metrics.
Click OK.
Using the options in the View menu, you can filter the main metrics view based on scope and metric type. You can also display metrics in a table view or box view.
The Log Viewer module allows you to search Oracle Beehive logs to monitor performance and gauge the overall stability of your Oracle Beehive installation.
To search for log entries:
Enter the search string in the Find field. You can perform a search using one or more of the following attributes:
Date Range
Severity
Message Text
Beehive Error Code
Message Group
Hostname
Component ID
Beehive Component ID
Beehive Component Name
Logon Record ID
Principal ID
Organization ID
Module ID
Instance ID
Thread ID
Process ID
User ID
Error Instance ID
Execution Context ID
For more information, see Performing Simple Searches.
Click the Search icon.
Click x to reset the Log Viewer pane and repeat the search with a new string.
Alternatively, perform an advanced search by following the steps described in Performing Advanced Searches.
Using the options in the View menu, you can control which attributes are displayed as columns for your search results.
Clicking a column header will sort your search results by that attribute.
You can export individual log entries in an XML format.
To export a log entry, select it in the Log Viewer window and click Export. Alternatively, select multiple log entries while holding down Ctrl and click Export.
You can also create a temporary snapshot of part of your search results by selecting multiple log entries and clicking New.
The Client Applications module allows you to manage applications in the application repository.
Clicking Client Applications in the System pane brings up the application tree view, which lists the following details for each application:
Name
Vendor
Application version
Supported device type
Supported operating system
Supported processor
Supported languages
Selecting an application brings up the detail area for the application.
Clicking + next to an application displays all versions for the selected application. Selecting an application version brings up a read-only detail area for the version.
Using the options in the View menu, you can filter items in the Client Applications window by type, device class, processor, or operating system. You can also choose to view all applications or only installable applications in the repository.
Clicking + next to an application version displays all installable applications for the version. By default, the base application is always listed as patch 0 and cannot be provisioned. Dynamic installable applications are shown under the base application, while static installable applications are nested in the patch set they represent.
A static installable application points to a specific patch set. A dynamic installable application points to the latest patch set for a given application version.
To delete an application, version, or patch set from the repository, select it in the Client Applications window, click Delete, and click OK to confirm the deletion. Deleting an item deletes all nested application versions and patch sets. If you want to delete an item that contains an installable application, you must manually delete the installable application before deleting the parent item.
To upload an application to the repository:
From the Actions menu, select Upload.
Click Browse.
Select an appropriate package in .zip format and click Open.
Click Upload.
Optionally, repeat steps 2 through 4 to upload additional applications.
Click Close to return to the Client Applications window.
You can create a static installable application from a selected patch-set, or from an existing static installable application. For more information, see Static and Dynamic Installable Applications.
To create a static installable application:
In the Client Applications window, select the patch-set for the desired application. Alternatively, select an existing installable application.
Click New.
Enter a name for the installable application in the Installable Name field.
Click Yes.
You can create a dynamic installable application when an application version is selected and no dynamic installable application exists for the selected version. For more information, see Static and Dynamic Installable Applications.
To create a dynamic installable application:
In the Client Applications window, select an application version for which no dynamic installable application currently exists.
Click New.
Enter a name for the installable application in the Installable Name field.
Click Yes.
You can provision installable applications for organizations within your enterprise or your entire enterprise.
To provision an installable application:
In the Client Applications window, select the installable application.
Click the Provisioning tab.
Click Add.
To provision the installable application for your entire enterprise, select your enterprise from the list and click >. Alternatively, select your enterprise, click the View Organizations icon, select an organization from the list, and click >.
Click Add.
Click Apply to save your changes.
To implement the Oracle Beehive coexistence solution, you must add and configure coexistence connectors based on the requirements of your deployment. Typically, there is one connector between each Oracle Beehive server and Microsoft Exchange Server routing group.
The Records module allows you to set or modify the settings for Oracle Universal Records Management (Oracle URM), to enable Records Managment in Oracle Beehive.
From the Records pane, you can view the URM Adaptor's status in the Adaptor Status box. Click Refresh to refresh the Adaptor Status.
From the URM Adaptor Settings box, you can view or modify the current connection settings for the URM Adaptor. Click the Create button to add additional URM Adaptors.
You can modify parameters for the URM Agent in the URM Agent Settings box. Enter new values, and then click Apply to apply your changes.
Note:
Oracle URM is a separate product not included with Oracle Beehive. For more information about using Records Management with Oracle Beehive, see "Managing Records Management" in Chapter 6, "Managing Oracle Beehive Workspaces" of the Oracle Beehive Administrator's Guide.You can configure the User Directory Service (UDS) for integration with supported external user directory servers. You can also configure the Authentication Service to leverage the same external user directories for authentication attributes such as user names and passwords.
Caution:
If you are using an external user directory, you cannot use Oracle Beehive to create users directly. When you set up an external user directory, any existing users you have created directly in Oracle Beehive will be deleted.For more information, consult the "Integrating and Synchronizing LDAP with Oracle Beehive" module of the Oracle Beehive Installation Guide.
|
 Copyright © 2008, Oracle. All rights reserved. Legal Notices |
|
