Less13 3 e_loadmodule_3

482 views

Published on

This is part of R12 Testing Suite for Oracle Applications or E-Business suite.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
482
On SlideShare
0
From Embeds
0
Number of Embeds
28
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Data Sources - Select the type of object that is going to supply the data. Security information and other details are necessary to connect to the various system, components in a web application. A data source is where monitor information is coming from Metrics - Individual monitor information collected. For example CPU % Busy Time under systems gives and percent usage of the CPU. Metric Profiles - A collection of individual monitors for a given server or system type.
  • Oracle Application Testing Suite: Introduction 13 - Data Sources Expand the Data Sources node as shown. For simplicity, we will use Windows perfmon as the data source. Click “Next”
  • Click Edit to open the dialog for configuring permissions on the monitored system.
  • Less13 3 e_loadmodule_3

    1. 1. ServerStats Introduction to Oracle Application Testing Suite: e-Load
    2. 2. ServerStats <ul><li>Server performance monitoring tool </li></ul><ul><li>Collects data from various tiers </li></ul><ul><li>Real-time displays </li></ul><ul><li>Charting capabilities and alarm setup </li></ul><ul><li>Server data saved to e-Reporter </li></ul><ul><li>Correlated with load test results from e-Load for bottleneck analysis </li></ul><ul><li>Add new ServerStats monitors to a running load test session. </li></ul><ul><li>A URL Data Source is available for collecting performance metrics that are accessible via a Web page (that is, Apache performance statistics). </li></ul><ul><li>The Metrics interface allows you to enable multiple metrics to be created at once. </li></ul>
    3. 3. Back-End System Monitoring <ul><li>System Architecture Map </li></ul>
    4. 4. What Systems to Monitor <ul><li>Look at a system architecture map, determine what systems are contained within the web application. </li></ul><ul><li>Talk to developers or system architects to learn about the various pieces of the system and how they interact. </li></ul><ul><li>Also, determine who will monitor and setup these counters. Individuals responsible for monitoring might be a system admin, DBA or QA engineer for example. </li></ul>
    5. 5. Useful Counters on Web Server <ul><li>CPU Usage </li></ul><ul><li>Memory Usage </li></ul><ul><li>Hits/pages per second </li></ul><ul><li>Web process system utilization </li></ul><ul><li>Current connections </li></ul><ul><li>Disk swapping </li></ul><ul><li>Disk utilization </li></ul>
    6. 6. Useful Counters on Application Servers <ul><li>CPU Usage </li></ul><ul><li>Memory Usage </li></ul><ul><li>Hits/pages per second </li></ul><ul><li>Request queue </li></ul><ul><li>Application Server process system utilization </li></ul><ul><li>Queue wait time </li></ul><ul><li>Disk swapping </li></ul><ul><li>Disk utilization </li></ul>
    7. 7. Useful Counters on Database Servers <ul><li>CPU Usage </li></ul><ul><li>Memory Usage </li></ul><ul><li>Database process system utilization </li></ul><ul><li>Table scans </li></ul><ul><li>Query wait times </li></ul><ul><li>Selects/inserts/deletes/updates per second </li></ul><ul><li>SQL recompilations </li></ul><ul><li>Table locks </li></ul><ul><li>Index hits (%) </li></ul>
    8. 8. Run-Time ServerStats Configuration <ul><li>ServerStats configuration is located under the “Set up autopilot” tab </li></ul><ul><li>To Create new or edit existing ServerStats Monitors click “Edit Configurations” or select from the ServerStats menu. </li></ul>
    9. 9. Add New ServerStats Configuration <ul><li>ServerStats > Configurations </li></ul>
    10. 10. ServerStats Configurations <ul><li>Click the “New” button to add a new configuration </li></ul><ul><li>Use the Edit button to modify an existing configuration </li></ul><ul><li>Use the Delete button to delete and existing configuration </li></ul><ul><li>Click the “New” button under monitors after you create a configuration </li></ul>
    11. 11. Add New Monitor <ul><li>Click on “Add a New Monitor” </li></ul><ul><li>Select monitor to add </li></ul><ul><ul><li>Data Sources </li></ul></ul><ul><ul><li>Metrics </li></ul></ul><ul><ul><li>Metric Profiles </li></ul></ul>
    12. 12. Configure Data Sources
    13. 13. Configure Data Sources <ul><li>Click edit and enter a user who has appropriate access to the system. </li></ul>
    14. 14. Configure Data Sources <ul><li>Click next to discover. </li></ul>Select the desired monitor as shown. In this example, we choose memory and CPU objects.
    15. 15. Configure Data Sources <ul><li>After clicking finish, the following screen is shown </li></ul>
    16. 16. Metrics <ul><li>The process for configuring a metric (individual monitor) is the similar to that of the data source. </li></ul><ul><li>Metric is done one by one and automatically selects an appropriate data source. </li></ul>
    17. 17. Metric Profiles <ul><li>Metric Profiles are used to configure several monitors in one step. </li></ul><ul><li>Commonly used metrics are preconfigured in the profiles </li></ul><ul><li>Data sources are automatically selected when creating metric profiles. </li></ul>
    18. 18. Select ServerStats Configuration <ul><li>Before starting a test, select the appropriate ServerStats configuration to use. </li></ul><ul><li>Monitors for that configuration will be displayed in the monitors window </li></ul>
    19. 19. Exercise 3 <ul><li>Set up server stats to collect the following information. </li></ul><ul><li>If possible, set this up to monitor the web server, otherwise just setup to monitor the e-Load client machine executing the VU’s </li></ul><ul><li>Percent CPU and Percent Memory Utilization </li></ul><ul><li>Web Server Total Requests/Sec (if available) </li></ul><ul><li>Application Server Queued Requests (if available) </li></ul><ul><li>Database Server User Connections (if available) </li></ul><ul><li>Rerun the load test that you setup in Workshop 1 but this time collect the ServerStats data </li></ul>

    ×