| Oracle® Beehive Beekeeper Online Help Release 2 (2.0.1.8) Part Number E16651-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Beekeeper Online Help Release 2 (2.0.1.8) Part Number E16651-04 |
|
|
PDF · Mobi · ePub |
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 components, while providing you with a broad view of your deployment topology. You can review your deployment By Topology (with each set of component instances separated by Application tier, or By Service (with all instances of a given service listed together).
From the Topology module, you can also do the following:
View the Virtual Server for a site
Create and modify the Virus Scan Engine Cluster configuration for a site
Manage the Database settings for your Oracle Beehive Database
Compare topology configuration versions
To access these options, from the Topology pane, select the site you want to manage, and from the View menu, click View Configuration. Or, in the By Service tab, select the site you want to manage, and from the View menu, click View Configuration.
To access virus scan engine configuration options, from the Topology pane, select the the site you want to manage, and from the View menu, click View Configuration. Or, in the By Service tab, select the site you want to manage, and from the View menu, click View Configuration.
Then, click the Virus Scan Engine Cluster tab.
Notes:
In this section, you create a configuration in Oracle Beehive that points to a virus scan engine cluster. The actual virus scan engine cluster is a system external to Oracle Beehive.
Virus scanning of e-mail is only enabled after you also configure virus scanning rules for the Email Service.
From the Topology pane, select the site you want to manage, and from the View menu, click View Configuration. Or, in the By Service tab, select the site you want to manage, and from the View menu, click View Configuration.
Then, click the Virus Scan Engine Cluster tab.
Click Edit. From the Proposed Configuration Version window, select the Virus Scan Engine Cluster tab, and click the Create Virus Scan Engine Cluster button.
Optionally, enter an Alias for your cluster. Select a Virus Scan Policy from the drop down list.
To access additional advanced parameters, click the Advanced link.
in the ScanEngines section, click the plus icon to add one or more scan engines. For each scan engine, enter the Scan Engine Host Name and Scan Engine Client Comm Port, and optionally, enter an Alias.
Click Apply to apply your configuration changes without closing the window, or click Save & Close to apply your changes and close the window.
The settings used by Oracle Beehive to access the Oracle Database are first set during installation of Oracle Beehive.
To access Oracle Database configuration options, from the Topology pane, select the the site you want to manage, and from the View menu, click View Configuration. Or, in the By Service tab, select the site you want to manage, and from the View menu, click View Configuration.
Then, click the Database tab.
Expand the subsections of database configuration settings, and then click Advanced to see advanced settings.
To edit database connection settings, click the Edit button. In the Proposed Configuration window, click the Database tab.
Caution:
Most database configuration parameters are Advanced. If you incorrectly configure database attributes, you could cause Oracle Beehive to lose connectivity to the database, or otherwise impact the performance of Oracle Beehive.When you have finished making configuration changes, click Apply to apply your changes to the proposed configuration, or click Save & Close to apply your changes and close the window.
To validate and apply your configuration changes, use the Configuration Control module.
From the Virtual Server, Virus Scan Engine Cluster, or Database tabs, or from any component in the Topology viewer, you can compare current and prior configurations and proposed configurations, to see which properties may have been changed. To compare configurations:
Click on any component in the Topology viewer. Or, select the site you want to manage and from the View menu, click View Configuration. Or, in the By Service tab, select the site you want to manage, and from the View menu, click View Configuration.
On the Configuration tab, click Compare. The Compare Configuration Versions window opens.
Using the drop down boxes, select a Baseline Version and an Other Version to compare to it. Click Compare. In the lower pane, any differences between the two configuration versions are shown.
When you are done reviewing the changes, close the Compare Configuration Versions window.
The Configuration Control module allows you to verify, activate, and clear changes made to components 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. Metrics shown on the dashboard are static; to update the values shown, click Refresh.
To add metrics from the Metrics Dashboard:
From the Metrics Dashboard pane, click New.
From the Service pull-down menu, select an Oracle Beehive service to be monitored.
Select one or more metrics using the check boxes in the Metric 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. Alternatively, select the All check box to add every scope for the metrics you have chosen.
Click OK.
To add metrics from any Service panel:
From any Service or Service Instance view, click the Metrics tab.
Select one or more metrics, and click Add. The metrics are added to the Metrics Dashboard.
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.
Once you have added a metrics group to the dashboard, from the Table view, you can remove the whole group. From the Action pull-down menu, select Remove All Metrics to clear the metrics dashboard, or, select Remove Group and select a metrics group to remove that group.
You can also remove individual metrics. Select one or more metrics, and from the Action pull-down menu, select Remove Selected.
The Log Viewer module allows you to search Oracle Beehive logs to monitor performance and gauge the overall stability of your Oracle Beehive installation.
From the Search drop down list, pick Repository to search the log repository, or pick FileSystem to search log files stored in the Oracle Beehive Application tier log folder
If you are searching the FileSystem, pick values from the Hostname and Beehive Home drop down lists to determine which Oracle Beehive homes will be included in the search.
Pick one or more components from the Component drop down list to include logs from those components in the search.
Enter the search string in the Search field. You can perform a search using one or more of the following attributes (with the format attribute:value). Click the Advanced icon to create a complex query:
Date Range
Severity
Message Text
Message Details
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.
With the cursor in the search box, use the Enter key to run the search. Or, from the Advanced Search menu, click Search.
Click the Clear icon 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.
To view the details for a given log entry, select the entry in the Log Viewer window and click Action, and then Open, or double-click the log entry.
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.
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.
See Also:
For more information about uploading applications, see "Uploading and Provisioning a New Application" in Chapter 7, "Managing Oracle Beehive Mobility Services" of the Oracle Beehive Administrator's Guide.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 Management in Oracle Beehive.
From the Records pane, you can view the URM Adapter's status in the Adapter Status box. Click Refresh to refresh the Adapter Status.
From the URM Adapter Settings box, you can view or modify the current connection settings for the URM Adapter. Click the Create button to add a new URM Adapter.
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.
For each external user directory, you must create a directory profile. You can have multiple profiles, if your deployment includes multiple LDAP-based server hosts, but only one profile can be set to Default and Active. Additional profiles can be set to Active, but they will not be in effect. Only one profile can be flagged as Default.
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.See Also:
For more information, consult the "Integrating and Synchronizing LDAP with Oracle Beehive" module of the Oracle Beehive Installation Guide.To synchronize with a remote LDAP-based user directory, you must create a directory profile.
From the System menu, click External Directories. From the External Directories pane, click Edit.
From the External Directories Edit window, click New.
In the New Directory Profile window, enter information about your external directory:
Give the profile a Profile Name
Select the Directory Type
Optionally, enter a Primary Authentication Attribute
Note:
The Primary Authentication Attribute is mandatory when the Default check box is checked.Enter a User Search Base
Enter a Server Host, Server Port, User Name, and User Password, which Oracle Beehive will use to access your remote directory. Enter the password again in the Confirm Password field. Check the Use secure connection check box to use an encrypted protocol to connect to the indicated port.
Optionally, enter a Group Search Base
Optionally, enter a Polling Interval (in seconds).
Check the Default box if this directory profile will be the default directory profile for your enterprise.
Check the Enable check box to enable this directory profile once it is created.
Click Next.
On the Rulesets page, configure the following:
In Scope and Membership Ruleset, click Configure. On the Scope Ruleset table, click Add to add rows. Type the name of a level of scope in the source directory, and then enter a Value to map it to an Oracle Beehive level of scope. When a scope rule is added, you may optionally add membership rules corresponding to the scope rule. Click Apply when you are done adding rows.
In User Type Ruleset, click Configure. On the User Type Ruleset table, click Add to add rows. Set the Source Field to a field in the source directory, set the Value to the value of that field that maps to an Oracle Beehive user type, and then use the drop down list to map it to an Oracle Beehive user type. Click Apply when you are done adding rows.
In Group Type Ruleset, click Configure. On the Group Type Ruleset table, click Add to add rows. Set the Source Field to a field in the source directory, and set the Value to a value that corresponds to a static group in Oracle Beehive. Click Apply when you are done adding rows.
Click Next.
On the Mapping page, configure the following:
In Enterprise User Attributes Mapping, click Configure. On the Enterprise User Mapping table, the default mappings for your directory type have already been added. Click Add to add rows. Enter a Source Attribute from your external directory, select a Beehive Attribute from the drop down list, select an attribute type, and, where applicable, select an attribute subtype or an OraPostal type. Click Apply when you are done adding rows.
In Extended Enterprise User Attributes Mapping, click Configure. On the Extended Enterprise User Mapping table, the default mappings for your directory type have already been added. Click Add to add rows. Enter a Source Attribute from your external directory, select a Beehive Attribute from the drop down list, select an attribute type, and, where applicable, select an attribute subtype or an OraPostal type. Click Apply when you are done adding rows.
In External Person Attributes Mapping, click Configure. On the External Person Mapping table, the default mappings for your directory type have already been added. Click Add to add rows. Enter a Source Attribute from your external directory, select a Beehive Attribute from the drop down list, select an attribute type, and, where applicable, select an attribute subtype or an OraPostal type. Click Apply when you are done adding rows.
In Static Group Attributes Mapping, click Configure. On the Static Group Mapping table, the default mappings for your directory type have already been added. Click Add to add rows. Enter a Source Attribute from your external directory, select a Beehive Attribute from the drop down list, select an attribute type, and, where applicable, select an attribute subtype or an OraPostal type. Click Apply when you are done adding rows.
Click Finish to create the directory profile.
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
