While we talk about monitoring applications in general, can OMC monitor packaged applications such as E-Business Suite, PeopleSoft and so on. Yes, OMC provides a 3600 monitoring of packaged applications. This demo shows how you can monitor E-Business entities running on OCI.
This slide shows all the enterprise applications that can be monitored by Oracle Management Cloud
Why OMC? What are some of the unique capabilities of OMC that it will give it an edge?
Complete Visibility
Shift from multiple siloed tools to OMC to get unified/centralized visibility into your application and associated infrastructure. This helps you manage availability and performance of your packaged applications efficiently.
Rapid Problem Isolation
Identification of problems by correlating logs across entire infrastructure.
Resolve Performance Bottlenecks Machine learning capability of OMC helps identify potential issues and solve before the end-user is impacted
Predictive capacity planning
OMC uses seasonality aware capacity forecasting and trending, get to know any capacity bottlenecks problems before you actually experience it.
Optimize Cost of Operations
Identify under utilized resources and reclaim those. OMC processes the operational data set and provides intelligent, actionable insights. This in turn helps you optimize your cost and/or operational efficiency
Solve visibility issues caused by rapid software updates by leveraging APM to see across Traditional IT Silos in Dev or Production
Handle dynamically changing infrastructure (Infrastructure as code) by using dynamic application discovery and modeling
Solve functional issues in production with integrated log analytics
So let’s start our demo!
Note: Please Use Google Chrome to run through the demo.
Here we can see all the different integrated services on Oracle Management Cloud.
[Click Dashboards]
EBS Health is a custom dashboard designed to manage all EBS related entities and the associated Infrastructure. This dashboard demonstrates OMC’s capability of managing the Oracle EBS Infrastructure on cloud in the single dashboard.
[Click ‘EBS Health’]
Provides complete visibility to your E-Business services whether those are running in on-premises or deployed in the cloud and natively monitored by OMC. It shows the associated entities and their status, alerts, performance, database errors, middleware errors, CPU utilization, memory utilization and so on.
Search for the EBS composite
Type EBS and the select EBS12_2_OCI
[Change the timeline to Last 7 days to view the Top Programs by Maximum Running Time and Average Running Time]
View widgets “Top Programs by Maximum Running Time” and “Top Programs by Average Running Time”
[Scroll Down]
View the widgets - Errored Transactions, Database Errors, Middleware Errors, Web Request Rate, EBS Front End Activity
Observe that there are no Errored Transactions or Database Errors in the last 7 days.
[Click Topology icon to view the complete topology]
You can maximize the topology view. The topology clearly indicates that middleware entities are down with the entity colors in red. You can hover the mouse over those entities to check the details.
Let us now take a look at the complete EBS Infrastructure Monitoring.
[Click Topology icon to close the topology and then click Monitoring]
You will see the enterprise summary page. Let us now take a look at all entities associated with this EBS composite.
[Click Entities]
Observe the entity types, the number of entities in each entity type, and overall status.
[Click EBS12_2_OCI] to drill down
View the success rate and error rate of concurrent processing and also the resource utilization of Hosts, DB, HTTP Server, and WebLogic
[In the Hamburger menu click the arrow icon]
[Click Log Analytics]
Let’s move to the next use-case which is diagnosing issues rapidly.
We have now switched to log analytics which enables us to view all logs associated with the composite and drill down as required.
[Click Topology icon]
[Click on the Middleware entity EBS Workflow Notification Mailer which is down]
[Change Visualization from Pie to Records with Histogram]
This will open this widget in the Log Explorer.
[Scroll down]
Observe that there are 94000+ logs. It is very easy to overlook the logs/issues that might be leading to a potential bottleneck. Log explorer helps us find a needle in a haystack and thereby helps us focus on the key issues.
[Click Records with Histogram dropdown and then click the Cluster icon]
The 94000+ logs are now grouped to clusters and potential issues that need attention are identified
[Click Potential Issues]
Thus you can drill down into potential issues, isolate them and take necessary actions.
We saw that OMC provides complete visibility to health and performance of EBS Application and Infrastructure.
Now let’s see how you can use OMC to get an insight into the performance of the EBS Application, related end user activity, server requests, sessions and so on.
OMC allows you to monitor end users and help you diagnose end-user issues tracing that to back-end code.
Provide deep visibility to application code and identify response time issues and faults
3. Correlate application code issues with infrastructure logs for troubleshooting
Note that at this time, End User Monitoring (EUM) is available only to non-forms UI activity.
Let us navigate to APM.
[Clear the global context by removving both the entities]
[In the Hamburger menu click the arrow icon and then click APM ]
You will see the APM Home page.
Type EBS to search for the EBS Application
OMC’s Application Performance Monitoring helps you understand end-user behavior, where users are coming from and whether they are having performance issues or running into any errors. You can monitor total users, response times and Errors
It also helps you identify issues in your application code by identifying top server requests and provides visibility to application server performance.
[Click Sessions]
Let us drill down to sessions
Observe the session details such as date and time, location, duration and so on.
Click on any session and observe detail breakdown of page executions for that particular session.
[Click Server Requests]
You can see here APM automatically identifies different endpoints associated with EBS such as login page, wls console and so on.
Let us drill down to get more details about the requests to EBS login page
[Click /OA_HTML/AppsLogin]
We can clearly see the flow diagram of server requests
Hover mouse on any node to see more details.
This overview provides details on what actions were performed and various database interactions that take place, in the server, in order to process the request.
Scroll down the page and check out more details about the calls.
Diagnose Concurrent Manager Issues
[Clear the global context to remove the server request and the Composite]
[In the Hamburger menu click the Arrow, then click Monitoring > Entities]
[Under Entity Type, click EBS Concurrent Processing check box]
[Click the Entity]
[Click Performance Charts tab]
View the availability, success rate and error rate of the concurrent manager.
[Click Performance Tables tab]
Expand Active Concurrent Requests By Application and observe the repeating requests on various applications.
Similarly expand “Long Active Concurrent Requests” to check which user has such requests
You can also observe that SYSADMIN user has the most pending requests by expanding “Users With Most Pending Requests”
Let us now switch to the out of the box dashboard of Concurrent Processing. We can do this from the Entity Card of Concurrent Processing.
[Hover the mouse over the composite and click the 3 dots to open the entity card]
[In the entity card click Open In > Dashboard]
Alternately, you can also open the EBS Concurrent Processing Health dashboard from Dashboards
Observe the Latest Long Active Concurrent Requests. Make a note of the Request ID, for example 7600194. We can search for any logs associated with request ID’s.
Also, you can drill down to log explorer by clicking on any of the widgets.
[Click on Concurrent Requests By Issue]
[Remove the composite]
[Remove everything in the Log Explorer field and type the Request ID that you noted in earlier step]
[Change the timeline to 1 year as the request is an old request and click Run]
You will see the log information associated with this request.
