CA Erwin Data Modeler Release Notes

CA ERwin® Data Modeler

Release Notes r7.3

r7.3.8 SP2 Edition

This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be used or disclosed by you except as may be permitted in a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

CA Product References

This document references the following CA products: ■ CA ERwin® Data Modeler ■ CA ERwin® Model Manager

Contact CA

Contact Technical Support

For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.com/support, you can access the following: ■ Online and telephone contact information for technical assistance and customer services ■ Information about user communities and forums ■ Product and documentation downloads ■ CA Support policies and guidelines ■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about CA product documentation, you can send a message to [email protected].

If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs.

Documentation Changes

This Release Notes document is cumulative - it is updated as features are added or changed during the patch and Service Pack releases.The following list summarizes the documentation updates that have been made since the initial release (r7.3 GA) of CA ERwin Data Modeler: Chapter 1: New Features and Enhancements ■ Macro Added (r7.3.5)—Addition of the macro DatabaseConnection to the Forward Engineering Template macros. ■ Metadata Integration Bridges Updated (r7.3.2, r7.3.4 SP1, and r7.3.8 SP2)—List of Import/Export bridges added, removed, and renamed. ■ Enhancement made to Rename Column Dialog (r7.3.4 SP1). ■ Allow Special DBMS Characters check box added to the Derive Wizard, Naming Standards pane (r7.3.8 SP2). Chapter 2: System Information ■ Operating System Support - Note added regarding requirement that Administrative privileges are needed when installing, updating, or removing the software. ■ r7.3.8 SP2 includes certification on Microsoft Windows 7, and Microsoft Windows XP (SP3).

Chapter 3: Installation Considerations ■ Silent Install for CA ERwin Data Modeler and Crystal Reports (r7.3.6) - Overview and examples for performing a silent install of CA ERwin Data Modeler and Crystal Reports. Chapter 5: Known Issues ■ Known Issue With Meta Integration Bridges for Microsoft Office Excel (r7.3.8 SP2) - Import and Export issues when working with the Microsoft Office Excel bridges. ■ The silent install is not supported on the Windows 7 operating system.

Contents

Chapter 1: New Features and Enhancements 7

Support for Teradata 2.6/12 ...... 8 Model Validation Enhancements for Teradata ...... 9 Integrated SQL Query Tool ...... 9 ODBC-Based Metadata Access ...... 10 Crystal Reports 2008 Included with CA ERwin DM ...... 10 Enhancements to Complete Compare ...... 11 Features Added to Improve Complete Compare Performance with CA ERwin Model Manager ... 11 Advanced Options ...... 12 Type Resolution Wizard ...... 13 Change to Type Selection Filtering ...... 13 Demand Loading Enhancement ...... 13 Demand Loading and DB Sync ...... 14 Object Selection Enhancement ...... 14 Range Selection Enhancement ...... 14 "Explain" Button Added ...... 14 Template Editor for Forward Engineering Template Files ...... 15 Macro Enhancements ...... 15 Macro Added (r7.3.5) ...... 16 Universal File Close Dialog ...... 17 Enhancements to Open or Save a Model in XML Format ...... 17 Enhancements to Triggers ...... 18 Customize Model Explorer Display...... 19 Metadata Integration Bridges Updated (r7.3 Initial Release) ...... 20 Import Bridges Added/Removed ...... 20 Export Bridges Added/Removed ...... 20 Bridges Renamed ...... 20 Metadata Integration Bridges Updated (r7.3.2) ...... 22 Import Bridges Added/Removed ...... 22 Export Bridges Added/Removed ...... 22 Bridges Renamed ...... 22 Metadata Integration Bridges Updated (r7.3.8 SP2) ...... 24 Import Bridges Added/Removed ...... 24 Export Bridges Added/Removed ...... 24 Bridges Renamed ...... 25 Enhancement to Rename Column Dialog (r7.3.4 SP1) ...... 27 Allow Special Characters During Derive (r7.3.8 SP2) ...... 27 Database Support Update ...... 28

Contents 5

Databases Removed ...... 28 Databases Added ...... 28 User Interface Changes for Selected Databases ...... 28 Operating System Support Update ...... 29 Integration With Microsoft Visual Studio Team System 2008 Database Edition ...... 29 Metamodel Reference Documentation ...... 29 Compiled HTML Online Help ...... 30 Documentation Bookshelf ...... 30 Feature-Specific Training Videos ...... 31

Chapter 2: System Information 33

Operating System Support ...... 33 System Requirements ...... 34 Supported Target Server Databases ...... 34

Chapter 3: Installation Considerations 35

Installation Wizard on DVD ...... 35 Silent Install for CA ERwin DM and Crystal Reports (r7.3.6) ...... 36 Examples ...... 36 Important Note ...... 36 Installing VSTS Database Edition ...... 37

Chapter 4: General Considerations 39

Metadata Elements Renamed ...... 40 Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler ...... 41

Chapter 5: Known Issues 43

Double-Byte Character Display ...... 43 Known Issue With Meta Integration Bridges for Microsoft Office Excel ...... 43 Silent Install on Windows 7 ...... 43

Chapter 6: Documentation 45

PDF Guides ...... 45 New Release Notes PDF ...... 46 Release Numbers ...... 46

6 Release Notes

Chapter 1: New Features and Enhancements

This chapter of the Release Notes for CA ERwin Data Modeler (CA ERwin DM) documents new features and enhancements for r7.3.

This section contains the following topics: Support for Teradata 2.6/12 (see page 8) Model Validation Enhancements for Teradata (see page 9) Integrated SQL Query Tool (see page 9) ODBC-Based Metadata Access (see page 10) Crystal Reports 2008 Included with CA ERwin DM (see page 10) Enhancements to Complete Compare (see page 11) Template Editor for Forward Engineering Template Files (see page 15) Macro Enhancements (see page 15) Universal File Close Dialog (see page 17) Enhancements to Open or Save a Model in XML Format (see page 17) Enhancements to Triggers (see page 18) Customize Model Explorer Display (see page 19) Metadata Integration Bridges Updated (r7.3 Initial Release) (see page 20) Metadata Integration Bridges Updated (r7.3.2) (see page 22) Metadata Integration Bridges Updated (r7.3.8 SP2) (see page 24) Enhancement to Rename Column Dialog (r7.3.4 SP1) (see page 27) Allow Special Characters During Derive (r7.3.8 SP2) (see page 27) Database Support Update (see page 28) Operating System Support Update (see page 29) Integration With Microsoft Visual Studio Team System 2008 Database Edition (see page 29) Metamodel Reference Documentation (see page 29) Compiled HTML Online Help (see page 30) Documentation Bookshelf (see page 30) Feature-Specific Training Videos (see page 31)

Chapter 1: New Features and Enhancements 7

Support for Teradata 2.6/12

Support has been added for data modeling with Teradata Version 2.6 and Version 12. Editors have been added for the following objects: ■ Authorization ■ Cast ■ Database ■ File ■ Function ■ Join Index ■ Index (Key Group) ■ Macro ■ Method ■ Permission ■ Profile ■ Replication Group ■ Role ■ Stored Procedure

■ Table (Entity) ■ Trigger ■ User Id ■ View

You can access new features in the property editors from the Database menu or from the Model Explorer. Reverse Engineering and Forward Engineering functionality has been updated to support the new properties. Support is not provided for any password or encryption key information in the model.

For information on the individual Teradata property editors, see the online help.

8 Release Notes

Model Validation Enhancements for Teradata

You can create a Model Validation report before you forward engineer your model. The validation process checks for corrupt objects and reports other errors associated with correct forward engineering. A full suite of check model validation routines has been added for Teradata models. In a physical model, from the Tools menu choose Forward Engineering, then Check Model. You can also click the Check Model icon on the Database toolbar.

Click F1 in the Model Check dialog for detailed information about the objects and properties that are validated during a model check.

Integrated SQL Query Tool

The Query Tool provides an easy way to execute SQL SELECT queries against the model or against a database catalog. You can execute a query against the objects and properties in the current model, the metadata defining those objects and properties, and the action log that records the changes that are made to your model during the modeling session.

You can create new queries, open existing query files, or paste text from another source (such as a *.sql file) into a query.

Sample SQL queries based on the r7.2.x Report Template Builder reports are installed with the product in the \ODBC Reports\RTB Queries folder. Click the Open Query item on the Query Tool toolbar to open a sample report. Each sample report includes a comment summarizing the purpose of the query.

For more information on working with the Query Tool, see the ODBC Reporting Guide, which is located in the Doc subdirectory of your CA ERwin Data Modeler installation. You can also open this document from a shortcut on the Start menu.

Chapter 1: New Features and Enhancements 9

ODBC-Based Metadata Access

CA ERwin Data Modeler r7.3 allows you to use any third-party reporting tool that has ODBC capability to query CA ERwin Data Modeler metadata. For example, you can use queries you created in Excel, Access, Crystal Reports and Cognos and run them against the CA ERwin Data Modeler metadata. At this time only query syntax (SQL SELECT statements) is supported.

To enable this functionality, you activate the read-only ODBC-based driver provided with CA ERwin Data Modeler on the Integrations tab of the Options menu. This feature enables open access to the modeling metadata for reporting purposes.

This new feature lets you query one model at a time (the current model). Although you cannot query a model in CA ERwin Model Manager, you can query an open model from a mart, if it is the current model.

This feature is compliant with ANSI 92 specifications and therefore can be used with any standard ODBC query tool.

Crystal Reports 2008 Included with CA ERwin DM

Starting with CA ERwin DM r7.3, a licensed copy of Business Objects™ Crystal Reports® 2008 is provided with each copy of CA ERwin DM. The CA ERwin DM install wizard includes an option to install Crystal Reports 2008 edition.

With r7.3.6 or later, you can install Crystal Reports using a silent install. See the section on Silent Install under Installation Considerations below.

You can use CA ERwin DM as a data source to which you connect via Crystal Reports 2008. Two data sources are installed with CA ERwin DM: ■ ERwin - provides the option to select from among open models in the CA ERwin DM workplace ■ ERwin_current - reports on the current model in the CA ERwin DM workplace

The option to use Crystal Reports 2008 with CA ERwin DM widens the range of reporting features available to you. The CA ERwin DM metadata schemas are exposed via the data sources, enabling you to craft reports against all the CA ERwin DM metadata including the contents of the Action Log.

To help you get started, several sample reports are installed with CA ERwin DM to the \ODBC Reports folder.

10 Release Notes

Enhancements to Complete Compare

The following enhancements have been added to the Complete Compare functionality.

Features Added to Improve Complete Compare Performance with CA ERwin Model Manager

New features have been added to maximize performance when working with CA ERwin Model Manager models and Complete Compare. When two different users check out a model from CA ERwin Model Manager, change the model, and check it back in to the mart, the differences display in the Difference Reconciliation dialog (part of the Complete Compare user interface).

A conflict exists when two users check the same model out of the mart, and then change the same object or property. When each user checks their models back in to the mart, a "three-way merge" is necessary to reconcile the differences made by each user, and the unchanged objects and properties in the mart. The three-way merge of the models is sometimes slow for large models because all objects participate in the compare process.

This compare functionality has changed to reduce the scope of comparison to only objects that have changed for both the local and mart version of the models. The criteria for detecting changes include the following:

■ Objects that have been created in either the local or the mart copy. ■ Objects that have been deleted or modified in at least one of either the local or mart copy.

Two new options have been added to the Options dialog available from the Tools menu. The Model Manager tab of the Options dialog now includes the following check boxes: Bypass Difference Reconciliation Dialog if there are no conflicts Select this check box to skip the Difference Reconciliation dialog if no conflicts are detected between the version of the model in the mart and the local version. If no conflicts are detected, the local copy is updated from the mart version before the model is saved. Show All Objects in Difference Reconciliation Dialog Select this check box to turn off the options to optimize the compare process. The Difference Reconciliation dialog will display all objects including those that were not modified in the checked out model and in the mart copy of the model.

Note: This feature was first made available with the r7.2.5 SP1 release.

Chapter 1: New Features and Enhancements 11

Enhancements to Complete Compare

Advanced Options

Several options have been added to the Advanced pane of the Complete Compare wizard. They are:

Auto-Resolve Missing UDPs

In some cases, the Type Resolution box appears when Complete Compare detects missing UDPs or property differences for common UDPs. You can select to skip the Type Resolution popup box when all the differences are due to missing UDPs. When you select this check box, all missing UDPs are automatically copied to the target model. This option is not selected by default.

Display Unified Attributes

Select this check box to simplify the display of foreign-key attributes in the Resolve Differences dialog. When selected, a Unified Attributes group object is used to display all unified attributes (role-named or not) of the same unified set of attributes.

Any attributes that are aligned to the attributes under the Unified Group object appear as part of the Unified Group object, even if they are not unified attributes.

The Unified Attributes group object carries the unified name if all the attributes under it are part of the same unified set. If not, the name consists of a comma-delimited list of names of all the attributes under it.

Select Active Subject Area

Specifies that you want to select the active subject area by default in the Object Selection pane. This simplifies the subject area selection, especially in models that contain a large number of subject areas.

Ignore Code Comments

Select this option to exclude blocks of comments from the body of a trigger, before including it in the compare process. This enables Complete Compare to recognize that a trigger has not changed, if the only difference is in the comment text attached to the trigger.

12 Release Notes

Enhancements to Complete Compare

Exclude Unaligned Objects/Display Only Aligned Objects

Two features on the Advanced Options pane of the Complete Compare wizard enable you to exclude unaligned model-level objects in either the left or right model. They are "Exclude Unaligned Objects in the Left Model" and "Exclude Unaligned Objects in the Right Model". In earlier versions of the product, these options were mutually exclusive - you could not select both. In CA ERwin Data Modeler r7.3 you can now select both check boxes to display only (model-level) aligned objects in the Resolve Differences dialog.

These features are useful when you work with a submodel or subject area of a larger model, and then want to compare changes against the larger model. When you select the "Exclude Unaligned Objects..." check box for the larger model, you exclude the model-level unaligned objects from the Resolve Differences dialog display. This results in a more relevant list of differences and a display that is easier to read.

Type Resolution Wizard

In earlier versions of CA ERwin Data Modeler when the type signatures of the two models were not identical, a popup window displayed, enabling you to review and accept the choices for missing types or type conflicts. In CA ERwin Data Modeler r7.3 this popup dialog has been replaced with a wizard. The wizard makes it easier to navigate and use the available options.

Change to Type Selection Filtering

In earlier versions of CA ERwin Data Modeler type selection in the Complete Compare wizard resulted in hiding the selected item from the user, not strictly removing the object from the compare process. This resulted in no performance improvement for type filtering. In CA ERwin Data Modeler r7.3 type selection has been updated so that filtering is applied strictly according to the choices made in the Type Selection pane of the Complete Compare wizard.

Demand Loading Enhancement

When working with a database in Complete Compare, selecting the Allow Demand Loading check box enables you load only the names of the top-level objects from the database catalog. When you perform an action on a partially loaded object in the Resolve Difference dialog, it is fully loaded in order to complete the compare action. In CA ERwin Data Modeler r7.3, demand loading has been optimized to improve overall performance.

Chapter 1: New Features and Enhancements 13

Enhancements to Complete Compare

Demand Loading and DB Sync

To optimize performance when doing a DB Sync, the Demand Loading option is now activated by default. In earlier versions, the check box (on the Right Model pane of the DB Sync wizard) was selected by default, but could be changed. In r7.3 you cannot clear this check box.

Object Selection Enhancement

When a model contains a large number of objects it may be difficult to locate the objects that have been selected in the Right and Left Object Selection panes of the Complete Compare wizard. For example, if you select a Subject Area set, it may be difficult to locate the selected objects in the list. A check box with the label "Hide Unselected Objects" has been added to the Object Selection panes. Select the check box to remove unselected objects from the Selected Objects display.

Note: this change also applies to the DB Sync Wizard.

Range Selection Enhancement

Range selection functionality has been added to the Object Selection panes in Complete Compare. You can now select a range of items on the same level using SHIFT+LEFTCLICK, or select individual items using CTRL+LEFTCLICK. For example, you can use SHIFT+LEFTCLICK to select a range of Entities in the "Selected Objects" list, then clear one check box next to an entity name to clear the check boxes for all the selected entities.

In earlier versions of the product, it was necessary to select or clear each check box individually.

"Explain" Button Added

To improve performance and to make compare results displayed in the Resolve Differences dialog easier to understand, a new "Explain" button has been added to the Resolve Differences dialog. When you click the Explain button, an Explanation dialog opens. For object rows, the text explains why the two objects were aligned. For property rows, the text explains why the two property values are equal. The "Explain" button replaces the "Details" button available in earlier versions of the product.

14 Release Notes

Template Editor for Forward Engineering Template Files

The Forward Engineer wizard now includes a link to a Template Editor, which you can use to view, modify, and create new template files for use with schema generation. The Template Editor features give you a wide range of options for controlling schema generation for your models. You can review and print database-specific features of the default template files, create a custom template file based on a default template file, or create a completely new template file. The Template Editor also includes new macros and extensive customization options.

You can access the new Template Editor from within the Forward Engineer wizard, or from an option on the Tools menu.

This feature replaces the r7.2.x Database Template option,where you could edit the *.erwin_fe_template files outside the program to modify the schema generation options. The new feature uses *.FET files which you work with using the template editor interface.

A technical document, Editing Forward Engineering Templates, is installed with the product in the \Doc folder beneath the folder where you installed CA ERwin Data Modeler. This guide provides an introduction to working with the new template editor. You can also open this PDF from a shortcut on the Start menu.

Macro Enhancements

This release introduces CA ERwin Data Modeler's Template Language (TLX), the new template/macro language for Forward Engineering templates. The macros available in earlier versions of CA ERwin Data Modeler are still accessible using the Macro Toolbox which you can open from the Domain Dictionary dialog, Model Naming Options dialog, Pre and Post Scripts dialog, Triggers dialog, and so on.

A technical document, the Template Language and Macro Reference Guide, is installed with the product in the \Doc folder beneath the folder where you installed CA ERwin Data Modeler. This guide provides extensive technical documentation for the Forward Engineering template macros. You can open help for an individual macro when you right-click the macro name in the Macros pane of the Template Editor.

Chapter 1: New Features and Enhancements 15

Macro Enhancements

Macro Added (r7.3.5)

The following macro has been added to the list of r7.3 macros provided in the Forward Engineering Template Editor. Macro Name: DatabaseConnection Description: This macro returns information about the current database connection used by the model. Prototype: DatabaseConnection( Connection Parameter )

Parameter: Connection Parameter Status: Req Description: This identifies the type of information used by the connection. Result: This macro will fail in the following circumstances:

■ The required parameters are not passed in. ■ The model has no target database set. ■ The specified parameters cannot be parsed.

■ The model is not connected to a database. Deprecation Level: Active Sample: [ “Connected to database as user “ DatabaseConnection( “User” ) ]

Result: Connected to database as user User1

16 Release Notes

Universal File Close Dialog

The different Close dialogs in earlier releases have been replaced with a "universal" Close dialog to ensure a standardized look and feel throughout the product. When you finish working on a model either locally or from within CA ERwin Model Manager, you can close the current model and continue working on another, or you can close the model and exit. The Close Model dialog also shows the status of the file, such as if it was opened from the server, its lock status, and whether there are unsaved changes. The five model close scenarios are: ■ File/Close from the CA ERwin Data Modeler application menu ■ Service/Close from the CA ERwin Model Manager menu ■ Close model when closing the diagram window ■ File/Exit or Close models when exiting the CA ERwin Data Modeler application ■ Close button in the Complete Compare wizard

Note: You must be connected to CA ERwin Model Manager to save a model to the mart.

Enhancements to Open or Save a Model in XML Format

Changes have been implemented to let you save an XML file in one dialog. In earlier versions of the software, you needed to go through several dialogs to choose the proper XML format.

When you select Save As from the File menu, you can select one of the following XML format options as the file type from the Save as type drop-down menu: XML Standard Files (*.XML) Standard XML format does not expand macros or names. This file is suitable for importing back into CA ERwin Data Modeler. XML Standard with Min Info Files (*.XML) Only saves the minimum amount of information needed by CA ERwin Data Modeler to reopen the model. Properties that are derived from other properties or that are read-only are not saved. You can choose to not use this option and still use the standard XML format. XML Repository Format Files (*.XML) The Repository format expands names, macros, and physical names. Derived properties are exported. A file saved in this format cannot be opened with CA ERwin Data Modeler.

Chapter 1: New Features and Enhancements 17

Enhancements to Triggers

Changes have been implemented to allow you to create model objects for ERwin-generated triggers. In earlier versions of the software, triggers did not exist as objects in the model, they were created during the forward-engineering process but not recognized during reverse-engineering.

In CA ERwin DM r7.3, several features have been implemented to allow you to treat triggers as model objects. These enhancements allow you include the triggers in alter scripts, include triggers in Complete Compare scenarios, and associate triggers with model templates.

The RI Defaults tab on the Model Properties dialog now includes a check box with the label "Automatically Create RI Triggers". When you select this check box, you are prompted with an option to create RI triggers for existing relationships. The option is then enabled for new objects. If you click No to the prompt, RI Triggers are created only for new relationships. This check box is not selected by default - you must select it to activate this new feature.

In the Forward Engineer wizard, on the Options tab for the Triggers object, the wording of the triggers options has been updated to reflect the new distinction between ERwin-generated and User-Defined triggers. When you select to automatically generate RI triggers, a check box is provided with the label "Automatically Generate Missing RI Triggers".

The Reverse Engineer - Set Options dialog now includes a check box with the label "Include Generated Triggers". You select this check box to include RI Triggers in the reverse engineer process.

18 Release Notes

Customize Model Explorer Display

Two template files are provided with CA ERwin Data Modeler that let you customize the display of object names in the Model Explorer. By using macros in the template file, you can override the default display of selected object names.

The file Logical Names.ont includes display options for the logical model. The file Physical Names.ont includes display options for the physical model. The files are installed to the \Documents and Settings\\Application Data\CA\ERwin Data Modeler\7.3\Templates folder.

Comments and a sample macro are provided in the file to customize the display of the parent/child relationship phrase in the Model Explorer. By default, the display is formatted to include the elements . You can modify the macro to exclude one of the elements, for example if you wanted to exclude the parent name in the display. You can add or edit entries in this file to customize the display in Model Explorer. These entries are optional; if there is no macro specified for an object type, the Model Explorer displays the object's name.

Note: If earlier versions of CA ERwin Data Modeler these files were named ModelExplorer logical display names.tmpl and ModelExplorer physical display names.tmpl respectively.

Chapter 1: New Features and Enhancements 19

Metadata Integration Bridges Updated (r7.3 Initial Release)

The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3 (Initial Release). You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu.

The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide. This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product.

Import Bridges Added/Removed

Support has been added for the following MIMB import bridges: ■ Cognos ReportNet QueryStudio (File) ■ Oracle Business Intelligence Answers ■ Oracle Business Intelligence Enterprise Edition ■ Oracle Business Intelligence Server ■ Oracle Warehouse Builder ■ Sypherlink Harvester 5.x

Support has been dropped for the following MIMB import bridges:

■ Ab Initio SA XML Exporter ■ Microsoft SQL Server Analysis Services 7.0 to 9.0 (via DSO)

Export Bridges Added/Removed

Support has been added for the following MIMB export bridges: ■ CA Repository for Distributed Systems ■ CA Repository for z/OS

Support has been dropped for the following MIMB export bridges: ■ ASG Rochade (via CWM XMI) ■ Sybase PowerDesigner OOM 9.x to 15.x (via UML XMI)

Bridges Renamed

■ IBM Webshere DataStage to IBM InfoSphere DataStage

20 Release Notes

Metadata Integration Bridges Updated (r7.3 Initial Release)

■ IBM DB2 Data Warehouse Edition/OLAP Acceleration (Cube Views) to IBM InfoSphere Warehouse/Cubing Services for OLAP ■ IBM DB2 Data Warehouse Edition/Rational Data Architect to IBM InfoSphere Warehouse/Rational Data Architect ■ IBM Rational Rose 98(i) to 2000 to IBM Rational Rose 6.0 (98i) to 6.5 (2000) ■ IBM Rational Rose 2000e to 2003 to IBM Rational Rose 7.x (2000e and newer) ■ Oracle Data Integrator - Beta to Oracle Data Integrator

Chapter 1: New Features and Enhancements 21

Metadata Integration Bridges Updated (r7.3.2)

The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3.2 (Patch Release). You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu.

The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r7.3.2 Edition). This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product.

Import Bridges Added/Removed

Support has been added for the following MIMB import bridges: ■ Microsoft Office Excel Advanced

Support has been dropped for the following MIMB import bridges: ■ Adaptive Repository & Foundation (via MIR XMI) ■ Adaptive Repository & Foundation (via CWM XMI) ■ Adaptive Repository & Foundation (via UML XMI)

Export Bridges Added/Removed

Support has been added for the following MIMB export bridges: ■ Microsoft Office Excel Advanced ■ Microsoft SQL Server Integration Services (Project)

Support has been dropped for the following MIMB export bridges: ■ Adaptive Repository & Foundation (via MIR XMI) ■ Adaptive Repository & Foundation (via CWM XMI) ■ Adaptive Repository & Foundation (via UML XMI)

Bridges Renamed

■ Business Objects Crystal Reports XI (File) to SAP BusinessObjects Crystal Reports XI (File) ■ Business Objects Data Integrator (via CWM XMI) to SAP BusinessObjects Data Integrator (via CWM XMI) ■ Business Objects Designer (File) to SAP BusinessObjects Designer (File)

22 Release Notes

Metadata Integration Bridges Updated (r7.3.2)

■ Business Objects Desktop Intelligence (File) to SAP BusinessObjects Desktop Intelligence (File) ■ Business Objects Metadata Manager (via MIR XMI) to SAP Business Objects Metadata Manager (via MIR XMI) ■ CA Gen 4.1a to 7.5 to CA Gen 4.1a to r7.6 ■ Cognos Series 7 Impromptu to IBM Cognos Series 7 Impromptu ■ Cognos ReportNet Framework Manager to IBM Cognos ReportNet Framework Manager ■ Cognos 8 Framework Manager Services to IBM Cognos 8 Framework Manager Services ■ Cognos ReportNet QueryStudio (File) to IBM Cognos ReportNet QueryStudio (File) ■ Cognos ReportNet ReportStudio (File) to IBM Cognos ReportNet ReportStudio (File) ■ IBM Rational Data Architect (RDA) to IBM InfoSphere Data Architect ■ IBM InfoSphere Warehouse/Rational Data Architect to IBM InfoSphere Warehouse/InfoSphere Data Architect ■ Microsoft SQL Server Integration Services to Microsoft SQL Server Integration Services (File) ■ Telelogic Tau (via UML XMI) to IBM Telelogic Tau (via UML XMI) ■ Telelogic (Popkin) System Architect 7.1 to 11x (File) to IBM Telelogic (Popkin) System Architect 7.1 to 11x (File) ■ Telelogic (Popkin) System Architect 10.4 to 11.x (Encyclopedia) to IBM Telelogic (Popkin) System Architect 10.4 to 11.x (Encyclopedia)

Chapter 1: New Features and Enhancements 23

Metadata Integration Bridges Updated (r7.3.8 SP2)

The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3.8 SP2. You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu.

The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r7.3.8 SP2 Edition). This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product.

Import Bridges Added/Removed

Support has been added for the following MIMB import bridges: ■ Borland Together (via UML 2.x XMI) ■ Informatica Developer - Beta bridge ■ IBM Rational Software Architect (RSA) (via UML 2.x XMI) ■ Microsoft SQL Server Analysis Services (via DSV File) ■ Microsoft SQL Server Integration Services (via DSV File) ■ OMG UML 2.x XMI 2.x

■ SAP BusinessObjects Data Integrator ■ Sparx Enterprise Architect (EA) (via UML 2.x XMI)

Support has been dropped for the following MIMB import bridges: ■ Microsoft Office Excel (advanced) ■ MicroStrategy 7.0 to 8.1 ■ SAP BusinessObjects Crystal Reports 8.5 to 9.5 (File) ■ SAP BusinessObjects Data Integrator (via CWM XMI) ■ Sun Netbeans XMI Writer ■ Sypherlink Harvester ■ Sypherlink Harvester 5.x

Export Bridges Added/Removed

Support has been added for the following MIMB export bridges: ■ Database data definition language (DDL) ■ Informatica Developer - Beta bridge

24 Release Notes

Metadata Integration Bridges Updated (r7.3.8 SP2)

■ Microsoft SQL Server Integration Services (via DSV File) ■ SAP BusinessObjects Data Integrator

Support has been dropped for the following MIMB export bridges: ■ Embarcadero ER/Studio (via ERX) ■ Microsoft Office Access ■ Microsoft Office Excel (advanced) ■ MicroStrategy 7.0 to 8.1 ■ RedHat (MetaMatrix) Enterprise Designer (via MIR XMI) ■ SAP BusinessObjects Data Integrator (via CWM XMI) ■ SchemaLogic SchemaServer (via MIR XMI) ■ Sun Netbeans XMI Writer ■ Unisys ClearPath (via MIR XMI)

Bridges Renamed

■ Borland Together (via UML XMI) to Borland Together (via UML 1.x XMI) (Export) ■ CA Component Modeler 4.x (via UML XMI) to CA Component Modeler 4.x (via UML 1.x XMI) (Export)

■ Embarcadero Describe (via UML XMI) to Embarcadero Describe (via UML 1.x XMI) (Export) ■ Embarcadero EA/Studio (via DM1) to Embarcadero ER/Studio Business Architect (via DM1) (Import/Export) ■ Embarcadero ER/Studio to Embarcadero ER/Studio Data Architect (Import/Export) ■ Gentleware Poseidon (via UML XMI) to Gentleware Poseidon (via UML 1.x XMI) (Export) ■ IBM Cognos 8 Framework Manager Services to IBM Cognos 8 BI Reporting - Framework Manager (Import) ■ IBM Cognos 8 Framework Manager Services to IBM Cognos 8 BI Reporting - Framework Manager (Import/Export) ■ IBM Cognos ReportNet Framework Manager to IBM Cognos 8 BI Reporting - Framework Manager for ReportNet (Import) ■ IBM Cognos ReportNet Framework Manager to IBM Cognos 8 BI Reporting - Framework Manager for ReportNet (Import/Export) ■ IBM Cognos ReportNet QueryStudio (File) to IBM Cognos 8 BI Reporting - QueryStudio (Import)

Chapter 1: New Features and Enhancements 25

Metadata Integration Bridges Updated (r7.3.8 SP2)

■ IBM Cognos ReportNet ReportStudio (File) to IBM Cognos 8 BI Reporting - ReportStudio (Import) ■ IBM Telelogic System Architect 7.1 to 11.x (File) to IBM Rational System Architect 7.1 to 11.x (File) (Import/Export) ■ IBM Telelogic System Architect 10.4 to 11.x (Encyclopedia) to IBM Rational System Architect 10.4 to 11.x (Encyclopedia) (Import/Export) ■ IBM Telelogic Tau (via UML XMI) to IBM Telelogic Tau (via UML 1.x XMI) (Import/Export) ■ Microsoft SQL Server Analysis Services 9.0 (File) to Microsoft SQL Server Analysis Services 2005 to 2008 (File) (Import) ■ Microsoft SQL Server Analysis Services 9.0 (via DSV) to Microsoft SQL Server Analysis Services (via DSV File) (Export) ■ NoMagic MagicDraw (via UML XMI) to NoMagic MagicDraw (via UML 1.x XMI) (Import/Export) ■ Sparx Enterprise Architect (EA) (via UML XMI) to Sparx Enterprise Architect (EA) (via UML 1.x XMI) (Import/Export) ■ Sybase PowerDesigner CDM 8.0 to 12.0 to Sybase PowerDesigner CDM 8.0 to 15.x (Export) ■ Sybase PowerDesigner OOM 9.x to 15.x (via UML XMI) to Sybase PowerDesigner OOM 9.x to 15.x (via UML 1.x XMI) (Import/Export) ■ Tigris ArgoUML (via UML XMI) to Tigris ArgoUML (via UML 1.x XMI) (Import/Export)

26 Release Notes

Enhancement to Rename Column Dialog (r7.3.4 SP1)

In a logical/physical model, if you create column names using domains, you may want to maintain a different name on the logical side (attribute) and physical side (column).

A check box has been added to the Rename Column dialog that enables you to break or maintain name inheritance between attribute and column names.

For example, in a physical model, you can drag and drop a domain into a table to create a new column. By default, a corresponding attribute is created on the logical side of the model, using the same name. To maintain a unique column name, click Rename in the Column Editor to open the Rename Column dialog, then clear the check box for "Use logical/physical name inheritance". This allows you to alter the physical name without affecting the logical name.

Note: an asterisk next to the property name indicates that the value is derived from inheritance. If you do not see the asterisk, the inheritance override check box also is not displayed, indicating that inheritance is not in effect.

This option appears in the r7.3.4 (SP1) release and later.

Allow Special Characters During Derive (r7.3.8 SP2)

An enhancement has been made to the Derive Model Wizard, Naming Standards Tab. The "Allow Special DBMS Characters" check box has been added. This feature only applies when deriving a phyical-only model from a logical-only model. When you select the check box you can allow special characters in a physical object name when it is derived from the logical model. This feature enables you to override the restriction on invalid or special characters in physical model object names. See the SQL Reference Documentation for your target server for more information about special characters.

Previously, this feature only appeared on the Model Naming Options dialog, Physical tab.

Chapter 1: New Features and Enhancements 27

Database Support Update

Databases Removed

Support has been dropped for the following target server databases in CA ERwin Data Modeler: ■ Ingres 2.5 ■ Oracle 8i ■ Progress 8.x ■ SQL Server 7.0

Databases Added

Support has been added for the following target server databases in CA ERwin Data Modeler: ■ Oracle 11x ■ Teradata 2.6/12 (see note above) ■ DB2/zOS 9 (certification) ■ SQL Server 2008 (certification)

■ DB2 iSeries 6 (certification, r7.3.4 SP1 and later)

User Interface Changes for Selected Databases

Changes have been made to the user interface to support new modeling features for selected databases. Changes include: ■ The SQL tab on the View editor for SQL Server, Oracle, and Teradata has been changed. Two tabs are now used to provide the features. A SQL tab provides read-only information about the DDL statement that is used during forward engineering. A User-Defined SQL tab provides a box for editing a user-provided DDL statement. The box is blank by default. ■ An enhancement has been added for MySQL. The AUTO_INCREMENT feature is now supported. When you select a numeric datatype such as Integer in the Column editor (MySQL tab), the Identity option becomes available. When you select this option and perform forward engineering, it generates the AUTO_INCREMENT syntax. Note: There can be only one AUTO_INCREMENT column per table. ■ The Privilege object was replaced by the Permission object for SQL Server 2005/2008 logical/physical and physical models.

28 Release Notes

Operating System Support Update

CA ERwin Data Modeler r7.3 includes support for Microsoft Vista and Microsoft Windows 2008 Server. Support for Windows 2000 has been dropped.

Integration With Microsoft Visual Studio Team System 2008 Database Edition

CA ERwin Data Modeler r7.3 includes an integration with Microsoft Visual Studio Team System 2008 Database Edition (VSTS Database Edition).

In addition to support for this version, support is included for the previous version, Microsoft Visual Studio 2005 Team Edition for Database Professionals.

Metamodel Reference Documentation

A new metamodel reference document has been produced that provides a comprehensive list of the CA ERwin DM metadata object classes, property classes, aggregations, and associations. This metadata information can be used in any of the following CA ERwin DM functional areas: ■ API

■ Forward engineering templates ■ Macros ■ Metadata reports

The PDF is called ERwin Metamodel Reference.PDF. It is part of the CA ERwin Data Modeler Technical Documentation Series, which is installed to the \Doc folder. You can also open this PDF from a shortcut on the Start menu.

This document replaces the output you could create from the Generate Metamodel Documentation option on the Help menu in earlier versions of the product.

Chapter 1: New Features and Enhancements 29

Compiled HTML Online Help

Online help for all products in the Modeling Suite is now provided in Compiled HTML (CHM) format. This replaces Windows Help (HLP) format provided previously. The CHM help modules include full search capability, indexing, and a comprehensive table of contents. You can click the help button or press F1 in any program context and the online help file opens to the topic relevant to the feature you are using. The table of contents and topics are also synchronized, so that the topic opens the table of contents tree to the appropriate location at the same time it displays the help topic.

Documentation Bookshelf

The Documentation Bookshelf is a free-standing HTML-based reference tool that provides easy access to the online help and core reference documentation for CA ERwin Data Modeler and CA ERwin Model Manager. The Bookshelf provides a "front end" user interface where you can open individual PDF Guides or online help files, or search a combined index for all deliverables.

The Bookshelf is automatically installed with the product unless you select not to install it in the installation wizard. Click the Bookshelf item on the Start menu to open the bookshelf.

A zip file containing the complete Bookshelf is also provided as a download from the Technical Support page of CA Support Online at http://support.ca.com.

For more information on using the Bookshelf features, click the "Getting Started" link at the bottom of the main Bookshelf window. This topic introduces the layout of the Bookshelf, the various search options.

Note: The Bookshelf does not include the Template Language and Macro Reference Guide, nor the ERwin Metamodel Reference Guide files from the Technical Documentation Series. To access these documents, open them from the \Doc folder where you installed the product. You can also open these PDFs from a shortcut on the Start menu.

30 Release Notes

Feature-Specific Training Videos

Two new training videos are provided with CA ERwin Data Modeler r7.3 to assist you in getting started with new features. The videos are installed with the program, and can be accessed from the Start menu under CA, ERwin, ERwin Data Modeler r7.3, Videos. The two videos are: ODBC Data Source Introduces the new ODBC reporting functionality. Customizing Forward Engineering Templates (ERwin FE IDE) Provides an overview of customization options in the Forward Engineering Templates Editor, including an example of modifying a template and using it in schema generation.

Chapter 1: New Features and Enhancements 31

Chapter 2: System Information

Review the following system information before installing and using the product.

This section contains the following topics: Operating System Support (see page 33) System Requirements (see page 34) Supported Target Server Databases (see page 34)

Operating System Support

CA ERwin Data Modeler requires that you have one of the following operating systems installed: ■ Microsoft Windows Vista ■ Microsoft Windows 2008 Server ■ Microsoft Windows 2003 Server ■ Microsoft Windows XP (through SP3) ■ Microsoft Windows 7

Administrative Privileges Required for Installation

Because the installation process for CA ERwin Data Modeler writes to the registry and system folders, the person installing, upgrading, or removing CA ERwin Data Modeler must have Administrative privileges. If you run an install without Administrative privileges, all files may not be installed or upgraded, and users will encounter problems when running the software.

Compatibility With Microsoft Visual Studio

CA ERwin Data Modeler includes integration features for the following versions of Microsoft Visual Studio: ■ Microsoft Visual Studio 2005 Team Edition for Database Professionals, part of the Microsoft Visual Studio Team Suite ■ Microsoft Visual Studio Team System 2008 Database Edition (VSTS Database Edition)

The integration also requires that you install the Visual Studio Power Tools. An option to install the Power Tools is provided on the last screen of the AllFusion ERwin DM installation wizard.

Chapter 2: System Information 33

System Requirements

The following requirements must be met or exceeded for CA ERwin DM to install and run correctly: ■ Intel Pentium III or equivalent ■ 500 MB Hard Disk Space ■ DVD-readable device (only if installing from DVD media) ■ 1 GB RAM (2 GB recommended for large models)

Supported Target Server Databases

The following target server databases are supported in CA ERwin Data Modeler r7.3. ■ Access (2000/2002/2003) ■ DB2 iSeries (5.x/6) ■ DB2/UDB (8.x/9.x) ■ DB2/zOS (7, 8/9) ■ FoxPro (stabilized support) ■ Informix (7.x, 9.x/10.x/11.x)

■ Ingres (2.6, 2006) ■ MySql (5.x) ■ ODBC/Generic (2.0, 3.0) ■ Oracle (9.x, 10.x/11x) ■ Progress (9.x/10.x) ■ Redbrick (stabilized support, 5.x) ■ SAS (stabilized support) ■ SQL Server (2000, 2005/2008) ■ Sybase (12.5/15) ■ Sybase IQ (12.x) ■ Teradata (2.6, 12)

34 Release Notes

Chapter 3: Installation Considerations

Review the following installation considerations before installing the product.

This section contains the following topics: Installation Wizard on DVD (see page 35) Silent Install for CA ERwin DM and Crystal Reports (r7.3.6) (see page 36) Installing VSTS Database Edition (see page 37)

Installation Wizard on DVD

When you install from the product DVD, the installation wizard has been enhanced to make it easier for you to install more than one product from the CA ERwin Modeling Suite at a time. After the wizard starts, you are prompted to select from a list of applications to change or install. For example, you can select to install CA ERwin Data Modeler and Crystal Reports 2008 at the same time. After the install process completes, you are prompted to provide your license key for each product using the License Verification dialog.

If you select to install a product for which you do not have a license key, you can use the product for a trial period of thirty days.

Chapter 3: Installation Considerations 35

Silent Install for CA ERwin DM and Crystal Reports (r7.3.6)

Starting with patch release r7.3.6, you can perform a silent (unattended) installation/upgrade of CA ERwin Data Modeler and/or Crystal Reports. The following commands apply to the install shell executable provided when you download a patch or service pack from the CA ERwin Data Modeler product page on support.ca.com. The following commands and parameters can be used: PRODUCT=DM Installs CA ERwin Data Modeler PRODUCT=CR Installs Crystal Reports /s Makes the setup.exe process silent. /qn Makes the setup.msi process silent. /v" parameters" Passes the parameters specified in the quotes to the underlying setup.msi file.

Examples ERInstallShellSetup_DMCR.exe /s /v" /qn PRODUCT=DM,CR"

Installs/upgrades the products in the order: CA ERwin Data Modeler, Crystal Reports. ERInstallShellSetup_DMCR.exe /s /v" /qn PRODUCT=CR"

Installs/upgrades only Crystal Reports. Note: requires that CA ERwin Data Modeler r7.3 build 1666 or later is already installed. ERInstallShellSetup_DMCR.exe /s /v" /qn"

When the product switch is not provided, both products are installed/upgraded.

Important Note

Please note that the silent install is not supported on the Windows 7 operating system.

36 Release Notes

Installing VSTS Database Edition

When you install CA ERwin DM, the installation script checks for a copy of Microsoft Visual Studio 2005 Team Edition for Database Professionals or Visual Studio Team System 2008 Database Edition. If it detects a copy of either version, the integration components are automatically installed unless you cancel the selection to install the components. You can also modify an existing installation of CA ERwin DM to add the VSTS Database Edition integration. See the installation instructions in Chapter 1 of the Integration Guide, provided in PDF format in the \Doc folder where CA ERwin DM is installed.

Chapter 3: Installation Considerations 37

Chapter 4: General Considerations

This section contains general information you should know before using CA ERwin Data Modeler r7.3.

This section contains the following topics: Metadata Elements Renamed (see page 40) Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler (see page 41)

Chapter 4: General Considerations 39

Metadata Elements Renamed

For CA ERwin DM r7.3, much of the metadata has been renamed. The renaming affects object types, property types and SCAPI-specific property types. The name changes fall into two categories:

First are the changes to make the names more consistent and to better represent the model data. An example of this is the property type "For" which has been renamed "For_Character_Type".

Second is the replacement of space characters with underscores in all metadata element names. Prior to CA ERwin DM r7.3, both object type and property type names accessed via SCAPI contained spaces, but those same names used underscores instead when saved to XML. To remove this inconsistency, all space characters within such names have been replaced by underscores.

For most users of CA ERwin DM, this change is transparent and will not affect your day-to-day work. Awareness of this change, however, is important for users of SCAPI and the new CA ERwin DM ODBC interface. If you worked with the pre-r7.3 metadata names, you should be aware of the r7.3 changes. SCAPI applications and scripts created prior to r7.3 must be updated to account for the new metadata names before use with CA ERwin DM r7.3. To assist in this updating process, the following CSV files are installed to the \doc folder where you install CA ERwin DM r7.3: Renamed Metadata (SCAPI).csv

Contains the full set of changed metadata names. It is a two column CSV file that contains the old name, new name pairs. Renamed Metadata (XML).csv Contains the subset of metadata names that appear as changed in XML files. Metadata names whose only change was the replacement of space characters are not changed at all from the perspective of CA ERwin DM XML format, and therefore do not appear in this file. Renamed SCAPI Properties.csv Contains the SCAPI-only property names that were renamed. Replaced Properties.csv During the renaming process, several groups of properties emerged as essentially synonymous. Rather than create an artificial differentiator into the names, the names were merged. This file lists the properties affected by this process, providing the original property name and the replacement name.

40 Release Notes

Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler

When you add a CA ERwin DM model to a VSTS Database Edition project, a connection is established between the two products. When you save and close your CA ERwin DM model, your changes are made to the VSTS Database Edition schema.

A known problem with the Microsoft VSTS Database Edition API results in certain user objects not being renamed or deleted from the VSTS Database Edition schema after being renamed or deleted in the CA ERwin DM model. This applies to objects that are not owned by the schema, such as user, database role, partition function, partition scheme, and the schema itself. If you rename or delete these objects from a model and save your changes, the objects are not automatically renamed or deleted in the VSTS Database Edition project. You must manually delete the instances of these object types from the VSTS Database Edition Schema View. If you do not manually modify the VSTS Database Edition schema, the objects are automatically repopulated into the CA ERwin DM model the next time you open it in VSTS Database Edition.

This issue will be resolved when an updated API is available from Microsoft.

Chapter 4: General Considerations 41

Chapter 5: Known Issues

This section contains know issues you should know before using CA ERwin Data Modeler r7.3.

This section contains the following topics: Double-Byte Character Display (see page 43) Known Issue With Meta Integration Bridges for Microsoft Office Excel (see page 43) Silent Install on Windows 7 (see page 43)

Double-Byte Character Display

Some double-byte characters added to the Windows operating system since 2004 do not display correctly in CA ERwin DM when Vista is your operating system. This only applies to some languages in which CA ERwin DM is certified but not localized (e.g. Korean, Russian, Chinese) and does not affect English or European languages.

Known Issue With Meta Integration Bridges for Microsoft Office Excel

There is a known issue in r7.3.8 SP2 when working with the Microsoft Office Excel import and export Meta Integration bridges. ■ Importing XLS and XLSX Excel files using the Microsoft Office Excel import bridge fails. ■ Exporting to XLS Excel file format using the Microsoft Office Excel export bridge fails when the bridge parameter for “Format” is set to “Standard-1_0.”

Microsoft and Meta Integration Technology are aware of this issue and will provide a fix for a future CA ERwin DM patch release.

Silent Install on Windows 7

There is a known issue with r7.3.8 SP2 when running the silent install on Windows 7. At this time, we do not support the silent install on the Windows 7 operating system.

Chapter 5: Known Issues 43

Chapter 6: Documentation

This section contains information about current product documentation.

This section contains the following topics: PDF Guides (see page 45) New Release Notes PDF (see page 46) Release Numbers (see page 46)

PDF Guides

The core PDF guides for this product are as follows: ■ CA ERwin Data Modeler Implementation Guide (ERwin_Impl.PDF) ■ CA ERwin Data Modeler Release Notes (ERwin_RelNotes.PDF) ■ CA ERwin Data Modeler Methods Guide (ERwin_Methods.PDF) ■ CA ERwin Data Modeler API Reference Guide (ERwin_API_Ref.PDF) ■ CA ERwin Data Modeler and Microsoft Visual Studio Team System 2008 Database Edition Integration Guide (ERwin_VSTS_Int.PDF)

The following documents in the Technical Documentation Series are also provided: ■ ODBC Reporting Guide (ODBC Reporting Guide.PDF) ■ Editing Forward Engineering Templates (Editing Forward Engineering Templates.PDF) ■ Template Language and Macro Reference (Template Language and Macro Reference.PDF) ■ Metamodel Reference (ERwin Metamodel Reference.PDF)

To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.

Chapter 6: Documentation 45

New Release Notes PDF

Earlier versions of the CA ERwin Modeling Suite products included a readme.html and Release Summary PDF file. The readme file included information about system requirements, supported operating systems, installation considerations, general considerations, a list of the published documentation for the product, and last-minute known issues. The Release Summary provided short descriptions of new features and enhancements for the current release.

For easier access these documents have been combined to a new PDF file, the Release Notes. The list of new features and enhancements is presented in the first chapter. Subsequent chapters include all the information previously published in the readme file.

You can access the Release Notes file from the final screen of the installation process, from the Start menu, and from the \Doc folder, located beneath the folder where you installed the product. The file is also available in the Download Center on support.ca.com.

Release Numbers

The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, will support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r7 may still be valid for r7.3. Documentation bookshelves always reflect the current product release number.

Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.

46 Release Notes