Data Migration / Integrating Data Systems
While data migration may be a once off event, there are other times where data may need to be migrated more than once or where disparate data systems may need to be integrated with each other.
i-Con is the perfect tool for all of your data integration needs. I-Con’s mapping facility means that data can be profiled and integrated, or passed, to another system with a different data structure in real time or as a once off service.
i-Con pulls information from a database (or databases), formats it to meet the integration requirements of the new database or application and the passes the formatted data on. Any errors are logged by the i-Con monitor which sends a notification to the data technician to be resolved.
Examples of databases sources that can be migrated or integrated include: Flat files, XML files, MS SQL, Oracle, MySQL, UniVerse, jBase and many more.
Because i-Con already has the modules required to integrate between these databases a solution to meet your requirements can be generated quickly and at a low cost . For more information view or data migration service [link to data migration service page]
SQL Policy Data Migration to XMLife
An insurance client required data migration from an SQL database to XMLife in order to import the data into the target Policy Management System database.
In order to ensure the completeness of the migration a verification system was implemented that allowed the client to keep track of the total number of records before and after processing. If numbers did not match the problem was investigated and a re-run scheduled with exceptions reconciled and documented.
The solution allowed for an XMLife XML document to be received and validated. If the received document was not a valid XML document an error was returned and a notification was sent to a specified email account. The XML file was then passed to an i-Con component that could translate the data to conform to the Policy Management System.
Lastly a mapping component was developed to map the XMLife document to the Policy Management System database files, each node in the template was configured to write to a specified file/record/position in the database. Each XML node had the ability to write to more than on position in the database.