Skip to content

XAware Community

Get the Flash Player to see this player.
Flash Image Rotator Module by Joomlashack.
XAware 5.6
Need Help
Webinars and Events
Advanced Tutorials
Webinars and Events

You are here: Home arrow Forums
XAware Community Forums
Welcome, Guest
Please Login or Register.    Lost Password?
Pattern for a successful data migration (1 viewing) (1) Guest
Go to bottom Post Reply Favoured: 0
TOPIC: Pattern for a successful data migration
pdango (User)
XAware user
Posts: 8
User Offline Click here to see the profile of this user
Pattern for a successful data migration 12 Years, 3 Months ago Karma: 2  
When an enterprise has a requirement to migrate information from a legacy licensed relational database system such as Oralce or DB2 to MySql, XAware can play a significant role in realizing such a requirement.

Normally, in this exercise, one would identify and define the target data architecture where the legacy data would eventually be recorded. The target data architecture can be different from the source data architecture. The application team may change the target data architecture based on their experience with the source data architecture in terms of its flexibility to change and scalability . Such changes can range from improvements in data format, structure, and navigation to overall performance of the data architecture. In this situation, the migration exercise becomes complicated as it now includes not only a straightforward movement of data from one database to another, but now requires data structure transformation, format mapping, and value translation.

An enterprise data architecture is usually organized into domains of information. For example, information about customers are maintained in the Customer domain and information about user authentication and authorization are maintained in the Security domain. Each domain has its own data model or schema. A XML schema then can be created from the database schema. In XAware, given such a XML schema, a developer can easily create an XML document instance and use it as the data template or the Common Information Model (CIM) for the data migration.

The CIM drives the collection of relevant information from the legacy source system. Using XAware, executable XML elements or attributes are placed in specific nodes in the CIM. Executable XML or attributes in XAware are simply references to configurable components that are invoked by the XAware engine when it is processing the CIM. One such component in XAware is the SQL BizComponent. The SQL BizComponent provides the capability to access most relational database systems and manipulate data stored in these systems. Using this component, one can retrieve data from the underlying database system without writing any code by simply using the wizards to configure the component. This is so because it has the capability to retrieve the metadata stored in the these systems and mapped the selected data to specific elements or attributes in the CIM. After the components are invoked by the XAware engine, a fully realized CIM instance is created with information from the source system. The CIM instance is now the input to the loading process that populates the target database system.

In the same manner that the CIM drives the collection of data, it too can be used to drive the population of the target data model. As the CIM is a reusable data template, components are placed in specific nodes to read the fully realized CIM mentioned previously and to store the information in the target database. Because it is configurable to either insert, update, select, or even delete records, the SQL BizComponent can be used as well in this phase of the migration. In this phase, one can also include built-in functions provided in XAware that perform data format mapping as well as value translations. A subset of these functions include string manipulations, date and time conversion, math formulas, and xml based code value translation.

Because MySql and XAware are open source technologies, enterprises can deploy them to support business activities without incurring licensing fees. Although they may incur the overhead of their staff using these technologies, but such an overhead is not high because MySql and XAware implement standard based technologies such as ANSI SQL and XML. Such technologies are not only common and prevalent in the industry, but they are easy to learn and use.

Because relational database systems, including MySql, expose the metadata about the data they maintain and XAware provides the capability to use the metadata, migrating data among them can be realized without practically writing code.
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
      Topics Author Date
    thread link
Pattern for a successful data migration
pdango 2007/11/08 19:02
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop

Community Login

Get the Flash Player to see this player.
Flash Image Rotator Module by Joomlashack.
Free Training
QuickStart Packages
Image 4 Title
Image 5 Title