This chapter describes how you can discover and monitor Service Bus using Enterprise Manager Cloud Control.
In particular, this document covers the following:
The new features that have been introduced in the 13c version of the SOA Suite are:
Cluster-Level Target pages
Heat Maps
The following are the versions of Service Bus that are supported for monitoring in Enterprise Manager Cloud Control Release 13c.
Service Bus 12.2.1.x
Service Bus 12.1.3.x
Service Bus 11.1.1.7.x
Service Bus 10.3.2.0.x
The Service Bus 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.
The discovery of Service Bus 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 Service Bus 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 Domain to which the Oracle WebLogic Managed Server belongs. This will automatically discover the Service Bus that is deployed to it.
For instructions to discover Service Bus, see Discovering Service Bus.
The following table describes the overall process involved in discovering and monitoring Service Bus in Enterprise Manager Cloud Control. Follow the instructions outlined for each step in this process to successfully discover and monitor your Service Bus.
Table 10-1 Discovery Process
Step | Requirement | Description |
---|---|---|
1 |
Service Bus |
Install the Service Bus software. Note: Before you launch the Service Bus 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 . Oracle recommends that you install the Enterprise Manager Cloud Control components on a host that is different from the host where Service Bus is installed. For example, if Service Bus 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 Service Bus is installed. If Service Bus 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 Service Bus is installed. Alternatively, the Management Agent can also be installed on a different host and made to remotely monitor the Service Bus 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. |
4 |
Discovery in Enterprise Manager Cloud Control |
Service Bus is automatically discovered when the Oracle WebLogic Domain to which it is deployed is discovered and added to Enterprise Manager Cloud Control. |
The Service Bus 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.
Before discovering Service Bus, 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 Service Bus 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 Domain to which the Oracle WebLogic Managed Server belongs. This will automatically discover the Service Bus that is deployed to it.
This section outlines the instructions for discovering Service Bus for the cases described above. In particular, this section covers the following:
To discover Service Bus 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 Service Bus that is deployed to it. To discover Oracle WebLogic Manager Server, follow these steps:
Note:
After discovering and adding Service Bus to Enterprise Manager Cloud Control, you can monitor its status from the Service Bus 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 that are enabled in Oracle Enterprise Manager Release 12c. 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 Service Bus Console, and turn on the service monitoring and set the level to "pipeline" or "action".
In the case of clustered Service Bus domain, the Management Agent installed on Admin Server host should be used to discover the entire domain. This constraint is not applicable for version 12.1.0.2 of Cloud Control. This is only valid up to version 12.1.0.1 of Cloud Control.
For additional information about Fusion Middleware discovery, see Oracle Enterprise Manager Cloud Control Administrator's Guide.
To discover Service Bus deployed to Oracle WebLogic Managed Server that is already being monitored in Cloud Control, refresh the membership of the Oracle WebLogic Domain to which the Oracle WebLogic Managed Server belongs. This will automatically discover the Service Bus that is deployed to it.
To refresh the membership of the Oracle WebLogic Domain to which the Oracle WebLogic Managed Server belongs, follow these steps:
Besides monitoring the status of Service Bus, 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:
Enterprise Manager Cloud Control helps you monitor the health of Service Bus targets deployed to Oracle WebLogic Managed Servers. When you discover Oracle WebLogic Managed Servers, Cloud Control automatically discovers the Service Bus targets deployed to them and adds them for central monitoring and management.
For each Service Bus target being monitored, Cloud Control provides information about its status, availability, performance, services, alerts, business services, proxy services, pipeline services, and split-join services. It also allows you to view the latest configuration details, save them at a particular time, and compare them with other Service Bus instances. Service BusService Bus also provides a graphical view representation for the dependencies between proxy services and business services.
In addition to monitoring capabilities, Cloud Control also allows you to black out an Service Bus target and create infrastructure services. While blackout helps you suspend the monitoring of the target for a temporary period (for example, during maintenance), infrastructure services are dependency services that are created to identify the infrastructure components on which the Service Bus target depends.
If you are not able to view Service Bus data on Enterprise Manager pages, it may be because monitoring is disabled for Service Bus Services. Before you can view Service Bus data in Enterprise Manager, check to see if monitoring is enabled for Service Bus Services. You can do that by following these steps:
You can use Enterprise Manager to print Service Bus reports using BI Publisher Enterprise Reports. Oracle Business Intelligence (BI) Publisher is an enterprise reporting solution for authoring, managing, and delivering highly formatted documents. Oracle BI Publisher also allows you to build custom reporting applications that leverage existing infrastructure. Reports can be designed using familiar desktop products and viewed online or scheduled for delivery to a wide range of destinations.
For example, you can generate an Service Bus Services Report that describes the way Service Bus services have been performing over a period of time. The report provides charts to list the top 5 Service Bus Services and a table with critical metric details for all the services.
The following table describes the Service Bus-related reports you can choose.
Table 10-2 Service Bus Reports
Service Bus Report | Description |
---|---|
Service Bus Service Summary Report |
The Service Bus Service Summary Report provides information about the Average Response Time, Open Instances Count, Fault Instances Count, and Web Service Security Violation Count for the selected service. The Service Bus Service Summary Report displays a chart with the top 5 Service Bus services based on Average Response Time or Throughput across the selected Service Bus services for the specified time period. The report can be sorted based on a performance metric (for example, Average Response Time) or a usage metric (for example, Instance Count). As part of the report parameters setting, you can use options that allow you to select the Service Bus Service by Projects or by selecting individual services. |
Service Bus Service Operations Summary Report |
The Service Bus Service Operations Summary Report provides internal operation level details for the selected service. The details in the report cover the Average Response Time, Open Instances Count, Fault Instances Count, and Web Service Security Violation Count. The report can be sorted based on a performance metric or a usage metric. As part of the report parameters setting, you can use options that allow you to select the Service Bus Service by Projects or by selecting individual services. |
To print Service Bus reports using BI Publisher Enterprise reports, follow these steps:
This section describes the errors you might encounter while discovering Service Bus, and the workaround steps you can follow to resolve each of them.
The following error occurs if configuration information has not been collected for the selected Application Server.
Table 10-3 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. Click Configuration, and then select Last Collected from the Application Server menu. |
The following error occurs when the Management Agent is upgraded to Enterprise Manager 13c with OMS 10.2.0.5.
Table 10-4 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 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 Service Bus Homepage and from the Related Links section, select Monitoring Configuration. |
If the Management Agent has been upgraded to 12c, the following workaround must be applied to support the SOAP test. In the Monitoring Configuration page for the Service Bus 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: |