Our society increasingly depends on computer-based systems; the number of applications deployed has increased dramatically in recent years and this trend is accelerating. Many of these applications are expected to provide their services continuously. The Service Availability Forum has recognized this need and developed a set of specifications to help software designers and developers tofocus on the value added function of applications, leaving the availability management functions for the middleware.A practical and informative reference for the Service Availability Forum specifications, this book gives a cohesive explanation of the founding principles, motivation behind the design of the specifications, and the solutions, usage scenarios and limitations that a final system may have. Avoiding complex mathematical explanations, the book takes a pragmatic approach by discussing issues that are as close as possible to the daily software design/development by practitioners, and yet at a level that still takes in the overall picture. As a result, practitioners will be able to usethe specifications as intended.Takes a practical approach, giving guidance onthe use of the specifications to explain the architecture, redundancy models and dependencies of the Service Availability (SA) Forum servicesExplains how service availability provides fault tolerance at the service levelClarifies howthe SA Forum solution is supported by open source implementations of the middlewareIncludes fragments of code, simple example and use cases to give readersa practical understanding of the topicProvides a stepping stone for applications and system designers, developers and advanced students to help them understand and use the specifications INDICE: List of Contributors xiiiForeword xvPreface xixAcknowledgments xxvList of Abbreviations xxviiPart I INTRODUCTION TO SERVICE AVAILABILITY1 Definitions, Concepts, and Principles 3Francis Tam1.1 Introduction 31.2 Why Service Availability? 41.2.1 Dossier on Unavailability of Service 41.2.2 Issues and Challenges 51.3 Service Availability Fundamentals 61.3.1 System, Behavior, and Service 61.3.2 Dependable Computing Concepts 81.3.3 The Meaning of Availability101.4 Achieving Service Availability 131.4.1 Following the Framework of FaultTolerance 131.4.2 Redundancy is a Requisite 141.4.3 Dealing with Failures 161.4.4 Upgrade Matters 191.5 Conclusion 202 The Birth of the Service Availability Forum 23Francis Tam2.1 Introduction 232.2 Technology Environment 232.3 Business Environment 242.3.1 Ecosystem 252.3.2 COTS and Open Systems 262.4 The Service Availability Forum Era 272.5 Concluding Remarks 28Part II THE SA FORUM SYSTEM: SERVICES AND FRAMEWORKS3 Overview of the Service Availability Architecture 33Dave Penkler3.1 Introduction 333.1.1 Background and Business Context 333.1.2 Goals and Requirements 343.1.3 Service Availability Architecture Scope and Presentation 363.2 HA Concepts Applied 393.2.1 To Be or Not to Be High Availability Aware 393.2.2 HA Aware Application Perspective 423.3 Architecture 433.3.1 Basic Architectural Model 433.3.2 The AIS Services and Frameworks Architecture 473.3.3 Service Dependencies 583.4 Open Issues 593.4.1 The Optional Features Issue 603.4.2 Integrated AIS Service API 603.4.3 Common Low Level Communication Facility Interface 603.4.4 Common Distributed Process Management Interface613.4.5 System Trace Service 613.4.6 Diagnostics Framework 613.4.7 Overload Control Framework 613.5 Conclusion 624 The SA Forum Information Model: The Heart of Control and Monitoring 63Maria Toeroe4.1 Introduction 634.2 Background 644.2.1 Management Models Out There 644.2.2 The SA Forum Needs 654.3 The SA Forum Information Model 674.3.1 Overview of the SA Forum Solution 674.3.2 Administrative and Management Aspects 804.3.3 Application Information Models 814.3.4 Open Issues and Recommendations 814.4 Conclusion 835 Consistent and High Level Platform View 85Maria Toeroe5.1 Introduction 855.2 Hardware Platform Interface865.2.1 Background 865.2.2 Overview of the Hardware Platform Interface 875.2.3 The HPI Model 885.2.4 HPI Capability Discovery 935.2.5 Error Handling and Administrative Operations 945.2.6 Open Issues and Conclusions 955.3 Platform Management Service 965.3.1 The Conception of PLM 965.3.2 Overview of the SA ForumPlatform Management 975.3.3 The PLM Information Model 985.3.4 Tracking of PLMEntities 1075.3.5 Administrative and Management Aspects 1105.3.6 Service Interaction 1185.3.7 Open Issues and Conclusions 1205.4 Cluster Membership Service1215.4.1 Background 1215.4.2 Overview of the Cluster Membership Service 1225.4.3 CLM Configuration: The Bootstrap Trap 1255.4.4 Are You a Member? 1265.4.5 Administrative and Management Aspects 1275.4.6 Service Interaction 1295.4.7 Open Issues 1305.4.8 Recommendation 1315.5 Conclusion 1316 Model Based Availability Management: The Availability Management Framework 133Maria Toeroe6.1 Introduction 1336.2 Background 1346.2.1 Error Detection and Repair 1346.2.2 Fault Zones and Error Escalation 1356.2.3 Separation of Services from Serving Entities 1366.2.4 Service Provisioning Roles 1366.2.5 Delicacies of Service State Replication 1376.3 The Availability Management Framework 1386.3.1 Overview of theSA Forum Solution 1386.3.2 Components and Component Service Instances 1396.3.3 The AMF Information Model 1486.3.4 Redundancy Models 1676.3.5 The AMF Administrative Interface 1766.3.6 Interactions Between AMF and Other AIS Services 1876.3.7 Open Issues 1906.3.8 Recommendation 1916.4 Conclusion 1917 Communication and Synchronization Utilities 193Maria Toeroe and Sayandeb Saha7.1 Introduction 1937.2 Event Service 1947.2.1 Background: Event Service Issues, Controversies, and Problems 1947.2.2 Overview of the SA Forum Event Service 1957.2.3 Event Service Architecture and Model 1967.2.4 User Perspective 2007.2.5 Administrative and Management Aspects 2017.2.6 Service Interactions 2017.2.7 Open Issues and Recommendations 2027.3 Message Service 2027.3.1 Need for Reliability andLoad Distribution 2027.3.2 Overview of the SA Forum Message Service 2037.3.3 Message Service Architecture and Model 2057.3.4 User Perspective 2077.3.5 Administrative and Management Aspects 2107.3.6 Service Interaction 2107.3.7 Open Issues and Recommendations 2117.4 Checkpoint Service 2127.4.1 Background: Why Checkpoints 2127.4.2 Overview of the SA Forum Checkpoint Service 2137.4.3 Checkpoint Service Model 2157.4.4 User Perspective 2177.4.5 Administrative and Management Aspects 2207.4.6 Service Interaction 2217.4.7 Open Issues 2227.4.8 Recommendation 2227.5 Conclusion 2237.5.1 Common Issue: Entity Names 2237.5.2 Conclusion 2238 Services Needed for System Management 227Maria Toeroe8.1 Introduction 2278.2 Log Service 2288.2.1 Background: Data, Data, and More Data 2288.2.2Overview of the SA Forum Solution 2298.2.3 The LOG Information Model 2318.2.4User Perspective 2328.2.5 Administrative and Management Aspects 2338.2.6 Service Interaction 2338.2.7 Open Issues and Recommendations 2358.3 Notification Service 2368.3.1 Background: Issues, Controversies, and Problems 2368.3.2 Overview of the SA Forum Notification Service 2378.3.3 User Perspective 2398.3.4 Correlation of Notifications 2418.3.5 Administrative and Management Aspects 2438.3.6 Service Interaction 2448.3.7 Open Issues and Recommendation 2468.4 Information Model Management Service 2478.4.1 Background: Issues, Controversies, andProblems 2478.4.2 Overview of the SA Forum IMM Solution 2498.4.3 The Object Manager API 2518.4.4 The Object Implementer API 2558.4.5 IMM XML File 2588.4.6 Administrative and Management Aspects 2588.4.7 Service Interaction 2588.4.8 Open Issues 2608.4.9 Recommendation 2618.5 Conclusion 2629 Model-Based Software Management: The Software Management Framework 265Maria Toeroe9.1 Introduction 2659.2 Background 2669.3 Software Management a la Carte 2689.3.1 Overview of the SA Forum Solution 2689.3.2 Entity Types File: Is It Eaten or Drunk by SMF? 2719.3.3 The Upgrade Campaign and Its Specification 2739.3.4 Upgrade Campaign Execution Status and Failure Handling 2799.3.5 Administrative and Management Aspects 2859.3.6 User Perspective 2889.3.7 Service Interaction 2899.3.8 Open Issues 2919.3.9 Recommendation 2929.4 Conclusion 29410 Combining the Services 297Maria Toeroe10.1 Introduction 29710.2 Application Design and Development 29710.3 Application Platform Design 29910.4 Operation and Maintenance 301Part III SA FORUM MIDDLEWARE IN ACTION11 SA Forum Programming Model and API Conventions305Francis Tam11.1 Introduction 30511.2 Programming Model 30611.2.1 AIS Area Service Interfaces 30611.2.2 Real-Time Support 30611.2.3 Naming Conventions and Type Definitions 30811.2.4 Usage Model and Library Life Cycle 30911.2.5 Tracking 31111.3 Making Sense of the API Specifications 31211.3.1 Structure of Service API Specification 31411.3.2 Administration API 31511.4 Practical Topics 31611.4.1 Interacting with POSIX 31611.4.2 Allocating and Freeing Memory 31911.4.3 Handling Pointers 31911.4.4 Finding Out Implementation Limits 32011.4.5 When an Area Service is Unavailable 32111.4.6 Backward Compatibility 32211.5 Concluding Remarks 32212 SA Forum Java Mappings: Specifications, Usage, and Experience 325Robert Hyerle and Jens Jensen12.1 Introduction 32512.2 Background 32512.2.1 Early Exploration of Java Mappings in Hewlett-Packard 32512.2.2 Java inEricsson 32612.2.3 The SA Forum Java Mapping Initiative 32712.3 Understandingthe Java Mappings 32812.3.1 Java Application Integration Architecture 32812.3.2 Naming 32912.3.3 Package Structure 33012.3.4 The Underlying Objects 33012.3.5 Types 33112.3.6 Parameters, Exceptions, and Method Signatures 33212.3.7 Factories, Callbacks, and Life-cycles 33312.3.8 Callbacks and the Selection Object in Java 33412.4 Using the Java Mappings 33512.4.1 Integrating AIS Services with Java Applications 33512.4.2 Integrating AIS Services with Containerized Java Applications 34212.4.3 AIS Services in Mixed Language and Mixed Implementation Environments 34312.5 Going Further 34312.5.1 The Java Mapping Roadmap 34312.5.2 Related Java Standards and Other References 34413 SA Forum Middleware Implementations 347Mario Angelic and Ulrich Kleber13.1 Introduction 34713.1.1 OpenHPI 34713.1.2 OpenSAF 34813.2 The OpenHPI Project 34813.2.1 Overview of the OpenHPI Solution 34813.2.2 User Perspective 35113.2.3 OpenHPI Tools 35313.2.4 Open Issues and Recommendations 35413.3 The OpenSAF Project 35513.3.1 Background 35513.3.2 OpenSAF Architecture 35613.3.3 SA Forum Compliant Services 36013.3.4 OpenSAF Infrastructure Services 36413.3.5 Managing OpenSAF 36513.3.6 Deploying OpenSAF 36713.4 Conclusion 36814 Integration of the VideoLAN Client with OpenSAF: An Example 371Anik Mishra and Ali Kanso14.1 Introduction 37114.2 Going Under the Hood: The VLC Workflow 37214.3 Integrating VLC with OpenSAF 37314.3.1 Nonproxied-Non-SA-Aware Integration 37414.3.2 SA-Aware VLC Integration 37914.3.3 SA-Aware VLC with Service Continuity 38414.4 Summary and Conclusion 38715 Migration Paths for Legacy Applications 391Mario Angelic15.1 Introduction 39115.2 Reasons for Migration 39215.2.1 Benefits for System Owners 39215.2.2 Benefits for ISVs 39215.3 Integration Criteria 39315.3.1 Main Factors 39315.3.2 Easy Management 39415.3.3 Streamlined Architecture 39615.3.4 Code Quality 39715.3.5 Integration Levels 39715.4 How to Migrate 39915.4.1 Availability Integration 39915.4.2 Manageability Integration 40915.5 Open Issues 41315.6 Conclusion 41316 Overcoming Complexity: Formal Modeling Techniques at the Rescue 415Maria Toeroe and Ferhat Khendek16.1 Introduction 41516.2 Background 41616.2.1 TheModel-Based Approach 41616.2.2 Starting Points in the Specifications 41716.3 Model-Based Softw
- ISBN: 978-1-119-95408-8
- Editorial: John Wiley & Sons
- Encuadernacion: Cartoné
- Páginas: 488
- Fecha Publicación: 20/04/2012
- Nº Volúmenes: 1
- Idioma: Inglés