• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Less13 3 e_loadmodule_3

Less13 3 e_loadmodule_3



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

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



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • 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 Less13 3 e_loadmodule_3 Presentation Transcript

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