The Service Availability Forum Specification for High Availability Middleware
|
|
- Ira Bates
- 8 years ago
- Views:
Transcription
1 The Availability Forum Specification for High Availability Middleware Timo Jokiaho, Fred Herrmann, Dave Penkler, Manfred Reitenspiess, Louise Moser Availability Forum Abstract The Availability Forum Application Interface Specification is an industrial standard for high availability middleware that is intended for telecommunications, data communications and networking applications that must provide continuous service to their users. The Application Interface Specification allows application developers to write application software that is portable across different vendors implementations of the specification. 1. Introduction The Availability Forum (SA Forum) is a consortium of computer and communications industry companies that are dedicated to producing standards that enable the development of carrier-grade systems from commercial-off-the-shelf (COTS) hardware platforms, operating systems and middleware. The key characteristic of a carrier-grade system is its ability to provide uninterrupted service to its users. Typical applications for which the SA Forum standards might be employed to achieve high availability are telecommunication and data communication applications, such as connection establishment, routing and billing. Value-added services, such as voice mail, instant messaging, presence and caller id differentiated response, are becoming increasingly important and will be appropriately implemented using the SA Forum standards to ensure high availability of these services. The SA Forum has developed two standards: the Hardware Platform Interface and the Application Interface Specification. The relationship between these two interfaces is shown in Figure 1. The Hardware Platform Interface (HPI) is an industrial standard for managing a carrier-grade hardware platform that is independent of any particular hardware. The HPI represents the platform-specific characteristics of the physical hardware in an abstract model, and provides standard functions for monitoring and controlling that model. A vendor s implementation of the HPI represents the physical hardware in terms of this abstract model, and translates the library function calls defined by the specification into appropriate actions of the physical hardware. The Application Interface Specification (AIS) is a standard for high availability middleware that is independent of a particular vendor s implementation. As such, it supports portability of applications across high availability middleware supplied by different vendors, just as the Hardware Platform Interface defines an interface for platform management services that is platform-independent. The AIS defines extensive Application Program Interfaces (APIs), which an application programmer can use in conjunction with a vendor s high availability middleware that implements the specification. In particular, it defines APIs for: Availability Management Framework Cluster Membership Checkpoint Event Message Lock. Applications Operating System Availability Middleware Hardware Platform Platform Drivers AIS Interface HPI Interface Figure 1. Relationship between the AIS Interface and the HPI Interface.
2 This paper presents an overview of the SA Forum Application Interface Specification. A previous version of this paper appeared in [2]. For the complete Application Interface Specification standard, please see [7] 2. Application Interface Specification Model The Application Interface Specification represents the high-availability characteristics of the system in an abstract model, and defines extensive APIs that support that model Physical and Logical Entities The AIS model defines several physical and logical entities, including nodes, components, service units, service instances, component service instances, service groups and protection groups, as shown in Figure 2. Node Group Unit active standby Protection Group Protection Group active Node Unit standby Figure 2. Entities of the Application Interface Specification Model. A cluster node is a logical entity that represents a physical node, which behaves like a computer that runs a single instance of an operating system and exports the AIS and HPI APIs. A component is a logical entity that represents a set of resources, such as processes, that are managed by the Availability Management Framework. A service unit encapsulates the components representing hardware and/or software resources into a single management unit. A service instance is a particular service (workload) that the Availability Management Framework has assigned to a service unit. A component service instance is an element of a service instance that a component within a service unit provides. A service group is a set of one or more identical service units that provide service availability to its users. A protection group for a component service instance is the set of components to which that component service instance has been assigned Unit State The AIS model defines service unit states, including the Readiness State, which can be out-of-service, inservice or stopping, and the HA State, which can be active, standby or quiesced Capability Models The AIS model defines several Capability Models, in particular, the x_active_and_y_standby, x_active_or_x_standby and x_active models. In the x_active_and_y_standby model, a component can handle x active and y standby component service instances simultaneously. In the x_active_or_x_standby model, a component can handle either x active or x standby component service instances, but it supports only all active or all standby component service instances at a time. In the x_active model, the component can handle x active component service instances at a time, but does not support any standby component service instances Group Redundancy Models The AIS model also defines Group Redundancy Models, including the 2N and N+M models, showninfigure3. In the 2N redundancy model, each of N service groups contains two service units that provide service availability to one or more service instances. One of the services units is active on behalf of one or more service instances, and the other service unit is standby on behalf of those same services instances. In the N+M redundancy model, the service group has N+M service units. Each of the N service units is active on behalf of one or more service instances, and each of the M service units is standby on behalf of one or more service instances. Active Active Active Active 2N Redundancy Model Active Active Active Active N+M Redundancy Model Figure 3. 2N and N+M Redundancy Models.
3 3. Availability Applications The Availability Forum Application Interface Specification is intended for telecommunications, data communications and networking applications. The Availability Management Framework manages these applications, which are structured into sets of components. A component is an implementationoriented software abstraction for decomposing and distributing applications for service availability. The services that the application provides are decomposed into component service instances that are assigned to components, which support them in active or standby mode. s and component service instances are the basic entities that are manipulated by the APIs of the Availability Management Framework. They are further structured into higher-level entities for the purposes of application and system management. s that are co-located on a node and that must all be in-service or out-of-service together are grouped together in a service unit. The service unit is the unit of redundancy from the management perspective, whereas the component is the unit of redundancy from a design and runtime perspective. A set of identical service units that participate in a given redundancy model are grouped together into a service group. The redundancy model and other attributes of the service group describe how the service units are instantiated on different nodes. When structuring an application for service availability, it is important to take into account the important properties of redundancy, scalability, upgradability and isolation. depending on the redundancy model associated with the service group Upgradability A service unit and its components are upgraded as a unit. To maintain operation of service, component service instances must be able to be assigned from one version of a component to another Isolation Each component is expected to monitor its own state and detect, contain and isolate faults within its scope. 4. Application Interface Specification Areas The Application Interface Specification defines APIs for an Availability Management Framework and for core high availability services, namely, the Cluster Membership, Checkpoint, Event, Message and Lock s. These services provide the basic functionality of the cluster on which the Availability Management Framework and the applications that must be highly available are deployed. These areas of the Application Interface Specification are illustrated in Figure 4, and are explained in more detail below. Application Process Message Library Checkpoint Library Availability Management Framework Library Application Process Lock Library Event Library Cluster Membership Library Availability Management Framework Library 3.1. Redundancy To provide service availability, components deployed in service units are replicated on different cluster nodes according to a redundancy model. To participate in a given redundancy model, components must support the required capabilities. For example, the components must be able to support their component service instances in both the active and standby mode for the 2N redundancy model Scalability To increase application throughput or capacity, additional service units in a service group or additional service groups in a cluster can be deployed. The level of service availability can be traded off against capacity, Message Checkpoint Availability Management Framework Cluster Membership Event Lock Figure 4. Application Interface Specification Areas Availability Management Framework The Availability Management Framework is the software entity that provides service availability by coordinating redundant resources within a cluster. It is based on a view of a logical cluster that consists of a number of cluster nodes. These nodes host various resources in a distributed computing environment.
4 The Availability Management Framework provides a set of APIs to enable highly available applications. It determines the Readiness State and the HA State of a component and checks the health of a component by invoking callback functions of the component. It also allows a component to query the Availability Management Framework for information about the component s state, using functions of the Availability Management Framework Cluster Membership The Cluster Membership provides membership information about the nodes in a cluster to the applications. A cluster is simply a set of nodes, each with a unique identifier, that are connected together by a communication network. As nodes join and leave the cluster, the membership of the cluster changes. The Cluster Membership provides functions that allow an application process to retrieve information about the cluster membership and the cluster nodes. It also allows an application process to register a callback function to receive membership change notifications automatically as those changes occur. All functions of the Cluster Membership are available on all nodes in the cluster Checkpoint The Checkpoint provides a facility for an application to preserve its state across hardware and software faults. If a process fails and is restarted, it can recover quickly by retrieving its state from a checkpoint. If the node on which a process is running fails, then a standby on another node can become active quickly by obtaining its state from the checkpoint. Checkpoints are cluster-wide entities that are designated by unique names. A copy of the data stored in a checkpoint is called a checkpoint replica, which is typically stored in main memory rather than on disk for performance reasons. A given checkpoint may have several checkpoint replicas stored on different nodes in the cluster to protect it against node faults. To avoid accumulation of unused checkpoints in the system, checkpoint replicas have a retention time. If no process has opened a checkpoint for the duration of the retention time, the Checkpoint automatically deletes the checkpoint Event The Event is a publish/subscribe multipointto-multipoint communication mechanism that is based on the concept of event channels, where a publisher communicates asynchronously with one or more subscribers over an event channel. Multiple publishers and multiple subscribers can communicate over the same event channel, and publishers can also be subscribers on the same event channel. Individual publishers and individual subscribers can communicate over multiple event channels. Events consist of a standard header and zero or more bytes of publisher event data. The Event API does not impose any specific transfer syntax for the data, although an implementation of the Event is expected to use a standard for data marshalling to support heterogeneity of data representations between publishers and subscribers Message The Message provides a multipoint-to-point communication mechanism by which processes on the same or different nodes can communicate. Messages are written to, and read from, message queues. Queues are persistent or non-persistent, and migratable or nonmigratable. If an active process fails, a standby process can process the messages from the message queues. The source of the messages continues to communicate with the same queue, and is unaware that a fault has occurred. Queues can be grouped together to form queue groups. Queue groups are identified by logical names, so that a process is unaware of the number of queues and of the physical location of the queues to which it is communicating. Queue groups can be used to distribute workload among the queues in the group. Queue groups can be used to maintain transparency of the sender process to faults in the receiver processes, represented by the queues in the queue groups. The sender process communicates with the queue group. If a receiver process fails, the sender process continues to communicate with the queue group and is unaware of the fault, because it continues to obtain service from the other receiver processes Lock The Lock is a distributed lock service, intended for use in a cluster, where processes in different nodes might compete with each other for access to a shared resource. The Lock provides entities, called locks, which are used to synchronize access to shared data among the application processes. Each lock is claimed and released individually.
5 The Lock provides a simple lock model supporting two locking modes that support exclusive access and shared access. Synchronous and asynchronous calls, lock timeout, try lock, deadlock detection, lock orphaning and lock wait notifications are provided. 5. Using the Application Interface Specification The Application Interface Specification defines APIs for the functions of the Availability Management Framework and of the Cluster Membership, Event, Message, Checkpoint and Lock s that an application can invoke. These functions are implemented within libraries that are linked into the application processes that must be highly available. The AIS also defines callback functions of the application that the Availability Management Framework and the Cluster Membership, Event, Message, Checkpoint and Lock s can invoke. The application programmer must implement these callback functions within the application program. The application program initializes itself with the Availability Management Framework or the particular service, and registers the callback functions, by invoking an initialize function. Subsequently, it closes its association with the Framework or the particular service, by using a finalize function. The Framework and each of the services also provide functions to detect pending callbacks and to specify callback execution behavior. The header files for the functions of the libraries of the Availability Management Framework and the various services are taken directly from the Application Interface Specification, and are written in the C programming language. The header files must be included in the application program modules that use those libraries. 6. Related Work Over the past several decades, there has been much work, both in industry and in academia, on building highly available and fault-tolerant distributed systems. Several excellent general reference books in this field are [1], [3], [4] and [6]. There have been many research papers written in this field, far too many to cite here, and there have been a number of commercial products related to high availability and fault tolerance. There has also been work by other standards organizations in developing standards for high availability and fault tolerance middleware. In particular, the Object Management Group has adopted a specification for Fault Tolerant CORBA [5]. The OMG specification focuses on fault tolerance for CORBA based on replication with strong replica consistency, whereas the Availability Forum AIS specification provides high availability. Fault Tolerant CORBA defines interfaces related to replication, fault detection and notification, and checkpointing and restoration. CORBA itself provides a message service via remote method invocation using the Internet Inter-ORB Protocol, and includes an Event. The OMG has also defined a specification for Real-Time CORBA that is intended for embedded systems. The OMG s specifications are written in CORBA s Interface Definition Language and, thus, are language-independent and more abstract than the Availability Forum s specifications, which are written in C. The OMG specifications are, however, specific to CORBA. 7. Conclusion The Availability Forum Application Interface Specification, discussed in this paper, is an industrial standard for high availability middleware. It represents the high availability characteristics of the system in an abstract model, and defines extensive APIs that support that model. The Application Interface Specification defines a comprehensive set of APIs for an Availability Management Framework, and various services, in particular, a Cluster Membership, Checkpoint, Event, Message and Lock. 8. References [1] Birman, K. and van Renesse, R., Reliable Distributed Computing with the Isis Toolkit, IEEE Computer Society Press, Los Alamitos, CA, [2] Jokiaho, T., Herrmann, F., Penkler, D. and Moser, L., The Availability Forum Application Interface Specification, RTC Magazine, Vol. XII, No. 6, June 2003, pp [3] Marcus, E. and Stern, H. Blueprints for High Availability: Designing Resilient Distributed Systems, John Wiley, New York, NY, [4] Mullender, S., Distributed Systems, Addison-Wesley, ACM Press, Menlo Park, CA, [5] Object Management Group, Fault Tolerant CORBA, OMG Technical Committee Document ptc/ , April 2000, [6] Powell, D., ed., Delta-4: A Generic Architecture for Dependable Distributed Computing, Research Reports ESPRIT, Springer-Verlag, Berlin, [7] The Availability Forum, Application Interface Specification, April 2003,
Domains. Seminar on High Availability and Timeliness in Linux. Zhao, Xiaodong March 2003 Department of Computer Science University of Helsinki
Domains Seminar on High Availability and Timeliness in Linux Zhao, Xiaodong March 2003 Department of Computer Science University of Helsinki 1 1. Introduction The Hardware Platform Interface (HPI) is developed
More informationHighly Available Mobile Services Infrastructure Using Oracle Berkeley DB
Highly Available Mobile Services Infrastructure Using Oracle Berkeley DB Executive Summary Oracle Berkeley DB is used in a wide variety of carrier-grade mobile infrastructure systems. Berkeley DB provides
More informationThe EMSX Platform. A Modular, Scalable, Efficient, Adaptable Platform to Manage Multi-technology Networks. A White Paper.
The EMSX Platform A Modular, Scalable, Efficient, Adaptable Platform to Manage Multi-technology Networks A White Paper November 2002 Abstract: The EMSX Platform is a set of components that together provide
More informationHow To Understand The Concept Of A Distributed System
Distributed Operating Systems Introduction Ewa Niewiadomska-Szynkiewicz and Adam Kozakiewicz ens@ia.pw.edu.pl, akozakie@ia.pw.edu.pl Institute of Control and Computation Engineering Warsaw University of
More informationA Survey on Availability and Scalability Requirements in Middleware Service Platform
International Journal of Computer Sciences and Engineering Open Access Survey Paper Volume-4, Issue-4 E-ISSN: 2347-2693 A Survey on Availability and Scalability Requirements in Middleware Service Platform
More informationHigh-Availability and Standards The Way to Go! (Abstract)
High-Availability and Standards The Way to Go! (Abstract) Manfred Reitenspieß Fujitsu Siemens Computers Otto-Hahn-Ring 6 D-81739 München manfred.reitenspiess@fujitsu-siemens.com 1 High-Availability a Long
More informationMiddleware: Past and Present a Comparison
Middleware: Past and Present a Comparison Hennadiy Pinus ABSTRACT The construction of distributed systems is a difficult task for programmers, which can be simplified with the use of middleware. Middleware
More informationEnterprise Application Integration
Enterprise Integration By William Tse MSc Computer Science Enterprise Integration By the end of this lecturer you will learn What is Enterprise Integration (EAI)? Benefits of Enterprise Integration Barrier
More informationMiddleware Lou Somers
Middleware Lou Somers April 18, 2002 1 Contents Overview Definition, goals, requirements Four categories of middleware Transactional, message oriented, procedural, object Middleware examples XML-RPC, SOAP,
More informationNetwork Attached Storage. Jinfeng Yang Oct/19/2015
Network Attached Storage Jinfeng Yang Oct/19/2015 Outline Part A 1. What is the Network Attached Storage (NAS)? 2. What are the applications of NAS? 3. The benefits of NAS. 4. NAS s performance (Reliability
More informationIntroduction CORBA Distributed COM. Sections 9.1 & 9.2. Corba & DCOM. John P. Daigle. Department of Computer Science Georgia State University
Sections 9.1 & 9.2 Corba & DCOM John P. Daigle Department of Computer Science Georgia State University 05.16.06 Outline 1 Introduction 2 CORBA Overview Communication Processes Naming Other Design Concerns
More informationIntroduction to CORBA. 1. Introduction 2. Distributed Systems: Notions 3. Middleware 4. CORBA Architecture
Introduction to CORBA 1. Introduction 2. Distributed Systems: Notions 3. Middleware 4. CORBA Architecture 1. Introduction CORBA is defined by the OMG The OMG: -Founded in 1989 by eight companies as a non-profit
More informationSOFT 437. Software Performance Analysis. Ch 5:Web Applications and Other Distributed Systems
SOFT 437 Software Performance Analysis Ch 5:Web Applications and Other Distributed Systems Outline Overview of Web applications, distributed object technologies, and the important considerations for SPE
More informationClassic Grid Architecture
Peer-to to-peer Grids Classic Grid Architecture Resources Database Database Netsolve Collaboration Composition Content Access Computing Security Middle Tier Brokers Service Providers Middle Tier becomes
More informationChapter 2: Remote Procedure Call (RPC)
Chapter 2: Remote Procedure Call (RPC) Gustavo Alonso Computer Science Department Swiss Federal Institute of Technology (ETHZ) alonso@inf.ethz.ch http://www.iks.inf.ethz.ch/ Contents - Chapter 2 - RPC
More informationGuide to Scaling OpenLDAP
Guide to Scaling OpenLDAP MySQL Cluster as Data Store for OpenLDAP Directories An OpenLDAP Whitepaper by Symas Corporation Copyright 2009, Symas Corporation Table of Contents 1 INTRODUCTION...3 2 TRADITIONAL
More informationFeature Comparison. Windows Server 2008 R2 Hyper-V and Windows Server 2012 Hyper-V
Comparison and Contents Introduction... 4 More Secure Multitenancy... 5 Flexible Infrastructure... 9 Scale, Performance, and Density... 13 High Availability... 18 Processor and Memory Support... 24 Network...
More informationWSO2 Message Broker. Scalable persistent Messaging System
WSO2 Message Broker Scalable persistent Messaging System Outline Messaging Scalable Messaging Distributed Message Brokers WSO2 MB Architecture o Distributed Pub/sub architecture o Distributed Queues architecture
More informationRed Hat Enterprise linux 5 Continuous Availability
Red Hat Enterprise linux 5 Continuous Availability Businesses continuity needs to be at the heart of any enterprise IT deployment. Even a modest disruption in service is costly in terms of lost revenue
More informationMIDDLEWARE 1. Figure 1: Middleware Layer in Context
MIDDLEWARE 1 David E. Bakken 2 Washington State University Middleware is a class of software technologies designed to help manage the complexity and heterogeneity inherent in distributed systems. It is
More informationClient/Server Computing Distributed Processing, Client/Server, and Clusters
Client/Server Computing Distributed Processing, Client/Server, and Clusters Chapter 13 Client machines are generally single-user PCs or workstations that provide a highly userfriendly interface to the
More informationA standards-based approach to application integration
A standards-based approach to application integration An introduction to IBM s WebSphere ESB product Jim MacNair Senior Consulting IT Specialist Macnair@us.ibm.com Copyright IBM Corporation 2005. All rights
More informationBest Practices for Installing and Configuring the Captaris RightFax 9.3 Shared Services Module
WHITE PAPER Best Practices for Installing and Configuring the Captaris RightFax 9.3 Shared Services Module Taking Advantage of Multiple RightFax Servers Sharing a Single Database PREFACE Captaris has created
More informationBUILDING HIGH-AVAILABILITY SERVICES IN JAVA
BUILDING HIGH-AVAILABILITY SERVICES IN JAVA MATTHIAS BRÄGER CERN GS-ASE Matthias.Braeger@cern.ch AGENDA Measuring service availability Java Messaging Shared memory solutions Deployment Examples Summary
More informationMicrosoft SharePoint 2010 on VMware Availability and Recovery Options. Microsoft SharePoint 2010 on VMware Availability and Recovery Options
This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html. VMware
More informationLehrstuhl für Informatik 4 Kommunikation und verteilte Systeme. Middleware. Chapter 8: Middleware
Middleware 1 Middleware Lehrstuhl für Informatik 4 Middleware: Realisation of distributed accesses by suitable software infrastructure Hiding the complexity of the distributed system from the programmer
More informationEvent-based middleware services
3 Event-based middleware services The term event service has different definitions. In general, an event service connects producers of information and interested consumers. The service acquires events
More informationSCALABILITY AND AVAILABILITY
SCALABILITY AND AVAILABILITY Real Systems must be Scalable fast enough to handle the expected load and grow easily when the load grows Available available enough of the time Scalable Scale-up increase
More informationMotivation Definitions EAI Architectures Elements Integration Technologies. Part I. EAI: Foundations, Concepts, and Architectures
Part I EAI: Foundations, Concepts, and Architectures 5 Example: Mail-order Company Mail order Company IS Invoicing Windows, standard software IS Order Processing Linux, C++, Oracle IS Accounts Receivable
More informationDistributed Fault-Tolerant / High-Availability (DFT/HA) Systems
White Paper February 2010 Distributed Fault-Tolerant / High-Availability (DFT/HA) Systems By Ravi Raj Bhat, Vice President of Engineering Today s telecommunication platforms must provide five nines availability,
More informationChapter 16 Distributed Processing, Client/Server, and Clusters
Operating Systems: Internals and Design Principles Chapter 16 Distributed Processing, Client/Server, and Clusters Eighth Edition By William Stallings Table 16.1 Client/Server Terminology Applications Programming
More informationHigh Availability Storage
High Availability Storage High Availability Extensions Goldwyn Rodrigues High Availability Storage Engineer SUSE High Availability Extensions Highly available services for mission critical systems Integrated
More informationTier Architectures. Kathleen Durant CS 3200
Tier Architectures Kathleen Durant CS 3200 1 Supporting Architectures for DBMS Over the years there have been many different hardware configurations to support database systems Some are outdated others
More informationbe architected pool of servers reliability and
TECHNICAL WHITE PAPER GRIDSCALE DATABASE VIRTUALIZATION SOFTWARE FOR MICROSOFT SQL SERVER Typical enterprise applications are heavily reliant on the availability of data. Standard architectures of enterprise
More informationJournal of science STUDY ON REPLICA MANAGEMENT AND HIGH AVAILABILITY IN HADOOP DISTRIBUTED FILE SYSTEM (HDFS)
Journal of science e ISSN 2277-3290 Print ISSN 2277-3282 Information Technology www.journalofscience.net STUDY ON REPLICA MANAGEMENT AND HIGH AVAILABILITY IN HADOOP DISTRIBUTED FILE SYSTEM (HDFS) S. Chandra
More informationAvailability Digest. MySQL Clusters Go Active/Active. December 2006
the Availability Digest MySQL Clusters Go Active/Active December 2006 Introduction MySQL (www.mysql.com) is without a doubt the most popular open source database in use today. Developed by MySQL AB of
More informationHRG Assessment: Stratus everrun Enterprise
HRG Assessment: Stratus everrun Enterprise Today IT executive decision makers and their technology recommenders are faced with escalating demands for more effective technology based solutions while at
More informationJitterbit Technical Overview : Microsoft Dynamics CRM
Jitterbit allows you to easily integrate Microsoft Dynamics CRM with any cloud, mobile or on premise application. Jitterbit s intuitive Studio delivers the easiest way of designing and running modern integrations
More informationExecutive Summary WHAT IS DRIVING THE PUSH FOR HIGH AVAILABILITY?
MINIMIZE CUSTOMER SERVICE DISRUPTION IN YOUR CONTACT CENTER GENESYS SIP 99.999% AVAILABILITY PROVIDES QUALITY SERVICE DELIVERY AND A SUPERIOR RETURN ON INVESTMENT TABLE OF CONTENTS Executive Summary...1
More informationChapter Outline. Chapter 2 Distributed Information Systems Architecture. Middleware for Heterogeneous and Distributed Information Systems
Prof. Dr.-Ing. Stefan Deßloch AG Heterogene Informationssysteme Geb. 36, Raum 329 Tel. 0631/205 3275 dessloch@informatik.uni-kl.de Chapter 2 Architecture Chapter Outline Distributed transactions (quick
More informationBuilding Reliable, Scalable AR System Solutions. High-Availability. White Paper
Building Reliable, Scalable Solutions High-Availability White Paper Introduction This paper will discuss the products, tools and strategies available for building reliable and scalable Action Request System
More information000-608. IBM WebSphere Process Server V7.0 Deployment Exam. http://www.examskey.com/000-608.html
IBM 000-608 IBM WebSphere Process Server V7.0 Deployment Exam TYPE: DEMO http://www.examskey.com/000-608.html Examskey IBM 000-608 exam demo product is here for you to test the quality of the product.
More informationDiagram 1: Islands of storage across a digital broadcast workflow
XOR MEDIA CLOUD AQUA Big Data and Traditional Storage The era of big data imposes new challenges on the storage technology industry. As companies accumulate massive amounts of data from video, sound, database,
More informationA Survey Study on Monitoring Service for Grid
A Survey Study on Monitoring Service for Grid Erkang You erkyou@indiana.edu ABSTRACT Grid is a distributed system that integrates heterogeneous systems into a single transparent computer, aiming to provide
More informationCOMP5426 Parallel and Distributed Computing. Distributed Systems: Client/Server and Clusters
COMP5426 Parallel and Distributed Computing Distributed Systems: Client/Server and Clusters Client/Server Computing Client Client machines are generally single-user workstations providing a user-friendly
More informationHigh Availability Design Patterns
High Availability Design Patterns Kanwardeep Singh Ahluwalia 81-A, Punjabi Bagh, Patiala 147001 India kanwardeep@gmail.com +91 98110 16337 Atul Jain 135, Rishabh Vihar Delhi 110092 India jain.atul@wipro.com
More informationAn Oracle White Paper February 2012. Top Twelve Guidelines for Best-in-Class Service Availability in Communication Services and Applications
An Oracle White Paper February 2012 Top Twelve Guidelines for Best-in-Class Service Availability in Communication Services and Applications Introduction The rapid growth of mobile broadband services, proliferation
More informationVirtual machine interface. Operating system. Physical machine interface
Software Concepts User applications Operating system Hardware Virtual machine interface Physical machine interface Operating system: Interface between users and hardware Implements a virtual machine that
More informationIn Memory Accelerator for MongoDB
In Memory Accelerator for MongoDB Yakov Zhdanov, Director R&D GridGain Systems GridGain: In Memory Computing Leader 5 years in production 100s of customers & users Starts every 10 secs worldwide Over 15,000,000
More informationHigh Availability in a J2EE Enterprise Application Environment
High Availability in a J2EE Enterprise Application Environment Udo Pletat IBM Deutschland Entwicklung GmbH Schönaicher Str. 220 71032 Böblingen, Germany pletat@de.ibm.com Abstract Recent developments of
More informationDistributed Data Management
Introduction Distributed Data Management Involves the distribution of data and work among more than one machine in the network. Distributed computing is more broad than canonical client/server, in that
More informationImplementing and Managing Windows Server 2008 Clustering
Implementing and Managing Windows Server 2008 Clustering Course Number: 6423A Course Length: 3 Days Course Overview This instructor-led course explores Windows Server 2008 clustering and provides students
More informationPersistent, Reliable JMS Messaging Integrated Into Voyager s Distributed Application Platform
Persistent, Reliable JMS Messaging Integrated Into Voyager s Distributed Application Platform By Ron Hough Abstract Voyager Messaging is an implementation of the Sun JMS 1.0.2b specification, based on
More informationObjectives. Distributed Databases and Client/Server Architecture. Distributed Database. Data Fragmentation
Objectives Distributed Databases and Client/Server Architecture IT354 @ Peter Lo 2005 1 Understand the advantages and disadvantages of distributed databases Know the design issues involved in distributed
More informationService Availability TM Forum Application Interface Specification
Service Availability TM Forum Application Interface Specification Information Model Management Service SAI-AIS-IMM-A.02.0 This specification was reissued on September, under the Artistic License 2.0. The
More informationContents. SnapComms Data Protection Recommendations
Contents Abstract... 2 SnapComms Solution Environment... 2 Concepts... 3 What to Protect... 3 Database Failure Scenarios... 3 Physical Infrastructure Failures... 3 Logical Data Failures... 3 Service Recovery
More informationClustering and Queue Replication:
Clustering & Queue Replication Clustering and Queue Replication: How WatchGuard XCS Provides Fully Redundant Messaging Security Technical Brief WatchGuard Technologies, Inc. Published: March 2011 Introduction
More informationWindows Server 2008 R2 Hyper-V Server and Windows Server 8 Beta Hyper-V
Features Comparison: Hyper-V Server and Hyper-V February 2012 The information contained in this document relates to a pre-release product which may be substantially modified before it is commercially released.
More informationHow To Build A Clustered Storage Area Network (Csan) From Power All Networks
Power-All Networks Clustered Storage Area Network: A scalable, fault-tolerant, high-performance storage system. Power-All Networks Ltd Abstract: Today's network-oriented computing environments require
More informationTIBCO ActiveSpaces Use Cases How in-memory computing supercharges your infrastructure
TIBCO Use Cases How in-memory computing supercharges your infrastructure is a great solution for lifting the burden of big data, reducing reliance on costly transactional systems, and building highly scalable,
More informationCHAPTER 2 MODELLING FOR DISTRIBUTED NETWORK SYSTEMS: THE CLIENT- SERVER MODEL
CHAPTER 2 MODELLING FOR DISTRIBUTED NETWORK SYSTEMS: THE CLIENT- SERVER MODEL This chapter is to introduce the client-server model and its role in the development of distributed network systems. The chapter
More informationPervasive PSQL Meets Critical Business Requirements
Pervasive PSQL Meets Critical Business Requirements Pervasive PSQL White Paper May 2012 Table of Contents Introduction... 3 Data Backup... 3 Pervasive Backup Agent... 3 Pervasive PSQL VSS Writer... 5 Pervasive
More informationComponent Replication in Distributed Systems: a Case study using Enterprise Java Beans
Component Replication in Distributed Systems: a Case study using Enterprise Java Beans G. Morgan, A. I. Kistijantoro, S. K. Shrivastava and M.C. Little * School of Computing Science, Newcastle University,
More informationHigh Availability Solutions for the MariaDB and MySQL Database
High Availability Solutions for the MariaDB and MySQL Database 1 Introduction This paper introduces recommendations and some of the solutions used to create an availability or high availability environment
More informationindependent systems in constant communication what they are, why we care, how they work
Overview of Presentation Major Classes of Distributed Systems classes of distributed system loosely coupled systems loosely coupled, SMP, Single-system-image Clusters independent systems in constant communication
More informationDistributed System Principles
Distributed System Principles 1 What is a Distributed System? Definition: A distributed system consists of a collection of autonomous computers, connected through a network and distribution middleware,
More information<Insert Picture Here> Oracle In-Memory Database Cache Overview
Oracle In-Memory Database Cache Overview Simon Law Product Manager The following is intended to outline our general product direction. It is intended for information purposes only,
More informationA Framework for ADS Application Software Development Based on CORBA
A Framework for ADS Application Software Development Based on CORBA Stephen S. Yau and Shaowei Mao Computer Science and Engineering Department Arizona State University Tempe, AZ 85281-5406 USA email: (
More informationManaging a Fibre Channel Storage Area Network
Managing a Fibre Channel Storage Area Network Storage Network Management Working Group for Fibre Channel (SNMWG-FC) November 20, 1998 Editor: Steven Wilson Abstract This white paper describes the typical
More informationClient Server Architecture
Client Server Architecture Key concepts: - client server architecture - Functional requirements in the 2-tier structures - Functional distribution in the 2-tier structures - Implementation of Business
More informationDistributed Objects and Components
Distributed Objects and Components Introduction This essay will identify the differences between objects and components and what it means for a component to be distributed. It will also examine the Java
More informationOpenSAF A Standardized HA Solution
OpenSAF A Standardized HA Solution LinuxCON Edinburgh, UK 2013-10-21 Anders Widell Ericsson AB Outline What are OpenSAF and SA Forum? What is Service Availability? Simple Use Case: Web server The OpenSAF
More informationWindows Server Failover Clustering April 2010
Windows Server Failover Clustering April 00 Windows Server Failover Clustering (WSFC) is the successor to Microsoft Cluster Service (MSCS). WSFC and its predecessor, MSCS, offer high availability for critical
More informationFault Tolerant Servers: The Choice for Continuous Availability on Microsoft Windows Server Platform
Fault Tolerant Servers: The Choice for Continuous Availability on Microsoft Windows Server Platform Why clustering and redundancy might not be enough This paper discusses today s options for achieving
More informationOVERVIEW. CEP Cluster Server is Ideal For: First-time users who want to make applications highly available
Phone: (603)883-7979 sales@cepoint.com Cepoint Cluster Server CEP Cluster Server turnkey system. ENTERPRISE HIGH AVAILABILITY, High performance and very reliable Super Computing Solution for heterogeneous
More informationPrinciples and characteristics of distributed systems and environments
Principles and characteristics of distributed systems and environments Definition of a distributed system Distributed system is a collection of independent computers that appears to its users as a single
More informationIaaS Cloud Architectures: Virtualized Data Centers to Federated Cloud Infrastructures
IaaS Cloud Architectures: Virtualized Data Centers to Federated Cloud Infrastructures Dr. Sanjay P. Ahuja, Ph.D. 2010-14 FIS Distinguished Professor of Computer Science School of Computing, UNF Introduction
More informationOverview of CORBA 11.1 I NTRODUCTION TO CORBA. 11.4 Object services 11.5 New features in CORBA 3.0 11.6 Summary
C H A P T E R 1 1 Overview of CORBA 11.1 Introduction to CORBA 11.2 CORBA architecture 11.3 Client and object implementations 11.4 Object services 11.5 New features in CORBA 3.0 11.6 Summary In previous
More informationCHAPTER 1: OPERATING SYSTEM FUNDAMENTALS
CHAPTER 1: OPERATING SYSTEM FUNDAMENTALS What is an operating? A collection of software modules to assist programmers in enhancing efficiency, flexibility, and robustness An Extended Machine from the users
More informationDistributed File Systems
Distributed File Systems Mauro Fruet University of Trento - Italy 2011/12/19 Mauro Fruet (UniTN) Distributed File Systems 2011/12/19 1 / 39 Outline 1 Distributed File Systems 2 The Google File System (GFS)
More informationThe Advantages of CorBA For Network Based Training Systems
Support of multimedia services for distributed network training applications in CORBA-3 Fausto Rabitti CNUCE-CNR, Via S. Maria, 36, Pisa, Italy Abstract In this paper, fundamental technological issues
More informationWhat is Middleware? Software that functions as a conversion or translation layer. It is also a consolidator and integrator.
What is Middleware? Application Application Middleware Middleware Operating System Operating System Software that functions as a conversion or translation layer. It is also a consolidator and integrator.
More informationPERFORMANCE COMPARISON OF COMMON OBJECT REQUEST BROKER ARCHITECTURE(CORBA) VS JAVA MESSAGING SERVICE(JMS) BY TEAM SCALABLE
PERFORMANCE COMPARISON OF COMMON OBJECT REQUEST BROKER ARCHITECTURE(CORBA) VS JAVA MESSAGING SERVICE(JMS) BY TEAM SCALABLE TIGRAN HAKOBYAN SUJAL PATEL VANDANA MURALI INTRODUCTION Common Object Request
More informationAn Overview of CORBA-Based Load Balancing
An Overview of CORBA-Based Load Balancing Jian Shu, Linlan Liu, Shaowen Song, Member, IEEE Department of Computer Science Nanchang Institute of Aero-Technology,Nanchang, Jiangxi, P.R.China 330034 dylan_cn@yahoo.com
More informationDesigning a Cloud Storage System
Designing a Cloud Storage System End to End Cloud Storage When designing a cloud storage system, there is value in decoupling the system s archival capacity (its ability to persistently store large volumes
More informationHow To Balance A Single Failure With A Single Power Of Two (Sus)
Ranking Service Units for Providing and Protecting Highly Available Services with Load Balancing A. Kanso, F. Khendek, A. Hamou-Lhadj Electrical and Computer Engineering Department Concordia University
More informationReal-time Protection for Hyper-V
1-888-674-9495 www.doubletake.com Real-time Protection for Hyper-V Real-Time Protection for Hyper-V Computer virtualization has come a long way in a very short time, triggered primarily by the rapid rate
More informationCisco and EMC Solutions for Application Acceleration and Branch Office Infrastructure Consolidation
Solution Overview Cisco and EMC Solutions for Application Acceleration and Branch Office Infrastructure Consolidation IT organizations face challenges in consolidating costly and difficult-to-manage branch-office
More informationOracle WebLogic Server 11g Administration
Oracle WebLogic Server 11g Administration This course is designed to provide instruction and hands-on practice in installing and configuring Oracle WebLogic Server 11g. These tasks include starting and
More informationProviding Load Balancing and Fault Tolerance in the OSGi Service Platform
Providing Load Balancing and Fault Tolerance in the OSGi Service Platform ARNE KOSCHEL, THOLE SCHNEIDER, JOHANNES WESTHUIS, JÜRGEN WESTERKAMP Faculty IV, Department of Computer Science University of Applied
More informationIngegneria del Software II academic year: 2004-2005 Course Web-site: [www.di.univaq.it/ingegneria2/]
Course: Ingegneria del Software II academic year: 2004-2005 Course Web-site: [www.di.univaq.it/ingegneria2/] Middleware Technology: Middleware Applications and Distributed Systems Lecturer: Henry Muccini
More informationAdministering a Microsoft SQL Server 2000 Database
Aug/12/2002 Page 1 of 5 Administering a Microsoft SQL Server 2000 Database Catalog No: RS-MOC2072 MOC Course Number: 2072 5 days Tuition: $2,070 Introduction This course provides students with the knowledge
More informationBlackboard Collaborate Web Conferencing Hosted Environment Technical Infrastructure and Security
Overview Blackboard Collaborate Web Conferencing Hosted Environment Technical Infrastructure and Security Blackboard Collaborate web conferencing is available in a hosted environment and this document
More information2.1 What are distributed systems? What are systems? Different kind of systems How to distribute systems? 2.2 Communication concepts
Chapter 2 Introduction to Distributed systems 1 Chapter 2 2.1 What are distributed systems? What are systems? Different kind of systems How to distribute systems? 2.2 Communication concepts Client-Server
More informationICT Systems for Business Networking. B2B Messaging
B2B Messaging Note. The content of this document is mainly drawn from some papers (see references) and it is for educational purpose only. Table of contents 1 INTRODUCTION...3 2 E-MAIL...3 3 WHAT IS MESSAGING?...4
More informationDeploying Rule Applications
White Paper Deploying Rule Applications with ILOG JRules Deploying Rule Applications with ILOG JRules White Paper ILOG, September 2006 Do not duplicate without permission. ILOG, CPLEX and their respective
More informationState Transfer and Network Marketing
Highly Available Trading System: Experiments with CORBA Xavier Défago, Karim R. Mazouni, André Schiper Département d Informatique, École Polytechnique Fédérale CH-1015 Lausanne, Switzerland. Tel +41 21
More informationLSKA 2010 Survey Report Job Scheduler
LSKA 2010 Survey Report Job Scheduler Graduate Institute of Communication Engineering {r98942067, r98942112}@ntu.edu.tw March 31, 2010 1. Motivation Recently, the computing becomes much more complex. However,
More informationA Network Monitoring System with a Peer-to-Peer Architecture
A Network Monitoring System with a Peer-to-Peer Architecture Paulo Salvador, Rui Valadas University of Aveiro / Institute of Telecommunications Aveiro E-mail: salvador@av.it.pt; rv@det.ua.pt Abstract The
More information