Architecture for Integration and Migration of Information Systems by Using SOA Services across Heterogeneous System Boundaries

Architecture for Integration and Migration of Information Systems by Using SOA Services across Heterogeneous System Boundaries

Lars Frank, Rasmus Ulslev Pedersen
Copyright: © 2013 |Pages: 15
DOI: 10.4018/978-1-4666-4153-2.ch019
OnDemand:
(Individual Chapters)
Available
$37.50
Current Special Offers
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

The objective of this chapter is to describe how it is possible to integrate and/or migrate information system where local heterogeneous databases are involved. ERP (Enterprise Resource Planning) systems are very complex standardized information systems, and they are often vital for the companies that use them. Therefore, the authors use integration and migration of ERP systems as an example. Normally, ERP systems are migrated/converted overnight as it normally is not possible to integrate different ERP modules from different ERP suppliers. This is very risky as many types of industries cannot function without a running ERP system. The main focus of this chapter is to illustrate how it is possible to migrate/convert an ERP system module by module and thus minimizing the risk of staying without a functioning ERP system. In central databases, the consistency of data is normally implemented by using the ACID (Atomicity, Consistency, Isolation and Durability) properties of a DBMS (Data Base Management System). This is not possible if heterogeneous databases are involved and the availability of data also has to be optimized. Therefore, in this chapter, the authors use so called relaxed ACID properties across different database systems or ERP modules. The objective of designing relaxed ACID properties across different database systems is that the users can trust the data they use even if the involved database temporarily are inconsistent.
Chapter Preview
Top

Introduction

Database transactions are any logical operation on the data of the database. The ACID properties of a database are delivered by a DBMS to make database recovery easier and make it possible in a multi user environment to give concurrent transactions a consistent view of the data in the database. The ACID properties are consequently important for users that need a consistent view of the data. Information systems that use different DBMS systems can be integrated by using more or less common data and/or by exchanging information between the systems involved. In both situations, the union of the databases of the different systems may be implemented as a database with so called relaxed ACID properties where temporary inconsistencies may occur in a controlled manner. Therefore, the objective of implementing relaxed ACID properties it is that from a user’s point of view it must still seem as if traditional ACID properties were implemented in order to keep the local databases trustworthy for decision making.

In the following part of the introduction, we will first give an overview of how relaxed ACID properties may be implemented. Next, we will give an overview of how an ERP system with relaxed ACID properties across its modules may be used to migrate ERP modules one by one. Finally we will describe the objective of the chapter in more details.

Complete Chapter List

Search this Book:
Reset