View
218
Download
1
Tags:
Embed Size (px)
Citation preview
ASAP Release
2.0
ASAP Release
2.0
Mike MillerSoftware Architect
Nonstop Enterprise DivisionMay 18, 2002
Mike MillerSoftware Architect
Nonstop Enterprise DivisionMay 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
OverviewOverviewOverviewOverview
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/ASAP– InterNet http://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
DependenciesDependenciesDependenciesDependencies
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
Is a Relative NotionIs a Relative NotionIs a Relative NotionIs 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=10Q=0
Availability
5
Service Level ObjectivesService Level ObjectivesService Level ObjectivesService Level Objectives
Users need to define “Availability” according to their own criteria.
Notion is called - Service Level ObjectivesIf “SLO” not met... things “slow” down.
ATM Service Level Objectives - Taxi fare:– Status = Up
– Queue = 0
– Cash = $20
Availability
6
Varies with UsageVaries with UsageVaries with UsageVaries 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
Depends on ApplicationDepends on ApplicationDepends on ApplicationDepends 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
ReviewReviewReviewReview
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
Object• Status• Performance
IntroductionIntroductionIntroductionIntroduction
Objectifies• Information into
Object-State DB
Analyzes• Service Level Objectives• Determines Availability
Reports• Results
Monitors• Status• Performance
ASAPOverview
10
DOTs - Discrete Object ThresholdsDOTs - 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.0Features
11
MonitoringMonitoringMonitoringMonitoring
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
ASAPOverview
12
Object• Status• Performance
ObjectificationObjectificationObjectificationObjectification
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.
ATMWARNINGCash $150
ASAPOverview
13
AnalysisAnalysisAnalysisAnalysis
Analysis
Availability
Object• Status• Performance
ASAP Analyzes Object– Status and Performance:– Compares Service Objectives:– Determines Object Availability:
ATMCash $150
ATMWARNINGCash $150
Availability
ASAPOverview
14
ReportingReportingReportingReporting
ASAP Reports Object
– Availability Information.
– Information is Mapped to a Uniform State Model
– Visualized in the form of:TreeGraphGrid Views
– Context sensitive:Popup menus can be displayed on any object
– Analysis Includes Color synchronized Graph elements Grid elements State icons
TreeGraphGrid
ASAPOverview
15
State PropagationState PropagationState PropagationState 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
ASAPOverview
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 VectorAllows Availability Graphs/Icons
Result, Visual Display combines:Alpha, Numeric, Status, Performance, & SLOs allTogether in single uniform display
3D, Color-Coded, Graphical displayHuman mind good at patterns...Faces, Buildings, Automobiles...
Availability VectorsAvailability VectorsAvailability VectorsAvailability VectorsASAPOverview
21
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
Architectural OverviewArchitectural OverviewArchitectural OverviewArchitectural Overview
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
Right side of diagramRight side of diagram Represents Provider functionsRepresents Provider functions Including Smart Agents.Including Smart Agents.
Left side of diagram Left side of diagram Represents Consumer Functions.Represents Consumer Functions. Includes Presentation/Analysis Features.Includes Presentation/Analysis Features.
ASAPArchitecture
22
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
Smart Gathering Processes - SGPsSmart Gathering Processes - SGPsSmart Gathering Processes - SGPsSmart Gathering Processes - SGPs
ASAPServer
Collector
Smart Gathering Processes - SGPsSmart Gathering Processes - SGPs Collect Status & Performance infoCollect Status & Performance info Store Stats in ASAP history data baseStore Stats in ASAP history data base
Analysis&
ReportsGraphsGridsTrees
ASAPArchitecture
23
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
Service Level ObjectivesService Level ObjectivesService Level ObjectivesService Level Objectives
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
SGPs also provide Service Level Objectives.SGPs also provide Service Level Objectives. SGPs inform you when SLOs are not met.SGPs inform you when SLOs are not met. Tell you what objects did not meet objectives.Tell you what objects did not meet objectives. DB also provides history of failed objectives.DB also provides history of failed objectives.
ASAPArchitecture
24
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
Application Program Interface - APIApplication Program Interface - APIApplication Program Interface - APIApplication Program Interface - API
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
ASAP includes published API for application access.ASAP includes published API for application access. Allows Customer-Third Party access to infrastructure.Allows Customer-Third Party access to infrastructure. Allows you to utilize all ASAP Client/Server functions.Allows you to utilize all ASAP Client/Server functions. API is a shared-seg, high-performance, architecture.API is a shared-seg, high-performance, architecture. API calls include ASAP_Register, ASAP_Update.API calls include ASAP_Register, ASAP_Update.
ASAPArchitecture
25
ASAP API - ExampleASAP API - ExampleASAP API - ExampleASAP API - Example
ASAP_REGISTER_( domain_name : length
, segment_offset );
.
.ENDTRANSACTION;
ASAP_UPDATE_( segment_offset, error_detail
, Data_item, Value, Math );
ASAPX
SharedMemory
ASAP
ASAPDatabase
Data_item - Defined by EDL
Value - Defined by application
Math = 0 - Add Value to Data_itemMath = 1 - Assign Value to Data_item
ASAPArchitecture
26
ASAP API - BASE24 Plugin - SLO AlertsASAP API - BASE24 Plugin - SLO AlertsASAP API - BASE24 Plugin - SLO AlertsASAP API - BASE24 Plugin - SLO AlertsASAP
Architecture
27
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
API – Service Level ObjectivesAPI – Service Level ObjectivesAPI – Service Level ObjectivesAPI – Service Level Objectives
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
API also monitors Service Level Objectives for AppsAPI also monitors Service Level Objectives for Apps Informs you when Application SLOs are not met.Informs you when Application SLOs are not met. Tells what Apps did not meet objectives.Tells what Apps did not meet objectives. DB also provides history of failed App objectives.DB also provides history of failed App objectives.
ASAPArchitecture
28
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
Data BaseData BaseData BaseData Base
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
ASAP DB contains normalized object info.ASAP DB contains normalized object info. DB history is automatically maintained.DB history is automatically maintained. Includes Object, State, Performance, & Service ObjectivesIncludes Object, State, Performance, & Service Objectives DB Schema published in TIM, and DDL is on CD.DB Schema published in TIM, and DDL is on CD. Allows Customer & Third Party DB access.Allows Customer & Third Party DB access.
ASAPArchitecture
29
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
ASAP ClientASAP ClientASAP ClientASAP Client
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
Asap Client provides analysis & presentation functions. Asap Client provides analysis & presentation functions. Allows viewing of Availability, Performance, and SLOs.Allows viewing of Availability, Performance, and SLOs. Uses standard Windows visualization paradigm.Uses standard Windows visualization paradigm.
ASAPArchitecture
30
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
Client as Analysis ToolClient as Analysis ToolClient as Analysis ToolClient as Analysis Tool
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
Client displays analysis using Graph, Grid, Tree, & Report Windows.Client displays analysis using Graph, Grid, Tree, & Report Windows. Users can select their own sets of Entities, Objects, and Properties.Users can select their own sets of Entities, Objects, and Properties. Users can also specify their own sets of State Propagation Rules.Users can also specify their own sets of State Propagation Rules. All graphical objects automatically update in real-time.All graphical objects automatically update in real-time.
ASAPArchitecture
31
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
Client as Object-State ProviderClient as Object-State ProviderClient as Object-State ProviderClient as Object-State Provider
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
ASAP can also act as an Object-State Provider.ASAP can also act as an Object-State Provider. Utilizes the OEM Gateway to export Object-State information to EMFs.Utilizes the OEM Gateway to export Object-State information to EMFs. OEM also provides Alert Windows, with sorted highest-to-lowest state views.OEM also provides Alert Windows, with sorted highest-to-lowest state views. OEM acts as a multi-ported, bi-directional, Enterprise-Management Gateway OEM acts as a multi-ported, bi-directional, Enterprise-Management Gateway
ASAPArchitecture
32
Workstation Local Node Remote Nodes
Enterprise ManagementFramework
...
?Adapter
Enterprise ManagementFramework
Y
YAdapter
Enterprise ManagementFramework
X
XAdapter
Object IntegrationLayer
OIL
OILAdapter
OEM
ASAPDatabase
AppCpuDisk
ExpandProcess
…
AlertsWindow
Open EnterpriseManagement
Gateway
ASAP Client ASAP Server
ASAPClient
ASAPX...…
...
...
Enterprise Objects
ASAP...…
...
Enterprise Objects
ASAPExtension
...
...API
Enterprise Objects
ASAPServer
CpuDisk
ProcessExpand
OEM Gateway to EMFsOEM Gateway to EMFsOEM Gateway to EMFsOEM Gateway to EMFs
ASAPServer
Collector
Analysis&
ReportsGraphsGridsTrees
OEM Provides API to EMFs via AdaptersOEM Provides API to EMFs via Adapters Adapters handle Framework specific APIsAdapters handle Framework specific APIs Leverages Enterprise Framework ExpertiseLeverages Enterprise Framework Expertise Allows integration with different FrameworksAllows integration with different Frameworks
Simplifies Client/Agent API InterfaceSimplifies Client/Agent API Interface Minimizes impact on ApplicationsMinimizes impact on Applications Application-Agent Interface coded onceApplication-Agent Interface coded once Handles Client Object-State arbitrationHandles Client Object-State arbitration
OEMArchitecture
34
OEM Alerts View (No EMF)OEM Alerts View (No EMF)OEM Alerts View (No EMF)OEM Alerts View (No EMF)OEMArchitecture
35
OEM Multiple Alert views::OEM Multiple Alert views::OEM Multiple Alert views::OEM Multiple Alert views::
\Chicago Alerts Sorted
All Node Alerts Sorted & Filtered
OEMArchitecture
36
OEM Custom AdaptersOEM Custom AdaptersOEM Custom AdaptersOEM Custom Adapters
Custom Adapter – LeftCustom Adapter – Left OEM Alerts View - RightOEM Alerts View - Right
OEM Sends Object-StatesOEM Sends Object-States- Adapter Displays Updates:- Adapter Displays Updates:- Clicks callback Oem:- Clicks callback Oem:
OEM Options Dialog:OEM Options Dialog:- Allows you to add Adapter- Allows you to add Adapter
OEMArchitecture
37
OEM EMF Adapter Interface::OEM EMF Adapter Interface::OEM EMF Adapter Interface::OEM EMF Adapter Interface::OEMArchitecture
41
ASAP Release 2.0 – New FeaturesASAP Release 2.0 – New FeaturesASAP Release 2.0 – New FeaturesASAP 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.0Features
42
Multi-Entity AppsMulti-Entity AppsMulti-Entity AppsMulti-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.0Features
43
New EntitiesNew EntitiesNew EntitiesNew Entities
AppCpuDiskExpandProcessSystem
ASAP 1.0: Multi-Entity ApplicationsMulti-Entity Applications CpuCpu DiskDisk ExpandExpand FileFile Process SelectedProcess Selected Process BusyProcess Busy RDF 1.3RDF 1.3 SpoolerSpooler TapeTape TMFTMF SystemSystem
ASAP 2.0
ASAP 2.0Features
44
DB EnhancementsDB EnhancementsDB EnhancementsDB 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.0Features
46
Icons & ColorsIcons & ColorsIcons & ColorsIcons & Colors
Release 1.0 - Fixed set of Icons & Alert ColorsRelease 2.0 - Allows User Defined Icons & Colors
– Custom State Icons – Custom Alert Colors– Address Internationalization
ASAP 2.0Features
47
OSC MonitorOSC MonitorOSC MonitorOSC 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.0Features
48
OSC ViewOSC ViewOSC ViewOSC 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 instantanalysis of state changes.
Example… Click “15” in Matrix Locates all “Critical-Cpu”changes in log.
ASAP 2.0Features
49
OSC Analysis FunctionsOSC Analysis FunctionsOSC Analysis FunctionsOSC Analysis FunctionsASAP 2.0Features
50
DOTs - Discrete Object ThresholdsDOTs - 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.0Features
51
EMS EventsEMS EventsEMS EventsEMS Events
Discrete Object Thresholds - Availability Events– EMS Events now optionally Logged
when DOTs objectives are not met.
– Event Generation Options includeINFOCRITICALREPEATDISPLAY
Burst Suppression on EMS events:– Eliminates Event Avalanches
– Includes Burst Summary Reports
ASAP 2.0Features
52
EDL OverviewEDL OverviewEDL OverviewEDL 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.0Features
53
EDL RequirementsEDL RequirementsEDL RequirementsEDL 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.0Features
54
EDL ContainersEDL ContainersEDL ContainersEDL 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.0Features
55
EDL FeaturesEDL FeaturesEDL FeaturesEDL 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.0Features
56
EDL SummaryEDL SummaryEDL SummaryEDL 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.0Features
57
Availability SummaryAvailability Summary
Definition of Availability is subjective. It depends on how you intend to use object.
Studies indicate if you monitor AvailabilityActual 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
Feature SummaryFeature Summary
ASAP 2.0 - Uniformly Extends Features to overall ASAP infrastructure
Allows concurrent Customer & 3rd 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.0Summary