Application Runtime and CIM

Transcription

1 Application Runtime and CIM Modeling beyond today s CIM Application Model Authors: Andreas Köppel (SAP AG) andreas.koeppel@sap.com Version 1.1, June

2 Agenda Introduction SAP System Landscape Directory Runtime Model Requirements Runtime Model Concepts Conclusion

3 Applications Group Overview Major Activities Application Lifecycle Model (Deployment) Application Runtime Model Java Application Server Model Management and State Metrics

4 Status Today Software Deployment Initial model was available in CIM 2.x Major rework started by companies who will use it. Application Runtime Management Overall plan for model established Initial components in CIM 2.8 Preliminary Metrics Original work was Unit of Work Metrics Added base metrics Work in progress to expand use of metrics Java Application Server Model Initial model in CIM 2.8 preliminary (matches JSR 77)

5 Discussions Today The Runtime Application Model Andreas Köppel The App Server Model (later today) Guru Bhat

6 Lifecycle: Putting the Runtime in a Context app status sub -model deployable installable executable running transport setup installation initial life cycle runtime Inventory/Discovery = SAP System Landscape Directory (SLD)

7 Agenda Introduction SAP System Landscape Directory Runtime Model Requirements Runtime Model Concepts Conclusion

8 Inventory: Transition from Installation to Runtime System Landscape = Description of topology, components and dependencies of application systems Product and Production Management System Synchronize, XML Graphical Design Tool Applications and Tools Validation Registration Software Distribution Description Master Component Repository Component Types Landscape Patterns Possible Combinations Update System Landscape Directory Landscape description CIM Component information CIM WBEM, XML WBEM, XML Infrastructure Systems Customer SAP Systems 3 rd -Party Component Types SAP Customer

9 Installability/Upgradability Dependency Types SAP_SuccessorPredecessor SAP_IntegrationMovement SAP_ReleaseCompatibility Antecedent Antecedent * Dependent * * Dependent * same product, different versions Antecedent Antecedent * Dependent * CIM_ManagedElement {abstract} * Dependent * different products Antecedent Antecedent * Dependent * (Products, Features, Components) * Dependent * SAP_Requisite SAP_Compatibility SAP_Incompatibility SAP_ContextDependency {abstract} SAP_AssociatedContext * * Dependency Context SAP_DependencyContext constraints Name: string {key} Type: string {key}

10 Visualization with Visio (Prototype) Visualization of existing system landscapes / landscape patterns Design of landscape patterns Configuration of system landscape topology MS Visio SLD WBEM, CIM over HTTP Client Server

11 Agenda Introduction SAP System Landscape Directory Runtime Model Requirements Runtime Model Concepts Conclusion

12 Moving towards Runtime app status sub -model deployable installable executable running transport setup installation initial life cycle runtime Requirements: Architecture, Management, Manageability, Meta

13 Application Architectural Requirements Diversity requires model flexibility Stability by Design Complexity requires requires modeling abstractions as well as adhering to idiosyncrasies model to reflect distributed systems, different views and abstractions

14 Application Architecture: Views and Elements External System Scenario System Processing Elements Resource OS OS/ Host Software Service Code Component Logical Structure Lifecycle Time: shipping -> running Action Data Data Flow Application View Application Element

15 Manageability Requirements A Runtime Model must: Allow definition of the structure of complex app runtime environments including multiple apps and components/layers Support distributed and dynamic applications Relate Unit of Work information to runtime structure Link physical structures and logical runtime structures Model usage of system resources (host, network) Model dataflow between components and applications and between applications Allow monitor and control application state Support fault management

16 Requirements for a Runtime Model Application-, Service Level-, Business Process Management,... System Resource Usage, Dataflow, Report & Control State, Exhibit Faults, Managed Object & Support Classes Application Managed Objects Management Requirements Manageability Requirements Management Abstraction Model Management Objects Architectural Requirements + Views & Elements Application Views/ Elements, Diversity, Complexity,... Meta Requirements Granularity, Time-Relationship,... Sub-Model & Managed Object Class Managed Object & Support Classes

17 Agenda Introduction SAP System Landscape Directory Runtime Model Requirements Runtime Model Concepts Conclusion

18 Breaking Down the Model: Runtime Sub-Models app status sub -model executable installation running initial life cycle runtime model systems function structure data external systems history event configuration

19 Runtime Overview Overview, Monitoring Statistics, Summary, Aggre gations implements Performance metrics Status Errors Metrics per individual action Analysis External System System, Service, Resource, SWF/SWE Structure SWF/ SWE consists of Runtime Model interacts with System Application System Function Application Resource Service determines dataflow Data UoW (Action) provides performs applies Configuration Setting emits stores behavior of the past Event Indication History Metrics, Statistics Principal Management Object Class CIM Class Representing a Managed Object Support Object Class Sub-Model

20 Example: Catalog Application Webserver Presentation Layer Presentation (session handling, navigation) Business Layer Comm PlugIn Cache Business (logon, search, modify) Middleware (DB access, communication) Database Layer Database

21 Example Data MyCatalog SearchAction: CIM_UoW MySession Action: CIM_UoW MySearch Action: CIM_UoW Function MyCatalogSearch: CIM_Service MySessionHandler: CIM_Service dataflow MySearchEngine: CIM_Service dataflow MyCache: Resource System MyCatalogApp: CIM_Runtime ApplicationSystem MyPresentationTier: CIM_Runtime ApplicationSystem dataflow MyBusinessTier: CIM_Runtime ApplicationSystem Focus for V2.9 Focus for V2.8 External System ExternalWebServer: CIM_Runtime ApplicationSystem ExternalDB: CIM_Runtime ApplicationSystem

22 Model Concepts (Simplified) ApplicationSystem <<System>> System Sub-Model Parameter, Status, InnerError, InnerTimeBound, InnerAmountBound, IOError. IOTimeBound, IOAmountBound DistributedAppSystem <<System>> LocalAppSystem <<System>> Statistics CIM_Service Hosted Hosted NamedCommunication (SAP) Function Sub-Model LogicalStorage Configuration Logs Hierarchy ApplicationService <<Softw areservice>> s. document Implements Implicit: Data Flow Dependency Input/Output Resource <<Resource>> s. document Hierarchy Structure Sub-Model NamedComponents <<CodeComponents>> s. document Hierarchy Perf orms UnitOf Work <<Action>> s. document DataFlow Data Sub-Model

23 Function Sub-Model: Service Cube Application stack linked by technical dataflow (CIM_Dependency) Logical application layers linked by logical dataflow (CIM_Dependency) OS Middleware Domain/Application Layer (e.g. Presentation) Layer (e.g. Business/Domain) Layer (e.g. Database/Data Access) Overview Detail Overview Detail Overview Detail Hierarchy linked by containment (CIM_Component)

24 Example: Service Cube of Function Sub-Model Stack Layers Stack :TechnicalDataflow Representation LayerService: DependentService :LogicalDataflow Business LayerService :AntendentService :TechnicalDataflow CommunicationHandler: MiddlewareService Hierarchy LogonHandlerService: LowerLevelService CatalogSearch: LowerLevelService Hierarchy Infrastructure: MiddlewareService SessionHandlerService: LowerLevelService CatalogModification: LowerLevelService OutboundMessage Processor: LowerLevelService InboundMessage ParserService: LowerLevelService :TechnicalDataflow DBQueryOptimizer: LowerLevelService DestinationNameService: LowerLevelService

25 Function Sub-Model: Resources Characteristics Capacity (Max, Min) Only data transformation (no change, no create, no delete) Transfer of data over locus and/or time Owned by the application Types Communication (local, remote, e.g. protocol endpoint) Storage (volatile, persistent, e.g. buffer, table, pools, file) Queue

26 Data Sub-Model: Processing and UoW HostedServices Service1 Metrics Service2 Metrics Service3 Metrics Parameterized Statistics Metrics Default Aggregation Default Aggregation Default Aggregation Filter Context-Specific Aggregation Context Metrics Context Metrics Context Metrics Action Type 1 Context Metrics Context Metrics... Context Metrics Context Metrics... Context Metrics Context Metrics... Action Type 2 System Metrics Correlation & Aggregation Context Metrics Default Context Metrics Aggregation Context Metrics... Aggregated Action Type A Actions are translated to UoW They consist of metrics and context

27 Modeling FCAPS Fault Indications Error and status properties (counter, information) Log-entries, traces, etc. Performance Base metrics (IO, timebound metrics, etc.) UoW Metric properties Statistics Configuration Persistent configuration information: configuration, settings Control: methods Current configuration: object properties, support classes, associations

28 Too Complex? Design Patterns! System Sub-Model RunTime Application Model Function Sub-Model Sub-Model- Independent Design Patterns Data Sub-Model Configuration History Parameterized Statistics Tier Pattern Resource Action Distributed System Logical System Distributed Service Functional Service Dependency Cross-Process Correlation

29 Agenda Introduction SAP System Landscape Directory Runtime Model Requirements Runtime Model Concepts Conclusion

30 Applications WG Future Work CIM 2.9 Elaborate the Function sub-model Integrate UoW into RT model Extend Metric model ARM 4.0, UoW correlation, standard metrics, monitoring metrics and aggregating metrics Extend and fix application deployment Alignment of Database and AppServer to RT Integration/alignment with AQRM group (OpenGroup)

31 Additional Resources about the Runtime Model More detailed presentation Strategy working paper Design pattern working paper Semi-public: please send request to