Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management 12c Release 1 (12.1.0.1) Part Number E24215-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how you can discover and monitor Oracle Service Bus (OSB) using Enterprise Manager Cloud Control.
In particular, this document covers the following:
The following are the versions of OSB that are supported for monitoring in Enterprise Manager Cloud Control.
Table 7-1 Supported Versions
Supported OSB Version | Oracle WebLogic Managed Server Deployed To | Supported Enterprise Manager Cloud Control |
---|---|---|
Aqualogic Service Bus 2.6, 3.0, and Oracle Service Bus 10gR3, Oracle Service Bus 11.1.1.2.0, 11.1.1.3.0, and 11.1.1.4.0 |
Oracle WebLogic Server 9.2, 10, 10.3 |
Enterprise Manager 10g Release 5 (10.2.0.5) or higher Enterprise Manager 11g Enterprise Manager 12c |
The OSB deployed to Oracle WebLogic Managed Server is automatically discovered in Enterprise Manager Cloud Control when that Oracle WebLogic Managed Server is discovered and added to Enterprise Manager Cloud Control.
So, the discovery of OSB depends on the whether the Oracle WebLogic Managed Server is already being monitored in Enterprise Manager Cloud Control.
If Oracle WebLogic Managed Server is not being monitored in Cloud Control, then first discover and add it to Cloud Control; this will automatically discover the OSB that is deployed to it.
If Oracle WebLogic Managed Server is already being monitored in Cloud Control, then 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.
For instructions to discover OSB, see Section 7.5, "Discovering Oracle Service Bus".
The following describes the overall process involved in discovering and monitoring OSB in Enterprise Manager Cloud Control. Follow the instructions outlined against each step in this process to successfully discover and monitor your OSB.
Table 7-2 Discovery Process
Step | Requirement | Description |
---|---|---|
1 |
Oracle Service Bus |
Install the OSB software. Note: Before you launch the OSB Deployment Procedure, ensure that Sun JDK has been installed. |
2 |
Enterprise Manager Cloud Control |
Install Enterprise Manager 12c. For information about installing the base release of Enterprise Manager Cloud Control, see the Enterprise Manager Cloud Control Basic Installation and Configuration Guide available at:
Oracle recommends that you install the Enterprise Manager Cloud 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 12c on the host where OSB is installed. If OSB and Enterprise Manager Cloud 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 Cloud 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:
For information about installing the Management Agent, see the Enterprise Manager Cloud Control Basic Installation and Configuration Guide available at: |
4 |
One-Off Patches |
The support for discovering and monitoring of OSB is enabled only when the one-off patches as described in Section 7.4, "Downloading One-Off Patches" are applied to the WebLogic Server Home where OSB is running. |
5 |
Discovery in Enterprise Manager Cloud Control |
OSB is automatically discovered when the Oracle WebLogic Server Domain to which it is deployed is discovered and added to Enterprise Manager Cloud Control. |
To view OSB services in Enterprise Manager Cloud Control, you must apply the following patches to your OSB servers.
Table 7-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 |
|
Oracle Service Bus 11.1.1.3.0 and 11.1.1.4.0 |
No Patch Required |
You can apply the patches in one of the following ways:
Online mode - Using the SmartUpdate tool available with Oracle WebLogic Managed Server
Offline mode - Manually copying the JAR files and classes to the OSB directories
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:
Note:
After applying the patches, restart the WebLogic domain and all of the management agents monitoring the domain.The OSB deployed to Oracle WebLogic Managed Server is automatically discovered in Enterprise Manager Cloud Control when that Oracle WebLogic Managed Server is discovered and added to Enterprise Manager.
So, before discovering OSB, identify whether the Oracle WebLogic Managed Server is already being monitored in Enterprise Manager.
If Oracle WebLogic Managed Server is not being monitored in Enterprise Manager, then first discover and add it to Enterprise Manager Cloud Control; this will automatically discover the OSB that is deployed to it.
If Oracle WebLogic Managed Server is already being monitored in Enterprise Manager, then 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.
This section outlines the instructions for discovering OSB for the cases described above. In particular, this section covers the following:
Section 7.5.1, "Discovering OSB Deployed to WLS Not Monitored by Enterprise Manager"
Section 7.5.2, "Discovering OSB Deployed to WLS Monitored by Enterprise Manager"
To discover OSB deployed to Oracle WebLogic Manager Server that is not monitored in Cloud Control, first discover that Oracle WebLogic Manager Server in Enterprise Manager Cloud Control; this will automatically discover the OSB that is deployed to it. To discover Oracle WebLogic Manager Server, follow these steps:
Log in to Enterprise Manager Cloud Control (as a SYSMAN user).
Click Targets and then Middleware.
Enterprise Manager Cloud Control displays the Middleware page that lists all the middleware targets being monitored.
In the Middleware page, from the Add list, select Oracle Fusion Middleware/WebLogic Server Domain and click Go.
Enterprise Manager Cloud 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.
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.
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 Cloud Control for monitoring purposes.
Enterprise Manager displays the Middleware page with a confirmation message that confirms that the Oracle WebLogic Manager Server has been successfully added to Cloud 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 Cloud 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"
In the case of clustered OSB domain, the Management Agent installed on Admin Server host should be used to discover the entire domain.
To discover OSB deployed to Oracle WebLogic Managed Server that is already being monitored in Cloud 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:
Login to Enterprise Manager and click Targets and then Middleware.
On the Middleware page, from the table that lists all the middleware targets being monitored, click the name of the Oracle WebLogic Server Domain.
On the Oracle WebLogic Server Domain Home page, in the General section, click Refresh Domain. Enterprise Manager Cloud Control displays the membership page that lists the OSB that is currently not being monitored. Click OK.
Enterprise Manager Cloud 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 Cloud Control takes a few seconds to reflect the membership details in this section.Click the Members tab and verify whether the OSB has been added.
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:
Log in to Enterprise Manager Cloud Control.
Enterprise Manager Cloud Control displays the home page.
From the top-right corner of the Home page, click Setup > Management Pack > Management Pack Access.
Enterprise Manager Cloud Control displays the Management Pack Access page.
In the Management Pack Access page, from the Search list, select Oracle Service Bus.
Enterprise Manager Cloud Control lists all the Oracle Service Bus targets being monitored.
From the table, for the Oracle Service Bus target you are interested in, enable the SOA Management Pack Enterprise Edition and click Apply.
This section describes the errors you might encounter while discovering OSB, and the workaround steps you can follow to resolve each of them.
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 7-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 Section 7.4, "Downloading One-Off Patches". |
The following error occurs if configuration information has not been collected for the selected Application Server.
Table 7-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 Configuration and then select Last Collected from the Application Server menu. |
The following error occurs when the Management Agent is upgraded to Enterprise Manager 12c with OMS 10.2.0.5.
Table 7-6 SOAP Test Error - Workaround Steps
Error Message | Workaround Steps |
---|---|
Add SOAP Test failed. The selected service has an invalid or incorrect WSDL URL. Check whether the Oracle Service Bus Target URL value is valid in the Monitoring Configuration page of the selected target. To access the Monitoring Configuration page, go to the Oracle Service Bus Homepage and from the Related Links section, select Monitoring Configuration. |
If the Management Agent has been upgraded to 12c with OMS 10.2.0.5, the following workaround must be applied to support the SOAP test. In the Monitoring Configuration page for the OSB target, set the Server URL to Access Proxy Services property to the URL for the specific WebLogic Server target. The URL must be in the format: |