1 Course overview grouped by System integration software types: 1.Homogeneous ERP systems integrated by using a common database. 2.Heterogeneous ERP systems.

Slides:



Advertisements
Similar presentations
Transactions generalities 1 Transactions - generalities.
Advertisements

Data recovery 1. 2 Recovery - introduction recovery restoring a system, after an error or failure, to a state that was previously known as correct have.
Distributed databases 1. 2 Outline introduction principles / objectives problems.
1 Term 2, 2004, Lecture 6, TransactionsMarian Ursu, Department of Computing, Goldsmiths College Transactions 3.
1 Term 2, 2004, Lecture 9, Distributed DatabasesMarian Ursu, Department of Computing, Goldsmiths College Distributed databases 3.
Database Systems: Design, Implementation, and Management
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Chapter 6 Data Design.
1 Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal or quotation. An Introduction to Data.
Database System Concepts and Architecture
Executional Architecture
Chapter 10: The Traditional Approach to Design
Systems Analysis and Design in a Changing World, Fifth Edition
IDA / ADIT Lecture 10: Database recovery Jose M. Peña
TRANSACTION PROCESSING SYSTEM ROHIT KHOKHER. TRANSACTION RECOVERY TRANSACTION RECOVERY TRANSACTION STATES SERIALIZABILITY CONFLICT SERIALIZABILITY VIEW.
Properties of Data Replication : Replication can increase read performance Replication can be used to integrate heterogeneous systems that uses different.
Why should a database transaction be atomic?. ABORT = Removal of the updates of a transaction An abort is implemented by a roll back recovery where the.
Lars Frank: 1971 Cand. Scient. in computer science (Datalog) and math HD in organization Database consultant (primært i banksektoren) 1994-
ISOM Distributed Databases Arijit Sengupta. ISOM Learning Objectives Understand the concept and necessity of distributed databases Understand the types.
Workflow Management Kap. 3. Management of Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.
Enterprise Systems Distributed databases and systems - DT
Workflow Management Kap. 4. Analyzing Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.
Appendix A The Future of Workflows Wil van der Aalst has copyrights to almost all figures in the following slideshow made by Lars Frank.
Distributed databases
1 Chapter 3. Synchronization. STEMPusan National University STEM-PNU 2 Synchronization in Distributed Systems Synchronization in a single machine Same.
Properties of Data Replication : Replication can increase read performance Replication can be used to integrate heterogeneous systems that uses different.
The ACID properties of transactions: Atomicity = the all or nothing update property. Consistency = if a database is consistent before a transaction is.
1 Countermeasures against Consistency Anomalies in Databases with Relaxed ACID Properties. By Lars Frank Copenhagen Business School.
Transaction Management and Concurrency Control
Distributed DBMSPage © 1998 M. Tamer Özsu & Patrick Valduriez Outline Introduction Background Distributed DBMS Architecture Distributed Database.
Transaction Management and Concurrency Control
Chapter 11 Grid Concurrency Control 11.1 A Grid Database Environment 11.2 An Example 11.3 Grid Concurrency Control (GCC) 11.4 Correctness of GCC 11.5 Features.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 17 Client-Server Processing, Parallel Database Processing,
TRANSACTION PROCESSING TECHNIQUES BY SON NGUYEN VIJAY RAO.
 Mechanism for restoring a database quickly and accurately after loss or damage  RESPONSIBILITY OF ?????  Recovery facilities: Backup Facilities Backup.
How can ERP improve a company’s business performance?  Prior to ERP systems, companies stored important business records in many different departments.
Workflow Management Kap. 1. Organizing Workflows
Client/Server Databases and the Oracle 10g Relational Database
DBSQL 7-1 Copyright © Genetic Computer School 2009 Chapter 7 Transaction Management, Database Security and Recovery.
Session-9 Data Management for Decision Support
Chapter 6. Concurrency control Databases and Applications with Relaxed ACID Properties.
Workflow Management introduktion: Wil van der Aalst has copyrights to the slides conserning his book about Workflow Management. However, some of the slides.
Massively Distributed Database Systems - Distributed DBS Spring 2014 Ki-Joune Li Pusan National University.
Why should a database transaction be atomic?. ABORT = Removal of the updates of a transaction An abort is implemented by a DBMS roll back recovery where.
Distributed Database Systems Overview
Distributed Databases Midterm review. Lectures covered Everything until (including) March 2 nd Everything until (including) March 2 nd Focus on distributed.
Chapter 15 Recovery. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.15-2 Topics in this Chapter Transactions Transaction Recovery System.
Distributed Databases DBMS Textbook, Chapter 22, Part II.
Databases Illuminated
 Distributed file systems having transaction facility need to support distributed transaction service.  A distributed transaction service is an extension.
Overview of DBMS recovery and concurrency control: Eksemplerne er fra kapitel 3 I bogen: Lars Fank Databaser Teori og Praksis ISBN
INTRODUCTION TO DBS Database: a collection of data describing the activities of one or more related organizations DBMS: software designed to assist in.
1 Distributed Databases Chapter 21, Part B. 2 Introduction v Data is stored at several sites, each managed by a DBMS that can run independently. v Distributed.
Management Information Systems, 4 th Edition 1 Chapter 8 Data and Knowledge Management.
Chapter 20 Transaction Management Thomas Connolly, Carolyn Begg, Database System, A Practical Approach to Design Implementation and Management, 4 th Edition,
Introduction to Distributed Databases Yiwei Wu. Introduction A distributed database is a database in which portions of the database are stored on multiple.
Distributed Database Management Systems. Reading Textbook: Ch. 1, Ch. 3 Textbook: Ch. 1, Ch. 3 For next class: Ch. 4 For next class: Ch. 4 FarkasCSCE.
Distributed DBMS, Query Processing and Optimization
Chapter 1 Database Access from Client Applications.
DISTRIBUTED DATABASES AND DDBMS. Learning Objectives  Describe various DDBMS implementations  Explain how database design affects the DDBMS environment.
1 Chapter 22 Distributed DBMSs - Concepts and Design Simplified Transparencies © Pearson Education Limited 1995, 2005.
SAP Overview.
On-Line Transaction Processing
Transaction Management
CS 632 Lecture 6 Recovery Principles of Transaction-Oriented Database Recovery Theo Haerder, Andreas Reuter, 1983 ARIES: A Transaction Recovery Method.
Outline Introduction Background Distributed DBMS Architecture
Distributed Databases
Presentation transcript:

1 Course overview grouped by System integration software types: 1.Homogeneous ERP systems integrated by using a common database. 2.Heterogeneous ERP systems from different suppliers may be integrated by using relaxed ACID properties. 3.Workflows and Relaxed transaction can send subtransactions to other systems and they may use a common (distributed) database. 4.Data warehouses integrate distributed data by sending data to a common data warehouse database by using ETL (Extract, Transform, and Load) of data from the operative systems.

2 Work flow example with insurance claims. What are the differences between Work flow diagrams and Flow chart diagrams?

3 Petri Net is an attempt to standardize Work Flows: Transition = Task. Token = Case with a transaction illustrated as a black dot in a place. Place = Queue for cases/transactions before a transition.

4 Terminology of WorkFlow Management Coalition Task = Atomic logic activity in a process. Case = Transaction in a process. Place = Queue for cases/transactions before a transition. Process = A set of tasks and a set of conditions that determine the order of the tasks.

Workflow for making mobile control of supplier deliveries. Delivery larger than ordered Delivery matches an Orderline Delivery less than ordered Delivery is not ordered Select a con- trol action Product deliveries Orderlines are replicated to the mobile controllers New Supplier orders. Orderlines Reduced product delivery AND JOIN Update the local stock Replicate the mobile registrations to the central ERP system Error reports Accepted product deliveries Accepted product deliveries End of workflow AND SPLIT Reduced orderline Input Input is supplier orders or deliveries. What is the most important part of the workflow from a system integration point of view?

Workflow for making mobile control of supplier deliveries. Delivery larger than ordered Delivery matches an Orderline Delivery less than ordered Delivery is not ordered Select a con- trol action Product deliveries Orderlines are replicated to the mobile controllers New Supplier orders. Orderlines Reduced product delivery AND JOIN Update the local stock Replicate the mobile registrations to the central ERP system Error reports Accepted product deliveries Accepted product deliveries End of workflow AND SPLIT Reduced orderline Input Input is supplier orders or deliveries. How would you implement the database of the workflow?

A:

Integrated E-commerce workflows: 1.Design the workflow between an e-commerce system and an ERP system that manage the stocks of products? 2. Is the possible to use the ERP system of the suppliers if a product is out of stock?

Example: Petri net Work flow for global E-commerce transactions where the stocks are in the locations of the different suppliers. OR split

Sub- Petri net of activity 2 When are the suborders committed globally in the location of the suppliers? AND split OR split AND join

Exercise The figure illustrates an ER-diagram of a car rental company like Hertz or Avis. Design a workflow for the car rental company including reservation, car pic up, car return, and car return service.

Exercise: Design a workflow for producing healthy patients. ER-diagram for a hospital.

Opgave 1.30 Beskriv databasen for et transportfirma og dets underleverandører med et integreret logistikstyringssystem, hvor pakker kan indsættes i collies, som herefter kan indsættes i containers, der kan transporteres af firmaet selv eller andre operatører/underleverandører. Transportruternes enkelte dele kaldes ”legs”. Det er vigtigt for transportfirmaet altid at vide, hvor en pakke er også selv om der er opstået fejl, hvor f. eks. en pakke, collie eller container er blevet beskadiget og derefter genpakket. Det er også vigtigt altid at kunne vælge den optimale transportmulighed, som kan afhænge af både transporttid og pris. Beskriv herefter et workflow for det integrerede transportsystem.

Hertil

Concept definitions used in logistics: Pallet = wooden skeleton where packages may be stored in such a way that they all can be moved by a truck. Collie = alle the packages that are stored on a pallet(palle). Leg = Route or subroute where the transportation does not have stops

ER-diagram of a logistics management system Transport Orders Customers Transport medias like ships, airplanes, and trucks. Physical containers Scheduled routes and legs Orderlines Packages, Collies and Containers Locations Route-leg hierarchy Package- Collie hierarchy Routes and legs from to Damage relationship from to Container-routes relationships of order 3 Transport operator Describe the local databases in the central location of the transport company, the locations of the integrated transport suppliers, and the mobile locations of the Transport medias. Design a workflow with focus on the integration of the local database locations.

17 The ACID properties are implemented by a DBMS (DataBase Management System). Relaxed ACID properties are implemented by the application programs. Atomicity Concistency Isolation Durability

18 Evaluation of distrubution architectures Evaluation criteria Distribution architectures Synchronous distributed database management system (DDBMS) Central database with distributed clients Multidatabases with flexible transactions. (Relaxed ACID properties) Hot backup possibility n-safe and mirroringOnly mirroring is possible 0- safe, 1 safe and mirroring Read performance/ capacity BestWorstAverage Write performanceWorstAverageBest Blocking possibilityYesNono Ease of failure recovery Worst (The systems are very complex) Best Disaster recoveryBestWorstAverage The probability of lost data[1][1] Best. p n Worst p Average Transaction loggingNot supported Recommended Availability[2][2]1-q n 1-q1-q n AtomicityBest ConsistencyBest Worst IsolationBest Worst DurabilityBest Develop-ment costsBest Worst [1][1] The probability of lost data as a function of the probability, say p, of a local disaster. [2][2] The availability as a function of the probability, say q, of a local site failure.

19 Evaluation of distribution architectures 1. Evaluation criteria Synchronous distributed database management system (DDBMS) Central database with distributed clients Multidatabases with flexible transactions. Hot backup possibility n-safe and mirroringOnly mirroring is possible 0- safe, 1 safe and mirroring Read per- formance/ capacity BestWorstAverage Write per- formance WorstAverageBest Blocking possibility YesNo Ease of failure recovery Worst (The systems are very complex) Best Ease of disaster recovery BestWorstAverage

20 Evaluation of distribution architectures 2. Evaluation criteria Synchronous distributed database management system (DDBMS) Central database with distributed clients Multidatabases with flexible transactions. The probability of lost data Best p n Worst pAverage Logging of the update transaction Not supported Recommended Availability1-q n 1-q1-q n AtomicityBest ConsistencyBest Worst IsolationBest Worst DurabilityBest Develop- ment costs Best Worst

End of session Thank you !!!

22 Database recovery: Exersice. A DB logfile stores before images and after images of all dataabase updates. The logfile also stores transaction starts and commitments. Periodically the checkpoint records are logged with the IDs of all non committed transactions. How is it possible to recover transaction types 1 to 5 after a transaction failure and a CPU failure respectively?

23 Two Phase Commit (2PC) and Two Phase Locking (2PL) Exercise. Describe the basic principles for the Two Phase Commit (2PC) recovery protocol and the Two Phase Locking (2PL) protocol for concurrency control.

24 Exercise: Describe exactly when a transaction is committed. What is the difference between failure and disaster recovery? Is the durability property always trustworthy? Is it possible to run batch programs that lock many thousends records concurrent with on line updates that only locks a few records?

25 ACID kravene til transaktionsafvikling: Atomicity = udelelighed. Concistency = konsistensen skal bevares Isolation = en transaktions opdateringer må ikke ses af andre før de er committede. Durability = Holdbarhed dvs. committede opdateringer skal kunne retableres

26 Full ACID løsninger.Relaxed ACID løsning.