Migration of data for iKnow application at EURM-a case study (original) (raw)
Related papers
AUTOMATED APPROACH FOR CUSTOMIZED DATA MIGRATION
Data migration is the process of moving data from one environment to a new one; it may be used to support migration from one database to another or between major upgrades of a database. The implementation of master data management may also require data migration. The data integration, ETL,ELT and replication, which are primarily concerned with moving data between existing environments, may be used in order to support the migration process .Data migration is often undertaken as a part of a broader application migration (for example: migrating from SAP to Oracle, consolidating SAP environments or migrating from one version of SAP to another. or when migrating to SaaS (software as a service) environments it is important for data migration to be automated as much as possible, especially where these applications have been acquired directly by the business rather than via IT. Data migration projects are undertaken because they support business objectives. There are costs to the business if it goes wrong or if the project is delayed, and the most important factor in ensur¬ing the success of such projects is close collaboration between the busi¬ness and IT. Whether this means that the project should be owned by the business— treated as a business project with support from IT—or wheth¬er it should be delegated to IT with the business overseeing the project is debatable, but what is clear is that it must involve close collaboration. This white paper is about the acquisition of FMG(Fast Moving Goods)business of one company(COM-1) by another company (COM-II) resulting in the merger of the FMG business of COM-I into COM-IIs. It involves migration of huge amount of data from one company to the other resulting from partial M&A between COM-I and COM-II keeping the following parameters in check -Data integrity, Time(duration of engagement),Cost of technology, Man hours sent, Downtime, Maintaining availability of application. Huge data migration is not only cumbersome but requires special tools and techniques for maintaining integrity of the data. Migration of data from one source (company) to the other (company) requires time and effort and has huge cost implications that are not visible on the surface and hence extensive design, planning and funding are needed. Various tools are evaluated for migration of data but owing to the complexity of the existing system which involves Open road as front end, tuxedo at middle tier and Oracle 10g at the backend and there were many critical business rules applied at all the three tiers, that needs to be taken into account while migrating the data. This involved lots of study and research in term of determining the best methodology for migration data from one landscape to another landscape. Please note the two landscapes may be on two entirely different platforms involving lots of complexity and contradictions. There was a need to study in details the application and hardware architecture of both the systems for the purpose of data migration /integration. For the purpose of data migration from one environment to another, all the validation (including Biz validation at front end and middleware and data referential and integrity validations at backend) should be considered and cannot be bypassed for the sake of migration.
Migration of Legacy Information Systems
Springer eBooks, 2008
This chapter addresses the problem of platform migration of large business applications, that is, complex software systems built around a database and comprising thousands of programs. More specifically, it studies the substitution of a modern data management technology for a legacy one. Platform migration raises two major issues. The first one is the conversion of the database to a new data management paradigm. Recent results have shown that automated lossless database migration can be achieved, both at the schema and data levels. The second problem concerns the adaptation of the application programs to the migrated database schema and to the target data management system. This chapter first poses the problem and describes the State of the Art in information system migration. Then, it develops a two-dimensional reference framework that identifies six representative migration strategies. The latter are further analyzed in order to identify methodological requirements. In particular, it appears that transformational techniques are particularly suited to drive the whole migration process. We describe the database migration process, which is a variant of database reengineering. Then, the problem of program conversion is studied. Some migration strategies appear to minimize the program understanding effort, and therefore are sound candidates to develop practical methodologies. Finally, the chapter describes a tool that supports such methodologies and discusses some real-size case studies.
A Comparative Review of Migration of Legacy Systems
International journal of engineering research and technology, 2017
The Modernization of Legacy System is made appealing by several features of SOA in today’s world and migration of applications to the Cloud. In order to carry out a comparative review on the decades old migration approaches are classified in to Early Migration Approaches, SOA Migration Approaches and Cloud Migration. A comparative review is presented among this categories to depict the migration requirements. This paper also provides the research opportunities in the context of migration of legacy systems focusing on Legacy System Understanding, Study of Artefacts and their Relationships. Keywords— Migration; SOA; Legacy Systems; Software Evolution
DARWIN: On the Incremental Migration of Legacy Information Systems 1
1994
As is painfully evident today, the deterioration of the transportation, education 2 , and other national infrastructures negatively impacts many aspects of life, business, and our economy. This has resulted, in part, when responses to short term crises discourage investing in infrastructure enhancement and when there are no effective means for infrastructure evolution. This paper responds to the deterioration of the information system (IS) infrastructure that has strong negative impacts on ISs, on the organizations they support, and, ultimately, on the economy. This paper addresses the problem of legacy IS migration by methods that mediate between short term crises and long term goals. It presents an effective strategy and a spectrum of supporting methods for migrating legacy ISs into a target environment that includes rightsized hardware and modern technologies (i.e., infrastructure) such as a client-server architecture, DBMSs and CASE. We illustrate the methods with two migration case studies of multi-million dollar, mission critical legacy ISs. The contribution of this paper is a highly flexible set of migration methods that is tailorable to most legacy ISs and business contexts. The goal is to support continuous, iterative evolution. The critical success factor, and challenge in deployment, is to identify appropriate portions of the IS and the associated planning and management to achieve an incremental migration that is feasible with respect to the technical and business requirements. The paper concludes with a list of desirable migration tools for which basic research is required. The principles described in this paper can be used to design future ISs and an infrastructure that will support continuous IS evolution to avoid future legacy ISs.
Introducing Legacy System Migration Technologies in an Academic Context: a Controlled Experiment
To verify whether or not migration technologies can be adopted, systematic and quantitative evaluations should be performed. In this paper we present the results of a controlled experiment aimed at assessing the usefulness of an Eclipse plug-in, named MELIS (Migration Environment for Legacy Information Systems). This plug-in has been developed to support the migration of legacy information systems to a web-enabled multi-tier target architecture according with an incremental migration strategy. The context of the experiment was constituted of master students in Computer Science at the University of Salerno. The subjects without COBOL programming experience, while half of them had J2EE programming experience. The results of the experiment confirmed that the use of MELIS increases the productivity with respect to the use of traditional development tools.
Modern computer systems are expected to be up continuously: even planned downtime to accomplish system reconfiguration is becoming unacceptable, so more and more changes are having to be made to ?live? systems that are running production workloads. One of those changes is data migration: moving data from one storage device to another for load balancing, system expansion, failure recovery, or a myriad of other reasons. This document gives the overview of all the process involved in Data Migration. Data Migration is a multi-step process that begins with an analysis of the legacy data and culminates in the loading and reconciliation of data into the new applications.
An efficient and simple technique of data migration
Every type of system may replace or enhance the functionality currently delivered by legacy systems to new system, regardless of the type of project/application; some data conversion may take place. Difficulties arise when we take the information currently maintained by the legacy system and transform it to fit into the new system. We refer to this process as data migration. Data migration is a common element among most system implementations. It can be performed once, as with a legacy system redesign, or may be an ongoing process as in storage of historical data in the form of a data warehouse. Some legacy system migrations require ongoing data conversion if the incoming data requires continuous cleansing. It should be that any two systems that maintain the same sort of data must be doing very similar things and, therefore, should map from one to another with ease. Legacy systems have historically proven to be far too lenient with respect to enforcing integrity at the atomic level of data. Another common problem has to do with the theoretical design differences between hierarchical and relational systems. In data migration one method apply in twice (i.e. automated and manual). This paper explores the steps to migrate date in form of manual, i.e. process of data migration without the help of any special tool those made for data migration. Manual data cleaning is commonly performed in migration to improve data quality, eliminate redundant or obsolete information, and match the requirements of the new system in correct and efficient form.
Data migration – A case based task
—Data migration is one of the vital tasks of Data integration process. It is always assumed to be most tedious as there will never be a systematic defined procedure. Each migration process is to be treated as unique as the input data sets will be different and the output format required is always unique based on the services provided as well as the user and data handler requirements. In the recent years data migration became the most vital process in various departments of public and private services due to technological advancements and big data handling requirements caused by the increase in acquired data volume. This paper discusses about data migration requirement, data migration strategy finalization and various stages of data migration process discussion of each stage and why complete automation of data migration is not feasible etc.