Data Integration can be a tedious and error-prone process. This is why MetaSuite is aimed at making the important steps in this process fail-safe and manageable for end-users with few technical skills. These two important steps have been seperated in proprietary components within MetaSuite, called MetaStore Manager and MetaMap. Here's a short introduction.

MetaStore Manager (to maintain data descriptions)

MetaStore Manager guides you through the process of building a data descriptions dictionary, which can be obtained in four ways:

  • By creating data definitions manually for different source types. Dictionary Files, Records and Fields can be defined for standard Files, Adabas File Groups, Datacom File Groups, IMS PCB, SQL Table Groups, IDMS Sub Schemas, Supra Databases, XML files etc...
  • By collecting or capturing files directly from the database via an ODBC connection or from a specific file describing the record structures in one of the supported languages or formats. This can be done from Cobol Copy Books, PL/I Include Books, IDMS punches, SAP DMI, DB2 DDL, etc... During the collection process, MetaStore also generates the required load and unload scripts for various RDBMS types
  • By exporting and importing data definitions from other MetaSuite repositories;
  • By investigating data (CSV files, XML files) using the parsing tool.

All descriptions of all data sources and targets - including any RDBMS that runs on either Z/OS, BS/2000, UNIX, Linux or Windows - are stored into the MetaStore Repository. MetaStore Manager provides a central point of reference that is vital towards identifying the data integration platform and the source data held within it.

MetaMap (to define the data flow)

The transformation of operational data into a format that fits the target environment is achieved via the MetaMap application of MetaSuite. MetaMap enables users to quickly and easily create data integration mappings. Those mappings can be simple or highly complex. A Mapping Wizard and a Structured Editor guides users through the creation of the mapping rules, which define the cleaning, filtering, transformation, and consolidation processes.

Generating the MetaMap model will lead to a COBOL source code and a run script, which is operating system and COBOL vendor specific. The modification of the business map and technical rules, and the subsequent code generation is performed in the background. The complete run-time process can be customized to ensure performance optimization and to deal with specific conditions not taken care of in the rules. All process steps can be fully automated to reduce the development time and increase ease of use.

Back to previous page.Back to previous page

Customer stories