This release of the Data Mapping Tool has been rewritten in Java and Eclipse. In addition, the following enhancements and changes have been introduced:
Data is now stored in local XML files.
RDBMS tables are no longer created during the DDM drag-and-drop operation. GFB schemas can be changed, columns renamed or deleted; even whole MU/PE subtables can be removed from the field table (GFFT). The RDBMS tables are only created by the Event Replicator Target Adapter during the actual data replication.
The GFB schema name you specify when you create the schema will now be used for the resulting RDBMS table name. Once you have created a GFB schema for a relational database from a DDM, you can rename it and the fields within the schema. These updates will be reflected in the table and columns names of the RDBMS table.
For more information about renaming schemas and schema fields, read Renaming Schemas and Renaming Schema Fields.
You can now drag and drop single fields from a DDM onto existing RDBMS columns to create or modify a GFB schema that maps data to existing RDBMS tables.
For more information about dragging and dropping individual fields, read Creating the Schema from Individual Fields in the DDM.
Once you have created a GFB schema for a relational database from a DDM, you can redefine (split) fields within the schema. This allows the data in the field to be redefined over more than one column in the resulting RDBMS table.
Note:
Attempts to redefine schem fields require that Event Replicator for Adabas 3.2.1 be
installed and in use at your site.
For more information about redefining fields in a GFB schema, read Redefining Schema Fields.
Once you have created a GFB schema for a relational database from a DDM, you can change the primary key for a table. In addition, you can create a composite key from one or more fields in the schema.
Note:
Attempts to create composite keys require that Event Replicator for Adabas 3.2.1 be
installed and in use at your site.
For more information about creating composite keys in a GFB schema, read Specifying Keys.
When creating the GFB schema, the values for the RDBMS Format field have changed to match those generated for the Event Replicator Target Adapter. For example, the value "A - Alphanumeric" now appears as "S - String".
When generating the GFB and field table, the statistics shown for (MU) fields have changed. The statistics now show the ending occurrence number instead of the number of occurrences.
Note:
Support for 32-bit Linux operating systems will be dropped in a future
version.
