|Oracle® Enterprise Manager Administration
11g Release 1 (126.96.36.199)
|PDF · Mobi · ePub|
The Request Monitoring feature provides end-to-end visibility into requests for Java applications deployed to WebLogic Server. It establishes a clear view of a request flowing through a multi-tier java environment. This chapter describes the procedure to setup and enable the Request Monitoring feature in Enterprise Manager Grid Control. This chapter covers the following:
Before you enable Request Monitoring, you must do the following:
Identify the WebLogic Server targets and J2EE applications that are to be monitored.
Ensure that the necessary hardware for the ADP Manager, ADP database, and JVM Diagnostics Manager is available.
The following diagram shows the request monitoring architecture.
The JVM Diagnostics Agent and the ADP Agent are deployed on the WebLogic Server targets that are being monitored. These agents collect JVM Diagnostics and Application metrics and periodically report them to the JVM Diagnostics and ADP Managers. The Management Agent (EM Agent) on the ADP Manager machine, periodically runs a Fetchlet to retrieve the metrics from the ADP Manager and uploads them to the Management Repository. The Request Monitoring framework processes these metrics and uses them to monitor and analyze requests.
To setup end-user request tracing, follow these steps:
Deploy the Oracle Management Service and the Management Repository database. For details, see the Enterprise Manager Basic Installation and Configuration Guide.
Deploy the ADP Manager(s) on the designated machines. For details on deploying the ADP Manager, see the Getting Started with SOA Management Pack Plus Guide. The ADP Manager must be installed as the same user as the Management Agent (as described in the step below).
Deploy the Management Agent on all the machines on which the ADP Managers have been installed.
Deploy the Management Agent on the machine on which the WebLogic server target to be monitored is running. In Enterprise Manager Grid Control, click Targets and Middleware. On the Middleware page, check if the WebLogic Server target to be monitored has been discovered and registered as a target. If it has not been registered, add the WebLogic Server as a target and register it. For details on discovering and registering the WebLogic Server target, see the Oracle Fusion Middleware Administration Guide. If this WebLogic server target is configured to connect to a database running on a remote machine, ensure that the Management Agent is deployed on the remote machine, and confirm that this database is listed as a target in Enterprise Manager Grid Control.
Register the WebLogic Server target with ADP Manager. To do so, click the Application Dependency and Performance link on the Middleware page. Click the Registration tab on the right panel. The following screen is displayed.
Enter the name of the ADP Manager to be registered and the fully qualified host name of the machine that the ADP Manager is running on. The default port 51099 is pre-populated for you. Click Test Connect. If you can successfully connect to the host machine, click Add to complete the ADP Manager registration. For more details on registering the ADP Manager, see the Getting Started with SOA Management Pack Plus Guide.
Install the JVM Diagnostics Manager and deploy the JVM Diagnostics Agent on WebLogic Server targets. For more details, see the Setting Up the JVM Diagnostics Manager chapter.
To validate that the JVM Diagnostics Manager is communicating with the JVM Diagnostics Agent, click the JVM Diagnostics link on the Middleware page. Click on a target in the left hand panel, for example
__Farm01_medrec__medrec. In the right hand panel, click Pool > Threads > Real-Time Analysis. The following screen is displayed:
On this page, you can view the threads for each connected JVM.
Restart the ADP Manager and the WebLogic Server targets.
Click Application Dependency and Performance link on the Middleware page. Click the Monitoring tab on the right panel and select the CAMM option from the menu. The following screen is displayed.
You can validate that the ADP Agent has discovered the Java EE target by checking the Agent Status on this page.
Click the Request Monitoring link on the Middleware page. Click the Target Setup tab. A list of ADP Managers available for data collection is displayed as shown in the following screen.
On this page, do the following:
Select an ADP Manager from the list.
Select the Management Agent from the drop down list.
Enter the Key Store and Trust Store Password. The default password is
acseramanager. For security reasons, it is recommended that you change this password. For more details, see the Getting Started with SOA Management Pack Plus Guide.
Click Create Target. The ADP Manager is now registered as a target, and starts collecting data for Request Monitoring.
Request Monitoring setup is now complete. To view and configure requests, grant the Request Monitoring Administrator privilege which provides full access to the Request Monitoring pages and allows the user to modify the request configuration settings. For richer Request Monitoring functionality, we recommend that you grant the following privileges:
View any Target privilege which allows user to drill down to the Target Home page and to view the target metrics in the Topology view.
JVM Diagnostics privilege which allows user to drill down to the JVM Diagnostics pages from the Topology page.
After the appropriate privileges have been granted, click the Request Monitoring link on the Middleware page and then click the Request Definitions tab. The following screen is displayed.
You can now view requests and their performance, group requests, and set request response time violation thresholds (Critical and Warning).