InfoSphere Data Architect, Version 7.5.x releases: new features and enhancements

Product documentation


Abstract

InfoSphere Data Architect Version 7.5.x releases contain cumulative fixes, enhancements, and new features, meaning that they include all of the new features or enhancements, as well as additional fixes to Eclipse, from earlier releases.

Content




Version 7.5.3.1

InfoSphere Data Architect, Version 7.5.3.1

InfoSphere™ Data Architect Version 7.5.3.1 contains product fixes only. See the fixed APAR list for a list of bug fixes and improvements.

Version 7.5.3

InfoSphere Data Architect, Version 7.5.3

InfoSphere™ Data Architect Version 7.5.3 provides enhancements in the following categories:


Dimensional modeling


This release of InfoSphere Data Architect introduces dimensional modeling capabilities. This new feature has the following components:
  • Added dimensional notation for both logical and physical data models
  • Automatic discovery of star and snowflake schemas
  • Automatic denormalization of snowflake schemas
  • Native integration with IBM InfoSphere Warehouse and Cognos
  • Integration with third party tools through MIMB bridge


Data diagramming

  • This release of InfoSphere Data Architect introduces the integration of IBM ILOG Graph Layout for Eclipse V8.7 into data diagrams. This integration adds new layout algorithms, such as Graph Layout, Link Layout, and Label Layout, to significantly improve the automatic arrange feature for either entire diagrams or selected diagram elements.
  • New global preference for line connectors in a data diagram, allowing you to specify Oblique or Rectilinear routing style.
  • Support for merged generalization line connectors when two or more entities are sub-types of an entity.


Logical and physical data modeling

  • Auto-complete for entering data types in the Properties view.
  • For DB2 for z/OS databases, ability to filter the physical data model objects that are created from reverse engineering by owner or table space. This is a new filtering option in the New Physical Data Model and Reverse Engineer wizards.
  • Ability to reorder columns and attributes by dragging and dropping in the Properties view or in a data diagram.
  • Ability to insert columns or attributes below the selected location instead of the end of the list of columns or attributes in the Properties view.
  • Ability to drag and drop View dependencies that are children of views from the Data Project Explorer to a data diagram.
  • Support for Find/Replace for object name strings in the Data Model Search dialog.
  • Support for reusable attribute groups in a logical data model.
  • Icon changes in the explorers to give a visual indication when logical data model objects are designated as not persistent.
  • Support during table rename for optionally updating the name of related objects (for example, primary keys, foreign keys, or indexes).
  • Support for system-generated default constraints for Microsoft SQL Server data models.
  • In the Apply View wizard, new option to truncate a table name in order to guarantee that the length of the generated view name will not be longer than its maximum length.
  • Ability to copy the documentation value for a atomic domain to an attribute that is using the atomic domain as a data type.


Data model transformation


New Unique and Transform As > Index controls in the Properties view for inversion entries. These properties together allow the "unique" property to be carried over for indexes and inversion entries during logical-to-physical or physical-to-logical data model transformation.


Data model analysis


Ability to perform data model analysis on glossary models to discover duplicate words.


Data model reporting and Web publishing

  • Ability to publish a selected set of data model objects to a Web.
  • New BIRT report templates:
    • Logical data model > Transformation Report
    • Physical data model > Schema, Table, Column, Foreign Key Report
    • Physical data model > Schema, Table, Column, Index Report
    • Physical data model > Schema, Table, Column, Primary Key Report
    • Physical data model > Schema, Table, Column Report
  • New step-by-step tutorial for BIRT reporting in the product information center.


Compare and sync


This release of InfoSphere Data Architect introduces the following enhancements for comparing and synchronizing data objects and data models in the compare editor:
  • Enhanced filtering capabilities, allowing you to include or exclude data object types, for example, views or dependencies, from comparisons
  • Expand or collapse all differences
  • Traceability elements are used for matching renamed relationships and foreign keys


Mapping editor


Option to create new mapping models that cannot be used to generate SQL scripts. This option improves mapping editor performance. You can set a global preference for this option or specify it during mapping model creation with a wizard.


Product interface

  • A new Task Navigator drop-down menu has been added to the main menu bar to allow you to more easily switch between perspectives as you perform different types of development tasks.
  • A new Task Launcher view provides launch points and links to help you more quickly get started with key tasks in the product.

Version 7.5.2.2

InfoSphere Data Architect, Version 7.5.2.2

InfoSphere™ Data Architect Version 7.5.2.2 provides enhancements in the following categories:

Microsoft Windows 7 support


This release of InfoSphere Data Architect introduces support for the Microsoft Windows 7 operating system. For detailed system requirements information see the "http://www.ibm.com/support/docview.wss?uid=swg27015717" target="_blank">system requirements support document.


Database connections


Database connections that become invalid are now detected and indicated with an icon change in the Data Source Explorer. You can set preferences for this feature in the Preferences window.


SQL and XQuery editor


The SQL and XQuery editor has been enhanced so that you can view and change the database connection and parser information that is associated with the current editing session.


Version 7.5.2 .1

InfoSphere Data Architect, Version 7.5.2.1

InfoSphere™ Data Architect Version 7.5.2.1 provides enhancements in the following categories:
Floating license support


This release of InfoSphere Data Architect introduces support for floating licenses. For more information see the following topic in the InfoSphere Data Architect information center: Activating floating licenses


Physical data modeling

  • When you use the compare editor to compare and merge two indexes with different storage attributes, you now can generate delta DDL statements for the changes. The USING, PRIQTY, SECQTY, and ERASE clauses define the storage attributes of an index or partition.
  • Sequences
    • When you modify sequences in DB2® for z/OS® databases, ALTER SEQUENCE statements are generated instead of DROP SEQUENCE and CREATE SEQUENCE statements.
    • With the new Order option on the Type page of the sequence properties, you can specify whether the sequence numbers must be generated in order of request.
    • With the new Restart option on the Type page, you can specify to reset the sequence to the value specified implicitly or explicitly as the starting value when the sequence was created.
  • When you rename tables in physical data models by using the refactoring feature, you now can also update view references automatically.
  • You can import metadata about a physical data model that was discovered in InfoSphere Discovery or InfoSphere Information Analyzer. You can view the metadata in the Properties view. For databases that support informational constraints, you can also use InfoSphere Data Architect to generate informational constraints for discovered relationships. Alternatively, you can convert discovered relationships into enforced primary key/foreign key constraints.
  • You can create storage groups and index cluster partitions in a physical data model by reverse engineering from a DB2 for z/OS and OS/390 Version 7 DDL file.


Data model transformation

  • You can analyze a physical data model for validity while you are using a wizard to transform the physical data model to a logical data model.
    If the transform is updating an existing logical data model, the transformation algorithm can use traceability to match certain types of data model objects that have been renamed.
  • You can analyze a logical data model for validity while you are using a wizard to transform the logical data model to a physical data model.
    If the transform is updating an existing physical data model, the transformation algorithm can use traceability to match certain types of data model objects that have been renamed.
  • Value constraints that are expressed in a domain model are now transformed into physical check constraints.


Data diagramming

  • You can change print options, including displaying virtual page breaks and selecting their color, setting a print scaling factor, and displaying warnings when page breaks split diagram objects.
  • You can add table dependencies and their associated views to a data diagram either selectively or collectively.
  • If you change the referenced tables in the SQL expression of a view, the dependency objects between the affected tables and the view will be automatically updated.
  • Automatic diagram layout is improved when you select Arrange or Arrange All. There are also new layout options on the Layout tab of the diagram Properties view.


Compare and synchronization

  • There are two new ways to specify filters for model comparison and synchronization:
    • You can specify filter options at the workspace level on the Preferences page to streamline and improve overall comparison performance.
    • You can specify filter options using new toolbar icons in the compare editor to sort or filter differences.
  • In the Structural Compare view when copying structural differences from left to right or from right to left, you can select multiple differences by using the Ctrl or Shift key when selecting differences.


Data model import and export

  • You can import COBOL source code to a logical data model by using a wizard.
  • During the import of CA ERwin or CA Gen physical data models targeting DB2 for z/OS or DB2 for Linux, UNIX, and Windows, you can use supplemental DDL scripts to import additional database-specific properties; for example, storage properties. You specify the location of the DDL scripts on the Options page of the Data Model Import wizard.


Database connections


For SQL Server connections with one of the following JDBC drivers, you can use Windows® Integrated Authentication (which is also referred to as "Windows Integrated Security") to access a SQL Server database:
  • SQL Server 2000 - Microsoft® SQL Server 2005 JDBC Driver Default (for SQL Server 2000 Service Pack 4 only)
  • SQL Server 2005 - Microsoft SQL Server 2005 JDBC Driver Default
  • SQL Server 2005 - Microsoft SQL Server 2005 JDBC Driver with system tables filter Default


DB2 for z/OS object properties


There is new support for the following DB2 for z/OS object properties. These properties are also supported during DDL generation.
  • Storage Group
      VOLUME
      DATACLAS, MGMTCLAS, and STORCLAS
  • Table space
      MAXPARTITIONS
      TRACKMOD
      GBPCACHE
  • Table partition
      PARTITION BY SIZE
  • Table
      VALIDPROC
      APPEND
      WITH RESTRICT ON DROP
  • Column
      AS SECURITY LABEL
      HIDDEN
      Subtype of a data type (as applicable)
      FIELDPROC and FIELDPROC Parameter
      DEFAULT values - USER, SESSION_USER
      Change timestamp FOR EACH ROW ON UPDATE AS ROW
      AS IDENTITY
        ORDER or NO ORDER
        MINVALUE or NO MINVALUE
        MAXVALUE or NO MAXVALE
  • Index
      DEFINE
      GENERATE KEY USING XMLPATTERN
      PARTITION and PARTITION values
      GBPCACHE
  • Distinct type
      WITH COMPARISON
  • Distinct user-defined type
      Specify subtype and encoding (CCSID) for data type (as applicable)
  • Stored procedure
      Specify subtype and encoding (CCSID) for data type (as applicable)
  • User-defined function (scalar return type)
      Specify subtype and encoding (CCSID) for data type (as applicable)
  • User-defined function (table return type)
      Specify subtype and encoding (CCSID) for data type (as applicable)

Version 7.5.2

InfoSphere Data Architect, Version 7.5.2

InfoSphere Data Architect Version 7.5.2 introduces the following new features.

Customers who have InfoSphere Data Architect Version 7.5.1 can upgrade to InfoSphere Data Architect Version 7.5.2 using Installation Manager.

InfoSphere Data Architect Version 7.5.2 provides enhancements in the following categories:
See Functionality that is deprecated or removed for the application tooling features that are no longer available in InfoSphere Data Architect.

For a list of APARs and other key customer requirements and fixes that are included in this release, see: http://www.ibm.com/support/docview.wss?uid=swg27015776

Data modeling
    Volumetrics
      You can now specify sizing information, also called volumetric s , for tables and columns in a physical data model, or for entities and attributes in a logical data model. Volumetrics properties in a data model estimate the data stored and its expected rate of growth. This information can help an organization make decisions about necessary equipment and database storage design.
    Improved diagram layout
      You can now specify different layout options in the Properties page for a data model diagram, including a top to bottom and a left to right orientation.
    Improved behavior when inferring relationships
      General performance for this option is improved, and you can specify columns to ignore when using this option.

Enhanced support for DB2 for Linux, UNIX, and Windows
This release adds support for DB2 Version 9.7 for Linux®, UNIX®, and Windows®.

Database connections
You can store common database connection information, called connection configurations, in a database or configuration repository, so that team members can easily access and reuse the connection information. When you use connection configurations to connect to a database, the properties for the connection are pre-filled, so that the process of creating a connection is greatly simplified.

Functionality that is deprecated or removed
The following application tooling features are no longer available in InfoSphere Data Architect:
  • SQLJ development
  • Java™ routine development

These features are still available in the IBM® Data Studio 2.2 product, which is available for free download on the Web. To continue to use these features, you can use Installation Manager to install IBM Data Studio 2.2 into the same product package as InfoSphere Data Architect 7.5.2.

All tooling for routines (stored procedures and user-defined functions) is deprecated in this release. Deprecated functionality is still supported but might be removed in future releases.

Version 7.5.1

InfoSphere Data Architect, Version 7.5.1

For Version 7.5.1, Rational® Data Architect has been renamed to InfoSphere Data Architect. Customers who have Rational Data Architect Version 7.5 can upgrade to InfoSphere Data Architect using Installation Manager.

For a list of APARs that were fixed in this release, see: http://www.ibm.com/support/docview.wss?uid=swg27014021

Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Data Architect

Software version:

7.5.1, 7.5.1.1, 7.5.2, 7.5.2.1, 7.5.2.2, 7.5.3, 7.5.3.1

Operating system(s):

Linux, Windows

Reference #:

7017017

Modified date:

2009-12-10

Translate my page

Machine Translation

Content navigation