Skip Headers
Oracle® Enterprise Manager Getting Started with Oracle Fusion Middleware Management
11g Release 1 (11.1.0.1)

E17558-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

6 Discovering and Monitoring Oracle Service Bus

This chapter describes how you can discover and monitor Oracle Service Bus (OSB) using Enterprise Manager Grid Control.

In particular, this document covers the following:

Supported Versions

The following are the versions of OSB that are supported for monitoring in Enterprise Manager Grid Control.

Table 6-1 Supported Versions

Supported OSB Version Oracle WebLogic Managed Server Deployed To Supported Enterprise Manager Grid Control

Aqualogic Service Bus 2.6, 3.0, and Oracle Service Bus 10gR3

Oracle WebLogic Server 9.2, 10, 10.3

Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)

Enterprise Manager Enterprise Manager 11g Grid Control Release 1 (11.1.0.1) or higher


Understanding the Discovery Mechanism

The OSB deployed to Oracle WebLogic Managed Server is automatically discovered in Enterprise Manager Grid Control when that Oracle WebLogic Managed Server is discovered and added to Enterprise Manager Grid Control.

So, the discovery of OSB depends on the whether the Oracle WebLogic Managed Server is already being monitored in Enterprise Manager Grid Control.

For instructions to discover OSB, see Discovering Oracle Service Bus.

Understanding the Discovery Process

The following describes the overall process involved in discovering and monitoring OSB in Enterprise Manager Grid Control. Follow the instructions outlined against each step in this process to successfully discover and monitor your OSB.

Table 6-2 Discovery Process

Step Requirement Description

1

Oracle Service Bus

Install the OSB software.

2

Enterprise Manager Grid Control

Install Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher.

Note that 10.2.0.5 is a patch set. Therefore, if you are installing Enterprise Manager Grid Control for the first time, then install the base release first and then apply the 10.2.0.5 patch set on it. For information about installing the base release of Enterprise Manager Grid Control, see the Enterprise Manager Grid Control Installation and Basic Configuration Guide available at:

http://www.oracle.com/technology/documentation/oem.html

Oracle recommends that you install the Enterprise Manager Grid Control components on a host that is different from the host where OSB is installed. For example, if OSB is installed on host1.xyz.com, then install and configure Oracle Management Service (OMS) and the Management Repository on host2.xyz.com.

3

Oracle Management Agent

(Management Agent)

Install Oracle Management Agent 10g Release 5 (10.2.0.5) or higher on the host where OSB is installed.

If OSB and Enterprise Manager Grid Control are on the same host, then you do not have to install a separate Management Agent. The Management Agent that comes with Enterprise Manager Grid Control is sufficient. However, if they are different hosts, then you must install a separate Management Agent on the host where OSB is installed. Alternatively, the Management Agent can also be installed on a different host and made to remotely monitor the OSB target on another host.

You can install the Management Agent in one of the following ways:

  • Invoke the installer provided with Enterprise Manager 10 Grid Control Release 2 (10.2.0.1), and select the installation type Additional Management Agent. Then apply the 10.2.0.5 Agent patch on it.

  • Use the Agent Deploy application within the Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) console.

  • Use the full agent kit that is available at:

    http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html

For information about installing the Management Agent, see the Enterprise Manager Grid Control Installation and Basic Configuration Guide available at:

http://www.oracle.com/technology/documentation/oem.html

4

One-Off Patches

The support for discovering and monitoring of OSB is enabled only when the one-off patches as described in Downloading One-Off Patches are applied to the WebLogic Server Home where OSB is running.

5

Discovery in Enterprise Manager Grid Control

OSB is automatically discovered when the Oracle WebLogic Server Domain to which it is deployed is discovered and added to Enterprise Manager Grid Control.


Downloading One-Off Patches

To view OSB services in Enterprise Manager Grid Control, you must apply the following patches to your OSB servers.

Table 6-3 One-Off Patches

Oracle Service Bus Version ID Password

Oracle Service Bus 2.6

EMMU

83XNT2D4

Oracle Service Bus 2.6.1

9NAF

TLZE4IPI

Oracle Service Bus 3.0

RPCD

JJEC2EY2

Oracle Service Bus 10.3.0

9HPA

FFLQHDHP

Oracle Service Bus 10.3.1

No Patch Required

 

You can apply the patches in one of the following ways:

For information about downloading these patches and applying them in either offline or online mode, see My Oracle Support note 804148.1. You can access My Oracle Support at:

https://support.oracle.com/

Note:

After applying the patches, restart the WebLogic domain and all of the management agents monitoring the domain.

Discovering Oracle Service Bus

The OSB deployed to Oracle WebLogic Managed Server is automatically discovered in Enterprise Manager Grid Control when that Oracle WebLogic Managed Server is discovered and added to Enterprise Manager Grid Control.

So, before discovering OSB, identify whether the Oracle WebLogic Managed Server is already being monitored in Enterprise Manager Grid Control.

This section outlines the instructions for discovering OSB for the cases described above. In particular, this section covers the following:

Discovering OSB Deployed to Oracle WebLogic Managed Server That Is Not Monitored in Grid Control

To discover OSB deployed to Oracle WebLogic Manager Server that is not monitored in Grid Control, first discover that Oracle WebLogic Manager Server in Enterprise Manager Grid Control; this will automatically discover the OSB that is deployed to it. To discover Oracle WebLogic Manager Server, follow these steps:

  1. Log in to Enterprise Manager Grid Control (as a SYSMAN user).

  2. Click Targets and then Middleware.

    Enterprise Manager Grid Control displays the Middleware page that lists all the middleware targets being monitored.

  3. In the Middleware page, from the Add list, select Oracle Fusion Middleware/WebLogic Server Domain and click Go.

    Enterprise Manager Grid Control displays the Add Oracle Fusion Middleware / WebLogic Server Domain wizard that captures the details of the Oracle WebLogic Server Domain to be discovered and monitored.

  4. In the Add Oracle Fusion Middleware / WebLogic Server Domain wizard, specify the required details and click Next on each page to reach the end of the wizard.

    For information about the details to be provided for each page of the wizard, click Help on each page.

  5. In the last page of the Add Oracle Fusion Middleware / WebLogic Server Domain wizard, click Finish to complete the discovery process and add the target to Grid Control for monitoring purposes.

    Enterprise Manager Grid Control displays the Middleware page with a confirmation message that confirms that the Oracle WebLogic Manager Server has been successfully added to Grid Control.

    In the Middleware page that shows all the middleware targets being monitored, you can see the Oracle WebLogic Managed Server and the OSB you just added. Note that, at this point, OSB will be the last target listed in the table. To see it nested under its Oracle WebLogic Managed Server, click Refresh on this page. Alternatively, navigate to another tab or page, and then return to the Middleware page.

Note:

After discovering and adding OSB to Enterprise Manager Grid Control, you can monitor its status from the OSB Home page. You can use the Services page to view a list of services.

For the first collection that happens, you will see the value "0" for all the metrics. This is an expected behavior. From the second collection onwards, you should see the actual metric values. However, if you still see the value "0", then perhaps the service monitoring is turned off. To resolve this issue, on the Services page, click Launch Console to access the OSB Console, and turn on the service monitoring and set the level to "pipeline" or "action".

Discovering OSB Deployed to Oracle WebLogic Managed Server That Is Already Monitored in Grid Control

To discover OSB deployed to Oracle WebLogic Managed Server that is already being monitored in Grid Control, refresh the membership of the Oracle WebLogic Server Domain to which the Oracle WebLogic Managed Server belongs. This will automatically discover the OSB that is deployed to it.

To refresh the membership of the Oracle WebLogic Server Domain to which the Oracle WebLogic Managed Server belongs, follow these steps:

  1. In Grid Control, click Targets and then Middleware.

  2. On the Middleware page, from the table that lists all the middleware targets being monitored in Grid Control, click the name of the Oracle WebLogic Server Domain.

  3. On the Oracle WebLogic Server Domain Home page, in the General section, click Refresh Domain. Enterprise Manager Grid Control displays the membership page that lists the OSB that is currently not being monitored. Click OK.

    Enterprise Manager Grid Control refreshes the membership and returns to the Oracle WebLogic Server Domain Home page.

    Note:

    On the Oracle WebLogic Server Domain Home page, in the Status section, the legend of the status pie chart may not show an increased count to indicate the newly added OSB target. This is an expected behavior because Enterprise Manager Grid Control takes a few seconds to reflect the membership details in this section.
  4. Click the Members tab and verify whether the OSB has been added.

Enabling Management Packs

Besides monitoring the status of OSB, if you want to gain access to additional value-added features, then you must enable the Management Pack for SOA.

To enable the Management Pack for SOA:

  1. Log in to Enterprise Manager Grid Control.

    Enterprise Manager Grid Control displays the home page.

  2. From the top-right corner of the Home page, click Setup.

    Enterprise Manager Grid Control displays the Overview of Setup page.

  3. In the Overview of Setup page, from the left-vertical menu pane, click Management Pack Access.

    Enterprise Manager Grid Control displays the Management Pack Access page.

  4. In the Management Pack Access page, from the Search list, select Oracle Service Bus.

    Enterprise Manager Grid Control lists all the Oracle Service Bus targets being monitored.

  5. From the table, for the Oracle Service Bus target you are interested in, enable the SOA Management Pack Enterprise Edition and click Apply.

Troubleshooting

This section describes the errors you might encounter while discovering OSB, and the workaround steps you can follow to resolve each of them.

This section covers the following:

Required Patches Missing

The following error occurs when you try to discover OSB from an Oracle WebLogic Admin Server that has not been patched with the required one-off patches.

Table 6-4 oracle.sysman.emSDK.emd.fetchlet.FetchletException Error - Workaround Steps

Error Message Workaround Steps
oracle.sysman.emSDK.emd.fetchlet.FetchletException: 
The MBean is not available on the OSB instance. The 
required EM plug in patch should be missing on OSB 
instance.

Apply the one-off patches as described in Downloading One-Off Patches.


System and Service

The following error occurs if configuration information has not been collected for the selected Application Server.

Table 6-5 Create System and Service Error - Workaround Steps

Error Message Workaround Steps
An error encountered while discovering the 
dependencies. This may occur if some configuration 
information is missing. Check whether the 
configuration information was collected for the 
dependent targets and then try again.

Collect the latest configuration data by navigating to the Application Server Home page and clicking Administrations and then select Last Collected.