EWLM: Autonomic Manager for your Virtualized Systems

  • 1,281 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,281
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. EWLM: Autonomic Manager for your Virtualized Systems Hiren Shah [email_address] Las Vegas, NV
  • 2. Agenda
    • EWLM Objective
    • EWLM Structure
    • Power5 Partition Management
    • Load Balancing
    • EWLM Value
  • 3. What is Enterprise Workload Manager (EWLM)?
      • Workload management of heterogeneous environments – goal based
      • Goal based resource optimization
      • End to end topology view and statistics for business transactions
      • Improved effectiveness of physical resources
      • Rapidly understand quality of service delivery
  • 4. High level overview of EWLM
    • … e-business environment issues …
      • When a performance problem occurs, who knows?
        • What components of the environment are contributing to the problem?
        • What resources are being used by an application or business process?
        • What workloads are impacted by the problem?
    Manages business process service levels Helps improve utilization of IT resources
  • 5. Objectives: Autonomic Management
    • Expected to provide following types of autonomic management capabilities over time
      • Workload Balancing
      • Partition Management
      • Local Resource Optimization
      • Middleware resource Optimization
      • Server Provisioning
  • 6. ITCAM/RTT and EWLM Relationship 1. An IT administrator notes performance problems for a critical application using ITCAM for RTT 3. EWLM adjusts delays by (a) load balancing, or (b) virtual server mgmt and (c) working with TIO/TPM to recommend when servers need provisioning 2. Because of past application problems, the Administrator uses ITCAM for RTT to determine the root cause of the problem – the diagnosis: limited server capacity DCM Linux Resource Pool HTTP Cluster ITCAM for RTT
    • Future additional EWLM resource mgmt that will automatically be provided for ITCAM with this integration
    • Storage i/o mgmt
    • Power mgmt
    • Local CPU, memory class mgmt
    TPM
  • 7. EWLM Management Domain
      • Scope of EWLM performance management and reporting
      • Set of servers communicating with a single domain manager
      • Transactions classified on entry to domain
      • Flexible scope:
        • Servers supporting a business app.
        • Single tier
        • Single server to support testing
  • 8. EWLM domain with supported operating systems z/OS AIX i5/OS Windows Linux
  • 9. EWLM Domain Manager Domain Manager Provides a platform agnostic, global management component supporting thousands of distributed web servers, application servers, database servers, and transaction servers.
    • Coordinates policy actions across all servers in the management domain (e.g. “deploy, “activate”)
    • Aggregates server, application, and transaction statistics to construct the global view
    • Provides services to export data for management, reporting, and logging purposes
    • EWLM UI
    • Topology visualization
    • Drill-down
    • Policy alerts
    • Operational actions
    • Real-time monitoring
    • External APIs
    • Policy state coordination
    • Statistics export
    • Management services
  • 10. EWLM Managed Server * On all IBM platforms, shipped with operating system ARM Instrumented Applications Non-ARM Instrumented Applications JNI Process Start/End Process Start/End EWLM extension ARM APIs Transaction Start/End * On non-IBM operating systems, shipped with EWLM Operating System Domain Manager
    • Server statistics
    • Application statistics
    • Application topology
    • Transaction statistics
    • Process statistics
    • End to End statistics
    • Domain Policy
    Platform specific operating system extensions * Process Samples, Transaction Statistics Comm Java Managed Server
    • Platform-specific operating system extensions
      • ARM implementation
      • System, process resource data collections
    • EWLM Managed Server
      • Data aggregation
      • Management Algorithms
    • ARM ( Application Response Measurement ) support
      • ARM 4.0 standard
      • Java and C APIs
  • 11. EWLM at the 2006 French Open (Roland-Garros 2006)
    • EWLM, a component of the IBM Virtualization Engine, has been chosen to monitor the web hosting infrastructure of the French Open (Roland-Garros) tennis tournament May 28 – June12, 2006
    • EWLM is monitoring:
      • NetPoll- on-line user poll application
      • Guestbook-on-line user comment application
      • Playersearch-on-line research about participants
    • Applications running across IHS servers on 6 Linux partitions
    • WebSphere on 2 AIX partitions and DB2 on 1 AIX partition
    • At upcoming events EWLM management capability will be used to tune resources to meet requirements and application goals
    http://www.rolandgarros.com
  • 12. EWLM at the 2006 Championships, Wimbledon
    • EWLM, a component of the IBM Virtualization Engine, has been chosen to monitor the web hosting infrastructure for Wimbledon.org, the Official Web site of the 2006 Wimbledon Championships—June 26 th —July 9 th , 2006
    • EWLM is monitoring the following applications under WebSphere on 2 AIX partitions:
      • NetPoll—an on-line user poll application
      • Feedback—an on-line user comment application
      • Player Search—on-line research about participating players
    • IHS on 6 Linux partitions
    • DB2 on 1 AIX partition
    • At a future event, EWLM management capability will be used to automatically tune resources to meet business requirements
  • 13. EWLM managed server implementation of ARM APIs The managed server supplies the ARM APIs, but it is up to the middleware or applications to make use of them. If middleware is instrumented, application running on the middleware is not required to use ARM. An application coded to drive ARM APIs is said to be “instrumented” for ARM Not all applications are ARM Instrumented Application Server Web Server arm_start_transaction(...) ARM Services arm_stop_transaction(...) arm_stop_application(...) arm_register_application process request correlator TC=Buy Hop 0
    • Enables capturing of end-to-end response time
    • Topology reporting
    • Granular transaction goal management
    • Resource consumption for specific transaction across different tiers
    arm_stop_application(...) arm_start_transaction(...) arm_stop_transaction(...) ARM Services arm_register_application(...) process request
  • 14. What happens if some piece isn’t ARMed? Other AppServer There’s still value! App doesn’t drive API
    • Key Points:
      • Transaction flow not interrupted – flows just as it would were EWLM not in the picture at all
      • First “Hop” can determine “end-to-end” response time, but details at later “hops” get lost
      • EWLM does has a mechanism to monitor platform-initiated “processes”
    EWLM Domain Manager EWLM Manager Messaging Services Control Center EWLM Management Console ARM API EWLM Code Operating System WebServer with Plugin ARM API EWLM code Operating System ARM API EWLM Code Operating System DB2 Database Server
  • 15. Managing un-ARMed middleware / applications If an application doesn’t make use of the ARM APIs provided by EWLM, then EWLM can’t monitor the response times . But some monitoring is possible. EWLM agent can “see” elements of the platform operating environment, and detect the starting of processes.
      • Report on server statistics, like CPU utilization
      • Can make use of “Process Classes” or “Partition Classes” to monitor un-ARMed applications
      • Supports system level load balancing and LPAR management
    Message: having applications ARMed is preferable, but some monitoring and management possible even without EWLM Agent Operating System Processes
  • 16. Currently instrumented applications from IBM Here are the “applications” – middleware, really – instrumented by IBM WebSphere Application Server V5.1.1 (or later, on supported Managed Server platforms) DB2 Universal Database, Version 8.2 (or later, on supported Managed Server platforms) Webserver Plugins (on supported Managed Server platforms)
    • IBM HTTP Server, IIS, Apache,
    • Other Plugins delivered in Websphere 5.1.1
    • (or later, on supported Managed Server platforms)
    More on the way Key Message: IBM is committed to EWLM and ARM, so more and more middleware will get instrumented
  • 17. High Level of How the Installation Process Works Manager Function EWLM Domain Manager Control Center WebSphere EWLM Agent Product Media EWLM Agent Installation Executable Installation Executable Browser 1 2 ARM 3 4
    • Install EWLM Domain Manager code and configure
      • Domain name, ports
    • Copy Managed Node installation images to managed servers, install and configure
      • Point to Domain Manager host name and port
    • ARM-enable applications
    • Configure Domain Policy
  • 18. Select System Services
  • 19. EWLM is Installed! Now, What's Next?
    • Configure Domain Manager using command line or Wizard
    • Create Users for administrating EWLM
    • Configure Managed Servers using command line or Wizard
    • Creating a Firewall Broker (optional)
    • Start the EWLM Control Center (WebSphere)
    • Start the Domain Manager
    • Start the Managed Servers
    • Start the Firewall Broker (optional)
  • 20. Welcome to EWLM Control Center Web-based interface that is accessible from any Web browser
  • 21. Three Main Functions Found in Control Center Console Where you define the performance goals and what’s monitored in the Domain. Where you can activate other service policies, and act against the managed servers in the Domain. Where you can monitor the activity of the Domain
  • 22. Introduction to Workload Classification Three basic, essential things related to this: Average Response 3 seconds Average Response 5 seconds 99% within 4 seconds Goal Rule Rule Rule Performance Goal defines the objective Work occurs in the Domain Rules tie the work to the Performance Goal Then you can monitor actual against the goal Browser Trans Trans Trans
  • 23. EWLM Domain policy
    • Specify goals and importance for business work
    • Create the transaction, partition, and process classification rules to associate workloads to the business goals.
  • 24. When Performance Goals Go Unmet: Importance” Imagine a case where two or more Service Classes have their performance goals go unmet. How can EWLM prioritize between them? With “Importance”
    • EWLM provides five levels of “Importance”:
      • Highest
      • High
      • Medium
      • Low
      • Lowest
    • Importance is designated when the Service Class is defined through the Control Center console
    Though both Service Class goals are unmet, EWLM would treat the “Stock Trade” Service Class as being “more important” than the “Web Banking” class. Service Class Name: “Web Banking” Goal: 4 second average Actual: 8.2 second avg. Importance: Medium Service Class Name: “Stock Trade” Goal: 95% under 2 sec. Actual: 22% under 2 sec. Importance: Highest
  • 25. Big Picture View of Classification The process might be illustrated like this: Transaction or Process? Transaction or Process? Transaction Rule Engine TC TC TC TC TC TC TC TC Transaction Rule Engine Service Class Service Class Service Class Service Class Process Rule Engine PC PC PC PC PC PC PC PC Process Rule Engine Service Class Service Class Service Class Service Class Default Service Class Default Service Class No Match No Match No Match No Match Workload initiation Transaction Process You ’ ll want to insure your workload gets funneled into your defined Service Classes and not the “ Default Service Class. ” That means careful assessment, planning and policy definition. Rules and Filters Rules and Filters Unclassified Map to Application that initiated Tran Map to Application that initiated Tran Map to Platform that initiated Process Map to Platform that initiated Process TC TC TC TC Service Class Service Class PC PC PC PC Service Class Service Class
  • 26. Reporting & Analysis Domain Manager Statistics
    • How are we doing?
      • Compared to business objectives
    • What applications support each class of service?
      • Graphical map of workflow topology
      • Relationships between middleware instances
      • Comparison of various instances
    • What happens at each transaction “hop”?
      • Response times, distributions, etc.
      • Resource consumption and delays
    • What servers support each middleware instance?
      • General server-level statistics
  • 27.
    • Management of CPU resources based on EWLM domain policy
      • Similar to what was done for zSeries IRD
      • Virtual processor optimalisation
      • CPU management by changing the entitled capacity for a partition
    • Multiple partition groups
      • A partition group cannot span systems
    • Mixture of operating systems in the same partition group
    • Shared processor partitions only
    • Multiple EWLM domains allowed per machine
    LPAR management for POWER5 Linux i5/OS “ EWLM” management 1 CPU 2 CPUs 4 CPUs Linux SLES 9 SP2 I5/OS V5.3 Linux SLES 9 SP2 AIX 5L V 5.3 ML3 AIX 5L V5.3 ML3 AIX 5L V5.3 ML3 AIX 5L V5.2 2 CPUs Linux SLES 9 I5/OS V5.2 AIX 5L V5.3 Micro-partitioning Domain Manager Hypervisor
  • 28. CPU Management on POWER 5 - Hypervisor VP VP VP VP VP VP VP VP VP VP VP VP Power5 Hypervisor
    • Manages shared processors
    • Unused capacity is distributed to demanding partitions
    • Allows customer to dynamically
    • change CPU allocation via HMC
    • No dynamic management of dedicated processors
    • No dynamic management of VCPUS
    • Does not understand business importance of the work
    Limitations Apache WAS DB2 WAS
  • 29.  
  • 30. Example of LPAR Management…
    • Surge in SC1 work and it begins to miss goals. EWLM detects CPU delay in WAS and DB2 partition
    • EWLM takes resource away from the WAS partition supporting SC2
    • EWLM also determines SC1 will do better by taking resources away from Apache partition and giving them to WAS/DB2
    • Number of VPs adjusted to match new resource allocations
    VP VP VP VP VP VP VP VP VP VP VP External high importance work (service class SC1) Internal low importance work (service class SC2) VP VP VP VP VP Apache WAS DB2 WAS
  • 31. What’s involved in partition management
    • Manage CPU resource across partitions
      • Move resources dynamically to where needed to meet goals stated in policy
      • If all goals cannot be met, sacrifice least important work
    • Optimize number of virtual processors (VPs)
      • Adjust number of VPs based on the partition’s entitled capacity and actual CPU consumption
      • Ensure partition is not held back because it does not have enough virtual processors and does not suffer unnecessary overhead from having too many virtual processors
    • Optimize weight of partitions in group
      • Each uncapped partition’s weight is adjusted based on its entitled capacity and actual CPU consumption to take advantage of capacity in the free pool
    • Maintain the defined capacity of the group
      • EWLM actions should not change the defined group capacity
      • Spare capacity in a group is re-distributed and extra capacity relinquished based on each partition’s entitled capacity
  • 32. Configuration : HMC Settings
  • 33. Internal Alg: Determining Partition needs help Select receiver service class missing goals Is CPU a bottleneck? Receiver value to LPAR Action? Send Mgs to Domain Manager “ plea for help” Yes Yes No No
  • 34. Domain Manager receives “plea for help” from member of LPAR group Send Msg to other members of group asking for impact of taking resources Is there a combination of donors that has “ net value” Select combination with least impact Send Msg to each Donor to make change No action Yes No Internal Alg: Selecting Donor Partitions
  • 35. The new EWLM function allows user of IBM’s POWER5 servers to automatically change the LPAR configuration depending on business goals defined in the EWLM policies. Customer and use scenario A POWER5 L 5 LPAR 4 LPAR 2 LPAR 1 L 3 EWLM monitors business goal violation (LPAR2) EWLM Console Show System behaviour EWLM Interaction on LPAR 2 & 5 TO FROM AIX Admin Users Patches etc. Linux Admin Users Patches etc. Linux Admin Users Patches etc. i5/OS Admin Users Patches etc. AIX Admin Users Patches etc.
  • 36. Customer and use scenario B pSeries LPAR 1 LPAR 2 LPAR 3 LPAR 4 EWLM can manage partition running un-instrumented middleware (e.g. Oracle) with velocity goals. Time 1 Time 1 + x HTTP Srv. ARM DB non-ARM APP Srv. ARM Services non-ARM Managed by which goal transaction response time partition velocity transaction response time partition velocity partition velocity pSeries LPAR 1 LPAR 2 LPAR 3 LPAR 4 HTTP Srv. ARM DB non-ARM APP Srv. ARM Services non-ARM Managed by which goal transaction response time partition velocity transaction response time partition velocity partition velocity
  • 37. Case Study 1: Un-Instrumented DataBase
    • Transactions have equal business goal and importance.
    • 3 partitions on pSeries 570 box.
    • The database is not instrumented with ARM.
    • EWLM LPAR management was not turned on initially.
    hci088_AIX hci090_AIX hci092_AIX IHS WebSphere Un-Instrumented DataBase
  • 38. Case Study 1: Without EWLM LPAR Mgmt.
  • 39. Case Study 1: EWLM LPAR Mgmt. Adjustments hci088_AIX : IHS hci090_AIX : WAS hci092_AIX : Un-Instrumented Database
    • Virtual Processor Adjustment
    • Processing Capacity Adjustment
    • Weight Adjustment
    Actions
    • EWLM manages partition capacity for un-instrumented work.
    • Improved transaction rate
    Results Before After
  • 40. Case Study 1: EWLM LPAR Mgmt. Benefits Before After
  • 41. Case Study 2: Gold vs Silver Transactions IHS WebSphere DB2 hci233_AIX hci249_AIX hci092_AIX hci222_Linux WebSphere hci220_Linux IHS
  • 42. Case Study 2: Initial setup
    • Transactions have different business importance.
    • 5 partitions on pSeries 570 box.
    • “ Gold” transactions are handled by AIX partitions. “Silver” transactions are handled by ppcLinux partitions. Common DB2 partition on AIX.
    • EWLM LPAR management was not turned on initially.
  • 43. Case Study 2: Without EWLM LPAR Mgmt.
  • 44. Case Study 2: EWLM LPAR Mgmt. Adjustments hci233_AIX : IHS. hci249_AIX : WAS hci092_AIX : DB2 Hci220_Linux: IHS hci222_Linux : WAS
    • Virtual Processor Adjustment
    • Processing Capacity Adjustment
    • Weight Adjustment
    Actions
    • Cross platform management
    • EWLM manages lower importance work too.
    • Improved transaction rate
    Results Before After
  • 45. Case Study 2: EWLM LPAR Mgmt. Benefits Before After
  • 46. How does EWLM perform load balancing?
  • 47. Domain Manager Load balancers ask the Domain Manager for recommendations (weight) using SASP Management Domain with servers of different capacity Transactions Server and Application Health and Performance Statistics Tran 6 Tran 5 Transactions Tran 8 Tran 9 Tran 10 Tran 11
    • EWLM understands:
    • End to end performance goal
    • Convoluted application and server topology
    • Hardware characteristics: CPUs, Memory, IO
    • Application performance: response time, resource utilization.
    Transaction Routing Using EWLM’s Recommendations Tran 1 Tran 2 Tran 4 Tran 3 Tran 7 IP/ Port/ Protocol IP web 6 WAS 2 Sys A (Managed Server) web 7 WAS 5 Sys B (Managed Server) web 1 WAS 4 Sys D (Managed Server) Load Balancer Application Group 1 Group 2 Load Balancer Group 3 System Group 4 web 1 DB2 3 Sys C (Managed Server) WAS 4
  • 48. EWLM Works with TIO to provision new servers and software stacks based on End to End Response Time Goals Node 2 Node 3 Node 4 Tivoli Provisioning Manager EWLM Domain Mgr via ssh Probability of Breach Node 1 Node 5 EWLM Servers for Linux Performance Data Collect EWLM Data Tivoli Intelligent Orchestrator EWLM Remote Objective Analyzer Workload Generator Load Balancer
  • 49. Advanced features provided by EWLM 2.Provides recommendations to load balancers 9. Provide statistics that indicate the amount of active versus elapsed time for work. 8. View the flow of a transaction in the topology view. 1. Adjusts processing power among partitions to ensure that performance goals that you define are met. 3. Provides recommendations to Tivoli Orchestrator (TIO) for provisioning Capability – Autonomic Management Functions EWLM 6. View the end-to-end performance of a transaction. (Hop data) 4. View the performance of all work (application-level transactions and OS processes) processed on a partition. 2. View the performance of application-level transactions . 3. View the performance of operating system processes 5. View performance of any or all work compared to a performance goal that you define. 1. View how much CPU specific work consumes Capability – Monitors and reports
  • 50. The Value of EWLM: supporting business operations
    • Enterprise Workload Manager monitors and reports on an end-to-end basis the components of service delivery:
      • Links resource delay information to the contribution of each server, LPAR, operating system or subsystem.
    • Drill down capability to each level in the service chain
    • Without EWLM
    zSeries xSeries iSeries pSeries Sun
    • The Challenges
      • Often thousands of servers in the farm
      • Integration of disparate systems management tools
      • Increasing Complexity and support costs
    • Reaction Time to Problems
    • With EWLM
    Workload 1 Workload 2 Workload 3 Workload 4 Workload 5
  • 51. The Value of EWLM : Consolidating Management and Reducing Complexity
    • Business Based Goal Characterization
      • Service Class application framework
      • Policy based goals and service definitions
    • Policy Based Autonomic Management
      • Partition management on POWER5
      • Load balancing
    • Policy Based Reporting
      • Graphical map of workflow topology
      • Relationships between application and instances
    • Single, centralized point for system management capabilities
      • Common Console View
    Management Domain Domain Manager Control Center
  • 52. Partition Group Details Report
  • 53. Where to go for more information
    • IBM Enterprise Workload Manager Red Book: SG24-6350
      • URL: http://www.redbooks.ibm.com/abstracts/sg246785.html?Open
    • EWLM Information Center:
      • URL: http://publib.boulder.ibm.com/infocenter/eserver/v1r2/index.jsp
    • Hardening the EWLM performance Data – Red paper
      • URL: http://www.redbooks.ibm.com/abstracts/redp4018.html?Open
    • EWLM interpreting control center performance reports – Red paper
      • URL : http://www.redbooks.ibm.com/abstracts/redp3963.html?Open
    • EWLM Class
      • Enterprise Workload Manager Planning and Implementation (Course Code OZ200)
  • 54. Notices
      • Produced in the United States of America, 08/04, All Rights Reserved
      • IBM, IBM eServer logo, IBM logo, e-business on demand, DB2, DB2 Connect, DB2 Universal Database, HiperSockets, Enterprise Storage Server, Performance Toolkit for VM, Tivoli, TotalStorage, VM/ESA, WebSphere, z/OS, z/VM and zSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both.
      • Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries or both.
      • UNIX is a registered trademark of The Open Group in the United States and other countries.
      • Intel is a trademark of Intel Corporation in the United States, other countries or both.
      • Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
      • Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation
      • Other company, product and service names may be trademarks or service marks of others.
      • Information concerning non-IBM products was obtained from the suppliers of their products or their published announcements. Questions on the capabilities of the non-IBM products should be addressed with the suppliers.
      • IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
      • IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.
      • All statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
  • 55. Backup Charts: EWLM Policy Constructs
  • 56. EWLM Concepts: EWLM service class
    • Defines a performance goal.
    • Each transaction, partition, or process class specifies a corresponding service class.
    • EWLM monitors the actual performance of the work against the goal in the service class.
    • Types of performance goals
      • Average response time
        • Defines how fast work should complete.
        • Example: 1 second
      • Percentile response time
        • Defines how fast a percentage of the work should complete.
        • Example: 90% complete within 1 second
      • Velocity
        • Defines how fast work should run when ready, without delays due to processor constraints, storage problems, and I/O delays (for managed system resources). Use a velocity goal for work in which response time goals are not appropriate, such as service processes, daemons, and long-running batch work.
        • Example: Fastest, Fast, Moderate, Slow, Slowest
      • Discretionary
        • Defines that the work is to complete when resources are available. No time interval and no importance. Use this for work with low priority.
  • 57. EWLM Concepts: Transaction class
    • Identifies application-level transactions.
    • Specifies a corresponding service class performance goal.
    • Uses application specific filters to identify the work such as:
      • WebSphere Application Server: Wsdlport, QueryString, EJBname, ….
      • DB2: Database Name, Application Id, Client Protocol, ….
      • Webserving plugin: HostInfo, PluginType, Port, Protocol, QueryString…
    • EWLM-supplied filters can also be used to identify the work such as:
      • EWLM: Application Instance
      • EWLM: Hostname
      • EWLM: System name
      • EWLM: OS Platform
  • 58. Transaction Class, continued List of transaction classes belonging to this application Application name
  • 59. EWLM Concepts: Process class
    • Identifies operating system processes.
      • Example operating system processes:
        • Service processes, daemons, and long-running batch work
      • Supported operating systems include the following
        • AIX, i5/OS, Linux, Windows, Solaris, HP-UX
    • Specifies a corresponding service class performance goal.
    • Uses EWLM-supplied filters to identify processes such as:
      • EWLM: Cluster name
      • EWLM: System name
      • EWLM: OS Platform
      • EWLM: OS Level
      • EWLM: Hostname
      • EWLM: Management Domain Name
  • 60. EWLM Concepts: Process class c ont’d
    • Uses platform-specific filters to identify processes
    • AIX filter types:
      • ExecutionPath
      • UserName
      • GroupName
      • WLMTag
  • 61. EWLM Concepts: Partition class
    • Identifies both operating system processes and application-level work.
    • Does not require that the applications instrument the ARM 4.0 standard APIs.
    • Does not provide granular performance data for end-to-end transactions like a transaction class does.
    • Monitors the partition as a single entity.
    • Uses EWLM-supplied filters to identify partition such as:
      • EWLM: OS Level
      • EWLM: Hostname
      • EWLM: Cluster Name
      • EWLM: Management Domain Name
  • 62. EWLM Concepts: Classification rule
    • Use in transaction, partition, and process classes to identify the work for EWLM to monitor/manage
    • Available filter types vary by application and platform.
    • Wild card (*) and mask (?) values are allowed.
  • 63. Backup Charts: EWLM Monitoring Reports
  • 64. Exception Report This will show those Service Classes that are not meeting their goals:
    • Uses “Performance Index” (PI) as gauge:
      • “ PI” greater than 1  Not meeting goal
      • “ PI” less than 1  Meeting goal
        • If less than 1, won’t show on “Exceptions”
    This provides first-level indication of where problem may exist. (Remember: Service Class may be comprised of multiple Transaction Classes)
  • 65. Performance index (PI) monitor
    • Displays the actual performance index compared to a PI of 1 .
    • Use this monitor to view the performance index as it fluctuates over time.
    • PI>1 indicates the goal is not met
    • PI=1 indicates the goal is met
    • PI<1 indicates the goal is exceeded
    Yellow line represents goal Blue line indicates actual
  • 66. Transaction rate monitor
    • Displays the number of transactions (or processes) that complete per second.
    • Use this to determine when peak workloads exist, which may directly relate to a missed performance goal.
  • 67. Application topology
    • Displays all applications in the domain that EWLM is monitoring.
  • 68. Application topology details View Average active time to determine if time allocated to each hop is appropriate. Use to determine if a hop (application instance) does not adhere to a performance goal.
  • 69. Managed Servers and Server Details It’s even possible to drill down and see statistics on the server platform itself: For all servers in the Domain