1. ASAP Release 2.0 Mike Miller Software Architect Nonstop Enterprise Division May 18, 2002 Mike Miller Software Architect Nonstop Enterprise Division May 18, 2002 ASAP Overview Architecture New Features DOTs EDL Presentation contains animation sequences that are best viewed in slide show mode. A colon character at the end of a slide bullet indicates when to click the mouse button to advance animation:

2. 2 OverviewOverview  Presentation Provides Overview of –Availability Monitoring Concepts –ASAP Features, its Architecture –Release 2.0 Functions  ASAP Resources –White Paper & Migration Guide on TUT CD –Manuals on TIM Independent Products CD –IntraNet http://spg.web.tandem.com/ASAPhttp://spg.web.tandem.com/ASAP –InterNet http://nonstop.compaq.com/view.asp?PAGE=OpsMgmt_ASAPhttp://nonstop.compaq.com/view.asp?PAGE=OpsMgmt_ASAP  Before discussing ASAP –It’s important to understand, Why Monitor Availability? –It’s because monitoring increases actual Availability. –To understand why, first discuss Availability concepts. Contents

3. 3 DependenciesDependencies  Scenario - Person needs Taxi –Has No Cash... so needs ATM –Assumes ATM will be Available: –Availability has many dependencies: Right Card.. Valid Pin.. Remember Pin.. No Line.. Atm Up.. Network Up.. Routers Up.. Server Up.. Application running.. Account valid.. Balance OK.. Atm $ ? Card? Up? Line? Pin? Network? Availability

4. 4 Is a Relative Notion  Scenario - Person in hurry - Has 2 minutes to catch Taxi –If there is a long line, for example Q=10: –Even though ATM is Operational –For User at end of the line: –ATM is NOT Available Q=10 Q=0 Availability

5. 5 Service Level Objectives  Users need to define “Availability” according to their own criteria.  Notion is called - Service Level Objectives If “SLO” not met... things “slow” down.  ATM Service Level Objectives - Taxi fare: –Status = Up –Queue = 0 –Cash = $20 Availability

6. 6 Varies with Usage  User definition of “Availability” varies with usage.  Definition of ATM “Availability” is different for $20 Taxi fare versus $300 Air fare  Goal ATM: –Status = Up –Queue = 0 –Cash = $20 Availability

7. 7 Depends on Application  Availability depends on how you intend to use object.  Users define “Availability” based on their own criteria.  Goal ATM – Air Fare:: –Status = Up –Queue = 0 –Cash = $300 What if Air Fare were $800? Would ATM be available? Not dependent on Hardware. Availability

8. 8 ReviewReview  Availability –Has many Dependencies –Is a relative Notion –Depends on Usage or Application –Can be defined with Service Level Objectives  To provide true High Availability Enterprise –Cannot just Monitor Hardware & Operating System –But must also Monitor Availability of Application Domains –External Monitoring inadequate; Apps Hang, Loop, Deadlock –External Monitoring can’t know about internal domains & values  If Application Domain Service Levels are not monitored, it’s impossible to know when Application Domains are unavailable. Availability

9. 9 Object Status Performance IntroductionIntroduction Objectifies Information into Object-State DB Analyzes Service Level Objectives Determines Availability Reports Results Monitors Status Performance ASAP Overview

10. 10 DOTs - Discrete Object Thresholds  ASAP DOTs – Allow Discrete Object Thresholds: –Rank Atm Zeist\North, Cash > 5000, BadPins < 5 –Rank Process $MyApp, PCpu=0, Priority=150 –Rank Cpu 7, Busy < 60, Queue < 1.5, Swaps < 6 –Rank File $Data.Master.Accounts, Full < 80 Critical –Rank Disk $Data, Busy < 40 Info, Full < 90 Critical  Allow Dynamic Inclusion-Exclusion of Domains –Monitor Disk $Data1, ON –Monitor Disk $Data2, OFF –Monitor File $Data.Master.Accounts, ON –Monitor Process $Test, OFF ASAP 2.0 Features

11. 11 MonitoringMonitoring  ASAP Monitors the Status and Performance of System objects and Application domains  Status refers to –Qualitative Attributes, such as Up, Down, Warning...  Performance refers to –Quantitative Attributes, such as Busy, Queue, Rate,...  System Objects are –Subsystems or components, such as File, Process, Rdf, Tmf, …  Application Domains are –Abstract Domains of Service, such as Accounts\Payable, Funds, Sales,... Object Status Performance ASAP Overview

12. 12 Object Status Performance ObjectificationObjectification  ASAP Objectifies: –Status and performance information into normalized object-state data base  Objectification provides basis: –For Analysis and Visualization of whether objects meet their Service Level Objectives. ATM WARNING Cash $150 ASAP Overview

13. 13 AnalysisAnalysis Analysis Availability Object Status Performance  ASAP Analyzes Object –Status and Performance: –Compares Service Objectives: –Determines Object Availability: ATM Cash $150 ATM WARNING Cash $150 Availability ASAP Overview

14. 14 ReportingReporting  ASAP Reports Object –Availability Information. –Information is Mapped to a Uniform State Model –Visualized in the form of:  Tree  Graph  Grid Views – Context sensitive:  Popup menus can be displayed on any object – Analysis Includes  Color synchronized  Graph elements  Grid elements  State icons Tree Graph Grid ASAP Overview

15. 15 State Propagation  ASAP Provides a Uniform –Browsing paradigm for access to objects  Tree View –Allows object navigation –Access to many objects –Drives Graph/Grid views  State Information: –Propagated upward in tree –Provides guide to state of nodes, entities, and objects –State info always visible even if tree is collapsed: Example - Newyork ASAP Overview

16. 16  Easy to assume ASAP just  Graphs Data & Colors Elements.  Easy to Underestimate Content.  Includes Analysis Engine.  Determines Availability  Based on user defined rules.  Each Property=Availability Vector  Allows Availability Graphs/Icons  Result, Visual Display combines:  Alpha, Numeric, Status,  Performance, & SLOs all  Together in single uniform display  3D, Color-Coded, Graphical display  Human mind good at patterns...  Faces, Buildings, Automobiles... Availability Vectors ASAP Overview

17. 17 State Determination ASAP determines the state of Objects and their attributes Based on User Defined Rules ASAP Determines Object States. Propagates States to Graphical Interface Forwards States to OEM & EMFs ASAP Overview

18. 18 State Filtering ASAP Provides State Filtering to Help Manage Object Alerts State Filtering Allows objects with ‘High’er alert levels to be displayed ASAP Overview

19. 19 Report Windows  Context Sensitive Popups  Allow Reports on: –Object Details –Object History –Related Disks –Related Expand Lines –Related Processes –Related Objectives  Example –Busiest Processes Report –Busiest Process History –Reports Update in Real-time ASAP Overview

20. 20 Graph Windows  Graph Windows  Provide additional views  Update in real-time  Support Context Sensitive Popups ASAP Overview

21. 21 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand Architectural Overview ASAP Server Collector Analysis & Reports Graphs Grids Trees  Right side of diagram  Represents Provider functions  Including Smart Agents.  Left side of diagram  Represents Consumer Functions.  Includes Presentation/Analysis Features. ASAP Architecture

22. 22 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand Smart Gathering Processes - SGPs ASAP Server Collector  Smart Gathering Processes - SGPs  Collect Status & Performance info  Store Stats in ASAP history data base Analysis & Reports Graphs Grids Trees ASAP Architecture

23. 23 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand Service Level Objectives ASAP Server Collector Analysis & Reports Graphs Grids Trees  SGPs also provide Service Level Objectives.  SGPs inform you when SLOs are not met.  Tell you what objects did not meet objectives.  DB also provides history of failed objectives. ASAP Architecture

24. 24 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand Application Program Interface - API ASAP Server Collector Analysis & Reports Graphs Grids Trees  ASAP includes published API for application access.  Allows Customer-Third Party access to infrastructure.  Allows you to utilize all ASAP Client/Server functions.  API is a shared-seg, high-performance, architecture.  API calls include ASAP_Register, ASAP_Update. ASAP Architecture

25. 25 ASAP API - Example ASAP_REGISTER_( domain_name : length, segment_offset );. ENDTRANSACTION; ASAP_UPDATE_( segment_offset, error_detail, Data_item, Value, Math ); ASAPX Shared Memory ASAP ASAP Database Data_item - Defined by EDL Value - Defined by application Math = 0 - Add Value to Data_item Math = 1 - Assign Value to Data_item ASAP Architecture

26. 26 ASAP API - BASE24 Plugin - SLO Alerts ASAP Architecture

27. 27 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand API – Service Level Objectives ASAP Server Collector Analysis & Reports Graphs Grids Trees  API also monitors Service Level Objectives for Apps  Informs you when Application SLOs are not met.  Tells what Apps did not meet objectives.  DB also provides history of failed App objectives. ASAP Architecture

28. 28 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand Data Base ASAP Server Collector Analysis & Reports Graphs Grids Trees  ASAP DB contains normalized object info.  DB history is automatically maintained.  Includes Object, State, Performance, & Service Objectives  DB Schema published in TIM, and DDL is on CD.  Allows Customer & Third Party DB access. ASAP Architecture

29. 29 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand ASAP Client ASAP Server Collector Analysis & Reports Graphs Grids Trees  Asap Client provides analysis & presentation functions.  Allows viewing of Availability, Performance, and SLOs.  Uses standard Windows visualization paradigm. ASAP Architecture

30. 30 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand Client as Analysis Tool ASAP Server Collector Analysis & Reports Graphs Grids Trees  Client displays analysis using Graph, Grid, Tree, & Report Windows.  Users can select their own sets of Entities, Objects, and Properties.  Users can also specify their own sets of State Propagation Rules.  All graphical objects automatically update in real-time. ASAP Architecture

31. 31 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand Client as Object-State Provider ASAP Server Collector Analysis & Reports Graphs Grids Trees  ASAP can also act as an Object-State Provider.  Utilizes the OEM Gateway to export Object-State information to EMFs.  OEM also provides Alert Windows, with sorted highest-to-lowest state views.  OEM acts as a multi-ported, bi-directional, Enterprise-Management Gateway ASAP Architecture

32. 32 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand OEM Gateway to EMFs ASAP Server Collector Analysis & Reports Graphs Grids Trees  OEM Provides API to EMFs via Adapters  Adapters handle Framework specific APIs  Leverages Enterprise Framework Expertise  Allows integration with different Frameworks  Simplifies Client/Agent API Interface  Minimizes impact on Applications  Application-Agent Interface coded once  Handles Client Object-State arbitration OEM Architecture

33. 33 WorkstationLocal NodeRemote Nodes Enterprise Management Framework... ? Adapter Enterprise Management Framework Y Y Adapter Enterprise Management Framework X X Adapter Object Integration Layer OIL Adapter OEM ASAP Database App Cpu Disk Expand Process … Alerts Window Open Enterprise Management Gateway ASAP ClientASAP Server ASAP Client ASAPX... … Enterprise Objects ASAP... … Enterprise Objects ASAP Extension... API Enterprise Objects ASAP Server Cpu Disk Process Expand OEM Alerts ASAP Server Collector Analysis & Reports Graphs Grids Trees  Review of Architectural elements  SGPs gather statistics & store in ASAP DB:  ASAP Client analyzes and visualizes info:  ASAP Client Forwards object-state  To OEM Gateway:  OEM Gateway provides sorted Listview:  OEM Sends info  To Adapter interface:  Such as OIL adapter: OEM Architecture

34. 34 OEM Alerts View (No EMF) OEM Architecture

35. 35 OEM Multiple Alert views:: \Chicago Alerts Sorted All Node Alerts Sorted & Filtered OEM Architecture

36. 36 OEM Custom Adapters  Custom Adapter – Left  OEM Alerts View - Right  OEM Sends Object-States - Adapter Displays Updates: - Clicks callback Oem:  OEM Options Dialog: - Allows you to add Adapter OEM Architecture

37. 37 OEM EMF Adapter Interface:: OEM Architecture

38. 38 Server - Functions  SGPs - Smart Gathering Process Agents –Collect Status, Performance, and Availability info –Store statistics in history data base.  Server also provides Service Level Objectives on Entities and logs EMS events when SLOs are not met. SLOs tell you: –What Applications did not meet their service level objectives? –What Applications did not meet their objectives at 2AM this morning?  API provides Customer & Third Party access to AsapX-API, a high-performance, shared-segment, collection infrastructure. –ASAP_Register.. –ASAP_Update.. Architecture Summary

39. 39 Data Base – Functions  ASAP Relational DB provides History of Objects, States, Performance, and SLOs  Data Base Automatically maintained.  Schema published in TIM and as DDL on CD  Published DDL allows Ad Hoc DB Queries  Provides Customer/Third Party DB access Architecture Summary

40. 40 Client - Functions  Client provides visual integration of Availability, Performance, and Service Level Objectives. –Provides Graphical views via Tree, Graph, Grid, and Report windows – with real-time updates. –User can define their own sets of Entities, Properties, and State Propagation Rules for Client analysis. –Client can optionally act as Object-State provider to enterprise management frameworks, or other consumers. –Provides Application & Third Party access to Object-States via high-performance, Open-Enterprise-Management API. Architecture Summary

41. 41 ASAP Release 2.0 – New Features  Release 1.0 - Focus was on “infrastructure”: –Server-Side API access –Data Base File access –Client-Side API access  Release 2.0 - Focus is on “extensibility”: –Uniformly Extend features to infrastructure –Multi-Entity for Applications –New System Entities –Custom Icons and Colors –Object State Change Monitor –Discrete Object Thresholds –New EMS Availability Events –Extensible Entity Definition Language ASAP 2.0 Features

42. 42 Multi-Entity Apps  Support for Multi-Entity Applications –Release 1.0 supported multiple applications  But one record layout was permitted for all.  Metrics were forced into single record model.  Restrictive, and could lead to Nonhomogeneous data. –Release 2.0 allows separate App entity definitions:  Allows multiple Stats record definitions.  Allows different entity-attribute names.  Allows different service level objectives.  Allows disjoint Applications & Third Parties.  Allows user inclusion/exclusion of App entities. ASAP 2.0 Features

43. 43 New Entities  App  Cpu  Disk  Expand  Process  System ASAP 1.0:  Multi-Entity Applications  Cpu  Disk  Expand  File  Process Selected  Process Busy  RDF 1.3  Spooler  Tape  TMF  System ASAP 2.0 ASAP 2.0 Features

44. 44 DB Enhancements  Release 2.0 Data Base Enhancements –Six New System Entity Tables –New Service Level Objectives Data Base –Support for Multi-Entity Applications –Support for Format 2 (Big) Files –Maximum Number of Extents now Configurable –Primary/Secondary Extent size now Configurable –Data Base can now be Partitioned –Partitioning on System and/or Domain name ASAP 2.0 Features

45. 45 DB Partitioning  Release 2.0 Data Base Enhancements –SET DB $DATA00.ASAPDB.DB –SET PART APP ALL PRIEXT 1024, SECEXT 1024, MAXEXT 900 –SET PART APP 1 SYSNO 205, KEY "ATM\EASTERN\$T422",VOLUME $D0116 –SET PART APP 2 SYSNO 205, KEY "ATM\EASTERN\$TD21",VOLUME $D0118 –SET PART APP 3 SYSNO 205, KEY "ATM\LONGNAME",VOLUME $D0212 –SET PART APP 4 SYSNO 205, KEY "ATM\NORTHERN\$T715“,VOLUME $D0213 –SET PART APP 5 SYSNO 205, KEY "ATM\SOUTHERN\$T917“,VOLUME $D0215 –SET PART APP 6 SYSNO 205, KEY "ATM\WESTERN\$T444",VOLUME $D0313 –SET PART APP 7 SYSNO 205, KEY "ATM\WESTERN\$TB25",VOLUME $D0316 –SET PART APP 8 SYSNO 205, KEY "FUNDS\BOOZER\$T932“,VOLUME $D0412 –SET PART APP 9 SYSNO 205, KEY "FUNDS\PAYABLE\$T163“,VOLUME $D0414 –SET PART APP 10 SYSNO 205, KEY "FUNDS\PAYABLE\$T862“,VOLUME $D0511 –SET PART APP 11 SYSNO 205, KEY "FUNDS\PAYABLE\$TF50“,VOLUME $D0513 –SET PART APP 12 SYSNO 205, KEY "FUNDS\PAYMNT\$T960",VOLUME $D0516 –SET PART APP 13 SYSNO 205, KEY "FUNDS\RECEIPT\$T648“,VOLUME $D0517 –SET PART APP 14 SYSNO 205, KEY "FUNDS\RECEIVE\$T000“,VOLUME $D0611 –SET PART APP 15 SYSNO 205, KEY "FUNDS\RECEIVE\$T833“,VOLUME $D0614 ASAP 2.0 Features

46. 46 Icons & Colors  Release 1.0 - Fixed set of Icons & Alert Colors  Release 2.0 - Allows User Defined Icons & Colors –Custom State Icons –Custom Alert Colors –Address Internationalization ASAP 2.0 Features

47. 47 OSC Monitor  Release 2.0 – includes Object State Change Monitor –Tells you “What has Occurred” if ASAP is left unattended –Provides History of Object State Changes –Allows you to “Reach Back” in time  OSC View Includes –New State –Previous State –Date…Time of change –Reason for state change –Object or Domain affected by change –Functions to provide state change details ASAP 2.0 Features

48. 48 OSC View  Displays History of Object State Changes based on user criteria.  Provides Dual View:  Log – State Change log –Detailed History of state changes –Allows Monitoring of history & trends  Matrix – High-Level Summary –Summarizes Object-State Changes –Hyper-Matrix provides instant analysis of state changes.  Example… Click “15” in Matrix Locates all “Critical-Cpu” changes in log. ASAP 2.0 Features

49. 49 OSC Analysis Functions ASAP 2.0 Features

50. 50 DOTs - Discrete Object Thresholds  ASAP DOTs – Allow Discrete Object Thresholds: –Rank Atm Zeist\North, Cash > 5000, BadPins < 5 –Rank Process $MyApp, PCpu=0, Priority=150 –Rank Cpu 7, Busy < 60, Queue < 1.5, Swaps < 6 –Rank File $Data.Master.Accounts, Full < 80 Critical –Rank Disk $Data, Busy < 40 Info, Full < 90 Critical  Allow Dynamic Inclusion-Exclusion of Domains –Monitor Disk $Data1, ON –Monitor Disk $Data2, OFF –Monitor File $Data.Master.Accounts, ON –Monitor Process $Test, OFF ASAP 2.0 Features

51. 51 EMS Events  Discrete Object Thresholds - Availability Events –EMS Events now optionally Logged when DOTs objectives are not met. –Event Generation Options include  INFO  CRITICAL  REPEAT  DISPLAY  Burst Suppression on EMS events: –Eliminates Event Avalanches –Includes Burst Summary Reports ASAP 2.0 Features

52. 52 EDL Overview  ASAP R2 Requirements…  Needed to allow extensible Entity Definitions –Allow Customers to define different Application Entities. –Allow Third Parties & EMFs access to Application Entities.  Needed to provide an entity-attribute Name-Space –Allow DOTs to use entity-attribute Names, instead of metric id#s. –Allow users to customize entity-attribute Names (internationalization)  Needed to reduce Maintenance –Provide Version Independent code (R2 Client run against R1 Server) –Reduce Source Code maintenance (Add new Entity w/o code change) ASAP 2.0 Features

53. 53 EDL Requirements  Needed to Externalize Definition & Customization of –Entity Names –Attribute Names –Help Text –Heading Text –Availability Vectors –Data Integrity Checks –State Determination Rules –Graph Normalization Values –Data Formatting & Alignment –Command required to retrieve data –… –and any other ASAP property that is related to Entity-Attribute definitions. ASAP 2.0 Features

54. 54 EDL Containers  Result - Entity Definition Language (EDL) File  EDL File provides “Container” for ASAP properties  EDL File allows ASAP properties to be “Portable”. –Provides Portable encapsulation of ASAP Properties. –Entities, attributes, and data can be “moved around”. –You can save/share different ASAP environments. –Client registers the.EDL extension with Windows.  EDL also allows DATA to be included in an EDL File. –Allows Data to be associated with Entity-Attribute definitions. –Entities, Attributes, & Data are encapsulated all together ASAP 2.0 Features

55. 55 EDL Features  EDL allows encapsulation of entire ASAP environment.  EDL Provides a way to –Have different sets of customized ASAP settings. –Save your current environment for later reference. –Mail your entire ASAP environment (with data) to others. –Share observed behavior with other ASAP users.  EDL also useful for –Problem Reporting - Capture entire environment. –Prototyping – Entity, Attribute, Data definitions. –Version Independence - due to encapsulation. –Education – Demo features of environment. –QA/Testing - Reproducing test scenarios. ASAP 2.0 Features

56. 56 EDL Summary  EDL Defines how Application Entities and Attributes relate to ASAP features, functions, and infrastructure.  Developers use EDL to define how to Monitor Availability  EDL is not something that ASAP users –Need to see, –Understand, –Or even be aware of… ASAP 2.0 Features

57. 57 Availability Summary  Definition of Availability is subjective. It depends on how you intend to use object.  Studies indicate if you monitor Availability Actual object Availability is increased...  If Application Service Levels are not monitored, you will not know when Applications become unavailable.  ASAP provides both Availability monitoring, and Service-Level Objectives monitoring. ASAP 2.0 Summary

58. 58 Feature Summary  ASAP 2.0 - Uniformly Extends Features to overall ASAP infrastructure  Allows concurrent Customer & 3 rd party access - Multi-Entity Apps  Adds Subsystem Monitoring - RDF,File,Process,Spooler,TMF,...  Adds Service-Level-Objectives – For both new & old entities  Adds Service-Level Events - Satisfying EMS Requirements  Adds Custom Icons, Colors, & Namespace - Internationalization  Adds Object State Change View – Allows reaching-back in time  Permits External Entity definitions - Entity Definition Language  Shifts Focus from that of system monitoring Point-Product to an Availability Monitoring Infrastructure for Subsystems and Applications. ASAP 2.0 Summary