Metadata element renaming affects object types, property types, and API-specific property types. In r7.3, much of the metadata in CA ERwin DM was renamed. These name changes fall into two categories:
Overall, this change is transparent and will not affect your day-to-day work. Awareness of this change, however, is important if you use the API and the new ODBC interface, and have some familiarity with the pre-r7.3 metadata names. Existing API applications and scripts must be updated to account for any new metadata names before use with CA ERwin DM. To assist you with this updating process, the following CSV files are provided with the CA ERwin DM installation in the <Program Files>\CA\ERwin Data Modeler r9\metadata changes:
Provides a list of the full set of changed metadata names. It is a two column CSV file that contains the old name, new name pairs.
Provides the subset of metadata names that appear as changed in XML files.
Note: Not included in this file are those metadata names where the only change was the replacement of space characters with underscores, since CA ERwin DM's XML format already uses underscores in object type names and property type names.
Provides a list of the API-only property names that were renamed.
The metadata includes object and property classes, object aggregations, and property associations.
Define the type of objects that may occur within a model such as an entity class, an attribute class, or a relationship class.
Define the type of properties an object may have such as the Name property, Comment property, or Parent_Domain_Ref property.
Identify an ownership relationship between classes of objects, such as a model that owns entities, or entities that own attributes, and so on.
Define property usage by object classes. For example, the metadata includes property associations for every object class that has the Name property.
The following diagram shows the organization of the metadata:
CA ERwin DM organizes data as a group of linked model sets. The model sets are arranged in a tree-like hierarchy with a single model set at the top.
The top model set contains the bulk of the modeling data. The API uses the abbreviation EMX to identify the top model set.
The EMX model set owns a secondary model set, abbreviated as EM2, which contains user interface settings and user options for CA ERwin DM services such as Forward Engineering, Complete Compare, and so on.
The API clients access the model data by constructing a session and connecting it to a model set using the Session component.
A model set contains several levels of data. It contains the data the application manipulates, such as entity instances, attribute instances, relationship instances, and so on.
The model set also contains metadata, a description of the objects and properties that may occur within the application's data.
Each metadata object may include one or more tags. A tag is a metadata object property that conveys certain descriptive meta information, such as if an object class is logical, physical, valid for a specific target DBMS, and so on.
Note: A tag on an object aggregation overrides the identical tag set on the associated owned object class. A tag on a property association overrides the identical tag set on the associated property class.
The following table lists some of the EMX metadata tags:
|
Tag Name |
Datatype |
Description |
|---|---|---|
|
tag_Bit_Field_Values … tag_Bit_Field_Values_2 |
String |
Describes valid values for a bit field property. A combination of values from the description list can be used as a value for the property. The descriptions are grouped as follows: {<value>|<string equivalent>|<internal>} |
|
DBMS_Brands_And_Versions |
Integer, vector |
Defines conditions when an object or property class is available for physical modeling with the specific DBMS. Assumes that the tag_Is_Physical has a TRUE value. Absence of the tag indicates that the class is available for all DBMS targets, but only if tag_Is_Physical has a TRUE value. A NULL value for the tag indicates that the class is not available for any DBMS. DBMS brand IDs are described in the next table. |
|
DBMS_Is_Represented |
Integer, vector |
Defines conditions when an object or property class represents a concept in the specific DBMS. Assumes that the DBMS_Brands_And_Versions tag is valid for the class. Absence of the tag indicates that the class is available for all DBMS targets, but only if the DBMS_Brands_And_Versions tag is valid for the class. A NULL value for the tag indicates that the class is not available for any DBMS. DBMS brand IDs are described in the next table. |
|
DBMS_Is_Top_Level_Object |
Integer, vector |
Defines conditions when an object class is considered top level, such as when it has a CREATE or DROP statement associated with it for the specific DBMS. Assumes that the DBMS_Is_Represented tag is valid for the class. Absence of the tag indicates that the class is available for all DBMS targets, if the DBMS_Is_Represented tag is valid for the class. A NULL value for the tag indicates that the class is not a top level object for any DBMS. DBMS brand IDs are described in the next table. |
|
tag_Enum_Values … tag_Enum_Values_10 |
String |
Describes valid values for an enumerated property. Only one value from the description list can be used as a value for the property. The descriptions are grouped as follows: {<value>|<string equivalent>|<internal>} |
|
tag_Is_Font_Or_Color |
Boolean |
TRUE for classes responsible for model data visualization. |
|
tag_Is_For_Data_Movement |
Boolean |
TRUE for an object or property class that is available for dimensional and data warehouse modeling. |
|
tag_Is_Graphic_Data |
Boolean |
TRUE for classes responsible for model data visualization. |
|
tag_Is_Logical |
Boolean |
TRUE for an object or property class that is available for logical modeling. |
|
tag_Is_Physical |
Boolean |
TRUE for an object or property class that is available for physical modeling. |
|
tag_Holds_User_Settings |
Boolean |
TRUE for classes responsible for storing options for CA ERwin DM features. |
DBMS specific tags, such as DBMS_Brands_And_Versions, DBMS_Is_Represented, and DBMS_Is_Top_Level_Object, are vectors and organize data in groups of triplets as described below:
Specifies the DBMS brand ID.
Specifies the minimum version level for the DBMS, multiplied by 1000.
Specifies the maximum version level for the DBMS, multiplied by 1000; 999000 indicates the absence of a maximum level.
For example, consider the property Oracle_Index_Partition_Type. It contains a DBMS-specific tag, DBMS_Brands_And_Versions. This tag contains three elements specific for this property: 1075858979, 8000, 999000. The first element, the DBMS brand ID, is for Oracle, which is 1075858979. The second element, the minimum version level for this DBMS, multiplied by 1000, is 8000. This means the minimum DBMS version level for this DBMS, which is Oracle, is 8.0. The third element, the maximum version level for this DBMS, is 999000, which means there is no maximum version level for this DBMS.
The following table lists DBMS brand IDs:
|
DBMS Brand |
DBMS Brand ID |
|---|---|
|
DB2 |
1075858978 |
|
DB2 for i |
1075859019 |
|
DB2 LUW |
1075858977 |
|
Informix |
1075859006 |
|
ODBC |
1075859009 |
|
Oracle |
1075858979 |
|
Progress |
1075859010 |
|
SAS |
1075859013 |
|
SQL Server |
1075859016 |
|
Sybase |
1075859017 |
|
Teradata |
1075859018 |
The metadata organization makes use of generalizations with the ability to derive a specialized object class from an abstract object class using generalization association. Specialized classes can then be marked as abstract, and then they can be used as a source for further specializations.
Only instances of the concrete, non-abstract object classes may occur within the application's data. CA ERwin DM uses the generalization mechanism to flatten metadata by replicating aggregations, associations, and tags from the abstract object classes in the concrete object classes.
A unique metadata class identifies what type of metadata a model set contains.
Contains the bulk of model data such as entities and attributes. The class name is EMX and the class identifier is the value defined in the Application Environment component, category Application, property EMX_Metadata_Class.
Stores additional data such as user interface settings and user options for CA ERwin DM services such as Forward Engineering and Complete Compare. The class name is EM2 and the class identifier is the value defined in the Application Environment component, category Application, property EM2_Metadata_Class.
|
Copyright © 2016 CA Technologies.
All rights reserved.
|
|