Skip Headers
Oracle® Enterprise Manager Concepts
10g Release 5 (

Part Number B31949-10
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

12 Oracle Beehive Management

This chapter describes how you can use Grid Control to manage your Oracle Beehive targets.

This chapter contains the following sections:

About Oracle Beehive

Oracle Beehive is the next generation of Oracle's enterprise collaboration technologies. Oracle Beehive provides a unified collaboration application and platform comprised of a comprehensive set of integrated, Java-based services, offering a new paradigm for enterprise collaboration solutions.

Oracle Beehive provides the full range of collaborative services for enterprise users, including:

The following terms and concepts form the foundation of the Oracle Beehive system, enabling many of the collaboration-based features that it provides:

Using Grid Control for Monitoring Oracle Beehive Targets

Enterprise Manager helps you monitor Oracle Beehive components in your enterprise. You can discover Oracle Beehive components in your environment and add them to Grid Control for central monitoring and management. Enterprise Manager Agents will discover and monitor Oracle Beehive sites, services, and service instances. In Grid Control Oracle Beehive sites, services (called applications), and service instances (called application instances) have home pages.

Following are the target types defined for Oracle Beehive in Grid Control:

Discovering Oracle Beehive Sites

Enterprise Manager can discover Oracle Beehive sites from remote as well as local agents. Local agents could be used to monitor application instances. Oracle Beehive site, application and application instances discovery, monitoring and configuration parameter collections use the JMX interface exposed by Oracle Beehive's BEEMGMT OC4J. All Oracle Beehive application instances are grouped under the corresponding Oracle Beehive application type. For example, all E-mail application instances will be grouped under a single E-mail application.

To add new Oracle Beehive targets to be monitored by Grid Control, you will need to initiate the discovery process for each Oracle Beehive site.

Oracle Beehive Site Home Page

The Oracle Beehive Site Home page provides information about:

  • All Oracle Beehive applications and application instances within the Oracle Beehive site

  • Current Status, Availability, and Site Version

  • Site usage for commonly used Oracle Beehive Services including CalDAV, WebDAV, E-mail (IMAP), and XMPP

  • Configuring Systems and Services

  • Accessing System and Services dashboards for snapshots of the system and service-related information

  • Drill-downs to view monitoring metrics and configuration for each Oracle Beehive application and application instance

  • Alerts and diagnostic drill-downs so you can identify and resolve problems quickly

You can filter the view based on Physical or Application Deployment of Oracle Beehive. Application Deployment refers to the Oracle Beehive services deployed in an Oracle Beehive site. There can be multiple instances of Oracle Beehive services deployed within one or more OC4J containers. You can further filter the Application Deployment view by applications. Physical Deployment view shows the hosts, Oracle Application Servers, HTTP servers, OC4Js, and the database comprising an Oracle Beehive site. You can further filter this view based on the host, database, or platform components.

Figure 12-1 shows the Oracle Beehive Site home page.

Figure 12-1 Oracle Beehive Site Home Page

This is the Beehive Site Home Page.
Description of "Figure 12-1 Oracle Beehive Site Home Page"

If the Oracle Beehive System and Services have not been created, you can create them by configuring the service tests for the Oracle Beehive Site.

Once the Oracle Beehive System and Services is configured, you can view snapshots of the service and system related information from the service and system dashboards on the Oracle Beehive Site home page. For more information about Oracle Beehive System and Services, see "Oracle Beehive System and Services". For information about Systems and Services in Enterprise Manager, see Chapter 6, "Service Management".

Rediscovering an Oracle Beehive Site

Enterprise Manager allows you to rediscover an Oracle Beehive site and its sub-components. During rediscovery, all sub-components of Oracle Beehive are compared. Rediscovery of Oracle Beehive includes addition of new Oracle Beehive targets, deletion of Oracle Beehive targets, or changing the configuration of existing Oracle Beehive targets.


Ensure that you have the necessary privileges to create, delete, and view targets.

Oracle Beehive System and Services

Since Oracle Beehive offers a set of complex and critical applications and services, it is very important for IT organizations to monitor and manage them for availability and performance. Enterprise Manager Oracle Beehive Site Systems and Services help you to effectively manage Oracle Beehive services from the overview level to the individual component level. Using Grid Control, you can identify and map service unavailability and performance degradation to one or more component failures. Grid Control not only monitors individual components in Oracle Beehive deployments such as hosts, databases, OC4Js, application servers, Beehive Site, Beehive application instances (for example, E-mail application instances, Instant Messaging application instances), etc., but also the applications hosted by those components, allowing you to monitor critical applications using the top down approach and from end-user perspective.

A "Service" in Enterprise Manager is defined as an entity that provides a useful function to its users. It models a business process or application, such as e-mail, time management, instant messaging, and so on. A "System" is a group of underlying components, such as hosts, databases, OC4Js, application servers, etc., on which the Service runs. A "Service test" is a functional test that is run against a service to determine the availability and performance of a service. For example, an IMAP Service test would determine the availability and performance of the E-mail service accessed via standard IMAP protocol. Availability of a service is a measure of the end-users' ability to access the service at a given point in time. Performance indicates the response time as experienced by the end-users. For information about Services and Systems, see the Service Management and System Management chapters in this guide.

Following is the complete Services hierarchy included in the model template. The hierarchy shown in the wizard is subject to the Oracle Beehive applications deployment. For example, if there is no FTP application discovered during Oracle Beehive Site discovery, the wizard will not include FTP Service in the hierarchy.

Following is the complete Systems hierarchy included in the model template:

Based on the System and Services hierarchy configured through the wizard, an Oracle Beehive Site Service dashboard and an Oracle Beehive Site System dashboard will be automatically generated.


The Core System will be created only if there are agents monitoring the Oracle Beehive hosts, Oracle application servers, OC4Js, databases, LDAP servers, and so on.

For information about Oracle Beehive service dashboard metrics, see Appendix A.

Automated Oracle Beehive Monitoring and Alerts

Enterprise Manager automatically gathers and evaluates diagnostic information from Oracle Beehive targets distributed across the enterprise. As with all targets managed by Enterprise Manager, an extensive number of Oracle Beehive performance metrics are automatically monitored against predefined thresholds. Alerts are generated in Grid Control when metrics exceed these thresholds.